Re: versioning unversioned metadata + anonsvn strategies....

John Peacock <jpeacock@rowman.com> writes:
> Perry E. Metzger wrote:
>
>> 0) The documentation does not make it clear if "svnadmin dump" is safe
>> to run at any time (i.e. without quiescing the database). I assume
>> it is, but the docs might make that clear.
>
> Check out the BerkeleyDB docs if in doubt. I believe that it is safe
> at all times (i.e. a consistent dumpfile is guaranteed), but don't
> take my word for it.

My point is that users shouldn't have to do that -- the svn docs
should tell them. :)

>> 1) Having an ancient fear of binary databases, I'd like to back up my
>> subversion database to a text format dump file after every
>> commit.
>
> You need to get over that fear. ;~) Replace the word "subversion" in
> that paragraph with "Oracle" or "SQLServer" and you'll see exactly how
> crazy that scheme sounds.

I dump all my postgres databases to text files.

Also, I was at a company once some years ago where the version control
system, run inside a database, went corrupt and lost weeks of
work.

Also, in the last few days someone wrote about how their (apparently
buggy version of) db ate their revisions.

Backups are cheap, developers are expensive. I'll keep making
backups.

-- 
Perry E. Metzger		perry@piermont.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org