On Sep 13, 2007, at 11:57 AM, Blair Zajac wrote:
> 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
>>>> function name differences here, an examination of how we toggle
>>>> error output there. (Most of the 4.6 changes seem to be focused
>>>> 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
>> 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.
FWIW, this would not currently handle replication of the SQLite
mergeinfo.db which sits in the REPOS/db/ directory next to the other
The APIs which access this merge history index are abstracted with an
eye towards being storage-agnostic, so if someone later wanted to put
all the information in BDB (or some other backend FS implementation),
this would be possible.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Thu Sep 13 23:28:28 2007