PDF (US Ltr)
- 41.8Mb
PDF (A4)
- 41.9Mb
Man Pages (TGZ)
- 272.4Kb
Man Pages (Zip)
- 378.4Kb
Info (Gzip)
- 4.2Mb
Info (Zip)
- 4.2Mb
Search Results
https://dev.mysql.com/doc/refman/9.7/en/range-optimization.html
For EXPLAIN FOR CONNECTION, the output changes as follows if index dives are skipped: For traditional output, the rows and filtered values are NULL. Without FOR CONNECTION, EXPLAIN output does not change when index dives are skipped. The range ...
https://dev.mysql.com/doc/refman/9.7/en/replication-delayed.html
replication_connection_status: current status of the connection to the source, provides information on the last and current transaction the connection thread queued into the relay log. MySQL supports delayed replication such that a replica server ...
https://dev.mysql.com/doc/refman/9.7/en/replication-features-shutdowns.html
When a replica loses its connection to the source, the replica tries to reconnect immediately and retries periodically if that fails. A replica also is able to deal with network connectivity outages. It is safe to shut down a replication source ...
https://dev.mysql.com/doc/refman/9.7/en/replication-gtids-auto-positioning.html
When a replica has GTIDs enabled (GTID_MODE=ON, ON_PERMISSIVE, or OFF_PERMISSIVE ) and the SOURCE_AUTO_POSITION option enabled, auto-positioning is activated for connection to the source. The source must have GTID_MODE=ON set in order for the ...
https://dev.mysql.com/doc/refman/9.7/en/replication-gtids-howto.html
If you are starting with new servers, see Section 19.1.2.3, “Creating a User for Replication” for information about adding a specific user for replication connections and Section 19.1.2.1, “Setting the Replication Source Configuration” for ... This section describes a process for configuring and starting GTID-based replication in MySQL ...
https://dev.mysql.com/doc/refman/9.7/en/replication-implementation.html
Each replica that connects to the source requests a copy of the binary log. Because each replica is independent, the replaying of the changes from the source's binary log occurs independently on each replica that is connected to the source.
https://dev.mysql.com/doc/refman/9.7/en/replication-multi-source-monitoring.html
To monitor the connection status of all channels: mysql> SELECT * FROM replication_connection_status\G; *************************** 1. To monitor the connection status of a named channel, use a WHERE CHANNEL_NAME=channel clause: mysql> SELECT * FROM ... To monitor the status of replication channels the following options exist: Using the replication Performance Schema ...
https://dev.mysql.com/doc/refman/9.7/en/replication-options.html
If the server ID is set to 0, binary logging takes place, but a source with a server ID of 0 refuses any connections from replicas, and a replica with a server ID of 0 refuses to connect to a source. The following sections contain information about ...
https://dev.mysql.com/doc/refman/9.7/en/replication-solutions-backups-rawdata.html
If you want to be able to restore the data and operate as a replica (for example, in the event of failure of the replica), in addition to the data, you need to have the replica's connection metadata repository and applier metadata repository, and ...
https://dev.mysql.com/doc/refman/9.7/en/replication-solutions-backups-read-only.html
Note The instructions in this section place the server to be backed up in a state that is safe for backup methods that get the data from the server, such as mysqldump (see Section 6.5.4, “mysqldump — A Database Backup Program”). You should not ...