- Documentation Library
- Table of Contents
- MySQL 5.5 Manual
- MySQL 5.4 Manual
- MySQL 5.1 Manual
- MySQL 5.0 Manual
- MySQL 3.23/4.0/4.1 Manual
- Table of Contents
The following options to mysqld can be used
to change the behavior of the BDB storage
engine. For more information, see
Section 5.1.2, “Server Command Options”.
-
The base directory for
BDBtables. This should be the same directory that you use for--datadir. -
The
BDBlock detection method. The option value should beDEFAULT,OLDEST,RANDOM, orYOUNGEST. -
The
BDBlog file directory. -
Do not start Berkeley DB in recover mode.
-
Don't synchronously flush the
BDBlogs. This option is deprecated as of MySQL 4.0.18; use--skip-sync-bdb-logsinstead (see the description for--sync-bdb-logs). -
Start Berkeley DB in multi-process mode. (Do not use
DB_PRIVATEwhen initializing Berkeley DB.) -
The
BDBtemporary file directory. -
Disable the
BDBstorage engine. -
Synchronously flush the
BDBlogs. This option is enabled by default. Use--skip-sync-bdb-logsto disable it. This option was added in MySQL 4.0.18.
If you use the --skip-bdb option,
MySQL does not initialize the Berkeley DB library and this saves
a lot of memory. However, if you use this option, you cannot use
BDB tables. If you try to create a
BDB table, MySQL uses the default storage
engine instead.
Normally, you should start mysqld without the
--bdb-no-recover option if you
intend to use BDB tables. However, this may
cause problems when you try to start mysqld
if the BDB log files are corrupted. See
Section 2.10.2.3, “Starting and Troubleshooting the MySQL Server”.
With the bdb_max_lock variable,
you can specify the maximum number of locks that can be active
on a BDB table. The default is 10,000. You
should increase this if errors such as the following occur when
you perform long transactions or when mysqld
has to examine many rows to execute a query:
bdb: Lock table is out of available locks Got error 12 from ...
You may also want to change the
binlog_cache_size and
max_binlog_cache_size variables
if you are using large multiple-statement transactions. See
Section 5.3.4, “The Binary Log”.
See also Section 5.1.3, “Server System Variables”.
User Comments
Add your own comment.