System Variable Differences Between MariaDB 10.2 and MySQL 5.6

The following is a comparison of variables that either appear only in MariaDB 10.2 or MySQL 5.6, or have different default settings in MariaDB 10.2, and MySQL 5.6. MariaDB 10.2.19 and MySQL 5.6.27, with only default plugins enabled, were used for the comparison.

The most notable differences are that MariaDB includes, by default, the Aria storage engine (resulting in extra memory allocation), Galera Cluster and has a different thread pool implementation. For this reason, a default implementation of MariaDB 10.2 will use more memory than MySQL 5.6. MariaDB 10.2 and MySQL 5.6 also have different GTID implementations.

MariaDB's extra memory usage can be handled with the following rules of thumb:

Comparison Table

VariableMariaDB 10.1MySQL 5.6Notes
aria_**-The Aria storage engine is only available in MariaDB.
avoid_temporal_upgrade-OFFMySQL 5.6-only variable for determining whether ALTER TABLE implicitly upgrades temporal columns.
bind_address- has the value of the bind-address option as a variable.
binlog-annotate-row-eventsOFF-Introduced in MariaDB 5.3 for replicating between MariaDB 5.3 and MySQL/MariaDB 5.1.
binlog_checksumNONECRC32Specifies the type of BINLOG_CHECKSUM_ALG for log events in the binary log.
binlog_commit_wait_count0-For use in MariaDB's parallel replication.
binlog_commit_wait_usec100000-For use in MariaDB's parallel replication.
binlog_error_actionIGNORE_ERRORMySQL-only variable for controlling what happens when the server cannot write to the binary log.
binlog_gtid_simple_recovery-OFFMySQL 5.6-only GTID variable. MariaDB's GTID implementation is different.
binlog_max_flush_queue_time-0MySQL 5.6-only variable specifying a timeout for reading transactions from the flush queue before continuing with group commit and syncing log to disk.
binlog_optimize_thread_schedulingON-For optimized kernel thread scheduling.
binlog_order_commits-ONMySQL 5.6-only variable for determining whether transactions may be committed in parallel.
binlog_rows_query_log_events-OFFMySQL 5.6-only variable for logging extra information in row-based logging.
binlogging_impossible_mode-IGNORE_ERRORMySQL 5.6-only variable, determines what happens if a write to binlog fails.
block_encryption_mode-aes-128-ecbMySQL 5.6-only variable for controlling the block encryption mode for block-based algorithms.
deadlock_search_depth_long15-The Aria storage engine is only available in MariaDB.
deadlock_search_depth_short4-The Aria storage engine is only available in MariaDB.
deadlock_timeout_long50000000-The Aria storage engine is only available in MariaDB.
deadlock_timeout_short10000-The Aria storage engine is only available in MariaDB.
debug_no_thread_alarmOFF-Disable system thread alarm calls, for debugging or testing.
default_master_connectionempty-For use with MariaDB's multi-source replication.
default_regex_flagsempty-For handling incompatibilities between MariaDB's PCRE and the old regex library.
default_tmp_storage_engineemptyInnoDBDefault storage engine used for tables created with CREATE TEMPORARY TABLE.
disconnect_on_expired_password-ONMySQL 5.6 permits passwords to be expired.
encrypt_binlogOFF-MariaDB enables table and tablespace encryption.
encrypt_tmp_filesOFF-MariaDB enables table and tablespace encryption.
encrypt_tmp_disk_tablesOFF-MariaDB enables table and tablespace encryption.
end_markers_in_json-OFFMySQL 5.6-only variable for adding end markers to JSON output
enforce_gtid_consistency-OFFMariaDB and MySQL have different GTID implementations.
enforce_storage_enginenoneForces the use of a particular storage engine for new tables.
eq_range_index_dive_limit010Variable for tuning when the optimizer should switch from using index dives to index statistics for qualifying rows estimation.
expensive_subquery_limit100-Used for determining expensive queries for optimization.
extra_max_connections1-Introduced in the MariaDB 5.1 threadpool.
extra_port0-Introduced in the MariaDB 5.1 threadpool.
gtid_binlog_posempty-MariaDB and MySQL have different GTID implementations.
gtid_binlog_stateempty-MariaDB and MySQL have different GTID implementations.
gtid_current_posempty-MariaDB and MySQL have different GTID implementations.
gtid_domain_id0-MariaDB and MySQL have different GTID implementations.
gtid_executed-emptyMariaDB and MySQL have different GTID implementations.
gtid_ignore_duplicatesOFF-MariaDB and MySQL have different GTID implementations.
gtid_mode-OFFMariaDB and MySQL have different GTID implementations.
gtid_next-AUTOMATICMariaDB and MySQL have different GTID implementations.
gtid_owned-emptyMariaDB and MySQL have different GTID implementations.
gtid_purged-emptyMariaDB and MySQL have different GTID implementations.
gtid_seq_no0-MariaDB and MySQL have different GTID implementations.
gtid_slave_posempty-MariaDB and MySQL have different GTID implementations.
gtid_strict_modeOFF-MariaDB and MySQL have different GTID implementations.
have_opensslMariaDB's version indicates whether YaSSL or openssl was used. MySQL's is a synonym for have_ssl.
histogram_size0-MariaDB introduced Histogram-based Statistics.
histogram_typeSINGLE_PREC_HB-MariaDB introduced Histogram-based Statistics.
in_transaction0-Set to 1 if you are in a transaction, and 0 if not.
innodb_***The list of differences between MariaDB 10.2 and MySQL 5.6 Innodb variables is currently incomplete.
innodb_log_optimize_ddlON-Whether redo logging should be reduced when natively creating indexes or rebuilding tables
innodb_safe_truncateON-Use a backup-safe TRUNCATE TABLE implementation and crash-safe rename operations inside InnoDB.
join_buffer_space_limit2097152-Maximum size in bytes of the query buffer. See block-based join algorithms.
join_cache_level2-For determining the join algorithms. See block-based join algorithms
key_buffer_size1342177288388608Size of the buffer for the index blocks used by MyISAM tables and shared for all threads.
key_cache_file_hash_size512-Number of hash buckets for open and changed files.
key_cache_segments0-The number of segments in a key cache. See Segmented Key Cache.
last_gtid-emptyMariaDB and MySQL have different GTID implementations.
log_bin_compressOFF-MariaDB setting for whether or not the binary log can be compressed.
log_bin_compress_min_len256-Minimum length of sql statement (in statement mode) or record (in row mode) that can be compressed. See Compressing Events to Reduce Size of the Binary Log.
log_bin_index-emptyMySQL-only variable containing the index file for binary log file names.
log_bin_use_v1_row_events-OFFMySQL-only variable showing whether or not MySQL's version 2 binary logging format is being used.
log_slow_filteradmin, filesort, filesort_on_disk, full_join, full_scan, query_cache, query_cache_miss, tmp_table, tmp_table_on_disk-For slow query log filtering.
log_slow_rate_limit1-Limits the number of queries logged to the slow query log.
log_slow_verbosityempty-Controls information to be added to the slow query log. See also Slow Query Log Extended Statistics.
log_tc_size24576-Size in bytes of the transaction coordinator log, defined in multiples of 4096.
log_throttle_queries_not_using_indexes-0MySQL-only variable for limiting the number of statements without indexes written to the slow query log.
master_info_repository-FILEMySQL-only variable determining whether the slaves log info to file or table.
max_allowed_packet10485764194304Maximum size in bytes of a packet or a generated/intermediate string. Increased in MySQL 5.6.6 to 4MB.
max_long_data_size4194304-Maximum size for parameter values sent with mysql_stmt_send_long_data(). Removed in MySQL 5.6.
max_recursive_iterations4294967295-Maximum number of iterations when executing recursive queries.
max_relay_log_size10737418240Can be set by session in MariaDB.
max_seeks_for_key42949672954294967295 (32-bit) or 18446744073709547520 (64-bit)The most key seeks required when searching with an index, regardless of the actual index cardinality. If this value is set lower than its default and maximum, indexes will tend to be preferred over table scans.
max_statement_time0-Maximum time in seconds that a query can execute before being aborted.
max_write_lock_count42949672954294967295 (32-bit) or 18446744073709547520 (64-bit)Read lock requests will be permitted for processing after this many write locks.
mrr_buffer_size262144-Size of buffer to use when using multi-range read with range access. See Multi Range Read optimization.
myisam_block_size1024-Block size used for MyISAM index pages.
myisam_recover_optionsDEFAULTOFFMyISAM recovery mode.
myisam_sort_buffer_size1342167048388608Size in bytes of the buffer allocated when creating or sorting indexes on a MyISAM table.
mysql56_temporal_formatONCauses MariaDB to use the MySQL-5.6 low level formats for TIME, DATETIME and TIMESTAMP instead of the MariaDB 5.3+ version.
new-OFFUsed for backward-compatibility with MySQL 4.1, not present in MariaDB
old_modeEmpty string-Used for getting MariaDB to emulate behavior from an old version of MySQL or MariaDB. See OLD Mode.
optimizer_selectivity_sampling_limit100-Controls number of record samples to check condition selectivity.
optimizer_switchSee detailsA series of flags for controlling the query optimizer. MariaDB has introduced a number of new settings.
optimizer_trace-Off by defaultMySQL 5.6-only variable for optimizer tracing.
optimizer_trace_features-Off by defaultMySQL 5.6-only variable for optimizer tracing.
optimizer_trace_limit-1MySQL 5.6-only variable for optimizer tracing.
optimizer_trace_max_mem_size-16384MySQL 5.6-only variable for optimizer tracing.
optimizer_trace_offset--1MySQL 5.6-only variable for optimizer tracing.
optimizer_use_condition_selectivity1-Controls which statistics can be used by the optimizer when looking for the best query execution plan.
performance_schemaOFFONThe Performance Schema is off by default in MariaDB.
performance_schema_*Many performance schema variables are autoset in MySQL.
plugin_maturityunknown-Minimum acceptable plugin maturity.
progress_report_time5-Time in seconds between sending progress reports to the client for time-consuming statements.
query_alloc_block_size163848192Size in bytes of the extra blocks allocated during query parsing and execution (after query_prealloc_size is used up). The MariaDB default was increased to 16384 in 10.1.2.
query_cache_strip_commentsOFF-Whether to strip any comments from the query before searching to see if it exists in the query cache.
query_prealloc_size245768192Size in bytes of the persistent buffer for query parsing and execution, allocated on connect and freed on disconnect. The MariaDB default was increased to 24576 in 10.1.2.
relay_log_info_repository-FILEMySQL-only variable determining whether the slave's position in the relay logs is written to a file or table.
replicate_annotate_row_eventsOFF-Tells the slave to reproduce annotate_rows_events received from the master in its own binary log.
replicate_do_dbempty string-See Dynamic Replication Variables.
replicate_do_tableempty string-See Dynamic Replication Variables.
replicate_events_marked_for_skipreplicate-See Selectively skipping replication of binlog events.
replicate_ignore_dbempty string-See Dynamic Replication Variables.
replicate_ignore_tableempty string-See Dynamic Replication Variables.
replicate_wild_do_tableempty string-See Dynamic Replication Variables.
replicate_wild_ignore_tableempty string-See Dynamic Replication Variables.
rowid_merge_buff_size8388608-See Non-semi-join subquery optimizations.
rpl_stop_slave_timeout-31536000MySQL-only variable for controlling the time that STOP SLAVE waits before timing out.
secure_authOFFONMySQL 5.6 prohibits connections from clients using the old (pre-MySQL 4.1) password format.
server_id_bits-server_idMySQL-only variable for use in MySQL Cluster.
server_uuid-UUIDMySQL-only variable containing the UUID.
session_track_schemaON-Whether to track changes to the default schema within the current session.
session_track_state_changeOFF-Whether to track changes to the session state.
session_track_system_variables(empty)-Comma-separated list of session system variables for which to track changes.
session_track_transaction_infoOFF-Whether to track changes to the transaction attributes.
show_old_temporals-OFFMySQL-only variable for determining whether SHOW CREATE TABLE output should include comments for old format temporal columns.
simplified_binlog_gtid_recovery-OFFMySQL-only variable, deprecated shortly after it appeared.
skip_parallel_replicationOFF-See parallel replication.
skip_replicationOFF-See Selectively skipping replication of binlog events.
slave_allow_batching-OFFMySQL-only replication variable.
slave_checkpoint_group-512MySQL-only replication variable.
slave_checkpoint_period-300MySQL-only replication variable.
read_binlog_speed_limit0-Permits restricting the speed at which the slave reads the binlog from the master.
slave_ddl_exec_modeIDEMPOTENT-Modes for how replication of DDL events should be executed.
slave_domain_parallel_threads0-For configuring parallel replication.
slave_parallel_max_queued131072-For configuring parallel replication.
slave_parallel_modeconservative-Controls what transactions are applied in parallel when using parallel_replication.
slave_parallel_threads0-For configuring parallel replication.
slave_pending_jobs_size_max-16777216MySQL-only replication variable.
slave_rows_search_algorithms-TABLE_SCAN, INDEX_SCANMySQL-only replication variable.
slave_run_triggers_for_rbrNOSee Running triggers on the slave for Row-based events for a description and use-case for this setting.
sort_buffer_size2097152262144The default sort buffer allocated has been reduced in MySQL.
sql_modeNO_AUTO_CREATE_USER, NO_ENGINE_SUBSTITUTIONNO_ENGINE_SUBSTITUTIONMariaDB does not automatically create users with GRANT. See SQL Mode.
strict_password_validationON-In MariaDB, when password validation plugins are enabled, reject passwords that cannot be validated (passwords specified as a hash).
table_definition_cache400-1 (autosized)Number of table definitions that can be cached.
table_open_cache400-1 (autosized)Number of open tables for all threads. See Optimizing table_open_cache.
table_open_cache_instances81Maximum number of table cache instances in MariaDB. This is different to the MySQL version which specifies the number of table cache instances.
thread_cache_size0-1 (autosized)MariaDB uses an improved thread pool.
thread_pool_idle_timeout60-See Using the Thread Pool in MariaDB 5.5.
thread_pool_max_threads1000-See Using the Thread Pool in MariaDB 5.5.
thread_pool_min_threads1-Windows-only. See Using the Thread Pool in MariaDB 5.5.
thread_pool_oversubscribe3-See Using the Thread Pool in MariaDB 5.5.
thread_pool_prio_kickupauto-See Using the Thread Pool.
thread_pool_priorityauto-See Using the Thread Pool.
thread_pool_sizeNumber of processors16*See Using the Thread Pool in MariaDB 5.5. *Only available in MySQL with a commercial plugin.
thread_pool_stall_limit5006*See Using the Thread Pool in MariaDB 5.5. *Only available in MySQL with a commercial plugin.
thread_stack295936196608 or 262144See Using the Thread Pool in MariaDB 5.5.
tmp_disk_table_size18446744073709551615-Max size for data for an internal temporary on-disk MyISAM or Aria table.
tmp_memory_table_size16777216-Alias for tmp_table_size.
transaction_allow_batching-OFFMySQL-only variable for enabling batching of statements within the same transaction in MySQL Cluster.
use_stat_tablesNEVER-Controls the use of engine-independent table statistics.
userstatOFF-Whether to activate MariaDB's User Statistics implementation, not available in MySQL.
version_malloc_librarybundled_jemalloc-Version of the used malloc library.
wsrep_*-Galera cluster is only available in MariaDB.
VariableMariaDB 10.2MySQL 5.6Notes

See Also


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.