j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckM×<div class="post"><br/>DB_PRIVATE enables a few optimizations by making the assumption that only one process will access the db4 database. Notably, this flag enables db4 to use pthreads-style mutex locking rather than heavy, operating-system-provided flock and shared memory. Ref: <a href="http://pybsddb.sourceforge.net/api_c/env_open.html">DB_ENV->open documentation</a>.<br/><br/>The general motivation is that db4 databases can be safely accessed in parallel with bitcoin client, assuming (a) DB_PRIVATE is removed and (b) bitcoin properly uses db4 transactions. db4 transactions may even be employed to wrap around non-db4 data such as blk0001.dat, if the code is properly architected.<br/><br/></div> text/html
https://whatsonchain.com/tx/5ceaa1a3dde6a4e2fec5eff78ac8a83f5d78aa4f1cd24c76f3babc6cd740dc6b