PDF (US Ltr)
- 35.0Mb
PDF (A4)
- 35.1Mb
Man Pages (TGZ)
- 255.5Kb
Man Pages (Zip)
- 360.4Kb
Info (Gzip)
- 3.4Mb
Info (Zip)
- 3.4Mb
Search Results
https://dev.mysql.com/doc/refman/5.7/en/query-cache-operation.html
Note The query cache is deprecated as of MySQL 5.7.20, and is removed in MySQL 8.0. This section describes how the query cache works when it is operational. Section 8.10.3.3, “Query Cache Configuration”, describes how to control whether it is ...
https://dev.mysql.com/doc/refman/5.7/en/replication-administration-pausing.html
You can stop and start replication on the replica using the STOP SLAVE and START SLAVE statements. The replication I/O thread continues to read events from the source but they are not executed. This makes it easier for the replica to catch up when ...
https://dev.mysql.com/doc/refman/5.7/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 SLAVE STATUS statement, which you must execute on each replica, ...
https://dev.mysql.com/doc/refman/5.7/en/replication-delayed.html
MySQL 5.7 supports delayed replication such that a replica server deliberately lags behind the source by at least a specified amount of time. Use the MASTER_DELAY option for CHANGE MASTER TO to set the delay to N seconds: CHANGE MASTER TO ...
https://dev.mysql.com/doc/refman/5.7/en/replication-features-functions.html
Certain functions do not replicate well under some conditions: The USER(), CURRENT_USER() (or CURRENT_USER), UUID(), VERSION(), and LOAD_FILE() functions are replicated without change and thus do not work reliably on the replica unless row-based ...
https://dev.mysql.com/doc/refman/5.7/en/replication-features-memory.html
When a replication source server shuts down and restarts, its MEMORY tables become empty. To replicate this effect to replicas, the first time that the source uses a given MEMORY table after startup, it logs an event that notifies replicas that the ...
https://dev.mysql.com/doc/refman/5.7/en/replication-features-temptables.html
The discussion in the following paragraphs does not apply when binlog_format=ROW because, in that case, temporary tables are not replicated; this means that there are never any temporary tables on the replica to be lost in the event of an unplanned ...
https://dev.mysql.com/doc/refman/5.7/en/replication-features-views.html
Views are filtered by their own name, not by the tables they refer to. This means that a view can be replicated to the replica even if the view contains a table that would normally be filtered out by replication-ignore-table rules. Care should ...
https://dev.mysql.com/doc/refman/5.7/en/replication-multi-source-configuration.html
A multi-source replication topology requires at least two sources and one replica configured. In these tutorials, we assume you have two sources source1 and source2, and a replica replicahost. The replica replicates one database from each of the ...
https://dev.mysql.com/doc/refman/5.7/en/replication-multi-source.html
MySQL multi-source replication enables a replica to receive transactions from multiple immediate sources in parallel. In a multi-source replication topology, a replica creates a replication channel for each source that it should receive ...