https://bugs.openldap.org/show_bug.cgi?id=9431
--- Comment #1 from Howard Chu <[email protected]> --- We can set back-mdb to always configure this index itself on startup. But should we still allow it to be explicitly configured by the admin? Currently, configuring a redundant index triggers an error. Also, should it be visible in the config LDIF, or an invisible default? Should it be possible to delete the index setting? Do we need to detect if the setting exists but the actual index hasn't been created yet? Or just assume that DBs have been properly reloaded when migrating from 2.6 to 2.7? I think the simplest approach for now is to check if the index was set in db_open, after all configuration has been completed, and then set it if it's missing, before the rest of db_open finishes. That means if an admin explicitly deletes it from their config, it will silently be added back again on next restart. -- You are receiving this mail because: You are on the CC list for the issue.
