---- START access-control.html ---- ---- END access-control.html ---- ---- START appendix-changes.html ---- ---- END appendix-changes.html ---- ---- START appendix-common-errors.html ---- ---- END appendix-common-errors.html ---- ---- START appendix-configs.html ---- ---- END appendix-configs.html ---- ---- START appendix-contrib.html ---- ---- END appendix-contrib.html ---- ---- START appendix-deployments.html ---- ---- END appendix-deployments.html ---- ---- START appendix-ldap-result-codes.html ---- ---- END appendix-ldap-result-codes.html ---- ---- START appendix-recommended-versions.html ---- ---- END appendix-recommended-versions.html ---- ---- START appendix-upgrading.html ---- ---- END appendix-upgrading.html ---- ---- START autoconf.html ---- ---- END autoconf.html ---- ---- START backends.html ---- 37,38c37,38 <

The bdb backend to slapd(8) is the recommended primary backend for a normal slapd database. It uses the Oracle Berkeley DB (BDB) package to store data. It makes extensive use of indexing and caching (see the Tuning section) to speed data access.

<

hdb is a variant of the bdb backend that uses a hierarchical database layout which supports subtree renames. It is otherwise identical to the bdb behavior, and all the same configuration options apply.

--- >

The hdb backend to slapd(8) is the recommended primary backend for a normal slapd database. It uses the Oracle Berkeley DB (BDB) package to store data. It makes extensive use of indexing and caching (see the Tuning section) to speed data access.

>

hdb is a variant of the original bdb backend which was first written for use with BDB. hdb uses a hierarchical database layout which supports subtree renames. It is otherwise identical to the bdb behavior, and all the same configuration options apply.

41a42,44 >

> Note: The hdb backend has superseded the bdb backend, and both will soon be deprecated in favor of the new mdb backend. See below. >

126c129 <

11.4. MDB

--- >

11.4. LMDB

128c131 <

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

--- >

The mdb backend to slapd(8) is the upcoming 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.

131c134 <

Unlike the BDB backends, the MDB backend can be instantiated with very few configuration lines:

--- >

Unlike the BDB backends, the mdb backend can be instantiated with very few configuration lines:

142c145 <

In addition to the usual parameters that a minimal configuration requires, the MDB backend requires a maximum size to be set. This should be the largest that the database is ever anticipated to grow (in bytes). The filesystem must also provide enough free space to accommodate this size.

--- >

In addition to the usual parameters that a minimal configuration requires, the mdb backend requires a maximum size to be set. This should be the largest that the database is ever anticipated to grow (in bytes). The filesystem must also provide enough free space to accommodate this size.

---- END backends.html ---- ---- START config.html ---- ---- END config.html ---- ---- START copyright.html ---- ---- END copyright.html ---- ---- START dbtools.html ---- ---- END dbtools.html ---- ---- START glossary.html ---- 614c614 < MD5 --- > LMDB 617c617 < Message Digest 5 --- > Lightning Memory-Mapped Database 622c622 < MDB --- > MD5 625c625 < Memory-Mapped Database --- > Message Digest 5 ---- END glossary.html ---- ---- START index.html ---- 26c26 <
3 March 2013
--- >
19 August 2013
246c246 < 11.4. MDB