[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [PATCH] Hotcopy fix

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: 2005-05-09 16:50:53 CEST

Ben Collins-Sussman <sussman@collab.net> writes:

> On May 8, 2005, at 10:58 PM, D.J. Heap wrote:
> >
> > Additionally, the locks table was never being copied in FSFS
> > repositories.
> >
> Just a sanity check here:
> Is the consensus that lock-data is just 'temporary' repository
> metadata, and therefore it's okay that 'svnadmin dump' doesn't
> preserve it? That was my understanding. A dump is about preserving/
> migrating versioned data only.
> Does it matter, therefore, whether 'svnadmin hotcopy' preserves lock-
> data? If the point is to make a backup, I guess one could go either
> way...?

Uncommitted, stale transactions and the nodes which hang off of them
are also arguably "temporary repository metadata" that 'svnadmin dump'
doesn't preserve, and yet we don't bother shaking those suckers out of
hotcopy'd repositories. A hotcopy is a just that, a copy, void of all
knowledge of repository internals, and should therefore assume that
everything in range in copy worthy. Hotcopy should copy the locks

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon May 9 17:31:06 2005

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.