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

Re: Subversion 1.8.9 repository access issue [Urgent]

From: Nico Kadel-Garcia <nkadel_at_gmail.com>
Date: Mon, 7 Jul 2014 08:11:49 -0400

On Mon, Jul 7, 2014 at 7:14 AM, Branko Čibej <brane_at_wandisco.com> wrote:
> On 07.07.2014 12:48, Nico Kadel-Garcia wrote:
>> On Mon, Jul 7, 2014 at 3:23 AM, Branko Čibej <brane_at_wandisco.com> wrote:
>>> On 06.07.2014 23:54, Andreas Stieger wrote:

>>> Berkeley DB databases can always be upgraded from older BDB versions with
>>> db_upgrade, if the BDB version on the new server is incompatible with the
>>> one on the old server. Nothing else should really matter.
>>>
>> This is not necessarily reliable. I've encountered at least 4 BDB
>> environments that worked as they were, but for which 'db_upgrade' was
>> impossible. It even paid serious consulting rates while I backported a
>> bunch of CentOS tools to work with an old BDB environment that someone
>> had hand built and not written a usable 'export' function for.
>>
>> I have never found BDB to be stable or reliable enough for production use.
>
> That's an answer to a different question. :)

Clipping some material: no, it's not a different question. BDB
databases *cannot* always be upgraded with db_upgrade, I thought I was
clear about that.
Received on 2014-07-07 14:12:19 CEST

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.