Mysql 8.0 en 91 120
Mysql 8.0 en 91 120
• These thread states: checking privileges on cached query, checking query cache
for query, invalidating query cache entries, sending cached result to client,
storing result in query cache, Waiting for query cache lock.
These deprecated query cache items remain deprecated, but have no effect; expect them to be removed
in a future MySQL release:
The have_query_cache system variable remains deprecated, and always has a value of NO; expect it
to be removed in a future MySQL release.
• The data dictionary provides information about database objects, so the server no longer checks
directory names in the data directory to find databases. Consequently, the --ignore-db-dir option
and ignore_db_dirs system variables are extraneous and are removed.
• The DDL log, also known as the metadata log, has been removed. Beginning with MySQL 8.0.3, this
functionality is handled by the data dictionary innodb_ddl_log table. See Viewing DDL Logs.
• The tx_isolation and tx_read_only system variables have been removed. Use
transaction_isolation and transaction_read_only instead.
• The sync_frm system variable has been removed because .frm files have become obsolete.
• The secure_auth system variable and --secure-auth client option have been removed. The
MYSQL_SECURE_AUTH option for the mysql_options() C API function was removed.
• The log_warnings system variable and --log-warnings server option have been removed. Use the
log_error_verbosity system variable instead.
• The global scope for the sql_log_bin system variable was removed. sql_log_bin has session
scope only, and applications that rely on accessing @@GLOBAL.sql_log_bin should be adjusted.
• These deprecated compatibility SQL modes are removed: DB2, MAXDB, MSSQL, MYSQL323, MYSQL40,
ORACLE, POSTGRESQL, NO_FIELD_OPTIONS, NO_KEY_OPTIONS, NO_TABLE_OPTIONS. They can no
59
Features Removed in MySQL 8.0
longer be assigned to the sql_mode system variable or used as permitted values for the mysqldump --
compatible option.
Removal of MAXDB means that the TIMESTAMP data type for CREATE TABLE or ALTER TABLE is
treated as TIMESTAMP, and is no longer treated as DATETIME.
• The deprecated ASC or DESC qualifiers for GROUP BY clauses are removed. Queries that previously
relied on GROUP BY sorting may produce results that differ from previous MySQL versions. To produce a
given sort order, provide an ORDER BY clause.
• The EXTENDED and PARTITIONS keywords for the EXPLAIN statement have been removed. These
keywords are unnecessary because their effect is always enabled.
In place of the removed encryption functions: For ENCRYPT(), consider using SHA2() instead for one-
way hashing. For the others, consider using AES_ENCRYPT() and AES_DECRYPT() instead.
• In MySQL 5.7, several spatial functions available under multiple names were deprecated to move in the
direction of making the spatial function namespace more consistent, the goal being that each spatial
function name begin with ST_ if it performs an exact operation, or with MBR if it performs an operation
based on minimum bounding rectangles. In MySQL 8.0, the deprecated functions are removed to leave
only the corresponding ST_ and MBR functions:
• These functions are removed in favor of the MBR names: Contains(), Disjoint(), Equals(),
Intersects(), Overlaps(), Within().
• These functions are removed in favor of the ST_ names: Area(), AsBinary(), AsText(),
AsWKB(), AsWKT(), Buffer(), Centroid(), ConvexHull(), Crosses(), Dimension(),
Distance(), EndPoint(), Envelope(), ExteriorRing(), GeomCollFromText(),
GeomCollFromWKB(), GeomFromText(), GeomFromWKB(), GeometryCollectionFromText(),
GeometryCollectionFromWKB(), GeometryFromText(), GeometryFromWKB(),
GeometryN(), GeometryType(), InteriorRingN(), IsClosed(), IsEmpty(),
IsSimple(), LineFromText(), LineFromWKB(), LineStringFromText(),
LineStringFromWKB(), MLineFromText(), MLineFromWKB(), MPointFromText(),
MPointFromWKB(), MPolyFromText(), MPolyFromWKB(), MultiLineStringFromText(),
MultiLineStringFromWKB(), MultiPointFromText(), MultiPointFromWKB(),
MultiPolygonFromText(), MultiPolygonFromWKB(), NumGeometries(),
NumInteriorRings(), NumPoints(), PointFromText(), PointFromWKB(), PointN(),
PolyFromText(), PolyFromWKB(), PolygonFromText(), PolygonFromWKB(), SRID(),
StartPoint(), Touches(), X(), Y().
• The functions described in Section 14.16.4, “Functions That Create Geometry Values from WKB Values”
previously accepted either WKB strings or geometry arguments. Geometry arguments are no longer
permitted and produce an error. See that section for guidelines for migrating queries away from using
geometry arguments.
60
Features Removed in MySQL 8.0
• The parser no longer treats \N as a synonym for NULL in SQL statements. Use NULL instead.
This change does not affect text file import or export operations performed with LOAD DATA or
SELECT ... INTO OUTFILE, for which NULL continues to be represented by \N. See Section 15.2.9,
“LOAD DATA Statement”.
• The client-side --ssl and --ssl-verify-server-cert options have been removed. Use --ssl-
mode=REQUIRED instead of --ssl=1 or --enable-ssl. Use --ssl-mode=DISABLED instead of --
ssl=0, --skip-ssl, or --disable-ssl. Use --ssl-mode=VERIFY_IDENTITY instead of --ssl-
verify-server-cert options. (The server-side --ssl option is still available, but is deprecated as of
MySQL 8.0.26 and subject to removal in a future MySQL version.)
• The server no longer performs conversion of pre-MySQL 5.1 database names containing special
characters to 5.1 format with the addition of a #mysql50# prefix. Because these conversions are
no longer performed, the --fix-db-names and --fix-table-names options for mysqlcheck,
the UPGRADE DATA DIRECTORY NAME clause for the ALTER DATABASE statement, and the
Com_alter_db_upgrade status variable are removed.
Upgrades are supported only from one major version to another (for example, 5.0 to 5.1, or 5.1 to 5.5),
so there should be little remaining need for conversion of older 5.0 database names to current versions
of MySQL. As a workaround, upgrade a MySQL 5.0 installation to MySQL 5.1 before upgrading to a
more recent release.
• The mysql_install_db program has been removed from MySQL distributions. Data directory
initialization should be performed by invoking mysqld with the --initialize or --initialize-
insecure option instead. In addition, the --bootstrap option for mysqld that was used by
mysql_install_db was removed, and the INSTALL_SCRIPTDIR CMake option that controlled the
installation location for mysql_install_db was removed.
• The generic partitioning handler was removed from the MySQL server. In order to support partitioning
of a given table, the storage engine used for the table must now provide its own (“native”) partitioning
handler. The --partition and --skip-partition options are removed from the MySQL Server,
and partitioning-related entries are no longer shown in the output of SHOW PLUGINS or in the Information
Schema PLUGINS table.
Two MySQL storage engines currently provide native partitioning support: InnoDB and NDB. Of these,
only InnoDB is supported in MySQL 8.0. Any attempt to create partitioned tables in MySQL 8.0 using
any other storage engine fails.
Ramifications for upgrades. The direct upgrade of a partitioned table using a storage engine other
than InnoDB (such as MyISAM) from MySQL 5.7 (or earlier) to MySQL 8.0 is not supported. There are
two options for handling such a table:
• Remove the table's partitioning, using ALTER TABLE ... REMOVE PARTITIONING.
• Change the storage engine used for the table to InnoDB, with ALTER TABLE ... ENGINE=INNODB.
61
Features Removed in MySQL 8.0
At least one of the two operations just listed must be performed for each partitioned non-InnoDB table
prior to upgrading the server to MySQL 8.0. Otherwise, such a table cannot be used following the
upgrade.
Due to the fact that table creation statements that would result in a partitioned table using a storage
engine without partitioning support now fail with an error (ER_CHECK_NOT_IMPLEMENTED), you must
make sure that any statements in a dump file (such as that written by mysqldump) from an older version
of MySQL that you wish to import into a MySQL 8.0 server that create partitioned tables do not also
specify a storage engine such as MyISAM that has no native partitioning handler. You can do this by
performing either of the following:
• Remove any references to partitioning from CREATE TABLE statements that use a value for the
STORAGE ENGINE option other than InnoDB.
• Specifying the storage engine as InnoDB, or allow InnoDB to be used as the table's storage engine
by default.
For more information, see Section 26.6.2, “Partitioning Limitations Relating to Storage Engines”.
• The Performance Schema setup_timers table was removed, as was the TICK row in the
performance_timers table.
• The mysql_plugin utility was removed. Alternatives include loading plugins at server startup using
the --plugin-load or --plugin-load-add option, or at runtime using the INSTALL PLUGIN
statement.
• The resolveip utility is removed. nslookup, host, or dig can be used instead.
62
Features Removed in MySQL 8.0
• The resolve_stack_dump utility is removed. Stack traces from official MySQL builds are always
symbolized, so there is no need to use resolve_stack_dump.
• The following server error codes are not used and have been removed. Applications that test specifically
for any of these errors should be updated.
ER_BINLOG_READ_EVENT_CHECKSUM_FAILURE
ER_BINLOG_ROW_RBR_TO_SBR
ER_BINLOG_ROW_WRONG_TABLE_DEF
ER_CANT_ACTIVATE_LOG
ER_CANT_CHANGE_GTID_NEXT_IN_TRANSACTION
ER_CANT_CREATE_FEDERATED_TABLE
ER_CANT_CREATE_SROUTINE
ER_CANT_DELETE_FILE
ER_CANT_GET_WD
ER_CANT_SET_GTID_PURGED_WHEN_GTID_MODE_IS_OFF
ER_CANT_SET_WD
ER_CANT_WRITE_LOCK_LOG_TABLE
ER_CREATE_DB_WITH_READ_LOCK
ER_CYCLIC_REFERENCE
ER_DB_DROP_DELETE
ER_DELAYED_NOT_SUPPORTED
ER_DIFF_GROUPS_PROC
ER_DISK_FULL
ER_DROP_DB_WITH_READ_LOCK
ER_DROP_USER
ER_DUMP_NOT_IMPLEMENTED
ER_ERROR_DURING_CHECKPOINT
ER_ERROR_ON_CLOSE
ER_EVENTS_DB_ERROR
ER_EVENT_CANNOT_DELETE
ER_EVENT_CANT_ALTER
ER_EVENT_COMPILE_ERROR
ER_EVENT_DATA_TOO_LONG
ER_EVENT_DROP_FAILED
ER_EVENT_MODIFY_QUEUE_ERROR
ER_EVENT_NEITHER_M_EXPR_NOR_M_AT
ER_EVENT_OPEN_TABLE_FAILED
ER_EVENT_STORE_FAILED
ER_EXEC_STMT_WITH_OPEN_CURSOR
ER_FAILED_ROUTINE_BREAK_BINLOG
ER_FLUSH_MASTER_BINLOG_CLOSED
ER_FORM_NOT_FOUND
ER_FOUND_GTID_EVENT_WHEN_GTID_MODE_IS_OFF__UNUSED
ER_FRM_UNKNOWN_TYPE
ER_GOT_SIGNAL
ER_GRANT_PLUGIN_USER_EXISTS
ER_GTID_MODE_REQUIRES_BINLOG
ER_GTID_NEXT_IS_NOT_IN_GTID_NEXT_LIST
ER_HASHCHK
ER_INDEX_REBUILD
ER_INNODB_NO_FT_USES_PARSER
ER_LIST_OF_FIELDS_ONLY_IN_HASH_ERROR
ER_LOAD_DATA_INVALID_COLUMN_UNUSED
ER_LOGGING_PROHIBIT_CHANGING_OF
ER_MALFORMED_DEFINER
ER_MASTER_KEY_ROTATION_ERROR_BY_SE
ER_NDB_CANT_SWITCH_BINLOG_FORMAT
ER_NEVER_USED
ER_NISAMCHK
ER_NO_CONST_EXPR_IN_RANGE_OR_LIST_ERROR
ER_NO_FILE_MAPPING
ER_NO_GROUP_FOR_PROC
ER_NO_RAID_COMPILED
ER_NO_SUCH_KEY_VALUE
ER_NO_SUCH_PARTITION__UNUSED
63
Features Removed in MySQL 8.0
ER_OBSOLETE_CANNOT_LOAD_FROM_TABLE
ER_OBSOLETE_COL_COUNT_DOESNT_MATCH_CORRUPTED
ER_ORDER_WITH_PROC
ER_PARTITION_SUBPARTITION_ERROR
ER_PARTITION_SUBPART_MIX_ERROR
ER_PART_STATE_ERROR
ER_PASSWD_LENGTH
ER_QUERY_ON_MASTER
ER_RBR_NOT_AVAILABLE
ER_SKIPPING_LOGGED_TRANSACTION
ER_SLAVE_CHANNEL_DELETE
ER_SLAVE_MULTIPLE_CHANNELS_HOST_PORT
ER_SLAVE_MUST_STOP
ER_SLAVE_WAS_NOT_RUNNING
ER_SLAVE_WAS_RUNNING
ER_SP_GOTO_IN_HNDLR
ER_SP_PROC_TABLE_CORRUPT
ER_SQL_MODE_NO_EFFECT
ER_SR_INVALID_CREATION_CTX
ER_TABLE_NEEDS_UPG_PART
ER_TOO_MUCH_AUTO_TIMESTAMP_COLS
ER_UNEXPECTED_EOF
ER_UNION_TABLES_IN_DIFFERENT_DIR
ER_UNSUPPORTED_BY_REPLICATION_THREAD
ER_UNUSED1
ER_UNUSED2
ER_UNUSED3
ER_UNUSED4
ER_UNUSED5
ER_UNUSED6
ER_VIEW_SELECT_DERIVED_UNUSED
ER_WRONG_MAGIC
ER_WSAS_FAILED
Note
In MySQL 5.7, the LOCK_TABLE column in the INNODB_LOCKS table and the
locked_table column in the sys schema innodb_lock_waits and x
$innodb_lock_waits views contain combined schema/table name values.
In MySQL 8.0, the data_locks table and the sys schema views contain
separate schema name and table name columns. See Section 30.4.3.9, “The
innodb_lock_waits and x$innodb_lock_waits Views”.
• InnoDB no longer creates .isl files (InnoDB Symbolic Link files) when creating tablespace data
files outside of the MySQL data directory. The innodb_directories option now supports locating
tablespace files created outside of the data directory.
With this change, moving a remote tablespace while the server is offline by manually modifying
an .isl file is no longer supported. Moving remote tablespace files is now supported by the
innodb_directories option. See Section 17.6.3.6, “Moving Tablespace Files While the Server is
Offline”.
64
Server and Status Variables and Options Added, Deprecated, or Removed in MySQL 8.0
• innodb_file_format
• innodb_file_format_check
• innodb_file_format_max
• innodb_large_prefix
File format variables were necessary for creating tables compatible with earlier versions of InnoDB
in MySQL 5.1. Now that MySQL 5.1 has reached the end of its product lifecycle, these options are no
longer required.
The FILE_FORMAT column was removed from the INNODB_TABLES and INNODB_TABLESPACES
Information Schema tables.
• The innodb_support_xa system variable, which enables support for two-phase commit in XA
transactions, was removed. InnoDB support for two-phase commit in XA transactions is always enabled.
• Support for placing table partitions in shared InnoDB tablespaces was removed in MySQL 8.0.13.
Shared tablespaces include the InnoDB system tablespace and general tablespaces. For information
about identifying partitions in shared tablespaces and moving them to file-per-table tablespaces, see
Section 3.6, “Preparing Your Installation for Upgrade”.
• Support for setting user variables in statements other than SET was deprecated in MySQL 8.0.13. This
functionality is subject to removal in MySQL 8.4.
• The --ndb perror option was removed. Use the ndb_perror utility instead.
• Support for the ALTER TABLE ... UPGRADE PARTITIONING statement has been removed.
• The DISABLE_SHARED CMake option was unused and has been removed.
65
Options and Variables Introduced in MySQL 8.0
This section lists server variables, status variables, and options that were added for the first time, have
been deprecated, or have been removed in MySQL 8.0.
66
Options and Variables Introduced in MySQL 8.0
• Com_replica_start: Count of START REPLICA and START SLAVE statements. Added in MySQL
8.0.22.
• Com_replica_stop: Count of STOP REPLICA and STOP SLAVE statements. Added in MySQL
8.0.22.
• Com_show_replicas: Count of SHOW REPLICAS and SHOW SLAVE HOSTS statements. Added in
MySQL 8.0.22.
67
Options and Variables Introduced in MySQL 8.0
• Innodb_redo_log_capacity_resized: Redo log capacity after the last completed capacity resize
operation. Added in MySQL 8.0.30.
• Innodb_system_rows_read: Number of rows read from system schema tables. Added in MySQL
8.0.19.
68
Options and Variables Introduced in MySQL 8.0
• Mysqlx_compression_level: Compression level in use for X Protocol connection for this session.
Added in MySQL 8.0.20.
• Replica_open_temp_tables: Number of temporary tables that replication SQL thread currently has
open. Added in MySQL 8.0.26.
• Resource_group_supported: Whether server supports the resource group feature. Added in MySQL
8.0.31.
• Rpl_semi_sync_source_net_wait_time: Total time source has waited for replies from replica.
Added in MySQL 8.0.26.
• Rpl_semi_sync_source_net_waits: Total number of times source waited for replies from replica.
Added in MySQL 8.0.26.
69
Options and Variables Introduced in MySQL 8.0
• admin_port: TCP/IP number to use for connections on administrative interface. Added in MySQL
8.0.14.
• admin_ssl_ca: File that contains list of trusted SSL Certificate Authorities. Added in MySQL 8.0.21.
• admin_ssl_capath: Directory that contains trusted SSL Certificate Authority certificate files. Added in
MySQL 8.0.21.
• admin_ssl_crl: File that contains certificate revocation lists. Added in MySQL 8.0.21.
• admin_ssl_crlpath: Directory that contains certificate revocation list files. Added in MySQL 8.0.21.
• admin_tls_version: Permissible TLS protocols for encrypted connections. Added in MySQL 8.0.21.
70
Options and Variables Introduced in MySQL 8.0
• audit_log_database: Schema where audit tables are stored. Added in MySQL 8.0.33.
• audit_log_flush: Close and reopen audit log file. Added in MySQL 8.0.11.
• audit_log_max_size: Limit on combined size of JSON audit log files. Added in MySQL 8.0.26.
• audit_log_prune_seconds: The number of seconds after which audit log files become subject to
pruning. Added in MySQL 8.0.24.
• audit_log_read_buffer_size: Audit log file read buffer size. Added in MySQL 8.0.11.
• audit_log_rotate_on_size: Close and reopen audit log file at this size. Added in MySQL 8.0.11.
71
Options and Variables Introduced in MySQL 8.0
72
Options and Variables Introduced in MySQL 8.0
• binlog_encryption: Enable encryption for binary log files and relay log files on this server. Added in
MySQL 8.0.14.
• binlog_expire_logs_seconds: Purge binary logs after this many seconds. Added in MySQL 8.0.1.
• binlog_row_metadata: Whether to record all or only minimal table related metadata to binary log
when using row-based logging. Added in MySQL 8.0.1.
• build_id: A unique build ID generated at compile time (Linux only). Added in MySQL 8.0.31.
73
Options and Variables Introduced in MySQL 8.0
• clone_block_ddl: Enables an exclusive backup lock during clone operations. Added in MySQL
8.0.27.
• clone_buffer_size: Defines size of intermediate buffer on donor MySQL server instance. Added in
MySQL 8.0.17.
• clone_ddl_timeout: Number of seconds cloning operation waits for backup lock. Added in MySQL
8.0.17.
• clone_delay_after_data_drop: The time delay in seconds before the clone process starts. Added
in MySQL 8.0.29.
• clone_max_data_bandwidth: Maximum data transfer rate in MiB per second for remote cloning
operation. Added in MySQL 8.0.17.
• clone_max_network_bandwidth: Maximum network transfer rate in MiB per second for remote
cloning operation. Added in MySQL 8.0.17.
• clone_ssl_ca: Specifies path to certificate authority (CA) file. Added in MySQL 8.0.14.
• clone_ssl_cert: Specifies path to public key certificate file. Added in MySQL 8.0.14.
• clone_valid_donor_list: Defines donor host addresses for remote cloning operations. Added in
MySQL 8.0.17.
74
Options and Variables Introduced in MySQL 8.0
• connection_memory_limit: Maximum amount of memory that can be consumed by any one user
connection before all queries by this user are rejected. Does not apply to system users such as MySQL
root. Added in MySQL 8.0.28.
• default_collation_for_utf8mb4: Default collation for utf8mb4 character set; for internal use by
MySQL Replication only. Added in MySQL 8.0.11.
• early-plugin-load: Specify plugins to load before loading mandatory built-in plugins and before
storage engine initialization. Added in MySQL 8.0.0.
• explain_format: Determines default output format used by EXPLAIN statements. Added in MySQL
8.0.32.
75
Options and Variables Introduced in MySQL 8.0
76
Options and Variables Introduced in MySQL 8.0
• init_replica: Statements that are executed when replica connects to source. Added in MySQL
8.0.26.
• innodb_buffer_pool_debug: Permits multiple buffer pool instances when buffer pool is less than
1GB in size. Added in MySQL 8.0.0.
• innodb_ddl_buffer_size: The maximum buffer size for DDL operations. Added in MySQL 8.0.27.
• innodb_ddl_log_crash_reset_debug: Debug option that resets DDL log crash injection counters.
Added in MySQL 8.0.3.
• innodb_ddl_threads: The maximum number of parallel threads for index creation. Added in MySQL
8.0.27.
• innodb_dedicated_server: Enables automatic configuration of buffer pool size, log file size, and
flush method. Added in MySQL 8.0.3.
• innodb_directories: Defines directories to scan at startup for tablespace data files. Added in
MySQL 8.0.4.
77
Options and Variables Introduced in MySQL 8.0
• innodb_fsync_threshold: Controls how often InnoDB calls fsync when creating new file. Added in
MySQL 8.0.13.
• innodb_idle_flush_pct: Limits I/0 operations when InnoDB is idle. Added in MySQL 8.0.18.
• innodb_log_writer_threads: Enables dedicated log writer threads for writing and flushing redo
logs. Added in MySQL 8.0.22.
• innodb_print_ddl_logs: Whether or not to print DDL logs to error log. Added in MySQL 8.0.3.
• innodb_redo_log_capacity: The size limit for redo log files. Added in MySQL 8.0.30.
• innodb_redo_log_encrypt: Controls encryption of redo log data for encrypted tablespaces. Added
in MySQL 8.0.1.
• innodb_scan_directories: Defines directories to scan for tablespace files during InnoDB recovery.
Added in MySQL 8.0.2.
• innodb_tmpdir: Directory location for temporary table files created during online ALTER TABLE
operations. Added in MySQL 8.0.0.
• innodb_undo_log_encrypt: Controls encryption of undo log data for encrypted tablespaces. Added
in MySQL 8.0.1.
78
Options and Variables Introduced in MySQL 8.0
• innodb_use_fdatasync: Whether InnoDB uses fdatasync() instead of fsync() when flushing data to
the operating system. Added in MySQL 8.0.26.
• keyring-migration-host: Host name for connecting to running server for key migration. Added in
MySQL 8.0.4.
• keyring-migration-password: Password for connecting to running server for key migration. Added
in MySQL 8.0.4.
• keyring-migration-port: TCP/IP port number for connecting to running server for key migration.
Added in MySQL 8.0.4.
• keyring-migration-socket: Unix socket file or Windows named pipe for connecting to running
server for key migration. Added in MySQL 8.0.4.
• keyring-migration-user: User name for connecting to running server for key migration. Added in
MySQL 8.0.4.
• keyring_aws_cmk_id: AWS keyring plugin customer master key ID value. Added in MySQL 8.0.11.
• keyring_aws_conf_file: AWS keyring plugin configuration file location. Added in MySQL 8.0.11.
• keyring_aws_data_file: AWS keyring plugin storage file location. Added in MySQL 8.0.11.
79
Options and Variables Introduced in MySQL 8.0
• keyring_oci_key_fingerprint: OCI RSA private key file fingerprint. Added in MySQL 8.0.22.
• keyring_okv_conf_dir: Oracle Key Vault keyring plugin configuration directory. Added in MySQL
8.0.11.
80
Options and Variables Introduced in MySQL 8.0
• lock_order_print_txt: Whether to perform lock-order graph analysis and print textual report. Added
in MySQL 8.0.17.
• lock_order_trace_loop: Whether to print log file trace when LOCK_ORDER tool encounters
dependency flagged as loop. Added in MySQL 8.0.17.
• log_replica_updates: Whether replica should log updates performed by its replication SQL thread
to its own binary log. Added in MySQL 8.0.26.
• log_slow_extra: Whether to write extra information to slow query log file. Added in MySQL 8.0.14.
• mandatory_roles: Automatically granted roles for all users. Added in MySQL 8.0.2.
• mysqlx_interactive_timeout: Number of seconds to wait for interactive clients to time out. Added
in MySQL 8.0.4.
81
Options and Variables Introduced in MySQL 8.0
• mysqlx_read_timeout: Number of seconds to wait for blocking read operations to complete. Added in
MySQL 8.0.4.
• mysqlx_wait_timeout: Number of seconds to wait for activity from connection. Added in MySQL
8.0.4.
• mysqlx_write_timeout: Number of seconds to wait for blocking write operations to complete. Added
in MySQL 8.0.4.
• no-dd-upgrade: Prevent automatic upgrade of data dictionary tables at startup. Added in MySQL
8.0.4.
• no-monitor: Do not fork monitor process required for RESTART. Added in MySQL 8.0.12.
• password_history: Number of password changes required before password reuse. Added in MySQL
8.0.3.
82
Options and Variables Introduced in MySQL 8.0
• regexp_stack_limit: Regular expression match stack size limit. Added in MySQL 8.0.4.
• replica_checkpoint_period: Update progress status of multithreaded replica and flush relay log
info to disk after this number of milliseconds. Not supported by NDB Cluster. Added in MySQL 8.0.26.
• replica_exec_mode: Allows for switching replication thread between IDEMPOTENT mode (key and
some other errors suppressed) and STRICT mode; STRICT mode is default, except for NDB Cluster,
where IDEMPOTENT is always used. Added in MySQL 8.0.26.
• replica_load_tmpdir: Location where replica should put its temporary files when replicating LOAD
DATA statements. Added in MySQL 8.0.26.
• replica_max_allowed_packet: Maximum size, in bytes, of packet that can be sent from replication
source server to replica; overrides max_allowed_packet. Added in MySQL 8.0.26.
• replica_net_timeout: Number of seconds to wait for more data from source/replica connection
before aborting read. Added in MySQL 8.0.26.
• replica_pending_jobs_size_max: Maximum size of replica worker queues holding events not yet
applied. Added in MySQL 8.0.26.
• replica_skip_errors: Tells replication thread to continue replication when query returns error from
provided list. Added in MySQL 8.0.26.
• replica_sql_verify_checksum: Cause replica to examine checksums when reading from relay log.
Added in MySQL 8.0.26.
83
Options and Variables Introduced in MySQL 8.0
• resultset_metadata: Whether server returns result set metadata. Added in MySQL 8.0.3.
• rpl_read_size: Set minimum amount of data in bytes which is read from binary log files and relay log
files. Added in MySQL 8.0.11.
• rpl_stop_replica_timeout: Number of seconds that STOP REPLICA waits before timing out.
Added in MySQL 8.0.26.
• select_into_buffer_size: Size of buffer used for OUTFILE or DUMPFILE export file; overrides
read_buffer_size. Added in MySQL 8.0.22.
• select_into_disk_sync: Synchronize data with storage device after flushing buffer for OUTFILE or
DUMPFILE export file; OFF disables synchronization and is default value. Added in MySQL 8.0.22.
84
Options and Variables Introduced in MySQL 8.0
• show-replica-auth-info: Show user name and password in SHOW REPLICAS on this source.
Added in MySQL 8.0.26.
• skip-replica-start: If set, replication is not autostarted when replica server starts. Added in MySQL
8.0.26.
• source_verify_checksum: Cause source to examine checksums when reading from binary log.
Added in MySQL 8.0.26.
• sql_replica_skip_counter: Number of events from source that replica should skip. Not compatible
with GTID replication. Added in MySQL 8.0.26.
• sql_require_primary_key: Whether tables must have primary key. Added in MySQL 8.0.13.
• ssl_fips_mode: Whether to enable FIPS mode on server side. Added in MySQL 8.0.11.
• sync_source_info: Synchronize source information after every #th event. Added in MySQL 8.0.26.
• syseventlog.tag: Tag for server identifier in syslog messages. Added in MySQL 8.0.13.
• temptable_max_mmap: The maximum amount of memory the TempTable storage engine can allocate
from memory-mapped temporary files. Added in MySQL 8.0.23.
• temptable_max_ram: Defines maximum amount of memory that can occupied by TempTable storage
engine before data is stored on disk. Added in MySQL 8.0.2.
85
Options and Variables Introduced in MySQL 8.0
• terminology_use_previous: Use terminology from before specified version where changes are
incompatible. Added in MySQL 8.0.26.
86
Options and Variables Deprecated in MySQL 8.0
• Slave_open_temp_tables: Number of temporary tables that replication SQL thread currently has
open. Deprecated in MySQL 8.0.26.
• character-set-client-handshake: Do not ignore client side character set value sent during
handshake. Deprecated in MySQL 8.0.35.
87
Options and Variables Deprecated in MySQL 8.0
• expire_logs_days: Purge binary logs after this many days. Deprecated in MySQL 8.0.3.
• init_slave: Statements that are executed when replica connects to source. Deprecated in MySQL
8.0.26.
• innodb_api_enable_binlog: Allows use of InnoDB memcached plugin with MySQL binary log.
Deprecated in MySQL 8.0.22.
• innodb_log_file_size: Size of each log file in log group. Deprecated in MySQL 8.0.30.
88