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

Re: Subversion's use of Berkeley DB [#11511]

From: Keith Bostic <bostic_at_abyssinian.sleepycat.com>
Date: 2004-12-12 23:58:12 CET

> On Wed, 2004-12-08 at 12:38, Keith Bostic wrote:
>> 3. Subversion isn't recovering the database after application or
>> system failure -- it's only running recovery if Berkeley DB
>> explicitly returns DB_RUNRECOVERY.
>
> I'd like to point out that, in principle, anything Subversion can do to
> work around this problem (in its current architecture) could be done by
> the Berkeley DB library itself. Perhaps more robustly, as Subversion's
> BDB tables could conceivably be accessed without going through the
> Subversion libraries.

This is true, and it's a fair question to ask why Berkeley DB
doesn't provide a solution to this problem out-of-the-box.

The reason is because Subversion is, to my knowledge, unique
among Berkeley DB applications. I know of no other software
using DB that is:

        + also a library (and a library where the people writing
          the library don't also write the application software
          using the library),

        + used in a multi-process model, and

        + called from a variety of different languages and APIs.

I'll make a deal -- if someone in the Subversion development
group will help me build and test a solution, I'll try and
maintain the resulting code in the Berkeley DB distribution.

Regards,
--keith

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Keith Bostic bostic@sleepycat.com
Sleepycat Software Inc. keithbosticim (ymsgid)
118 Tower Rd. +1-781-259-3139
Lincoln, MA 01773 http://www.sleepycat.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Dec 12 23:59:18 2004

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.