You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by ia...@ubs.com on 2008/09/15 15:53:25 UTC

Subversion 1.5 - Clarification for upgrading a 1.3 format repository

For the upgrade from 1.3 to 1.4, you had to use the dump/load cycle to
get the repository to utilise the new svndiff format.

I notice that in Subversion 1.5, if I do an "svnadmin upgrade" on a FSFS
based 1.3 repository only a few backend changes occur.

New
------
db/txn-current
db/txn-current-lock
db/txn-protorevs

Modified
------------
format
db/format

My questions are:

What svndiff format will the upgraded repository be using (1.3 or 1.4)?
I'm assuming 1.4 but would like confirmation.
If its using the new format (1.4) will this cause any issues for older
revisions stored in the repo using the old svndiff format? I'm assuming
not, as clients are backward compatible with older repo formats.

If my assumptions are true, then I believe the benefits to the dump/load
cycle for 1.5 will be:

i) To convert the existing svndiff data to the newer format potentially
saving space.
ii) Eliminate the need for the separate node-origins index.

Thanks

Ian