You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Steve Whitson <st...@gmail.com> on 2008/09/10 14:04:04 UTC
upgrade from 1.3 to 1.5 - if possible should include a dump & load?
I'm planing on upgrading from 1.3.1 to 1.5.2 in the near future. I've
worked with the svnadmin upgrade sub-command as well as the
svn-populate-node-origins-index tool w/in 1.5.2, along with the need for
both, and performed some migration-upgrades to another system-location
(using svn switch --relocate). The process seems fairly simple.
My two questions wrt 1.4 are:
1. to get the benefits of 1.4 with regard to repository size, must I
dump and load my repositories?
2. to get the benefits of smaller/faster network traffic must I dump
and load my repositories?
I ask due to what I found in the 1.4 release notes:
/In Subversion 1.4, the svndiff format has been improved to use much
less disk space --- up to 50% less on plain text files in some cases.
Thus, if you choose to dump and reload your repository, the new
repository should be noticeably smaller on disk. (Make sure to svnadmin
create the new repository using svnadmin 1.4.) Additionally, if a client
and server are both version 1.4 , then network traffic becomes smaller
and faster./
Also (wrt 1.5), is it recommended to dump and load them when possible
between such upgrades? Based on the 1.5 release notes I'll get the new
features of 1.5 by just preforming the upgrade operation, but the
svnadmin upgrade subcommand says two things that lead me to believe a
dump and load would be better when possible:
-/the upgrade performs only the minimum amount of work needed to
accomplish this/
-/It does not guarantee the most optimized repository state as a
dump and load would./
Thanks much,
-Steve
Re: upgrade from 1.3 to 1.5 - if possible should include a dump &
load?
Posted by Craig McQueen <mc...@edsrd1.yzk.co.jp>.
Mark Phippard wrote:
> On Wed, Sep 10, 2008 at 10:29 AM, Steve Whitson
> <st...@gmail.com> wrote:
>
>> It sounds like you understand everything. You would most likely want
>> to do a dump/load so that you could pick up the benefits of a 1.4
>> repository and 1.5 at the same time. svnadmin upgrade will not get
>> you any of the 1.4 improvements.
>>
>> Can I perform the dump of 1.3.1 repositories using the 'svnadmin dump' from
>> my 1.5.2 installation (I plan on piping the dump directly into the load)?
>>
>
> Yes, it should be possible to do that.
>
>
I tried doing a similar upgrade from a 1.2 repository to 1.5.
At first, I tried a dump with the 1.2 tools, and a load with 1.5 tools.
I had problems with files with Japanese file names. Using the 1.5 tools
for both dump and load avoided the problem.
Regards,
Craig McQueen
Re: upgrade from 1.3 to 1.5 - if possible should include a dump &
load?
Posted by Steve Whitson <st...@gmail.com>.
Mark Phippard wrote:
> On Wed, Sep 10, 2008 at 10:29 AM, Steve Whitson
> <st...@gmail.com> wrote:
>
>> It sounds like you understand everything. You would most likely want
>> to do a dump/load so that you could pick up the benefits of a 1.4
>> repository and 1.5 at the same time. svnadmin upgrade will not get
>> you any of the 1.4 improvements.
>>
>> Can I perform the dump of 1.3.1 repositories using the 'svnadmin dump' from
>> my 1.5.2 installation (I plan on piping the dump directly into the load)?
>>
>
> Yes, it should be possible to do that.
>
>
Thanks much for you helpful info! :)
Re: upgrade from 1.3 to 1.5 - if possible should include a dump & load?
Posted by Mark Phippard <ma...@gmail.com>.
On Wed, Sep 10, 2008 at 10:29 AM, Steve Whitson
<st...@gmail.com> wrote:
> It sounds like you understand everything. You would most likely want
> to do a dump/load so that you could pick up the benefits of a 1.4
> repository and 1.5 at the same time. svnadmin upgrade will not get
> you any of the 1.4 improvements.
>
> Can I perform the dump of 1.3.1 repositories using the 'svnadmin dump' from
> my 1.5.2 installation (I plan on piping the dump directly into the load)?
Yes, it should be possible to do that.
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: upgrade from 1.3 to 1.5 - if possible should include a dump &
load?
Posted by Steve Whitson <st...@gmail.com>.
Mark Phippard wrote:
> On Wed, Sep 10, 2008 at 10:04 AM, Steve Whitson
> <st...@gmail.com> wrote:
>
>> I'm planing on upgrading from 1.3.1 to 1.5.2 in the near future. I've
>> worked with the svnadmin upgrade sub-command as well as the
>> svn-populate-node-origins-index tool w/in 1.5.2, along with the need for
>> both, and performed some migration-upgrades to another system-location
>> (using svn switch --relocate). The process seems fairly simple.
>>
>> My two questions wrt 1.4 are:
>> 1. to get the benefits of 1.4 with regard to repository size, must I dump
>> and load my repositories?
>> 2. to get the benefits of smaller/faster network traffic must I dump and
>> load my repositories?
>>
>> I ask due to what I found in the 1.4 release notes:
>> In Subversion 1.4, the svndiff format has been improved to use much less
>> disk space — up to 50% less on plain text files in some cases. Thus, if you
>> choose to dump and reload your repository, the new repository should be
>> noticeably smaller on disk. (Make sure to svnadmin create the new repository
>> using svnadmin 1.4.) Additionally, if a client and server are both version
>> 1.4 , then network traffic becomes smaller and faster.
>>
>> Also (wrt 1.5), is it recommended to dump and load them when possible
>> between such upgrades? Based on the 1.5 release notes I'll get the new
>> features of 1.5 by just preforming the upgrade operation, but the svnadmin
>> upgrade subcommand says two things that lead me to believe a dump and load
>> would be better when possible:
>> -the upgrade performs only the minimum amount of work needed to
>> accomplish this
>> -It does not guarantee the most optimized repository state as a dump and
>> load would.
>>
>
> It sounds like you understand everything. You would most likely want
> to do a dump/load so that you could pick up the benefits of a 1.4
> repository and 1.5 at the same time. svnadmin upgrade will not get
> you any of the 1.4 improvements.
>
>
Can I perform the dump of 1.3.1 repositories using the 'svnadmin dump'
from my 1.5.2 installation (I plan on piping the dump directly into the
load)?
Re: upgrade from 1.3 to 1.5 - if possible should include a dump & load?
Posted by Mark Phippard <ma...@gmail.com>.
On Wed, Sep 10, 2008 at 10:04 AM, Steve Whitson
<st...@gmail.com> wrote:
> I'm planing on upgrading from 1.3.1 to 1.5.2 in the near future. I've
> worked with the svnadmin upgrade sub-command as well as the
> svn-populate-node-origins-index tool w/in 1.5.2, along with the need for
> both, and performed some migration-upgrades to another system-location
> (using svn switch --relocate). The process seems fairly simple.
>
> My two questions wrt 1.4 are:
> 1. to get the benefits of 1.4 with regard to repository size, must I dump
> and load my repositories?
> 2. to get the benefits of smaller/faster network traffic must I dump and
> load my repositories?
>
> I ask due to what I found in the 1.4 release notes:
> In Subversion 1.4, the svndiff format has been improved to use much less
> disk space — up to 50% less on plain text files in some cases. Thus, if you
> choose to dump and reload your repository, the new repository should be
> noticeably smaller on disk. (Make sure to svnadmin create the new repository
> using svnadmin 1.4.) Additionally, if a client and server are both version
> 1.4 , then network traffic becomes smaller and faster.
>
> Also (wrt 1.5), is it recommended to dump and load them when possible
> between such upgrades? Based on the 1.5 release notes I'll get the new
> features of 1.5 by just preforming the upgrade operation, but the svnadmin
> upgrade subcommand says two things that lead me to believe a dump and load
> would be better when possible:
> -the upgrade performs only the minimum amount of work needed to
> accomplish this
> -It does not guarantee the most optimized repository state as a dump and
> load would.
It sounds like you understand everything. You would most likely want
to do a dump/load so that you could pick up the benefits of a 1.4
repository and 1.5 at the same time. svnadmin upgrade will not get
you any of the 1.4 improvements.
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org