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-quick-start.html
These tables provide event names and explanatory notes or status information. This section briefly introduces the Performance Schema with examples that show how to use it. For additional examples, see Section 29.19, “Using the Performance Schema ...
https://dev.mysql.com/doc/refman/8.0/en/persisted-system-variables.html
However, as noted previously, removing this file results in a loss of all persisted settings. Note A keyring component must be enabled on the MySQL Server instance to support secure storage for persisted system variable values, rather than a keyring ... The MySQL server maintains system variables that configure its ...
https://dev.mysql.com/doc/refman/8.0/en/processlist-access.html
Note As of MySQL 8.0.22, an alternative implementation for SHOW PROCESSLIST is available based on the Performance Schema processlist table, which, like the threads table, does not require a mutex and has better performance characteristics. Note ...
https://dev.mysql.com/doc/refman/8.0/en/replica-logs-status.html
For cloning operations, note that when the replication metadata repositories are created as tables, they are copied to the recipient during a cloning operation, but when they are created as files, they are not copied. Note that for ... A replica ...
https://dev.mysql.com/doc/refman/8.0/en/replication-administration-skip.html
Note that if binary logging is in use on this replica, the empty transaction enters the replication stream if the replica becomes a source or primary in the future. One event normally corresponds to one SQL statement in the binary log, but note that ... If replication stops due to an issue with an event in a replicated transaction, you can resume replication by skipping the failed transaction on the ...
https://dev.mysql.com/doc/refman/8.0/en/replication-asynchronous-connection-failover-replica.html
Note A server participating in a group in single-primary mode must be started with --skip-replica-start=ON. Note that if there is more than one channel with SOURCE_CONNECTION_AUTO_FAILOVER=1 , the member action covers all the channels, so they ...
https://dev.mysql.com/doc/refman/8.0/en/replication-features-transactions.html
Note A mixed statement is unrelated to mixed binary logging format. Note For restrictions that apply specifically to XA transactions, see Section 15.3.8.3, “Restrictions on XA Transactions”. In general, you should avoid transactions that update ...
https://dev.mysql.com/doc/refman/8.0/en/replication-formats.html
You should note that NDB Cluster Replication always uses row-based replication, and that the NDB storage engine is incompatible with statement-based replication. Note Changing the binary logging format (binlog_format system variable) is deprecated ... Replication works because events written to the binary log are read from the source and then processed on the ...
https://dev.mysql.com/doc/refman/8.0/en/replication-howto-masterbaseconfig.html
Note that if a value of 0 (which was the default in earlier releases) was set previously for the server ID, you must restart the server to initialize the source with your new nonzero server ID. Note The following options also have an impact on the ... To configure a source to use binary log file position based replication, you must ensure that binary logging is enabled, and establish a unique server ...
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 ...