[Date Prev][Date Next]
ITS#3824 [Fwd: Re: BDB 4.2.52 environment flags not updated correctly [#12822]]
I reported this issue to Sleepycat, here's their response. It pretty
much convinces me that we need to go the DB_ENV->remove route.
-------- Original Message --------
Subject: Re: BDB 4.2.52 environment flags not updated correctly [#12822]
Date: Sun, 03 Jul 2005 10:36:15 -0400
From: Keith Bostic <firstname.lastname@example.org>
Hi, Howard, Keith Bostic here. I'll own this Support Request
> If you create an environment with a small set of features, then later
> (after closing cleanly) re-open it with additional features, the process
> that opened the environment works fine, but the environment flags are
> not updated so other processes that try to join the environment don't
> detect that the additional features are enabled.
> E.g., to speed up our bulk load tool we create an environment with no
> transaction/locking support. Later when the main process runs it enables
> transaction and locking support.
Thanks for the note, Howard.
To be honest, I'm not sure if we're going to be able to support
this functionality in Berkeley DB 4.4 (that is, in 4.4 it may
be impossible to modify database environments once set). I'm
trying to avoid limiting the application's ability to
incrementally configure their database environments, but there
are some races and mutex changes we're looking at for 4.4 that
may require the limitation. So, I don't want to patch this for
4.2, since the functionality might actually have to go away in
-- Howard Chu
Chief Architect, Symas Corp. Director, Highland Sun
Symas: Premier OpenSource Development and Support