https://bugs.openldap.org/show_bug.cgi?id=10552
--- Comment #5 from donxenapo@gmail.com --- Okay, then I guess it's important to note that we're using LMDB in a potentially non-conventional way where we set the _maximum_ database size to a very large value (we use 100GB) for a database that we expect to be ~1-5GB on average for most users. So we rely on the functionality that LMDB implemented in 1.0.0 (and we also have that in our 0.9.90) where the actual space used by the database on the disk grows proportionally to how much data we store in it. Looks like that functionality is not available in 0.9.35, so it would be non-trivial for us to downgrade to that version, hence we'd really prefer to change to a tag that does support this dynamic growing behavior.
So a couple questions here: is it actually intended behavior to allocate the database of size much larger than what a user might have available on their drive?In order to use that, should we stick to 1.0.0 and up?