#Postfix 3.11 (for Workgroups!) released a few days ago with tools to mitigate the removal of #BerkeleyDB databases in some distros (it has been discussed for 5 years in Debian)
#Postfix 3.11 (for Workgroups!) released a few days ago with tools to mitigate the removal of #BerkeleyDB databases in some distros (it has been discussed for 5 years in Debian)
Python "bindings" for Oracle Berkeley DB 18.1.13 released. Now you can use it easily under ARM, RISC-V and others!
https://www.jcea.es/programacion/pybsddb.htm#berkeleydb-18.1.13
Python "bindings" for Berkeley DB, release 18.1.12.
https://www.jcea.es/programacion/pybsddb.htm#berkeleydb-18.1.12
389DS has switched their default backend from #BerkeleyDB to #LMDB. https://www.port389.org/docs/389ds/FAQ/Berkeley-DB-deprecation.html
The difference in config complexity is quite dramatic.
Regarding #email, screw the old #filesystem-centric non #transactional approach btw.
Program crashed while you were modifying a mail? Who knows what the on-disk file looks like now. You had it git-versioned? Good. If all goes well and git or the computer itself doesn't crash while updating things, that might be enough.
Even key-value #databases like #BerkeleyDB do it better, and they did so before #SQLite even existed.
So why can't I have tools using DBs?
@teajaygrey back when we were still using #BerkeleyDB, on a 5M user DB, #OpenLDAP authentication rates were over 2 orders of magnitude faster than ActiveDirectory on the same hardware and OS. (Even faster than that with OpenLDAP on Linux vs Windows too.) https://web.archive.org/web/20071214114023/http://connexitor.com/blog/pivot/entry.php?id=185#body
They've only gotten slower, while our transition to #LMDB got even faster...