Howard Chu hyc@symas.com schrieb am 08.09.2022 um 17:30 in Nachricht
f331a21a-7062-de6d-73b6-60a925de7cd8@symas.com:
Ulrich Windl wrote:
Howard Chu hyc@symas.com schrieb am 08.09.2022 um 01:34 in Nachricht
4bc80e7e-17f9-b385-6b11-2aab806edc43@symas.com:
Steffen Michels wrote:
Hi,
We are considering using the mdb.master3 branch of LMDB, but it is not clear
to me whether the data.mdb format will remain stable. Is there a chance that
another migration of all databases will be required in the future when
switching now?
Yes. It is still unreleased because additional changes to the freelist format are planned, and possibly a few other changes.
In any case, mdb_dump/mdb_load will always work for migrating to a new version.
I think at some point an inplace upgrade would be the way to go. On Linux filesystems, you could even upgrade yout ext3 to btrfs ;-)
That will never happen here. Supporting an in-place upgrade requires the library to support old and new formats simultaneously, which is a waste of RAM. Anything that pushes the object code size of the hot path over 64KB is a non-starter.
First, the so much criticized bdb could do that also, and second I don't think that a one-time conversion would be part of the code "hot path".
Regards, Ulrich
regards,
Steffen
-- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/
-- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/