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

Re: Hot backup changes

From: Blair Zajac <blair_at_orcaware.com>
Date: 2002-08-22 17:27:44 CEST

cmpilato@collab.net wrote:
> Blair Zajac <blair@orcaware.com> writes:
> > Maybe revision 2 of the dump file format dumps all the log
> > messages for the entire repository??? svnadmin load would
> > only update log messages for those that have changed. This
> > would take care of this issue.
> >
> > Not that clean, but it would work.
> Actually, a really simple script that wrapped `svnlook log old-repos' and
> `svnadmin setlog new-repos' could do the trick, I imagine. Both
> operations are pretty darn fast.

True, but on the current svn repository, that would mean forking at
least 3000 processes, which is too many.

How about adding a new table to the repository that just stores a
binary flag indicating for a particular revision if the log message
has been modified. Then we can have several new svnadmin commands
(these aren't the best names)

    svnadmin logs_get_set just prints those revision numbers
                                 with set bits
    svnadmin logs_clear_change takes a list of revisions to clear
                                 the bit

This bit gets set whenever `svnadmin setlog' or a `svn commit' runs
on the repos. Then the hot backup script runs `svnadmin logs_get_set'
and only runs `svnlook log' on the indicated revisions.


Blair Zajac <blair@orcaware.com>
Web and OS performance plots - http://www.orcaware.com/orca/
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Aug 22 17:28:32 2002

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.