The Ultimate Guide to High Availability with MariaDB

mysqld Options (full list)

You are viewing an old version of this article. View the current version here.

Contents

  1. Compatibility options
  2. Replication options
  3. Optimizer options
  4. Options when debugging mysqld
  5. Options for MyISAM
  6. Options for InnoDB
  7. Options for PBXT
    1. PBXT Cache Memory Variables
    2. PBXT Transaction Manager Variables
    3. PBXT Data Log Variables
    4. PBXT File Grow Variables
  8. Other Options
  9. Log warnings options
  10. Default values

This page lists all of the options for mysqld.

Compatibility options

The following options have been added to MariaDB to make it more complaint with other MariaDB and MySQL versions:

OptionDescription
-a, --ansiUse ANSI SQL syntax instead of MySQL syntax. This mode will also set transaction isolation level 'serializable'.
--newUse new functionality that will exist in next version of MariaDB. This function exist to make it easier to prepare for an upgrade. For version 5.1 this functions enables the LIST and RANGE partitions functions for ndbcluster.
--oldUse compatible behavior with previous main version for some functionality. For MariaDB 5.1 this means that we are using the old, MySQL 5.1 compatible, way to calculate checksums for records. If you are using --old, CHECKSUM TABLE will always do a full table scan.
--old-alter-tableUse old, non-optimized alter table.
--old-passwordsUse old password encryption method (needed for 4.0 and older clients).
--old-style-user-limitsEnable old-style user limits (before 5.0.3, user resources were counted per each user+host vs. per account).
--safe-modeDisable some potential unsafe optimization. For 5.2 these are: INSERT DELAYED is disabled, myisam_recover_options is set to DEFAULT (automatically recover crashed MyISAM files) and the query cache is disabled. For Aria table, disable bulk insert optimization to enable one to use maria_read_log to recover tables even if tables are deleted (good for testing recovery).
--skip-newDisables --new in 5.2. In 5.1 used to disable some new potentially unsafe functions.

Replication options

OptionDescriptionIntroduced   
--abort-slave-event-count=# Option used by mysql-test for debugging and testing of replication.
--auto-increment-increment[=#]Auto-increment columns are incremented by this.
--auto-increment-offset[=#]Offset added to Auto-increment columns. Used when auto-increment-increment != 1.
--binlog-annotate-rows-eventsWrite Annotate_rows events to the binary log.MariaDB 5.3
--binlog-checksum=nameType of BINLOG_CHECKSUM_ALG. Include checksum for log events in the binary log. Possible values are NONE and CRC32; default is NONE.MariaDB 5.5
--binlog-direct-non-transactional-updatesCauses updates to non-transactional engines using statement format to be written directly to binary log. Before using this option, make sure that there are no dependencies between transactional and non-transactional tables such as in the statement INSERT INTO t_myisam SELECT * FROM t_innodb; otherwise, slaves may diverge from the master.
--binlog-do-db=nameTells the master it should log updates for the specified database, and exclude all others not explicitly mentioned.
--binlog-ignore-db=nameTells the master that updates to the given database should not be logged to the binary log.
--binlog-row-event-max-size=# 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.
--binlog_cache_size=# The size of the cache to hold the SQL statements for the binary log during a transaction. If you often use big, multi-statement transactions you can increase this to get more performance.
--binlog_format=nameDoes not have any effect without '--log-bin'. Tell the master the form of binary logging to use: either 'row' for row-based binary logging, 'statement' for statement-based binary logging, or 'mixed'. 'mixed' is statement-based binary logging except for statements where only row-based is correct: Statements that involve user-defined functions (i.e., UDFs) or the UUID() function.
--disconnect-slave-event-count=# Option used by mysql-test for debugging and testing of replication.
--init-rpl-role=nameSet the replication role.
--init-slave=nameCommand(s) that are executed by a slave server each time the SQL thread starts.
--log-basename=nameBasename 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 recommend to be set if you are using replication as it ensures that your log file names are not depending on your host name. Sets names for --log-bin, --log-bin-index, --relay-log, --relay-log-index, --general-log-file, --log-slow-query-log-file, --log-error-file, and --pid-file.MariaDB 5.2
--log-bin[=name]Log update queries in binary format. Optional argument should be name for binary log. If not given datadir/'log-basename'-bin or 'datadir'/mysql-bin will be used (the later if --log-basename is not specified). We strongly recommend you to use either --log-basename or specify a filename to ensure that replication doesn't stop if the real hostname of the computer changes.
--log-bin-index=nameFile that holds the names for last binary log files.
--log-bin-trust-function-creatorsIf equal to 0 (the default), then when --log-bin is used, creation of a stored function (or trigger) is allowed only to users having the SUPER privilege, and only if this stored function (trigger) may not break binary logging.Note that if ALL connections to this server ALWAYS use row-based binary logging, the security issues do not exist and the binary logging cannot break, so you can safely set this to 1.
--log-bin-trust-routine-creators(deprecated) Use log-bin-trust-function-creators.
--master-host=nameMaster hostname or IP address for replication. If not set, the slave 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=nameThe location and name of the file that remembers the master and where the I/O replication thread is in the master's binlogs.
--master-password=nameThe password the slave thread will authenticate with when connecting to the master. If not set, an empty password is assumed. The value in master.info will take precedence if it can be read.
--master-port=# 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=The number of tries the slave will make to connect to the master before giving up.
--master-sslEnable the slave to connect to the master using SSL.
--master-ssl-ca[=name]Master SSL CA file. Only applies if you have enabled master-ssl.
--master-ssl-capath[=name]Master SSL CA path. Only applies if you have enabled master-ssl.
--master-ssl-cert[=name]Master SSL certificate file name. Only applies if you have enabled master-ssl.
--master-ssl-cipher[=name]Master SSL cipher. Only applies if you have enabled master-ssl.
--master-ssl-key[=name]Master SSL keyfile name. Only applies if you have enabled master-ssl.
--master-user=nameThe username the slave thread will use for authentication when connecting to the master. The user must have FILE privilege. If the master 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=# Option used by mysql-test for debugging and testing of replication.
--max-relay-log-size=# If non-zero: relay log will be rotated automatically when the size exceeds this value; if zero (the default): when the size exceeds max_binlog_size. 0 excepted, the minimum value for this variable is 4096.
--relay-log=nameThe location and name to use for relay logs.
--relay-log-index=nameThe location and name to use for the file that keeps a list of the last relay logs.
--relay-log-info-file=nameThe location and name of the file that remembers where the SQL replication thread is in the relay logs.
--relay_log_purge0 = do not purge relay logs. 1 = purge them as soon as they are no more needed.
--relay_log_space_limit=# Maximum space to use for all relay logs.
--replicate-annotate-rows-eventsTells the slave to reproduce Annotate_rows events recieved from the master in its own binary log. This option is sensible only when used in tandem with the log-slave-updates option.MariaDB 5.3
--replicate-do-db=nameTells the slave thread to restrict replication to the specified database. To specify more than one database, use the directive multiple times, once for each database. Note that this will only work if you do not use cross-database queries such as UPDATE some_db.some_table SET foo='bar' while having selected a different or no database. If you need cross database updates to work, make sure you have 3.23.28 or later, and use replicate-wild-do-table=db_name.%.

As of MariaDB 5.5.22 this variable is dynamic.
--replicate-do-table=nameTells the slave thread to restrict replication to the specified table. To specify more than one table, use the directive multiple times, once for each table. This will work for cross-database updates, in contrast to replicate-do-db.

As of MariaDB 5.5.22 this variable is dynamic.
--replicate-events-marked-for-skipThis option tells the slave whether to replicate events that are marked with the @@skip_replication flag. See Selectively skipping replication of binlog events for details.MariaDB 5.5.21
--replicate-ignore-db=nameTells the slave thread to not replicate to the specified database. To specify more than one database to ignore, use the directive multiple times, once for each database. This option will not work if you use cross database updates. If you need cross database updates to work, make sure you have 3.23.28 or later, and use replicate-wild-ignore-table=db_name.%.

As of MariaDB 5.5.22 this variable is dynamic.
--replicate-ignore-table=nameTells the slave thread to not replicate to the specified table. To specify more than one table to ignore, use the directive multiple times, once for each table. This will work for cross-database updates, in contrast to replicate-ignore-db.

As of MariaDB 5.5.22 this variable is dynamic.
--replicate-rewrite-db=nameUpdates to a database with a different name than the original. Example: replicate-rewrite-db=master_db_name->slave_db_name.
--replicate-same-server-idIn 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.
--replicate-wild-do-table=nameTells the slave thread to restrict replication to the tables that match the specified wildcard pattern. To specify more than one table, use the directive multiple times, once for each table. This will work for cross-database updates. Example: replicate-wild-do-table=foo%.bar% will replicate only updates to tables in all databases that start with foo and whose table names start with bar.

As of MariaDB 5.5.22 this variable is dynamic.
--replicate-wild-ignore-table=nameTells the slave thread to not replicate to the tables that match the given wildcard pattern. To specify more than one table to ignore, use the directive multiple times, once for each table. This will work for cross-database updates. Example: replicate-wild-ignore-table=foo%.bar% will not do updates to tables in databases that start with foo and whose table names start with bar.

As of MariaDB 5.5.22 this variable is dynamic.
--report-host=nameHostname or IP of the slave to be reported to the master during slave registration. Will appear in the output of SHOW SLAVE HOSTS. Leave unset if you do not want the slave to register itself with the master. Note that it is not sufficient for the master to simply read the IP of the slave from the socket once the slave connects. Due to NAT and other routing issues, that IP may not be valid for connecting to the slave from the master or other hosts.
--report-password=nameUndocumented.
--report-port=# Port for connecting to slave reported to the master during slave registration. Set it only if the slave is listening on a non-default port or if you have a special tunnel from the master or other clients to the slave. If not sure, leave this option unset.
--report-user=nameUndocumented.
--rpl-recovery-rank=# Undocumented and not used.
--server-id=# Uniquely identifies the server instance in the community of replication partners.
--skip-replicationWhen this variable is set to true, events are logged into the binlog with the flag @@skip_replication set. Such events will not be replicated by slaves that run with --replicate-events-marked-for-skip set different from its default of REPLICATE. See Selectively skipping replication of binlog events for details.MariaDB 5.5.21
--slave-exec-mode=nameModes for how replication events should be executed. Legal values are STRICT (default) and IDEMPOTENT. In IDEMPOTENT mode, replication will not stop for operations that are idempotent. In STRICT mode, replication will stop on any unexpected difference between the master and the slave.
--slave-load-tmpdir=nameThe location where the slave should put its temporary files when replicating a LOAD DATA INFILE command.
--slave-skip-errors=nameTells the slave thread to continue replication when a query event returns an error from the provided list.
--slave_compressed_protocolUse compression on master/slave protocol.
--slave_net_timeout=# Number of seconds to wait for more data from a master/slave connection before aborting the read.
--slave_transaction_retries=# Number of times the slave SQL thread will retry a transaction in case it failed with a deadlock or elapsed lock wait timeout, before giving up and stopping.
--sporadic-binlog-dump-failOption used by mysql-test for debugging and testing of replication.
--sysdate-is-nowNon-default option to alias SYSDATE() to NOW() to make it safe-replicable. Since 5.0, SYSDATE() returns a `dynamic' value different for different invocations, even within the same statement.

Optimizer options

OptionDescription
--big-tablesAllow big result sets by saving all temporary sets on file (solves most 'table full' errors).
--bulk_insert_buffer_size=# Size of tree cache used in bulk insert optimization. Note that this is a limit per thread.
--join_buffer_size=# The size of the buffer that is used for full joins.
--max_heap_table_size=# Don't allow creation of heap tables bigger than this.
--max_join_size=# Joins that are probably going to read more than max_join_size records return an error.
--max_sort_length=# 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).
--optimizer_prune_level[=#]Controls the heuristic(s) applied during query optimization to prune less-promising partial plans from the optimizer search space. Meaning: 0 - do not apply any heuristic, thus perform exhaustive search; 1 - prune plans based on number of retrieved rows.
--optimizer_search_depth[=#]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).
--optimizer_switch=nameoptimizer_switch=option=val[,option=val...], where option={index_merge, index_merge_union, index_merge_sort_union, index_merge_intersection} and val={on, off, default}.
--query_alloc_block_size=# Allocation block size for extra blocks (after query_prealloc_size is exhausted) during query parsing and execution.
--query_prealloc_size=# Persistent buffer for query parsing and execution. This is allocated at connection start and freed on disconnect.
--range_alloc_block_size=# Allocation block size for storing ranges during optimization.
--read_buffer_size=# 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.
--record_buffer=# Alias for read_buffer_size. This variable is deprecated and will be removed in a future release.
--table_cache=# Deprecated; use --table_open_cache instead.
--table_definition_cache=# The number of cached table definitions.
--table_open_cache=# The number of cached open tables.
--tmp_table_size=# If an internal in-memory temporary table exceeds this size, MySQL will automatically convert it to an on-disk MyISAM/Aria table.

Options when debugging mysqld

OptionDescriptionIntroduced
--consoleWrite error output on screen; don't remove the console window on windows.
--core-fileWrite core on errors.
-#, --debug[=name]Use logging trough the DBUG library. Just using --debug will write a trafe of what mysqld is doing to /tmp/mysqld.trace.
--debug-assert-if-crashed-tableDo an assert in handler::print_error() if we get a crashed table.
-debug-crc-break=# Call my_debug_put_break_here() if crc matches this number (for debug).
--debug-flushDefault debug log with flush after write.
--debug-sync-timeout[=#]Enable the debug sync facility and optionally specify a default wait timeout in seconds. A zero value keeps the facility disabled.
--gdbSet up signals usable for debugging.
--sync-sys Enable/disable system sync calls. Syncs should only be turned off (--disable-sync-sys) when running tests or debugging!
--thread-alarmEnable/disable system thread alarm calls. Should only be turned off (--disable-thread-alarm) when running tests or debugging!MariaDB 5.3
--binlog_dbug_fsync_sleep=# If this is set different from zero, then it is 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 fsync().MariaDB 5.3

Options for MyISAM

OptionDescription
--concurrent-insert[=#]Use concurrent insert with MyISAM. Disable with --concurrent-insert=0.
--delay-key-write-for-all-tablesDon't flush key buffers between writes for any MyISAM table. (Deprecated option, use --delay-key-write=all instead.)
--delayed_insert_limit=# After inserting delayed_insert_limit rows, the INSERT DELAYED handler will check if there are any SELECT statements pending. If so, it allows these to execute before continuing.
--delayed_insert_timeout=# How long a INSERT DELAYED thread should wait for INSERT statements before terminating.
--delayed_queue_size=# What size queue (in rows) should be allocated for handling INSERT DELAYED. If the queue becomes full, any client that does INSERT DELAYED will wait until there is room in the queue again.
--external-lockingUse system (external) locking (disabled by default). With this option enabled you can run myisamchk to test (not repair) tables while the MySQL server is running. Disable with --skip-external-locking.
--keep_files_on_createDon't overwrite stale .MYD and .MYI even if no directory is specified.
--key_buffer_size=# The size of the buffer used for index blocks for MyISAM tables. Increase this to get better index handling (for all reads and multiple writes) to as much as you can afford; 1GB on a 4GB machine that mainly runs MySQL is quite common.
--key_cache_age_threshold=# This characterizes the number of hits a hot block has to be untouched until it is considered aged enough to be downgraded to a warm block. This specifies the percentage ratio of that number of hits to the total number of blocks in key cache.
--key_cache_block_size=# The default size of key cache blocks.
--key_cache_division_limit=# The minimum percentage of warm blocks in key cache.
--log-isam[=name]Log all MyISAM changes to file.
--myisam-recover[=name]Syntax: myisam-recover[=option[,option...]], where option can be DEFAULT, BACKUP, BACKUP_ALL (new in 5.1.51) FORCE or QUICK.
--myisam_block_size=# Block size to be used for MyISAM index pages.
--myisam_data_pointer_size=# Default pointer size to be used for MyISAM tables.
--myisam_max_extra_sort_file_size=# This is a deprecated option that does nothing anymore. It will be removed in MySQL 5.6
--myisam_max_sort_file_size=# Don't use the fast sort index method to created index if the temporary file would get bigger than this.
--myisam_mmap_size=# Can be used to restrict the total memory used for memory mmaping of myisam files
--myisam_repair_threads=# Specifies whether several threads should be used when repairing MyISAM tables. For values > 1, one thread is used per index. The value of 1 disables parallel repair.
--myisam_sort_buffer_size=# The buffer that is allocated when sorting the index when doing a REPAIR or when creating indexes with CREATE INDEX or ALTER TABLE.
--myisam_stats_method=nameSpecifies how MyISAM index statistics collection code should threat NULLs. Possible values of name are "nulls_unequal" (default behavior for 4.1/5.0), "nulls_equal" (emulate 4.0 behavior), and "nulls_ignored".
--myisam_use_mmapUse memory mapping for reading and writing MyISAM tables.

Options for InnoDB

OptionDefault ValueDescription
--innodbONThis variable controls whether or not to load the InnoDB storage engine. Possible Values are ON, OFF, or FORCE.
--innodb-adaptive-checkpointestimate
--innodb-adaptive-flushingFALSESet whether to use adaptive flushing to determine when to flush dirty buffer cache pages.
--innodb-adaptive-hash-indexTRUEUsed to enable or disable InnoDB adaptive hash indexes.
--innodb-additional-mem-pool-size8388608The size (in bytes) of the memory pool InnoDB uses to store internal data structures (including data dictionary information). Possible values are between 2097152 and 4294967295.
--innodb-auto-lru-dump0
--innodb-autoextend-increment8Increment size (in MB) for extending the size of an auto-extended shared tablespace file. Does not affect per-table tablespace files created if you use --innodb_file_per_table=1.
--innodb-autoinc-lock-mode1Sets the lock mode to use when generating auto-increment values. Possible values are 0 (traditional), 1 (consecutive), or 2 (interleaved).
--innodb-buffer-pool-pagesON
--innodb-buffer-pool-pages-blobON
--innodb-buffer-pool-pages-indexON
--innodb-buffer-pool-shm-checksumTRUE
--innodb-buffer-pool-shm-key0
--innodb-buffer-pool-size134217728The size (in bytes) of the InnoDB memory buffer. Allowed values on 32-bit systems range from 1048576 to 232-1. On dedicated database servers this value can normally be safely set to 80% of physical memory, but may need to be reduced depending on your individual setup.
--innodb-change-bufferinginserts
--innodb-checkpoint-age-target0
--innodb-checksumsTRUEWhether to ensure extra fault tolerance with checksums.
--innodb-cmpON
--innodb-cmp-resetON
--innodb-cmpmemON
--innodb-cmpmem-resetON
--innodb-commit-concurrency0Set the number of threads which can commit at the same time. '0' permits any number of transactions to commit at the same time.
--innodb-concurrency-tickets500The number of free "tickets" a thread is given which it can use to enter and leave InnoDB without being subject to a concurrency check or queuing.
--innodb-data-file-path(No default value)The path to individual data files.
--innodb-data-home-dir(No default value)The common part of the directory path to data files.
--innodb-dict-size-limit0
--innodb-doublewriteTRUE
--innodb-doublewrite-file(No default value)
--innodb-enable-unsafe-group-commit0
--innodb-expand-import0
--innodb-extra-rsegments0
--innodb-extra-undoslotsFALSE
--innodb-fast-checksumFALSE
--innodb-fast-recoveryFALSE
--innodb-fast-shutdown1Possible values are '0' (slow shutdown with a full purge and insert buffer merge before shutdown), '1' (fast shutdown without the purge and merge), or '2' (flush logs and exit hard, as if MariaDB had crashed). Only use innodb_fast_shutdown=2 in emergency or troubleshooting situations (e.g. if data is at risk of corruption and you need to shutdown as fast as possible).
--innodb-file-formatAntelopeThe file format to use for new InnoDB tables. Possible values are 'Antelope' or 'Barracuda'.
--innodb-file-format-checkBarracuda
--innodb-file-io-threads4
--innodb-file-per-tableFALSEIf disabled, InnoDB will create tables in the system tablespace. If enabled, InnoDB will create each new table with its own .ibd file.
--innodb-flush-log-at-trx-commit1Possible values are '0' (write the log buffer to the log file once per second and flush to disk but do nothing at a transaction commit), '1' (write the log buffer to the log file and flush to disk at each transaction commit), or '2' (write the log buffer to the log file at each commit but flush to disk once per second). Option '1' is required for full ACID compliance.
--innodb-flush-log-at-trx-commit-session3
--innodb-flush-method(No default value)Possible values are 'O_DSYNC', or 'O_DIRECT'. This variable is only useful on Linux and Unix. The flush method is always 'async_unbuffered' on Windows.
--innodb-flush-neighbor-pages1
--innodb-force-recovery0Possible values are '0', '1', '2', '3', '4', '5', or '6'.
--innodb-ibuf-accel-rate100
--innodb-ibuf-active-contract1
--innodb-ibuf-max-size9223372036854775807
--innodb-index-statsON
--innodb-io-capacity200On 32-bit systems, possible values range from 100 to 232-1 (2**32-1). On 64-bit systems, possible values range from 100 to 264-1 (2**64-1). Set this value to the approximate number if I/O operations your system can perform per second.
--innodb-lazy-drop-table0
--innodb-lock-wait-timeout50The amount of time and InnoDB transaction will wait (in seconds) before it gives up. Possible values range from '1' to '1073741824'.
--innodb-lock-waitsON
--innodb-locksON
--innodb-locks-unsafe-for-binlogFALSE
--innodb-log-block-size512
--innodb-log-buffer-size8388608The size (in bytes) of the buffer used for writing log files on disk. Possible values range from '262144' to '4294967295'.
--innodb-log-file-size5242880The size (in bytes) of each log file in a log group. Possible values range from '108576' to '4294967295'.
--innodb-log-files-in-group2The number of log files in the log group. Allowed values range from '2' to '100'.
--innodb-log-group-home-dir(No default value)Directory path to the InnoDB redo log files. The default (if no value is set) is to put the log files in the data directory.
--innodb-max-dirty-pages-pct75Possible values range from '0' to '99'. InnoDB will try to write pages from the buffer pool so that the percentage of dirty (unwritten) pages does not exceed this value.
--innodb-max-purge-lag0How to delay INSERT, UPDATE, and DELETE operations. '0' means "no delays".
--innodb-mirrored-log-groups1The number of identical copies of log groups to keep. Should be '1'.
--innodb-old-blocks-pct37The percentage of the buffer pool to use for the old block sublist. Possible values range from '5' to '95'.
--innodb-old-blocks-time0How long (in milliseconds) an inserted block must stay in the old sublist after its first access before it can be moved to the new sublist. '0' means "no delay". Possible values range from '0' to '232-1' (2**32-1).
--innodb-open-files300The max number of .ibd files InnoDB can keep open simultaneously. Allowed values range from '10' to '4294967295'. Only applies if you use multiple tablespaces.
--innodb-overwrite-relay-log-infoFALSE
--innodb-page-size16384
--innodb-pass-corrupt-table0
--innodb-read-aheadlinear
--innodb-read-ahead-threshold56Allowed values range from '0' to '64'. Default of '56' means that InnoDB must read at least 56 pages sequentially from an extent to initiate an asynchronous read for the following extent.
--innodb-read-io-threads4The number of I/O threads for InnoDB read operations. Possible values range from '1' to '64'.
--innodb-recovery-statsFALSE
--innodb-replication-delay0Replication thread delay (in milliseconds) on a slave server if innodb_thread_concurrency is reached. Allowed values range from '0' (no delay) to '4294967295'.
--innodb-rollback-on-timeoutFALSE
--innodb-rsegON
--innodb-show-locks-held10
--innodb-show-verbose-locks0
--innodb-spin-wait-delay6
--innodb-stats-auto-update1
--innodb-stats-methodnulls_equalDetermines how the server treats NULL values when collecting statistics regarding index value distribution for InnoDB tables. Possible values are 'nulls_equal', 'nulls_unequal', or 'nulls_ignored'.
--innodb-stats-on-metadataTRUEControls whether or not to update statistics during metadata statements (e.g. SHOW TABLE STATUS or SHOW INDEX) or when accessing the INFORMATION_SCHEMA.TABLES or INFORMATION_SCHEMA.STATISTICS tables.
--innodb-stats-sample-pages8The number of index pages to sample when calculating index distribution statistics. Possible values range from '1' to '264-1' (2**64-1).
--innodb-stats-update-need-lock1
--innodb-status-fileFALSE
--innodb-strict-modeFALSEControls whether or not to return errors instead of warnings for certain conditions. This option is analogous to strict SQL mode.
--innodb-support-xaTRUEControls whether of not to use a two-phase commit in XA transactions (this causes an extra disk flush for transaction preparation).
--innodb-sync-spin-loops30The number of times a thread will wait for an InnoDB mutex to be freed before the thread is suspended. Possible values range from '0' to '4294967295'.
--innodb-sys-indexesON
--innodb-sys-statsON
--innodb-sys-tablesON
--innodb-table-locksTRUE
--innodb-table-statsON
--innodb-thread-concurrency0How many concurrent operating system threads InnoDB will try and stay at or below. Possible values range from '0' (no concurrency checking) to '1000'.
--innodb-thread-concurrency-timer-basedFALSE
--innodb-thread-sleep-delay10000
--innodb-trxON
--innodb-use-purge-thread1
--innodb-use-sys-mallocTRUEIf TRUE, InnoDB will use the operating system's memory allocator. If 'FALSE', InnoDB will use its own.
--innodb-use-sys-stats-tableFALSE
--innodb-write-io-threads4The number of I/O threads for write operations. Possible values range from '1' to '64'.

Options for PBXT

The following system variables are available for controlling the behavior of the PBXT engine.

System variables can be set in the my.cnf file or on the mysqld command line. Variables that can be set dynamically can be set using the SET GLOBAL command which is sent to the server. System variables that can be set dynamically are specified as such below.

Variables that specify a number of bytes may include a unit indication after the value. For example: 100KB, 64MB, etc. There should be no space between the number and the unit. Units are case insensitive (KB = Kb = kb). If no unit is specified then bytes is assumed. The recognized units are:

  • KB (or K) - Kilobyte, 1024 bytes
  • MB (or M) - Megabyte, 1024 KB
  • GB (or G) - Gigabyte, 1024 MB
  • TB (or T) - Terabyte, 1024 GB
  • PB (or P) - Petabyte, 1024 TB

Variables which use this type of value are: pbxt_index_cache_size, pbxt_record_cache_size, pbxt_log_cache_size, pbxt_log_file_threshold, pbxt_checkpoint_frequency, pbxt_data_log_threshold, pbxt_log_buffer_size, pbxt_data_file_grow_size, and pbxt_row_file_grow_size.

OptionDefault ValueDescription
--pbxtON
--pbxt-max-threads0
--pbxt-statisticsON

PBXT Cache Memory Variables

OptionDefault ValueDescription
--pbxt-index-cache-size32MBThe amount of memory allocated to the index cache. The memory allocated here is used only for caching index pages (.xti files).
--pbxt-record-cache-size32MBThis is the amount of memory allocated to the record cache used to cache table data. This memory is used to cache changes to the handle data (.xtd) and row index (.xtr) files.
--pbxt-log-cache-size16MBThe amount of memory allocated to the transaction log cache used to cache on transaction log data (xlog-*.xt files).

PBXT Transaction Manager Variables

OptionDefault ValueDescription
--pbxt-log-file-threshold32MBThe size of a transaction log file (xlog-*.xt files) before "rollover", and a new log file is created.
--pbxt-transaction-buffer-size1MBThe size of the global transaction log buffer (the engine allocates 2 buffers of this size). Data to be written to a transaction log file is first written to the transaction log buffer. Since the buffer is flushed on transaction commit, it only makes sense to use a large transaction log buffer if you have longer running transactions, or many transaction running in parallel.
--pbxt-checkpoint-frequency24MBThe amount of data written to the transaction log before a checkpoint is performed.
--pbxt-sweeper-priority0Determines the priority of the background Sweeper thread. Possible values are '0' (Low), '1' (Normal), or '2' (High). The Sweeper is responsible for removing deleted records and index entries (deleted records also result from UPDATE statements). If many old deleted records accumulate search operations become slower. Therefore it may improve performance to increase the priority of the Sweeper on a machine with 4 or more cores.
--pbxt-auto-increment-mode0The parameter determines how PBXT manages auto-increment values. Possible values are '0' (MySQL standard) or '1' (Previous IDs are never re-used).

In the standard 'MySQL' mode it is possible that an auto-increment value is re-issued. This occurs when the maximum auto-increment value is deleted, and then MariaDB is restarted. This occurs because the next auto-increment value to be issued is determined at startup by retrieving the current maximum auto-increment value from the table.

In mode 1, auto-increment values are never re-issued because PBXT automatically incrementing the table level AUTO_INCREMENT table option. The AUTO_INCREMENT table is incremented in steps of 100. Since this requires the table file to be flushed to disk, this can influence performance.
--pbxt-flush-log-at-trx-commit1This variable specifies the durability of recently committed transactions. By reducing the durability, the speed of write operations can be increased.

'0' - Lowest durability, the transaction log is not written or flushed on transaction commit. In this case it is possible to loose transactions if the server executable crashes.
'1' - Full-durability, the transaction log is written and flushed on every transaction commit.
'2' - Medium durabilty, the transaction log is written, but not flushed on transaction commit. In this case it is possible to loose transactions of the server machine crashes (for example, a power failer).

In all cases, the transaction log is flushed at least once every second. This means that it is only every possible to loose database changes that occurred within the last second.
--pbxt-log-file-count3The number of transaction log files on disk before logs that are no longer required are deleted, default value is 3. The number of transaction logs on disk may exceed this number if the logs are still being read.

If a transaction log has been read (i.e. the log is offline), it will be recycled for writing again, unless it must be deleted because the number of logs on disk exceeds this threshold. Recycling logs is an optimization because the writing a pre-allocated file is faster then writing to the end of a file.

Note: an exception to this rule is Mac OS X. On Mac OS X old log files are not recycled because writing pre-allocated file is slower than writing to the end of file.
--pbxt-offline-log-function0This variable determines what happens to a transaction log when it is offline. A log is offline if PBXT is no longer reading or writing to the log. There are 3 possibilities:

'0' - Recycle log (default). This means the log is renamed and written again.
'1' - Delete log (default on Mac OS X).
'2' - Keep log. The logs can be used to repeat all operations that were applied to the database.
--pbxt-support-xaTRUEThis variable determines if XA (2-phase commit) support is enabled.

PBXT Data Log Variables

PBXT stores part of the database in the data logs. This is mostly data from rows containing long VARCHAR fields or BLOB data. The data logs are managed by the "compactor" thread. When a record is deleted from a data log, the data is marked as garbage. When the total garbage in a data log reaches a certain threshold, the compactor thread compacts the data log by copying the valid data to a new data log, and deleting the old data log.

The following system variables control the way data logs are managed.

OptionDefault ValueDescription
--pbxt-data-log-threshold64MBThe maximum size of a data log file. PBXT can create a maximum of 32000 data logs, which are used by all tables. So the value of this variable can be increased to increase the total amount of data that can be stored in the database.
--pbxt-log-buffer-size256MBThis is the size of the buffer used when writing a data log. The engine allocates one buffer per thread, but only if the thread is required to write a data log.
--pbxt-garbage-threshold50The percentage of garbage in a data log file before it is compacted. This is a value between 1 and 99.

PBXT File Grow Variables

The handle data and row index files are grown in chunks.

OptionDefault ValueDescription
--pbxt-data-file-grow-size2MBThe grow size of the handle data (.xtd) files.
--pbxt-row-file-grow-size256KBThe grow size of the row index (.xtr) files.

Other Options

OptionDescriptionIntroduced
--allow-suspicious-udfsAllows use of UDFs consisting of only one symbol xxx() without corresponding xxx_init() or xxx_deinit(). That also means that one can load any function from any library, for example exit() from libc.so
--automatic-sp-privilegesCreating and dropping stored procedures alters ACLs. Disable with '--skip-automatic-sp-privileges'.
--back_log=# The number of outstanding connection requests MySQL can have. This comes into play when the main MySQL thread gets very many connection requests in a very short time.
-b, --basedir=namePath to installation directory. All paths are usually resolved relative to this.
--bind-address=nameIP address to bind to
--bootstrapUsed by mysql installation scripts.
--character-set-client-handshakeDon't ignore client side character set value sent during handshake.
--character-set-filesystem=nameSet the filesystem character set.
-C, --character-set-server=nameSet the default character set.
--character-sets-dir=nameDirectory where character sets are.
-r, --chroot=nameChroot mysqld daemon during startup.
--collation-server=nameSet the default collation.
--completion-type=# Default completion type
--connect_timeout=# The number of seconds the mysqld server is waiting for a connect packet before responding with 'Bad handshake'.
-h, --datadir=namePath to the database root.
--datetime_format=nameThe DATETIME/TIMESTAMP format (for future).
--date_format=nameThe DATE format (for future).
--deadlock-search-depth-long=# Long search depth for the two-step deadlock detection
--deadlock-search-depth-short=# Short search depth for the two-step deadlock detection
--deadlock-timeout-long=# Long timeout for the two-step deadlock detection (in microseconds)
--deadlock-timeout-short=# Short timeout for the two-step deadlock detection (in microseconds)
--default-character-set=nameSet the default character set (deprecated option, use --character-set-server instead).
--default-collation=nameSet the default collation (deprecated option, use --collation-server instead).
--default-storage-engine=nameSet the default storage engine (table type) for tables.
--default-table-type=name(deprecated) Use '--default-storage-engine'.
--default-time-zone=nameSet the default time zone.
--default_week_format=# The default week format used by WEEK() functions.
--delay-key-write[=name]Type of DELAY_KEY_WRITE.
--des-key-file=nameLoad keys for des_encrypt() and des_encrypt from given file.
--div_precision_increment=# Precision of the result of '/' operator will be increased on that value.
--enable-lockingDeprecated option, use --external-locking instead.
--engine-condition-pushdownPush supported query conditions to the storage engine.
--event-scheduler[=name]Enable/disable the event scheduler.
-T, --exit-info[=#]Used for debugging. Use at your own risk.
--expire_logs_days=# If non-zero, binary logs will be purged after expire_logs_days days; possible purges happen at startup and at binary log rotation.
--extra-max-connections=# The number of connections on 'extra-port.
--extra-port=# Extra port number to use for tcp-connections in a one-thread-per-connection manner. 0 means don't use another port
--flushFlush tables to disk between SQL commands.
--flush_time=# A dedicated thread is created to flush all tables at the given interval.
--ft_boolean_syntax=nameList of operators for MATCH ... AGAINST ( ... IN BOOLEAN MODE).
--ft_max_word_len=# The maximum length of the word to be included in a FULLTEXT index. Note: FULLTEXT indexes must be rebuilt after changing this variable.
--ft_min_word_len=# The minimum length of the word to be included in a FULLTEXT index. Note: FULLTEXT indexes must be rebuilt after changing this variable.
--ft_query_expansion_limit=# Number of best matches to use for query expansion.
--ft_stopword_file=nameUse stopwords from this file instead of built-in list.
--general_logEnable/disable general log.
--general_log_file=nameLog connections and queries to given file.
--group_concat_max_len=# The maximum length of the result of function group_concat.
-?, --helpDisplay this help and exit.
--ignore-builtin-innodbDisable initialization of builtin InnoDB plugin.
--ignore-db-dirTells the server that this directory can never be a database. That means two things - firstly it is ignored by the SHOW DATABASES command and INFORMATION_SCHEMA tables. And secondly, USE, CREATE DATABASE and SELECT statements will return an error if the database from the ignored list specified. Use this option several times if you need to ignore more than one directory. To make the list empty set the void value to the option as --ignore-db-dir=. Corresponding read-only variable @@ignore_db_dirs shows the current list. New in 5.3.9.
--init-connect=nameCommand(s) that are executed for each new connection that has not the SUPER USER privilege.
--init-file=nameRead SQL commands from this file at startup.
--interactive_timeout=# The number of seconds the server waits for activity on an interactive connection before closing it.
-L, --language=nameClient error messages in given language. May be given as a full path. Depricated option in 5.5. One should use --lc-messages and --lc-messages-dir instead.
--large-pagesEnable support for large pages. Disable with '--skip-large-pages'.
--lc-messages=nameSet the language used for the error messages. Default en_us.MariaDB 5.5
--lc-messages-dir=nameDirectory where error message directories are (czech, english etc)MariaDB 5.5
--lc-time-names=nameSet the language used for the month names and the days of the week.
--local-infileEnable/disable LOAD DATA LOCAL INFILE (takes values 1 or 0).
-l, --log[=name]Log connections and queries to file (deprecated option, use --general_log/--general_log_file instead).
--log-error[=name]Error log file.
-0, --log-long-formatLog some extra information to update log. Please note that this option is deprecated; see --log-short-format option.
--log-output[=name]Syntax: log-output[=value[,value...]], where "value" could be TABLE, FILE or NONE.
--log-queries-not-using-indexesLog queries that are executed without benefit of any index to the slow log if it is open.
--log-short-formatDon't log extra information to update and slow-query logs.
--log-slave-updatesTells the slave to log the updates from the slave thread to the binary log. You will need to turn it on if you plan to daisy-chain the slaves.
--log-slow-admin-statementsLog slow OPTIMIZE, ANALYZE, ALTER and other administrative statements to the slow log if it is open.
--log-slow-file=nameLog slow queries to given log file. Defaults logging to hostname-slow.log
--log-slow-filter=nameLog only the queries that followed certain execution plan. Multiple flags allowed in a comma-separated string. [admin, filesort, filesort_on_disk, full_join, full_scan, query_cache, query_cache_miss, tmp_table, tmp_table_on_disk]. Sets log-slow-admin-command to ON
--log-slow-queries[=name]Log slow queries to a table or log file. Defaults logging to table mysql.slow_log or hostname-slow.log if --log-output=file is used. Must be enabled to activate other slow log options. (deprecated option, use --slow_query_log/--slow_query_log_file instead)
--log-slow-rate_limit=# If set, only write to slow log every 'log_slow_rate_limit' query (use this to reduce output on slow query log)
--log-slow-slave-statementsLog slow statements executed by slave thread to the slow log if it is open.
--log-slow-time=# Log all queries that have taken more than long_query_time seconds to execute to file. The argument will be treated as a decimal value with microsecond precission.
--log-slow-verbosity=nameChoose how verbose the messages to your slow log will be. Multiple flags allowed in a comma-separated string. [query_plan, innodb]
--log-tc=namePath to transaction coordinator log (used for transactions that affect more than one storage engine, when binary log is disabled).
--log-tc-size=# Size of transaction coordinator log.
--log-update[=name]The update log is deprecated since version 5.0, is replaced by the binary log and this option just turns on --log-bin instead.
-W, --log-warnings[=#]Log some not critical warnings to the log file. See for details.
--long_query_time=# Log all queries that have taken more than long_query_time seconds to execute. The argument will be treated as a decimal value with microsecond precision.
--low-priority-updatesINSERT/DELETE/UPDATE has lower priority than selects.
--lower_case_table_names[=#]If set to 1, table names are stored in lowercase on disk and table names will be case-insensitive. Should be set to 2 if you are using a case-insensitive file system.
--master-connect-retry=# The number of seconds the slave thread will sleep before retrying to connect to the master, in case the master goes down or the connection is lost.
--max_allowed_packet=# The maximum packet length to send to or receive from server.
--max_binlog_cache_size=# Can be used to restrict the total size used to cache a multi-transaction query.
--max_binlog_size=# Binary log will be rotated automatically when the size exceeds this value. Will also apply to relay logs if max_relay_log_size is 0. The minimum value for this variable is 4096.
--max_connections=# The number of simultaneous clients allowed.
--max_connect_errors=# If there is more than this number of interrupted connections from a host this host will be blocked from further connections.
--max_delayed_threads=# Don't start more than this number of threads to handle INSERT DELAYED statements. If set to zero, which means INSERT DELAYED is not used.
--max_error_count=# Max number of errors/warnings to store for a statement.
--max_length_for_sort_data=# Max number of bytes in sorted records.
--max_prepared_stmt_count=# Maximum number of prepared statements in the server.
--max_sp_recursion_depth[=#]Maximum stored procedure recursion depth. (discussed with docs).
--max_tmp_tables=# Maximum number of temporary tables a client can keep open at a time.
--max_user_connections=# The maximum number of active connections for a single user (0 = no limit).
--max_write_lock_count=# After this many write locks, allow some read locks to run in between.
--memlockLock mysqld in memory.
--min_examined_row_limit=# Don't log queries which examine less than min_examined_row_limit rows to file.
--multi_range_count=# Number of key ranges to request at once.
--ndb-use-copying-alter-tableForce ndbcluster to always copy tables at alter table (should only be used if on-line alter table fails).
--net_buffer_length=# Buffer length for TCP/IP and socket communication.
--net_read_timeout=# Number of seconds to wait for more data from a connection before aborting the read.
--net_retry_count=# If a read on a communication port is interrupted, retry this many times before giving up.
--net_write_timeout=# Number of seconds to wait for a block to be written to a connection before aborting the write.
--one-thread(Deprecated): Only use one thread (for debugging under Linux). Use thread-handling=no-threads instead.
--open_files_limit=# If this is not 0, then mysqld will use this value to reserve file descriptors to use with setrlimit(). If this value is 0 then mysqld will reserve max_connections*5 or max_connections + table_cache*2 (whichever is larger) number of files.
--pid-file=namePid file used by safe_mysqld.
--plugin-load=nameOptional semicolon-separated list of plugins to load, where each plugin is identified as name=library, where name is the plugin name and library is the plugin library in plugin_dir.
--plugin_dir=nameDirectory for plugins.
-P, --port=# Port number to use for connection or 0 for default to, in order of preference, my.cnf, $MYSQL_TCP_PORT, /etc/services, built-in default (3306).
--port-open-timeout=# Maximum time in seconds to wait for the port to become free. (Default: No wait).
--preload_buffer_size=# The size of the buffer that is allocated when preloading indexes.
--profiling_history_size=# Limit of query profiling memory.
--progress_report_time=# Seconds between sending progress reports to the client for slow commands. Set to 0 to disable progress. New in 5.3
--query_cache_limit=# Don't cache results that are bigger than this.
--query_cache_min_res_unit=# Minimal size of unit in which space for results is allocated (last unit will be trimmed after writing all result data).
--query_cache_size=# The memory allocated to store results from old queries.
--query_cache_type=# 0 = OFF = Don't cache or retrieve results. 1 = ON = Cache all results except SELECT SQL_NO_CACHE ... queries. 2 = DEMAND = Cache only SELECT SQL_CACHE ... queries.
--query_cache_wlock_invalidateInvalidate queries in query cache on LOCK for write.
--read_onlyMake all non-temporary tables read-only, with the exception of replication (slave) threads and users with the SUPER privilege.
--read_rnd_buffer_size=# When reading rows in sorted order after a sort, the rows are read through this buffer to avoid disk seeks. If not set, then it's set to the value of record_buffer.
--safe-show-databaseDeprecated option; use GRANT SHOW DATABASES instead.
--safe-user-createDon't allow new user creation by the user who has no write privileges to the mysql.user table.
--safemalloc-mem-limit=# Simulate memory shortage when compiled with the --with-debug=full option.
--secure-authDisallow authentication for accounts that have old (pre-4.1) passwords.
--secure-file-priv=nameLimit LOAD DATA, SELECT ... OUTFILE, and LOAD_FILE() to files within specified directory.
-O, --set-variable=nameChange the value of a variable. Please note that this option is deprecated; you can set variables directly with '--variable-name=value'.
--show-slave-auth-infoShow user and password in SHOW SLAVE HOSTS on this master.
--skip-grant-tablesStart without grant tables. This gives all users FULL ACCESS to all tables.
--skip-host-cacheDon't cache host names.
--skip-lockingDeprecated option, use --skip-external-locking instead.
--skip-name-resolveDon't resolve hostnames. All hostnames are IP's or 'localhost'.
--skip-networkingDon't allow connection with TCP/IP.
--skip-show-databaseDon't allow 'SHOW DATABASE' commands.
--skip-slave-startIf set, slave is not autostarted.
--skip-stack-traceDon't print a stack trace on failure.
--skip-symlinkDon't allow symlinking of tables. Deprecated option. Use --skip-symbolic-links instead.
--skip-thread-priorityDon't give threads different priorities. Deprecated option.
--slow-query-logEnable/disable slow query log.
--slow_launch_time=# If creating the thread takes longer than this value (in seconds), the Slow_launch_threads counter will be incremented.
--slow_query_log_file=nameLog slow queries to given log file. Defaults logging to hostname-slow.log. Must be enabled to activate other slow log options.
--socket=nameSocket file to use for connection.
--sort_buffer_size=# Each thread that needs to do a sort allocates a buffer of this size.
--sql-bin-update-same=# The update log is deprecated since version 5.0, is replaced by the binary log and this option does nothing anymore.
--sql-mode=nameSyntax: sql-mode=option[,option[,option...]] where option can be one of: REAL_AS_FLOAT, PIPES_AS_CONCAT, ANSI_QUOTES, IGNORE_SPACE, ONLY_FULL_GROUP_BY, NO_UNSIGNED_SUBTRACTION.
--sslEnable SSL for connection (automatically enabled with other flags).Disable with '--skip-ssl'.
--ssl-ca=nameCA file in PEM format (check OpenSSL docs, implies --ssl).
--ssl-capath=nameCA directory (check OpenSSL docs, implies --ssl).
--ssl-cert=nameX509 cert in PEM format (implies --ssl).
--ssl-cipher=nameSSL cipher to use (implies --ssl).
--ssl-key=nameX509 key in PEM format (implies --ssl).
-s, --symbolic-linksEnable symbolic link support.
--sync-binlog=# Synchronously flush binary log to disk after every #th event. Use 0 (default) to disable synchronous flushing.
--sync-frmSync .frm to disk on create. Enabled by default.
--table_lock_wait_timeout=# Timeout in seconds to wait for a table level lock before returning an error. Used only if the connection has active cursors.
--tc-heuristic-recover=nameDecision to use in heuristic recover process. Possible values are COMMIT or ROLLBACK.
--temp-poolUsing this option will cause most temporary files created to use a small set of names, rather than a unique name for each new file.
--test-expect-abortExpect that server aborts with 'abort'; Don't write out server variables on 'abort'. Useful only for test scripts
--test-ignore-wrong-optionsIgnore wrong enums values in command line arguments. Useful only for test scripts
--thread_cache_size=# How many threads we should keep in a cache for reuse.
--thread_concurrency=# Permits the application to give the threads system a hint for the desired number of threads that should be run at the same time.
--thread_handling=nameDefine threads usage for handling queries: one-thread-per-connection, pool-of-threads, or no-threads.
--thread_pool_size=# How many threads we should create to handle query requests in case of 'thread_handling=pool-of-threads'.
--thread_stack=# The stack size for each thread.
--timed_mutexesSpecify whether to time mutexes (only InnoDB mutexes are currently supported).
--time_format=nameThe TIME format (for future).
-t, --tmpdir=namePath for temporary files. Several paths may be specified, separated by a colon (:), in this case they are used in a round-robin fashion.
--transaction-isolation=nameDefault transaction isolation level.
--transaction_alloc_block_size=# Allocation block size for transactions to be stored in binary log.
--transaction_prealloc_size=# Persistent buffer for transactions to be stored in binary log.
--updatable_views_with_limit=# 1 = YES = Don't issue an error message (warning only) if a VIEW without presence of a key of the underlying table is used in queries with a LIMIT clause for updating. 0 = NO = Prohibit update of a VIEW, which does not contain a key of the underlying table and the query uses a LIMIT clause (usually get from GUI tools).
--use-symbolic-linksEnable symbolic link support. Deprecated option; use --symbolic-links instead.
-u, --user=nameRun mysqld daemon as user.
-v, --verboseUsed with --help option for detailed help.
-V, --versionOutput version information and exit.
--wait_timeout=# The number of seconds the server waits for activity on a connection before closing it.
--warnings[=#]Deprecated; use --log-warnings instead.

Log warnings options

What is logged for the different values of log_warnings:

  • log_warnings >= 1
    • Events_schedular info and warnings
    • Access denied errors
    • Connections that was forced to be closed or aborted
    • System signals
    • Wrong usage of --user
    • Failed setrlimit() and mlockall()
    • Changed limits
    • Wrong values of lower_case_table_names and stack_size
    • Wrong values for command line options
    • Start log position and some master information when starting slaves
    • Slave reconnects
    • Killed slaves
    • Error reading relay logs
    • Statements that was unsafe to log as statement based (when BINLOG_FLAG_UNSAFE_STMT_PRINTED is also set)
    • Disabled plugins that one tried to enable or use
    • UDF's files that didn't include the required init functions.
  • log_warnings >= 2
    • Table handler errors
  • log_warnings >= 3
    • All errors and warnings during MyISAM repair and auto recover.

Default values

You can verify the default values for an option by doing:

mysqld --no-defaults --help --verbose

The default values are at the end of this list

Comments

Comments loading...
Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.