There are many different options one can use to configure Drizzle.
Display this help and exit after initializing plugins.
Display this help and exit.
Configuration file defaults are not used if no-defaults is set
Configuration file to use
Base location for config files
Directory for plugins
Pid file used by drizzled.
Optional comma separated list of plugins to load at startup in addition to the default list of plugins.
For example:
--plugin_add=crc32,console,pbxt
Optional comma separated list of plugins to not load at startup. Effectively removes a plugin from the list of plugins to be loaded.
For example:
--plugin_remove=syslog,md5
Optional comma separated list of plugins to load at starup instead of the default plugin load list. This completely replaces the whole list.
Auto-increment columns are incremented by this
Offset added to Auto-increment columns. Used when auto-increment-increment != 1
Path to installation directory. All paths are usually resolved relative to this.
Chroot drizzled daemon during startup.
Set the default collation.
Default completion type.
Write core on errors.
Path to the database root.
Set the default storage engine for tables.
Set the default time zone.
Used for debugging; Use at your own risk!
Set up signals usable for debugging
Set the language used for the month names and the days of the week.
Log some not critical warnings to the log file.
Maximum time in seconds to wait for the port to become free. A value of 0 means not to wait.
Limit LOAD DATA, SELECT ... OUTFILE, and LOAD_FILE() to files within specified directory
Uniquely identifies the server instance in the community of replication partners.
Don’t print a stack trace on failure.
Enable symbolic link support.
Specify whether to time mutexes (only InnoDB mutexes are currently supported)
Path for temporary files.
Default transaction isolation level.
Run drizzled daemon as user.
Output version information and exit.
The number of outstanding connection requests Drizzle can have. This comes into play when the main Drizzle thread gets very many connection requests in a very short time.
Size of tree cache used in bulk insert optimization. Note that this is a limit per thread!
Precision of the result of ‘/’ operator will be increased on that value.
The maximum length of the result of function group_concat.
The size of the buffer that is used for full joins.
A global constraint for join-buffer-size for all clients, cannot be set lower than –join-buffer-size. Setting to 0 means unlimited.
Max packetlength to send/receive from to server.
If there is more than this number of interrupted connections from a host this host will be blocked from further connections.
Max number of errors/warnings to store for a statement.
Don’t allow creation of heap tables bigger than this.
Joins that are probably going to read more than max_join_size records return an error.
Max number of bytes in sorted records.
Limit assumed max number of seeks when looking up rows based on a key
The number of bytes to use when sorting BLOB or TEXT values (only the first max_sort_length bytes of each value are used; the rest are ignored).
After this many write locks, allow some read locks to run in between.
Don’t log queries which examine less than min_examined_row_limit rows to file.
Do not apply any heuristic(s) during query optimization to prune, thus perform an exhaustive search from the optimizer search space.
Maximum depth of search performed by the query optimizer. Values larger than the number of relations in a query result in better query plans, but take longer to compile a query. Smaller values than the number of tables in a relation result in faster optimization, but may produce very bad query plans. If set to 0, the system will automatically pick a reasonable value; if set to MAX_TABLES+2, the optimizer will switch to the original find_best (used for testing/comparison).
The size of the buffer that is allocated when preloading indexes
Allocation block size for query parsing and execution
Persistent buffer for query parsing and execution
Allocation block size for storing ranges during optimization
Each thread that does a sequential scan allocates a buffer of this size for each table it scans. If you do many sequential scans, you may want to increase this value. Note that this only affect MyISAM.
A global constraint for read-buffer-size for all clients, cannot be set lower than –read-buffer-size. Setting to 0 means unlimited.
When reading rows in sorted order after a sort, the rows are read through this buffer to avoid a disk seeks. If not set, then it’s set to the value of record_buffer.
A global constraint for read-rnd-buffer-size for all clients, cannot be set lower than –read-rnd-buffer-size. Setting to 0 means unlimited.
Select scheduler to be used.
Each thread that needs to do a sort allocates a buffer of this size.
A global constraint for sort-buffer-size for all clients, cannot be set lower than –sort-buffer-size. Setting to 0 means unlimited.
The number of cached table definitions.
The number of cached open tables.
Timeout in seconds to wait for a table level lock before returning an error. Used only if the connection has active cursors.
The stack size for each thread. 0 means use OS default.
If an internal in-memory temporary table exceeds this size, Drizzle will automatically convert it to an on-disk MyISAM table.