Search Results
https://dev.mysql.com/doc/refman/8.4/en/partitioning-columns.html
The next two sections discuss COLUMNS partitioning, which are variants on RANGE and LIST partitioning. COLUMNS partitioning enables the use of multiple columns in partitioning keys. All of these columns are taken into account both for the purpose ...
https://dev.mysql.com/doc/refman/8.4/en/performance-schema-error-summary-tables.html
The Performance Schema maintains summary tables for aggregating statistical information about server errors (and warnings). For a list of server errors, see Server Error Message Reference. Collection of error information is controlled by the error ...
https://dev.mysql.com/doc/refman/8.4/en/performance-schema-host-cache-table.html
The MySQL server maintains an in-memory host cache that contains client host name and IP address information and is used to avoid Domain Name System (DNS) lookups. The host_cache_size system variable controls the size of the host cache, as well as ...
https://dev.mysql.com/doc/refman/8.4/en/performance-schema-setup-metrics-table.html
The setup_metrics table lists the available metrics: mysql> select * from performance_schema.setup_metrics\G *************************** 34. row *************************** NAME: undo_tablespaces_active METER: mysql.inno METRIC_TYPE: ASYNC GAUGE ...
https://dev.mysql.com/doc/refman/8.4/en/program-variables.html
Many MySQL programs have internal variables that can be set at runtime using the SET statement. See Section 15.7.6.1, “SET Syntax for Variable Assignment”, and Section 7.1.9, “Using System Variables”. Most of these program variables also ...
https://dev.mysql.com/doc/refman/8.4/en/replication-features-differing-tables.html
Source and target tables for replication do not have to be identical. A table on the source can have more or fewer columns than the replica's copy of the table. In addition, corresponding table columns on the source and the replica can use ...
https://dev.mysql.com/doc/refman/8.4/en/replication-gtids-concepts.html
A global transaction identifier (GTID) is a unique identifier created and associated with each transaction committed on the server of origin (the source). This identifier is unique not only to the server on which it originated, but is unique across ...
https://dev.mysql.com/doc/refman/8.4/en/replication-gtids-functions.html
This section provides examples of stored functions (see Chapter 27, Stored Objects) which you can create using some of the built-in functions provided by MySQL for use with GTID-based replication, listed here: GTID_SUBSET(): Shows whether one GTID ...
https://dev.mysql.com/doc/refman/8.4/en/replication-options-replica.html
This section explains the server options and system variables that apply to replica servers and contains the following: Startup Options for Replica Servers System Variables Used on Replica Servers Specify the options either on the command line or ...
https://dev.mysql.com/doc/refman/8.4/en/reset-binary-logs-and-gtids.html
Note This statement takes the place of the old RESET MASTER statement, which is no longer supported. RESET BINARY LOGS AND GTIDS [TO binary_log_file_index_number] Warning Use this statement with caution to ensure you do not lose any wanted binary ...