All that I am suggesting is that
A) - the admin guide should provide similar documentation and examples
for the bdb configuration, since that is now their primary database.
Much of what is needed is already in the faq - and the other thing that
would be nice is an example or two which were documented. The
documentation would explain why these parameters were set, and what their
ramifications are for openldap. At least then there would be a starting
point for end users to compare their environment to, and adjust
accordingly.
B) - they don't fall back on the defaults for Berkeley db, when no
DB_CONFIG file is present, since everyone seems to agree that the
Berkeley defaults are bad choices for openldap (in nearly any use case).
MySQL has the option of using BDB as their backend, much like openldap.
And they provide the default settings. Settings that work well for most
use cases. I certainly don't hear anyone clamoring for the MySQL
developers to stop picking good initial variables, and instead making
everyone who wants to use mysql with a bdb backend go out and read the
BerkeleyDB documentation before they try to use it.