Thanks, thats a good point.
This (and previous answers) might be obvious to developers working on
Subversion, but less clear to ordinary end users like me. A brief note in
the book or FAQ as to what we can expect the db to look like over time would
be useful. Having spent some time looking around on the web at other peoples
experiences with the many different VC systems around, there were 2 common
themes - a) most people thought Subversion to be one of the best, and b)
several were concerned about the size of the database due to logfiles. It
would be good to dispel any myths.
Simon.
----- Original Message -----
From: "Branko ÄOibej" <brane@xbc.nu>
To: "Simon Large" <slarge@blazepoint.co.uk>
Cc: "C. Michael Pilato" <cmpilato@collab.net>; "Mark Phippard"
<MarkP@softlanding.com>; <users@subversion.tigris.org>
Sent: Saturday, July 31, 2004 12:37 PM
Subject: Re: Logfile growth
> Simon Large wrote:
>
> >Also, it looks like SubVersion is set up to delete the redundant
logfiles.
> >The DB_CONFIG file has 'set_flags DB_LOG_AUTOREMOVE',
> >but the logfiles do not appear to get deleted immediately they become
> >redundant, although they do disappear later on, which was a little
confusing
> >to start out.
> >
> >
> Heh, that's because a log file doesn't necessarily become redundant when
> a new one appears, only when all the transactions it refers to have been
> committed and the data changes synced to disk. So there's a transition
> period where it's quite reasonable to have at least two log files active
> at the same time. There can easily be more than two, for example, if
> you're committing a large file.
>
> -- Brane
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Aug 2 10:39:12 2004