mariadbd Options
This page lists all of the options for mariadbd (called mysqld before MariaDB 10.5), ordered by topic. For a full alphabetical list of all mariadbd options, as well as server and status variables, see Full list of MariaDB options, system and status variables.
In many cases, the entry here is a summary, and links to the full description.
By convention, server variables have usually been specified with an underscore in the configuration files, and a dash on the command line. You can however specify underscores as dashes - they are interchangeable.
See Configuring MariaDB with Option Files for which files and groups mariadbd reads for it's default options.
Prior to MariaDB 10.5, the client used to be called mysqld, and can still be accessed under this name, via a symlink in Linux, or an alternate binary in Windows.
Option Prefixes
--autoset-*
--autoset-*Description: Sets the option value automatically. Only supported for certain options.
--disable-*
--disable-*Description: For all boolean options, disables the setting (equivalent to setting it to
0). Same as--skip.
--enable-*
--enable-*Description: For all boolean options, enables the setting (equivalent to setting it to
1).
--loose-*
--loose-*Description: Don't produce an error if the option doesn't exist.
--maximum-*
--maximum-*Description: Sets the maximum value for the option.
--skip-*
--skip-*Description: For all boolean options, disables the setting (equivalent to setting it to
0). Same as--disable.
Option File Options
--defaults-extra-file
--defaults-extra-fileCommand line:
--defaults-extra-file=nameDescription: Read this extra option file after all other option files are read.
--defaults-file
--defaults-fileCommand line:
--defaults-file=nameDescription: Only read options from the given option file.
--defaults-group-suffix
--defaults-group-suffixCommand line:
--defaults-group-suffix=nameDescription: In addition to the default option groups, also read option groups with the given suffix.
--no-defaults
--no-defaultsCommand line:
--no-defaultsDescription: Don't read options from any option file.
--print-defaults
--print-defaultsCommand line:
--print-defaultsDescription: Read options from option files, print all option values, and then exit the program.
Compatibility Options
The following options have been added to MariaDB to make it more compliant with other MariaDB and MySQL versions. Options that are also system variables are listed after:
-a, --ansi
-a, --ansiDescription: Use ANSI SQL syntax instead of MariaDB syntax. This mode will also set transaction isolation level serializable.
--new
--newDescription: Use new functionality that will exist in next version of MariaDB. This function exists to make it easier to prepare for an upgrade.
--old-style-user-limits
--old-style-user-limitsDescription: Enable old-style user limits (before MySQL 5.0.3, user resources were counted per each user+host vs. per account).
--safe-mode
--safe-modeDescription: Disable some potential unsafe optimizations. For 5.2, INSERT DELAYED is disabled, myisam_recover_options is set to DEFAULT (automatically recover crashed MyISAM files) and the query cache is disabled. For Aria tables, disable bulk insert optimization to enable one to use aria_read_log to recover tables even if tables are deleted (good for testing recovery).
--skip-new
--skip-newDescription: Disables --new.
Compatibility Options and System Variables
Locale Options
Options that are also system variables are listed after:
--character-set-client-handshake
--character-set-client-handshakeCommand line:
--character-set-client-handshakeDescription: Don't ignore client side character set value sent during handshake.
--skip-character-set-client-handshakewill ignore the client value and use the default server value.
--default-character-set
--default-character-setCommand line:
--default-character-set=nameDescription: Still available as an option for setting the default character set for clients and their connections, it was deprecated and removed in MariaDB 10.2 as a server option. Use character-set-server instead.
--language
--languageDescription: This option can be used to set the server's language for error messages. This option can be specified either as a language name or as the path to the directory storing the language's error message file. See Server Locales for a list of supported locales and their associated languages.
This option is deprecated. Use the lc_messages and lc_messages_dir system variables instead.
See Setting the Language for Error Messages for more information.
Locale Options and System Variables
Windows Options
Options that are also system variables are listed after:
--console
--consoleDescription: Windows-only option that keeps the console window open and for writing log messages to stderr and stdout. If specified together with --log-error, the last option will take precedence.
--install
--installDescription: Windows-only option that installs the
mariadbdprocess as a Windows service.The Windows service created with this option auto-starts. If you want a service that is started on demand, then use the --install-manual option.
This option takes a service name as an argument. If this option is provided without a service name, then the service name defaults to "MARIADB".
This option is deprecated and may be removed in a future version. See MDEV-19358 for more information.
--install-manual
--install-manualDescription: Windows-only option that installs the
mariadbdprocess as a Windows service.The Windows service created with this option is started on demand. If you want a service that auto-starts, use the --install option.
This option takes a service name as an argument. If this option is provided without a service name, then the service name defaults to "MARIADB".
This option is deprecated and may be removed in a future version. See MDEV-19358 for more information.
--remove
--removeDescription: Windows-only option that removes the Windows service created by the --install or --install-manual options.
This option takes a service name as an argument. If this option is provided without a service name, then the service name defaults to "MARIADB".
This option is deprecated and may be removed in a future version. See MDEV-19358 for more information.
--slow-start-timeout
--slow-start-timeoutDescription: Windows-only option that defines the maximum number of milliseconds that the service control manager should wait before trying to kill the Windows service during startup. Defaults to
15000.
--standalone
--standaloneDescription: Windows-only option that has no effect. Kept for compatibility reasons.
Windows Options and System Variables
The following options and system variables are related to using MariaDB on Windows:
Replication and Binary Logging Options
The following options are related to replication and the binary log. Options that are also system variables are listed after:
--abort-slave-event-count
--abort-slave-event-countCommand line:
--abort-slave-event-count=#Description: Option used by mysql-test for debugging and testing of replication.
--binlog-do-db
--binlog-do-dbCommand line:
--binlog-do-db=nameDescription: This option allows you to configure a replication master to write statements and transactions affecting databases that match a specified name into its binary log. Since the filtered statements or transactions will not be present in the binary log, its replicas will not be able to replicate them.
This option will not work with cross-database updates with statement-based logging. See the Statement-Based Logging section for more information.
This option can not be set dynamically. Available as a system variable from MariaDB 11.2.0.
When setting it on the command-line or in a server option group in an option file, the option does not accept a comma-separated list. If you would like to specify multiple filters, then you need to specify the option multiple times.
See Replication Filters for more information.
--binlog-ignore-db
--binlog-ignore-dbCommand line:
--binlog-ignore-db=nameDescription: This option allows you to configure a replication master to not write statements and transactions affecting databases that match a specified name into its binary log. Since the filtered statements or transactions will not be present in the binary log, its replicas will not be able to replicate them.
This option will not work with cross-database updates with statement-based logging. See the Statement-Based Logging section for more information.
This option can not be set dynamically. Available as a system variable from MariaDB 11.2.0.
When setting it on the command-line or in a server option group in an option file, the option does not accept a comma-separated list. If you would like to specify multiple filters, then you need to specify the option multiple times.
See Replication Filters for more information.
--binlog-row-event-max-size
--binlog-row-event-max-sizeCommand line:
--binlog-row-event-max-size=#Description: The maximum size of a row-based binary log event in bytes. Rows will be grouped into events smaller than this size if possible. The value has to be a multiple of 256. Available as a system variable from MariaDB 11.2.0.
Default value
8192
--disconnect-slave-event-count
--disconnect-slave-event-countCommand line:
--disconnect-slave-event-count=#Description: Option used by mysql-test for debugging and testing of replication.
--flashback
--flashbackCommand line:
--flashbackDescription: Setup the server to use flashback. This enables the binary log and sets
binlog_format=ROW.
--init-rpl-role
--init-rpl-roleCommand line:
--init-rpl-role=nameDescription: Set the replication role. From MariaDB 10.6.19, MariaDB 10.11.9, MariaDB 11.1.6, MariaDB 11.2.5, MariaDB 11.4.3 and MariaDB 11.5.2, changes the condition for semi-sync recovery to truncate the binlog to instead use this option, when set to SLAVE. This allows for both rpl_semi_sync_master_enabled and rpl_semi_sync_slave_enabled to be set for a primary that is restarted, and no transactions will be lost, so long as
--init-rpl-roleis not set to SLAVE. In earlier versions, for servers configured with both rpl_semi_sync_master_enabled=1 and rpl_semi_sync_slave_enabled=1, if a primary is just re-started (i.e. retaining its role as primary), it can truncate its binlog to drop transactions which its replica(s) have already received and executed. If this happens, when the replica reconnects, its gtid_slave_pos can be ahead of the recovered primary’s gtid_binlog_pos, resulting in an error state where the replica’s state is ahead of the primary’s. See -init-rpl-role.Valid values: Empty,
MASTERorSLAVE
--log-basename
--log-basenameCommand line:
--log-basename=nameDescription: Basename for all log files and the .pid file. This sets all log file names at once (in 'datadir') and is normally the only option you need for specifying log files. This is especially recommended to be set if you are using replication as it ensures that your log file names are not dependent on your host name. Sets names for the binary log, relay log, general query log, slow query log and error log. Note that if you explicity set log file names with any of these other options; log-bin-index, relay-log, relay-log-index, general-log-file, log_slow_query_file (slow_query_log_file), log_error, and pid-file, these should be placed after
--log-basenamein the config files. Later settings override earlier settings, solog-basenamewill override any earlier log file name settings.
--log-bin-trust-routine-creators
--log-bin-trust-routine-creatorsCommand line:
--log-bin-trust-routine-creatorsDescription: Deprecated, use log-bin-trust-function-creators.
--master-host
--master-hostCommand line:
--master-host=nameDescription: Primary hostname or IP address for replication. If not set, the replica thread will not be started. Note that the setting of master-host will be ignored if there exists a valid master.info file.
--master-info-file
--master-info-fileCommand line:
--master-info-file=nameDescription: Name and location of the file on the replica where the
MASTER_LOG_FILEandMASTER_LOG_POSoptions (i.e. the binary log position on the primary) and most other CHANGE MASTER options are written. The replica's I/O thread keeps this binary log position updated as it downloads events.See CHANGE MASTER TO: Option Persistence for more information.
--master-password
--master-passwordCommand line:
--master-password=nameDescription: The password the replica thread will authenticate with when connecting to the primary. If not set, an empty password is assumed. The value in master.info will take precedence if it can be read.
--master-port
--master-portCommand line:
--master-port=#Description: The port the master is listening on. If not set, the compiled setting of MYSQL_PORT is assumed. If you have not tinkered with configure options, this should be 3306. The value in master.info will take precedence if it can be read.
--master-retry-count
--master-retry-countCommand line:
--master-retry-count=#Description: Number of times a replica will attempt to connect to a primary before giving up. The retry interval is determined by the MASTER_CONNECT_RETRY option for the CHANGE MASTER statement. A value of 0 means the replica will not stop attempting to reconnect. Reconnects are triggered when a replica has timed out. See slave_net_timeout.
Default Value:
86400through 10.5,100000as of 10.6Range - 32 bit:
0 to 4294967295Range - 64 bit:
0 to 18446744073709551615
--master-ssl
--master-sslCommand line:
--master-sslDescription: Enable the replica to connect to the master using TLS.
--master-ssl-ca
--master-ssl-caCommand line:
--master-ssl-ca[=name]Description: Master TLS CA file. Only applies if you have enabled master-ssl.
--master-ssl-capath
--master-ssl-capathCommand line:
--master-ssl-capath[=name]Description: Master TLS CA path. Only applies if you have enabled master-ssl.
--master-ssl-cert
--master-ssl-certCommand line:
--master-ssl-cert[=name]Description: Master TLS certificate file name. Only applies if you have enabled master-ssl.
--master-ssl-cipher
--master-ssl-cipherCommand line:
--master-ssl-cipher[=name]Description: Master TLS cipher. Only applies if you have enabled master-ssl.
--master-ssl-key
--master-ssl-keyCommand line:
--master-ssl-key[=name]Description: Master TLS keyfile name. Only applies if you have enabled master-ssl.
--master-user
--master-userCommand line:
--master-user=nameDescription: The username the replica thread will use for authentication when connecting to the primary. The user must have FILE privilege. If the primary user is not set, user test is assumed. The value in master.info will take precedence if it can be read.
--max-binlog-dump-events
--max-binlog-dump-eventsCommand line:
--max-binlog-dump-events=#Description: Option used by mysql-test for debugging and testing of replication.
--replicate-same-server-id
--replicate-same-server-idCommand line:
--replicate-same-server-idDescription: In replication, if set to 1, do not skip events having our server id. Default value is 0 (to break infinite loops in circular replication). Can't be set to 1 if log-slave-updates is used. Added as a system variable in MariaDB 12.0.
--sporadic-binlog-dump-fail
--sporadic-binlog-dump-failCommand line:
--sporadic-binlog-dump-failDescription: Option used by mysql-test for debugging and testing of replication.
--sysdate-is-now
--sysdate-is-nowCommand line:
--sysdate-is-nowDescription: Non-default option to alias SYSDATE() to NOW() to make it safe for replication. Since 5.0, SYSDATE() has returned a `dynamic' value different for different invocations, even within the same statement.
Replication and Binary Logging Options and System Variables
The options and system variables related to Replication and Binary Logging are described on Replication and Binary Logging System Variables.
Semisynchronous Replication Options and System Variables
The options and system variables related to Semisynchronous Replication are described here.
Optimizer Options
Options that are also system variables are listed after:
--record-buffer
--record-bufferCommand line:
--record-buffer=#Description: Old alias for read_buffer_size.
Removed: MariaDB 5.5
--table-cache
--table-cacheCommand line:
--table-open-cache=#Description: Removed; use --table-open-cache instead.
Removed: MariaDB 5.3.1
Optimizer Options and System Variables
Storage Engine Options
--skip-bdb
--skip-bdbCommand line:
----skip-bdbDescription: Deprecated option; Exists only for compatibility with very old my.cnf files.
Removed: MariaDB 10.5.1
--external-locking
--external-lockingCommand line:
--external-lockingDescription: Use system (external) locking (disabled by default). With this option enabled you can run myisamchk to test (not repair) tables while the server is running. Disable with --skip-external-locking. From MariaDB 10.2.40, MariaDB 10.3.31, MariaDB 10.4.21, MariaDB 10.5.12, MariaDB 10.6.4 and all later version, this effects InnoDB and can be used to prevent multiple instances running on the same data.
MyISAM Storage Engine Options
The options related to the MyISAM storage engine are described below. Options that are also system variables are listed after:
--log-isam
--log-isamCommand line:
--log-isam[=file_name]Description: Enable the MyISAM log, which logs all MyISAM changes to file. If no filename is provided, the default, myisam.log is used.
MyISAM Storage Engine Options and System Variables
Some options and system variables related to the MyISAM storage engine can be found here. Direct links to many of them can be found below.
InnoDB Storage Engine Options
The options related to the InnoDB storage engine are described below. Options that are also system variables are listed after:
--innodb
--innodbCommand line:
--innodb=value,--skip-innodbDescription: This variable controls whether or not to load the InnoDB storage engine. Possible values are
ON,OFF,FORCEorFORCE_PLUS_PERMANENT(from MariaDB 5.5). If set toOFF(the same as --skip-innodb), since InnoDB is the default storage engine, the server will not start unless another storage engine has been chosen with --default-storage-engine.FORCEmeans that the storage engine must be successfully loaded, or else the server won't start.FORCE_PLUS_PERMANENTenables the plugin, but if plugin cannot initialize, the server will not start. In addition, the plugin cannot be uninstalled while the server is running.
--innodb-cmp
--innodb-cmpCommand line:
--innodb-cmpDescription:
Default:
ON
--innodb-cmp-reset
--innodb-cmp-resetCommand line:
--innodb-cmp-resetDescription:
Default:
ON
--innodb-cmpmem
--innodb-cmpmemCommand line:
--innodb-cmpmemDescription:
Default:
ON
--innodb-cmpmem-reset
--innodb-cmpmem-resetCommand line:
--innodb-cmpmem-resetDescription:
Default:
ON
--innodb-file-io-threads
--innodb-file-io-threadsCommand line:
--innodb-file-io-threadsDescription:
Default:
4Removed: MariaDB 10.3.0
--innodb-index-stats
--innodb-index-statsCommand line:
--innodb-index-statsDescription:
Default:
ONRemoved: MariaDB 10.0.0
--innodb-lock-waits
--innodb-lock-waitsCommand line:
--innodb-lock-waitsDescription:
Default:
ON
--innodb-locks
--innodb-locksCommand line:
--innodb-locksDescription:
Default:
ON
--innodb-rseg
--innodb-rsegCommand line:
--innodb-rsegDescription:
Default:
ONRemoved: MariaDB 10.0.0
--innodb-status-file
--innodb-status-fileCommand line:
--innodb-status-fileDescription:
Default:
FALSE
--innodb-sys-indexes
--innodb-sys-indexesCommand line:
--innodb-sys-indexesDescription:
Default:
ON
--innodb-sys-stats
--innodb-sys-statsCommand line:
--innodb-sys-statsDescription:
Default:
ONRemoved: MariaDB 10.0.0
--innodb-sys-tables
--innodb-sys-tablesCommand line:
--innodb-sys-tablesDescription:
Default:
ON
--innodb-table-stats
--innodb-table-statsCommand line:
--innodb-table-statsDescription:
Default:
ONRemoved: MariaDB 10.0.0
--innodb-trx
--innodb-trxCommand line:
--innodb-trxDescription:
Default:
ON
InnoDB Storage Engine Options and System Variables
Some options and system variables related to the InnoDB storage engine can be found here. Direct links to many of them can be found below.
skip-innodb
Aria Storage Engine Options
Options related to the Aria storage engine are listed below:
Aria Storage Engine Options and System Variables
Some options and system variables related to the Aria storage engine can be found here. Direct links to many of them can be found below.
MyRocks Storage Engine Options
The options and system variables related to the MyRocks storage engine can be found here.
S3 Storage Engine Options
The options and system variables related to the S3 storage engine can be found here.
CONNECT Storage Engine Options
The options related to the CONNECT storage engine are described below.
CONNECT Storage Engine Options and System Variables
Some options and system variables related to the CONNECT storage engine can be found here. Direct links to many of them can be found below.
Spider Storage Engine Options
The options and system variables related to the Spider storage engine can be found here.
Mroonga Storage Engine Options
The options and system variables related to the Mroonga storage engine can be found here.
TokuDB Storage Engine Options
The options and system variables related to the TokuDB storage engine can be found here.
Vector Options
The options and system variables related to Vectors storage engine (beginning with mhnsw) can be found here.
Performance Schema Options
The options related to the Performance Schema are described below. Options that are also system variables are listed after:
--performance-schema-consumer-events-stages-current
--performance-schema-consumer-events-stages-currentCommand line:
--performance-schema-consumer-events-stages-currentDescription: Enable the events-stages-current consumer.
Default:
OFF
--performance-schema-consumer-events-stages-history
--performance-schema-consumer-events-stages-historyCommand line:
--performance-schema-consumer-events-stages-historyDescription: Enable the events-stages-history consumer.
Default:
OFF
--performance-schema-consumer-events-stages-history-long
--performance-schema-consumer-events-stages-history-longCommand line:
--performance-schema-consumer-events-stages-history-longDescription: Enable the events-stages-history-long consumer.
Default:
OFF
--performance-schema-consumer-events-statements-current
--performance-schema-consumer-events-statements-currentCommand line:
--performance-schema-consumer-events-statements-currentDescription: Enable the events-statements-current consumer. Use
--skip-performance-schema-consumer-events-statements-currentto disable.Default:
ON
--performance-schema-consumer-events-statements-history
--performance-schema-consumer-events-statements-historyCommand line:
--performance-schema-consumer-events-statements-historyDescription: Enable the events-statements-history consumer.
Default:
OFF
--performance-schema-consumer-events-statements-history-long
--performance-schema-consumer-events-statements-history-longCommand line:
--performance-schema-consumer-events-statements-history-longDescription: Enable the events-statements-history-long consumer.
Default:
OFF
--performance-schema-consumer-events-waits-current
--performance-schema-consumer-events-waits-currentCommand line:
--performance-schema-consumer-events-waits-currentDescription: Enable the events-waits-current consumer.
Default:
OFF
--performance-schema-consumer-events-waits-history
--performance-schema-consumer-events-waits-historyCommand line:
--performance-schema-consumer-events-waits-historyDescription: Enable the events-waits-history consumer.
Default:
OFF
--performance-schema-consumer-events-waits-history-long
--performance-schema-consumer-events-waits-history-longCommand line:
--performance-schema-consumer-events-waits-history-longDescription: Enable the events-waits-history-long consumer.
Default:
OFF
--performance-schema-consumer-global-instrumentation
--performance-schema-consumer-global-instrumentationCommand line:
--performance-schema-consumer-global-instrumentationDescription: Enable the global-instrumentation consumer. Use
--skip-performance-schema-consumer-global-instrumentationto disable.Default:
ON
--performance-schema-consumer-statements-digest
--performance-schema-consumer-statements-digestCommand line:
--performance-schema-consumer-statements-digestDescription: Enable the statements-digest consumer. Use
--skip-performance-schema-consumer-statements-digestto disable.Default:
ON
--performance-schema-consumer-thread-instrumentation
--performance-schema-consumer-thread-instrumentationCommand line:
--performance-schema-consumer-thread-instrumentationDescription: Enable the statements-thread-instrumentation. Use
--skip-performance-schema-thread-instrumentationto disable.Default:
ON
Performance Schema Options and System Variables
Some options and system variables related to the Performance Schema can be found here. Direct links to many of them can be found below.
Galera Cluster Options
The options related to Galera Cluster are described below. Options that are also system variables are listed after:
--wsrep-new-cluster
--wsrep-new-clusterCommand line:
--wsrep-new-clusterDescription: Bootstrap a cluster. It works by overriding the current value of wsrep_cluster_address. It is recommended not to add this option to the config file as this will trigger bootstrap on every server start.
Galera Cluster Options and System Variables
Some options and system variables related to Galera Cluster can be found here. Direct links to many of them can be found below.
Options When Debugging mariadbd
--debug-assert-if-crashed-table
--debug-assert-if-crashed-tableDescription: Do an assert in handler::print_error() if we get a crashed table.
--debug-binlog-fsync-sleep
--debug-binlog-fsync-sleepDescription:
--debug-binlog-fsync-sleep=#If not set to zero, sets the number of micro-seconds to sleep after running fsync() on the binary log to flush transactions to disk. This can thus be used to artificially increase the perceived cost of such an fsync().
--debug-crc-break
--debug-crc-breakDescription:
--debug-crc-break=#Call my_debug_put_break_here() if crc matches this number (for debug).
--debug-flush
--debug-flushDescription: Default debug log with flush after write.
--debug-no-sync
--debug-no-syncDescription:
debug-no-sync[=#]Disables system sync calls. Only for running tests or debugging!
--debug-sync-timeout
--debug-sync-timeoutDescription:
debug-sync-timeout[=#]Enable the debug sync facility and optionally specify a default wait timeout in seconds. A zero value keeps the facility disabled.
--gdb
--gdbDescription: Set up signals usable for debugging.
--silent-startup
--silent-startupDescription: Don't print Notes to the error log during startup.
--sync-sys
--sync-sysDescription: Enable/disable system sync calls. Syncs should only be turned off (
--disable-sync-sys) when running tests or debugging! Replaced by debug-no-sync from MariaDB 5.5.Removed: MariaDB 5.5
--thread-alarm
--thread-alarmDescription: Enable/disable system thread alarm calls. Should only be turned off (
--disable-thread-alarm) when running tests or debugging!
Debugging Options and System Variables
Other Options
Options that are also system variables are listed after:
--allow-suspicious-udfs
--allow-suspicious-udfsCommand line:
--allow-suspicious-udfsDescription: Allows use of user-defined functions consisting of only one symbol
x()without correspondingx_init()orx_deinit(). That also means that one can load any function from any library, for exampleexit()fromlibc.so. Not recommended unless you require old UDFs with one symbol that cannot be recompiled. From MariaDB 10.10, available as a system variable as well.
--bootstrap
--bootstrapCommand line:
--bootstrapDescription: Used by mariadb installation scripts, such as mariadb-install-db to execute SQL scripts before any privilege or system tables exist. Do no use while an existing MariaDB instance is running.
--chroot
--chrootCommand line:
--chroot=nameDescription: Chroot mariadbd daemon during startup.
--des-key-file
--des-key-fileCommand line:
--des-key-file=nameDescription: Load keys for des_encrypt() and des_encrypt from given file.
--exit-info
--exit-infoCommand line:
--exit-info[=#]Description: Used for debugging. Use at your own risk.
--getopt-prefix-matching
--getopt-prefix-matchingCommand line:
--getopt-prefix-matching={0|1}Description: Makes it possible to disable historical "unambiguous prefix" matching in the command-line option parsing.
Default: TRUE
Introduced: MariaDB 10.1.3
--help
--helpCommand line:
--helpDescription: Displays help with many commandline options described, and exits. From MariaDB 11.5, includes deprecation information.
--log-ddl-recovery
--log-ddl-recoveryCommand line:
--log-ddl-recovery=nameDescription: Path to file used for recovery of DDL statements after a crash.
Default Value:
ddl-recover.logIntroduced: MariaDB 10.6.1
--log-short-format
--log-short-formatCommand line:
--log-short-formatDescription: Don't log extra information to update and slow-query logs.
--log-slow-file
--log-slow-fileCommand line:
--log-slow-file=nameDescription: Log slow queries to given log file. Defaults logging to hostname-slow.log
--log-slow-time
--log-slow-timeCommand line:
--log-slow-time=#Description: Log all queries that have taken more than long-query-time seconds to execute to the slow query log, if active. The argument will be treated as a decimal value with microsecond precision.
--log-tc
--log-tcCommand line:
--log-tc=nameDescription: Defines the path to the memory-mapped file-based transaction coordinator log, which is only used if the binary log is disabled. If you have two or more XA-capable storage engines enabled, then a transaction coordinator log must be available. See Transaction Coordinator Log for more information. Also see the log_tc_size system variable and the --tc-heuristic-recover option.
Default Value:
tc.log
--master-connect-retry
--master-connect-retryCommand line:
--master-connect-retry=#Description: Deprecated in 5.1.17 and removed in 5.5. The number of seconds the replica thread will sleep before retrying to connect to the master, in case the master goes down or the connection is lost.
--memlock
--memlockCommand line:
--memlockDescription: Lock mariadbd in memory.
--ndb-use-copying-alter-table
--ndb-use-copying-alter-tableCommand line:
--ndb-use-copying-alter-tableDescription: Force ndbcluster to always copy tables at alter table (should only be used if on-line alter table fails).
--one-thread
--one-threadCommand line:
--one-threadDescription: (Deprecated): Only use one thread (for debugging under Linux). Use thread-handling=no-threads instead.
Removed: MariaDB 10.0.4
--plugin-load
--plugin-loadCommand line:
--plugin-load=nameDescription: This option can be used to configure the server to load specific plugins. This option uses the following format:
Plugins can be specified in the format
name=library, wherenameis the plugin name andlibraryis the plugin library. This format installs a single plugin from the given plugin library.Plugins can also be specified in the format
library, wherelibraryis the plugin library. This format installs all plugins from the given plugin library.Multiple plugins can be specified by separating them with semicolons.
Special care must be taken when specifying the --plugin-load option multiple times, or when specifying both the --plugin-load option and the --plugin-load-add option together. The --plugin-load option resets the plugin load list, and this can cause unexpected problems if you are not aware. The --plugin-load-add option does not reset the plugin load list, so it is much safer to use. See Plugin Overview: Specifying Multiple Plugin Load Options for more information.
See Plugin Overview: Installing a Plugin with Plugin Load Options for more information.
--plugin-load-add
--plugin-load-addCommand line:
--plugin-load-add=nameDescription: This option can be used to configure the server to load specific plugins. This option uses the following format:
Plugins can be specified in the format
name=library, wherenameis the plugin name andlibraryis the plugin library. This format installs a single plugin from the given plugin library.Plugins can also be specified in the format
library, wherelibraryis the plugin library. This format installs all plugins from the given plugin library.Multiple plugins can be specified by separating them with semicolons.
Special care must be taken when specifying both the --plugin-load option and the --plugin-load-add option together. The --plugin-load option resets the plugin load list, and this can cause unexpected problems if you are not aware. The --plugin-load-add option does not reset the plugin load list, so it is much safer to use. See Plugin Overview: Specifying Multiple Plugin Load Options for more information.
See Plugin Overview: Installing a Plugin with Plugin Load Options for more information.
--port-open-timeout
--port-open-timeoutCommand line:
--port-open-timeout=#Description: Maximum time in seconds to wait for the port to become free. (Default: No wait).
--safe-user-create
--safe-user-createCommand line:
--safe-user-createDescription: Don't allow new user creation by the user who has no write privileges to the mysql.user table.
--safemalloc-mem-limit
--safemalloc-mem-limitCommand line:
--safemalloc-mem-limit=#Description: Simulate memory shortage when compiled with the
--with-debug=fulloption.
--show-slave-auth-info
--show-slave-auth-infoCommand line:
--show-slave-auth-infoDescription: Show user and password in SHOW REPLICA HOSTS (SHOW SLAVE HOSTS) on this primary. Also added as a system variable in MariaDB 12.0.
--skip-grant-tables
--skip-grant-tablesCommand line:
--skip-grant-tablesDescription: Start without grant tables. This gives all users FULL ACCESS to all tables, which is useful in case of a lost root password. Use mariadb-admin flush-privileges, mariadb-admin reload or FLUSH PRIVILEGES to resume using the grant tables. From MariaDB 10.10, available as a system variable as well.
Because the Event Scheduler also depends on the grant tables for its functionality, it is automatically disabled when running with --skip-grant-tables.
--skip-host-cache
--skip-host-cacheCommand line:
--skip-host-cacheDescription: Don't cache host names.
--skip-partition
--skip-partitionCommand line:
--skip-partition,--disable-partitionDescription: Disables user-defined partitioning. Previously partitioned tables cannot be accessed or modifed. Tables can still be seen with SHOW TABLES or by viewing the INFORMATION_SCHEMA.TABLES table. Tables can be dropped with DROP TABLE, but this only removes .frm files, not the associated .par files, which will need to be removed manually.
--skip-slave-start
--skip-slave-startCommand line:
--skip-slave-startDescription: If set, replica is not autostarted. From MariaDB 12.0, server will display in the log if this option is set.
--skip-ssl
--skip-sslCommand line:
--skip-sslDescription: Disable TLS connections.
--skip-symlink
--skip-symlinkCommand line:
--skip-symlinkDescription: Don't allow symlinking of tables. Deprecated and removed in MariaDB 5.5. Use symbolic-links with the
skipoption prefix instead.Removed: MariaDB 5.5
--skip-thread-priority
--skip-thread-priorityCommand line:
--skip-thread-priorityDescription: Don't give threads different priorities. Deprecated and removed in MariaDB 10.0.
Removed: MariaDB 10.0
--sql-bin-update-same
--sql-bin-update-sameCommand line:
--sql-bin-update-same=#Description: The update log was deprecated in version 5.0 and replaced by the binary log, so this option did nothing since then. Deprecated and removed in MariaDB 5.5.
Removed: MariaDB 5.5
--ssl
--sslCommand line:
--sslDescription: Enable TLS for connection (automatically enabled with other flags). Disable with '
--skip-ssl'.
--stack-trace
--stack-traceCommand line:
--stack-trace,--skip-stack-traceDescription: Print a stack trace on failure. Enabled by default, disable with
-skip-stack-trace.
--symbolic-links
--symbolic-linksCommand line:
--symbolic-linksDescription: Enables symbolic link support. When set, the have_symlink system variable shows as
YES. Silently ignored in Windows. Use--skip-symbolic-linksto disable.
--tc-heuristic-recover
--tc-heuristic-recoverCommand line:
--tc-heuristic-recover=nameDescription: If manual heuristic recovery is needed, this option defines the decision to use in the heuristic recovery process. Manual heuristic recovery may be needed if the transaction coordination log is missing or if it doesn't contain all prepared transactions. This option can be set to
OFF,COMMIT, orROLLBACK. The default isOFF. See also the --log-tc server option and the log_tc_size system variable.
--temp-pool
--temp-poolCommand line:
--temp-poolDescription: Using this option will cause most temporary files created to use a small set of names, rather than a unique name for each new file. This behavior works around a bug in old Linux kernels where the kernel appeared to "leak" memory. In a Docker environment it might look like an unbounded working-set memory growth. Defaults to
1until MariaDB 10.5.6, use--skip-temp-poolto disable. Defaults to0from MariaDB 10.5.7, as benchmarking shows it causes a heavy mutex contention.
--test-expect-abort
--test-expect-abortCommand line:
--test-expect-abortDescription: Expect that server aborts with 'abort'; Don't write out server variables on 'abort'. Useful only for test scripts.
--test-ignore-wrong-options
--test-ignore-wrong-optionsCommand line:
--test-ignore-wrong-optionsDescription: Ignore wrong enums values in command line arguments. Useful only for test scripts.
--user
--userCommand line:
--user=nameDescription: Run mariadbd daemon as user.
--verbose
--verboseCommand line:
-v,--verboseDescription: Used with help option for detailed help.
Other Options and System Variables
Authentication Plugins - Options and System Variables
Authentication Plugin - ed25519
ed25519The options related to the ed25519 authentication plugin can be found here.
Authentication Plugin - gssapi
gssapiThe system variables related to the gssapi authentication plugin can be found here.
The options related to the gssapi authentication plugin can be found here.
Authentication Plugin - named_pipe
named_pipeThe options related to the named_pipe authentication plugin can be found here.
Authentication Plugin - pam
pamThe system variables related to the pam authentication plugin can be found here.
The options related to the pam authentication plugin can be found here.
Authentication Plugin - unix_socket
unix_socketThe options related to the unix_socket authentication plugin can be found here.
Encryption Plugins - Options and System Variables
Encryption Plugin - aws_key_management
aws_key_managementThe system variables related to the aws_key_management encryption plugin can be found here.
The options elated to the aws_key_management encryption plugin can be found here.
Encryption Plugin - file_key_management
file_key_managementThe system variables related to the file_key_management encryption plugin can be found here.
The options related to the file_key_management encryption plugin can be found here.
Password Validation Plugins - Options and System Variables
Password Validation Plugin - simple_password_check
simple_password_checkThe system variables related to the c password validation plugin can be found here.
The options related to the simple_password_check password validation plugin can be found here.
Password Validation Plugin - cracklib_password_check
cracklib_password_checkThe system variables related to the cracklib_password_check password validation plugin can be found here.
The options related to the cracklib_password_check password validation plugin can be found here.
Audit Plugins - Options and System Variables
Audit Plugin - server_audit
server_auditOptions and system variables related to the server_audit audit plugin can be found here.
Audit Plugin - SQL_ERROR_LOG
SQL_ERROR_LOGThe options and system variables related to the SQL_ERROR_LOG audit plugin can be found here.
Audit Plugin - QUERY_RESPONSE_TIME_AUDIT
The options related to the QUERY_RESPONSE_TIME_AUDIT audit plugin can be found here.
Daemon Plugins - Options and System Variables
Daemon Plugin - handlersocket
handlersocketThe options for the HandlerSocket plugin are all described on the HandlerSocket Configuration Option page.
Information Schema Plugins - Options and System Variables
Information Schema Plugin - DISKS
DISKSThe options related to the DISKS information schema plugin can be found here.
Information Schema Plugin - feedback
feedbackThe system variables related to the feedback plugin can be found here.
The options related to the feedback plugin can be found here.
Information Schema Plugin - LOCALES
LOCALESThe options related to the LOCALES information schema plugin can be found here.
Information Schema Plugin - METADATA_LOCK_INFO
METADATA_LOCK_INFOThe options related to the METADATA_LOCK_INFO information schema plugin can be found here.
Information Schema Plugin - QUERY_CACHE_INFO
QUERY_CACHE_INFOThe options related to the QUERY_CACHE_INFO information schema plugin can be found here.
Information Schema Plugin - QUERY_RESPONSE_TIME
QUERY_RESPONSE_TIMEThe system variables related to the QUERY_RESPONSE_TIME information schema plugin can be found here.
The options related to the QUERY_RESPONSE_TIME information schema plugin can be found here.
Information Schema Plugin - user_variables
user_variablesThe options related to the user_variables information schema plugin can be found here.
Information Schema Plugin - WSREP_MEMBERSHIP
WSREP_MEMBERSHIPThe options related to the WSREP_MEMBERSHIP information schema plugin can be found here.
Information Schema Plugin - WSREP_STATUS
WSREP_STATUSThe options related to the WSREP_STATUS information schema plugin can be found here.
Replication Plugins - Options and System Variables
Replication Plugin - rpl_semi_sync_master
rpl_semi_sync_masterThe system variables related to the rpl_semi_sync_master replication plugin can be found here.
The options related to the rpl_semi_sync_master replication plugin can be found here.
Replication Plugin - rpl_semi_sync_slave
rpl_semi_sync_slaveThe system variables related to the rpl_semi_sync_slave replication plugin can be found here.
The options related to the rpl_semi_sync_slave replication plugin can be found here.
Default Values
You can verify the default values for an option by doing:
mariadbd --no-defaults --help --verboseThis page is licensed: GPLv2
Last updated
Was this helpful?

