1 .TH SLAPD-BDB 5 "RELEASEDATE" "OpenLDAP LDVERSION"
2 .\" Copyright 1998-2003 The OpenLDAP Foundation All Rights Reserved.
3 .\" Copying restrictions apply. See COPYRIGHT/LICENSE.
6 slapd-bdb \- BDB backend to slapd
12 is the recommended backend for a normal slapd database.
13 It uses the Sleepycat Berkeley DB (BDB) package to store data.
14 It makes extensive use of indexing and caching to speed data access.
16 It is noted that these options are intended to complement
17 Berkeley DB configuration options set in the environment's
19 file. See Berkeley DB documentation for
22 configuration options. Where there is overlap, settings in
28 options apply to the BDB backend database.
29 That is, they must follow a "database bdb" line and come before any
30 subsequent "backend" or "database" lines.
31 Other database options are described in the
35 .B cachesize <integer>
36 Specify the size in entries of the in-memory cache maintained
37 by the BDB backend database instance.
38 The default is 1000 entries.
40 .B checkpoint <kbyte> <min>
41 Specify the frequency for checkpointing the database transaction log.
42 A checkpoint operation flushes the database buffers to disk and writes
43 a checkpoint record in the log.
44 The checkpoint will occur if either <kbyte> data has been written or
45 <min> minutes have passed since the last checkpoint.
46 Both arguments default to zero, in which case they are ignored.
47 See the Berkeley DB reference guide for more details.
50 Specify that on-disk database contents should not be immediately
51 synchronized with in memory changes.
52 Enabling this option may improve performance at the expense of data
55 .B directory <directory>
56 Specify the directory where the BDB files containing this database and
57 associated indexes live.
58 A separate directory must be specified for each database.
60 .BR LOCALSTATEDIR/openldap-data .
63 Allow reads of modified but not yet committed data.
64 Usually transactions are isolated to prevent other operations from
65 accessing uncommitted data.
66 This option may improve performance, but may also return inconsistent
67 results if the data comes from a transaction that is later aborted.
68 In this case, the modified data is discarded and a subsequent search
69 will return a different result.
72 index {<attrlist>|default} [pres,eq,approx,sub,<special>]
73 Specify the indexes to maintain for the given attribute (or
75 Some attributes only support a subset of indexes.
76 If only an <attr> is given, the indices specified for \fBdefault\fR
78 Note that setting a default does not imply that all attributes will be
81 A number of special index parameters may be specified.
84 can be decomposed into
91 may be specified to disallow use of this index by language subtypes.
94 may be specified to disallow use of this index by named subtypes.
95 Note: changing index settings requires rebuilding indices, see
98 .B lockdetect {oldest|youngest|fewest|random|default}
99 Specify which transaction to abort when a deadlock is detected.
100 The default is the same as
104 Specify the file protection mode that newly created database
105 index files should have.
108 .B searchstack <depth>
109 Specify the depth of the stack used for search filter evaluation.
110 Search filters are evaluated on a stack to accomodate nested AND / OR
111 clauses. An individual stack is assigned to each server thread.
112 The depth of the stack determines how complex a filter can be
113 evaluated without requiring any additional memory allocation. Filters that
114 are nested deeper than the search stack depth will cause a separate
115 stack to be allocated for that particular search operation. These
116 allocations can have a major negative impact on server performance,
117 but specifying too much stack will also consume a great deal of memory.
118 Each search stack uses 512K bytes per level. The default stack depth
119 is 16, thus 8MB per thread is used.
123 default slapd configuration file
126 Berkeley DB configuration file
133 .BR Berkeley DB documentation .
projects / openldap / blob