markus@greenrobot.de wrote:

Full_Name: Markus Junginger Version: OS: URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (77.189.91.168)

We have a 1GB LMDB file with 7M K/V entries. With MDB_VL32, we always get a MDB_TXN_FULL error for a transaction that is removing 2M entries (probably fails at a lower count, we haven't measured that). Without MDB_VL32 it works fine.

Another observation: Once the transaction fails with MDB_TXN_FULL, the data file has grown to 1.5GB. Without MDB_VL32, the data file stays consistent at 1 GB even if all 7M entries are deleted in a single transaction.

Expected behavior: No MDB_TXN_FULL error, no data file growth.

I believe this was fixed by commit 7edf504106c61639a89b9a4e5987242598196932 in mdb.master.