Search Results
https://dev.mysql.com/doc/refman/8.4/en/performance-schema-data-locks-table.html
For information about which lock requests are blocked by which held locks, see Section 29.12.13.2, “The data_lock_waits Table”. Example data lock information: mysql> SELECT * FROM performance_schema.data_locks\G *************************** 1.
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-table-wait-summary-tables.html
The following sections describe the table I/O and lock wait summary tables: table_io_waits_summary_by_index_usage: Table I/O waits per index table_io_waits_summary_by_table: Table I/O waits per table table_lock_waits_summary_by_table: Table lock ...
https://dev.mysql.com/doc/refman/8.4/en/performance-schema-tp-thread-state-table.html
The tp_thread_state table has one row per thread created by the thread pool to handle connections. The tp_thread_state table has these columns: TP_GROUP_ID The thread group ID. TP_GROUP_ID and TP_THREAD_NUMBER together provide a unique key within ...
https://dev.mysql.com/doc/refman/8.4/en/replication-features-row-searches.html
When a replica using row-based replication format applies an UPDATE or DELETE operation, it must search the relevant table for the matching rows. The algorithm used to carry out this process uses one of the table's indexes to carry out the search ...
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-howto-additionalslaves.html
You can add another replica to an existing replication configuration without stopping the source server. To do this, you can set up the new replica by copying the data directory of an existing replica, and giving the new replica a different server ...
https://dev.mysql.com/doc/refman/8.4/en/replication-howto-slavebaseconfig.html
Each replica must have a unique server ID, as specified by the server_id system variable. If you are setting up multiple replicas, each one must have a unique server_id value that differs from that of the source and from any of the other replicas.
https://dev.mysql.com/doc/refman/8.4/en/replication-options.html
The following sections contain information about mysqld options and server variables that are used in replication and for controlling the binary log. Options and variables for use on sources and replicas are covered separately, as are options and ...
MySQL 8.4 Reference Manual :: 19.2.1.3 Determination of Safe and Unsafe Statements in Binary Logging
https://dev.mysql.com/doc/refman/8.4/en/replication-rbr-safe-unsafe.html
The “safeness” of a statement in MySQL replication refers to whether the statement and its effects can be replicated correctly using statement-based format. If this is true of the statement, we refer to the statement as safe; otherwise, we ...