Search Results
https://dev.mysql.com/doc/refman/8.4/en/performance-schema-tp-thread-state-table.html
TP_GROUP_ID and TP_THREAD_NUMBER together provide a unique key within the table. 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 ...
https://dev.mysql.com/doc/refman/8.4/en/performance-schema-user-defined-functions-table.html
The user_defined_functions table has these indexes: Primary key on (UDF_NAME) TRUNCATE TABLE is not permitted for the user_defined_functions table. The user_defined_functions table contains a row for each loadable function registered automatically ...
https://dev.mysql.com/doc/refman/8.4/en/performance-schema-user-variable-tables.html
The user_variables_by_thread table has these indexes: Primary key on (THREAD_ID, VARIABLE_NAME) TRUNCATE TABLE is not permitted for the user_variables_by_thread table. The Performance Schema provides a user_variables_by_thread table that exposes ...
https://dev.mysql.com/doc/refman/8.4/en/performance-schema-users-table.html
The users table has these indexes: Primary key on (USER) . The users table contains a row for each user who has connected to the MySQL server. For each user name, the table counts the current and total number of connections. To set the table size ...
https://dev.mysql.com/doc/refman/8.4/en/replication-administration-status.html
The most common task when managing a replication process is to ensure that replication is taking place and that there have been no errors between the replica and the source. The SHOW REPLICA STATUS statement, which you must execute on each replica, ...
https://dev.mysql.com/doc/refman/8.4/en/replication-bugs.html
For example, if you update the replica outside of the replication threads, the data goes out of synchrony, and you can have unique key violations on updates. When you have determined that there is no user error involved, and replication still ...
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-failover.html
GTIDs play a key role in applying changes to the database: the server automatically skips any transaction having an identifier which the server recognizes as one that it has processed before. There are a number of techniques when using MySQL ...
https://dev.mysql.com/doc/refman/8.4/en/replication-gtids-howto.html
The key steps in this startup process for the simplest possible GTID replication topology, consisting of one source and one replica, are as follows: If replication is already running, synchronize both servers by making them read-only. This section ...
https://dev.mysql.com/doc/refman/8.4/en/replication-howto-slaveinit.html
To set up the replica to communicate with the source for replication, configure the replica with the necessary connection information. To do this, on the replica, execute the following CHANGE REPLICATION SOURCE TO statement, replacing the option ...