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

RE: On recent BDB usage issues

From: Guido Anzuoni <Guido.Anzuoni_at_technomind.it>
Date: 2005-07-11 16:52:39 CEST

now it is clear.
I am extensively using Subversion with BDB back-end on Windows/Linux
*****without****** ***any****
problem in 2 years.
Just a little corruption (successfully recovered in few minutes) due to
a power fail.......
Just to say that I am quite confident in the quality of the product and
the team :)))


> -----Original Message-----
> From: Ben Collins-Sussman [mailto:sussman@collab.net]
> Sent: Monday, July 11, 2005 4:40 PM
> To: Guido Anzuoni
> Cc: users@subversion.tigris.org
> Subject: Re: On recent BDB usage issues
> On Jul 11, 2005, at 9:21 AM, Guido Anzuoni wrote:
> >
> > My undestanding of the problem is that the issues are not
> related to a
> > specific access method but to the way independent processes
> coordinate
> > themselves in the usage of BDB.
> > Isn't it ?
> Here is the simple fact: if *any* process opens a BDB
> database and either (1) hits a permissions problem or (2)
> crashes, it will leave
> the BDB database wedged, in need of recovery. The process could be
> apache. It could be svnserve. It could be 'svn checkout
> file:///'.
> It could be svnadmin or svnlook or viewcvs or anything else.
> Even if you set things up such that only one program ever
> touches the database, you're not completely safe: it can
> crash too. So there is no "good" or "bad" configuration of
> server processes that causes BDB problems. If you use BDB,
> then the risk is always present.
> That said, BDB isn't some bomb waiting to explode, either.
> I've used BDB for my personal repositories for over 2 years,
> and never had a wedge happen.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jul 11 16:55:33 2005

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

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