sharing DB_ENV between DB berkeleydb instances

[Michael Meeks]

On Fri, 2012-03-23 at 16:42 +0000, Caolán McNamara wrote:
> Digging into our memory usage, I see that we have 6 berkeleydb DBs, all
> of which are opened with a NULL DB_ENV argument which makes berkeleydb
> create an internal one for each, which adds up to a substantial chunk of memory.

	:-) I would be surprised if on a recent install there were any
berkeleydb files created and/or opened anyway, IIRC I removed several
failure paths here for new profile creation in 3.5.

	Is it possible that we are firing that lot up, only then to discover
that in fact there is no .db file to load or somesuch ? perhaps there
are some instances where checking the db doesn't exist before
activiating whatever libdb linking component uses it might help (?)

	Otherwise, the mind boggles - what is the purpose of that db ? is it
ever written to ? :-) if not, why ... ? :-)

	ATB,

		Michael.

-- 
michael.meeks at suse.com  <><, Pseudo Engineer, itinerant idiot