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

Re: BDB-4.4 and automatic database recovery

From: Michael Pilato <cmpilato_at_collab.net>
Date: 2006-01-12 15:18:11 CET

On Thu, 2006-01-12 at 11:45 +0100, Branko Čibej wrote:
> As some of you may know, Berkeley DB 4.4 adds support for automatic
> recovery of wedged repositories. This feature was added to BDB
> specifically with Subversion in mind.
>
> For the past several weeks, I've been adding support for BDB-4.4 and
> automatic recovery on the bdb-fixes branch. This work (sponsored by
> Sleepycat) is now 99% done. You can test it by switching the
> libsvn_fs_base directory to this branch -- all changes are localised there.
>
> In the next several days, I'll make some final changes, then, if nobody
> objects, merge this branch to trunk and propose it for inclusion into
> svn-1.3.1.

Woohoo!

> I submit that this is not a new feature, but is essentially a
> bugfix for all those wedged-repository bugs we've seen, and is therefore
> a valid candidate for a patch release. There are of course no API
> changes involved.

I agree that this is 1.3.1-able. But I would caution against an overly
quick release of this code. News of BDB 4.4 support will be welcomed by
Subversion users everywhere, and we want to make sure that the hype is
backed by soundly tested code.

Would you (or anyone else) object to our running an RC cycle (maybe two
weeks) for the 1.3.1 release, during which time I can get svn.collab.net
running BDB 4.4 and subversion-1.3.1-rc1? For kicks I could even write
a cron job on that box that runs a binary which opens the repository and
then abort()s. :-)

> BTW, is issue 2449, and fixing it will produce minor collateral damage
> by incidentally closing issues 688, 739 and 2019.

Shucks. What a bummer.

-- 
C. Michael Pilato <cmpilato@collab.net> 
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand

Received on Thu Jan 12 15:30:40 2006

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