C. Michael Pilato wrote:
> Blair Zajac wrote:
>> C. Michael Pilato wrote:
>>> Oracle has released version 4.6.19 of its Berkeley DB library.
>>> According to
>>> my interpretation of the "Upgrading application to 4.6.x"
>>> I don't think there's anything especially difficult for us to do in
>>> Subversion to make the claim that we support 4.6.x. Some macros for
>>> function name differences here, an examination of how we toggle verbose
>>> error output there. (Most of the 4.6 changes seem to be focused around
>>> replication, which is -- and has been -- the latest hot topic for BDB.)
>>> Should we "go there" for Subversion 1.5?
>> Using BDB's replication to replicate Subversion repositories would be
>> pretty sweet. Presumably, this would also allow us to replicate
>> uncommitted transactions, which would be cool (well, cool for my
>> project, where I expect long-lived transactions).
> Well, BDB has had replication for some time now -- it's not new to 4.6.x.
> In fact, back when 4.4 was released, Keith Bostic asked me if I knew of any
> monster-sized Subversion datasets. He was wanting to do a proof of concept
> using replicated Subversion repositories!
Good to know.
> Anyway, my question was *absolutely not* "Should we try to expose BDB
> replication in Subversion 1.5?" It was simply "Should we try to make
> Subversion's code compile and work against BDB 4.6.x?"
Agreed, definitely not expose BDB replication through svn.
> Are you still +1?
But yes, +1 on supporting 4.6 in 1.5. 1.5 is going to be out a long time before
1.6, so we will want to support 4.6 for new distributions that may go to 4.6
This change also looks interesting:
"The format of Hash database pages was changed in the Berkeley DB 4.6 release,
and items are now stored in sorted order. The format changes are entirely
backward-compatible, and no database upgrades are needed. However, upgrading
existing databases can offer significant performance improvements."
I wonder how much faster svn performance we would see with 4.6 versus 4.5.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Thu Sep 13 20:54:10 2007