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-rwlock-instances-table.html
The rwlock_instances table lists all the rwlock (read write lock) instances seen by the Performance Schema while the server executes. An rwlock is a synchronization mechanism used in the code to enforce that threads at a given time can have access ...
https://dev.mysql.com/doc/refman/8.0/en/performance-schema-startup-configuration.html
To use the MySQL Performance Schema, it must be enabled at server startup to enable event collection to occur. To enable or disable it explicitly, start the server with the performance_schema variable set to an appropriate value. For example, use ...
https://dev.mysql.com/doc/refman/8.0/en/performance-schema-thread-pool-tables.html
Note The Performance Schema tables described here are available as of MySQL 8.0.14. Prior to MySQL 8.0.14, use the corresponding INFORMATION_SCHEMA tables instead; see Section 28.5, “INFORMATION_SCHEMA Thread Pool Tables”. The following ...
https://dev.mysql.com/doc/refman/8.0/en/postinstallation.html
This section discusses tasks that you should perform after installing MySQL: If necessary, initialize the data directory and create the MySQL grant tables. For some MySQL installation methods, data directory initialization may be done for you ...
https://dev.mysql.com/doc/refman/8.0/en/replication-asynchronous-connection-failover-source.html
To activate asynchronous connection failover for a replication channel set SOURCE_CONNECTION_AUTO_FAILOVER=1 on the CHANGE REPLICATION SOURCE TO statement (from MySQL 8.0.23) or CHANGE MASTER TO statement (before MySQL 8.0.23) for the channel. GTID ...
https://dev.mysql.com/doc/refman/8.0/en/replication-features-timeout.html
The global value of the system variable replica_transaction_retries (from MySQL 8.0.26) or slave_transaction_retries (before MySQL 8.0.26) sets the maximum number of times for applier threads on a single-threaded or multithreaded replica to ...
https://dev.mysql.com/doc/refman/8.0/en/replication-gtids-auto-positioning.html
GTIDs replace the file-offset pairs previously required to determine points for starting, stopping, or resuming the flow of data between source and replica. When GTIDs are in use, all the information that the replica needs for synchronizing with ...
https://dev.mysql.com/doc/refman/8.0/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.0/en/replication-mode-change-online-verify-transactions.html
This section explains how to monitor a replication topology and verify that all anonymous transactions have been replicated. This is helpful when changing the replication mode online as you can verify that it is safe to change to GTID transactions.
https://dev.mysql.com/doc/refman/8.0/en/replication-sbr-rbr.html
For most users, the mixed replication format should provide the best combination of data integrity and performance. If, however, you want to take advantage of the features specific to the statement-based or row-based replication format when ...