PDF (US Ltr)
- 43.3Mb
PDF (A4)
- 43.4Mb
Man Pages (TGZ)
- 297.2Kb
Man Pages (Zip)
- 402.4Kb
Info (Gzip)
- 4.3Mb
Info (Zip)
- 4.3Mb
Search Results
https://dev.mysql.com/doc/refman/8.0/en/performance-schema-tp-thread-group-stats-table.html
Note The Performance Schema table described here is available as of MySQL 8.0.14. Prior to MySQL 8.0.14, use the corresponding INFORMATION_SCHEMA table instead; see Section 28.5.3, “The INFORMATION_SCHEMA TP_THREAD_GROUP_STATS Table”. The ...
https://dev.mysql.com/doc/refman/8.0/en/performance-schema-tp-thread-state-table.html
TP_GROUP_ID and TP_THREAD_NUMBER together provide a unique key within the table. Note The Performance Schema table described here is available as of MySQL 8.0.14. Prior to MySQL 8.0.14, use the corresponding INFORMATION_SCHEMA table instead; see ...
https://dev.mysql.com/doc/refman/8.0/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.0/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.0/en/replication-compatibility.html
For example, foreign key names longer than 64 characters are no longer supported from MySQL 8.0. MySQL supports replication from one release series to the next higher release series. For example, you can replicate from a source running MySQL 5.6 to ...
https://dev.mysql.com/doc/refman/8.0/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.0/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.0/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. You must be able to connect to the source MySQL server using TCP/IP. The CHANGE REPLICATION SOURCE TO | CHANGE ...
https://dev.mysql.com/doc/refman/8.0/en/replication-mode-change-online-concepts.html
Before setting the replication mode of an online server, it is important to understand some key concepts of replication. This section explains these concepts and is essential reading before attempting to modify the replication mode of an online ...
https://dev.mysql.com/doc/refman/8.0/en/replication-multi-source-monitoring.html
This enables you to write complex queries based on Channel_Name as a key. To monitor the status of replication channels the following options exist: Using the replication Performance Schema tables. By default, if the FOR CHANNEL channel clause is ...