Re: What happens if the repos is accessed during upgrade?

On Tue, May 27, 2008 at 3:18 PM, <kmradke_at_rockwellcollins.com> wrote:

>> One way to potentially do an upgrade is to use svnsync. You can
>> create a new 1.5 repository and use the 1.5 version of svnsync to
>> populate it while the current repository stays live. When the process
>> ends, you can just swap the repositories when you have a convenient
>> window.
>
> Will this preserve any file locks from the old repository? I know
> that a dump/load process doesn't. Is it feasible that a
> script could help propagate locks?

AFAIK, locks do not get synched via svnsync. I cannot answer the
script question. I wonder of the locks folder (is that were they are
stored in fsfs?) could just be moved/replaced in the svnsynced version
when the process was concluded? The internal ID's change with 1.5, so
if locks use those, then probably not.

I'd say you'd probably just want to use svnadmin upgrade and build the
node-index-origins index. The size/performance penalty of doing it
this way is fairly small.

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org