https://bugs.openldap.org/show_bug.cgi?id=9735
--- Comment #3 from libor.peltan@nic.cz --- (In reply to jtgrassie from comment #2)
I wonder if this "try harder" approach is best activated via a flag on mdb_env_open? That way, only users who want the more aggressive search for free space get impacted.
I thought about it as well, but then I count'd find any use-case for the other (current) behavior. When the database can still grow, there is a clear trade-off between performance and occupied storage. But otherwise, should there be a trade-off between performance and (non-)functionality? Could you please think of an example where is it more desirable to return a failure than to continue trying hard (to find some free space)? Thank you!