Just a heads up. This isn't something to consider immediately, but sometime soon. The official release of LMDB v1.0 is probably a week or so away.
The LMDB code in the Monero source tree is mostly a snapshot of the LMDB 0.9 development branch with various bugfixes cherry-picked in on occasion. At this point it doesn't correspond to any officially released LMDB version.
The LMDB v1.0 release branch has just been created and will be tagged soon.
https://git.openldap.org/openldap/openldap/-/tree/mdb.RE/1.0?ref_type=heads
Featurewise there's not a lot that visibly affects Monero. Support for page-level encryption is now built by default. Otherwise, there's not much in the way of performance that differs either. Maybe a small perf gain on very large write transactions, but overall not much difference. But the on-disk layout has changed, so an explicit migration step is required. I.e., you must use v0.9 mdb_dump to export the old database and use v1.0 mdb_load to import it, to operate on it with the v1.0 code. There is no programmatic support in the library to migrate to the newer version.
Just a heads up. This isn't something to consider immediately, but sometime soon. The official release of LMDB v1.0 is probably a week or so away.
The LMDB code in the Monero source tree is mostly a snapshot of the LMDB 0.9 development branch with various bugfixes cherry-picked in on occasion. At this point it doesn't correspond to any officially released LMDB version.
The LMDB v1.0 release branch has just been created and will be tagged soon.
https://git.openldap.org/openldap/openldap/-/tree/mdb.RE/1.0?ref_type=heads
Featurewise there's not a lot that visibly affects Monero. Support for page-level encryption is now built by default. Otherwise, there's not much in the way of performance that differs either. Maybe a small perf gain on very large write transactions, but overall not much difference. But the on-disk layout has changed, so an explicit migration step is required. I.e., you must use v0.9 mdb_dump to export the old database and use v1.0 mdb_load to import it, to operate on it with the v1.0 code. There is no programmatic support in the library to migrate to the newer version.