Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use mdb over hdb #50

Merged
merged 1 commit into from
Jun 9, 2016
Merged

Use mdb over hdb #50

merged 1 commit into from
Jun 9, 2016

Conversation

mikefaille
Copy link
Contributor

«The mdb backend to slapd(8) is the recommended primary backend for a
normal slapd database. It uses OpenLDAP's own Lightning Memory-Mapped
Database (LMDB) library to store data and is intended to replace the
Berkeley DB backends.

It supports indexing like the BDB backends, but it uses no caching and
requires no tuning to deliver maximum search performance. Like hdb, it
is also fully hierarchical and supports subtree renames in constant
time.»
http://www.openldap.org/doc/admin24/backends.html

«The mdb backend to slapd(8) is the recommended primary backend for a
normal slapd database. It uses OpenLDAP's own Lightning Memory-Mapped
Database (LMDB) library to store data and is intended to replace the
Berkeley DB backends.

It supports indexing like the BDB backends, but it uses no caching and
requires no tuning to deliver maximum search performance. Like hdb, it
is also fully hierarchical and supports subtree renames in constant
time.»
http://www.openldap.org/doc/admin24/backends.html
@mikefaille
Copy link
Contributor Author

mikefaille commented Apr 28, 2016

Note: The hdb backend has superseded the bdb backend, and both will soon be deprecated in favor of the new mdb backend. See below.
http://www.openldap.org/doc/admin24/backends.html

@osixia
Copy link
Collaborator

osixia commented May 2, 2016

Hi,
thanks for the pull request. It's a great idea.

I saw that the replication ldif files are impacted,
I guess this will break the configuration if the image is used with an existing HDB backend ?

So i'm considering adding an LDAP_BACKEND environment variable to let people choose between hdb and mdb (the default) to bootstrap a new database but this variable could also be used in the replication files to keep it working with existings HDB databases.

is this would be ok for you ?

@mikefaille
Copy link
Contributor Author

@osixia It sounds correct to me ! (sorry for my latency)
I suggest give major version for this mdb on master branch. And having old version branch using hdb.

Maybe, you can use version 1.2.x for mdb. And keeping version 1.1.x for hdb.

@osixia
Copy link
Collaborator

osixia commented Jun 9, 2016

merged in 1.1.3

@osixia osixia merged commit 1166325 into osixia:stable Jun 9, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants