DB4 recovery with svnadmin

[Nuutti Kotivuori <na...@iki.fi>]

This doesn't like too much of a nice design thingy or anything, but I
thought I should still suggest it as atleast I personally would have
needed this several times already.

Would it be possible to add a flag to 'svnadmin' that forces recovery
of the database?

This could be flagged with all the possible warning flags that do this
only if you are certain that no-one else is using the repository.

The use case for this is when I handle dumping and loading of old
repositories and playing around with different subversions and so
on. I quite often happen to do something like 'svnadmin dump' and then
interrupt that. After that I have to remember to run db_recover before
I attempt anything else or otherwise I'm left wondering how nothing
happens. And to further complicate matters - I might not even have the
db-utils around.

If we would live in a perfect world, there would be absolutely no need
for this. But until that day, this would be something trivial to
implement if wanted.

-- Naked


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: DB4 recovery with svnadmin

[Karl Fogel <kf...@newton.ch.collab.net>]

Nuutti Kotivuori <na...@iki.fi> writes:
> Would it be possible to add a flag to 'svnadmin' that forces recovery
> of the database?

Open subversion/svnadmin/main.c, search for "subcommand_recover", and
read the comments. :-) 

(Note that although the code was in place, 'svnadmin recover' was
inactive even prior to rev 3258.)

-Karl

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org