BDB: restore DB_PRIVATE flag to environment
Satoshi’s commits fdbf76d4f49c220e2ed4412a3d8d8cd6efd74826 and c8ad9b8375f5308bb46a124f096a80926ea42fba (SVN import) removed the DB_PRIVATE flag from the environment. In part, this enables processes other than bitcoind to examine the active database environment.
However, this incurs a slight performance penalty versus working entirely within application memory (DB_PRIVATE). Because bitcointools and other direct-BDB-accessing tools are not used by the vast majority of users, prefer to default with DB_PRIVATE with the option of disabling it if needed via -privdb=0.
DB_REGION_INIT seems pointless if DB_PRIVATE is set.
Seems means no bench :D? Perhaps consider DB_REGION_INIT, if DB_PRIVATE is not set?
I’d like to know why DB_PRIVATE was enabled in the past, but disabled at some point. See commit fdbf76d4f49c2.
@sipa satoshi removed DB_PRIVATE at my urging ;)
See above: “In part, this enables processes other than bitcoind to examine the active database environment.”