PDF (US Ltr)
- 35.1Mb
PDF (A4)
- 35.2Mb
Man Pages (TGZ)
- 256.4Kb
Man Pages (Zip)
- 361.3Kb
Info (Gzip)
- 3.4Mb
Info (Zip)
- 3.4Mb
Search Results
https://dev.mysql.com/doc/refman/5.7/en/replication-delayed.html
To inspect what the database looked like long ago, without having to reload a backup. For example, if the delay is one week and the DBA needs to see what the database looked like before the last few days' worth of development, the delayed replica ...
https://dev.mysql.com/doc/refman/5.7/en/replication-features-charset.html
The following applies to replication between MySQL servers that use different character sets: If the source has databases with a character set different from the global character_set_server value, you should design your CREATE TABLE statements so ...A good workaround is to state the character set and collation explicitly in CREATE TABLE ...
https://dev.mysql.com/doc/refman/5.7/en/replication-features-create-if-not-exists.html
IF NOT EXISTS statements are replicated: Every CREATE DATABASE IF NOT EXISTS statement is replicated, whether or not the database already exists on the source. Similarly, every CREATE TABLE IF NOT EXISTS statement without a SELECT is replicated, ...
https://dev.mysql.com/doc/refman/5.7/en/replication-features-drop-if-exists.html
The DROP DATABASE IF EXISTS, DROP TABLE IF EXISTS, and DROP VIEW IF EXISTS statements are always replicated, even if the database, table, or view to be dropped does not exist on the source. This is to ensure that the object to be dropped no longer ...
https://dev.mysql.com/doc/refman/5.7/en/replication-howto.html
There are a number of different methods for setting up replication, and the exact method to use depends on how you are setting up replication, and whether you already have data in the database on the source. If you do not stop the execution of ...
https://dev.mysql.com/doc/refman/5.7/en/replication-problems.html
If you have followed the instructions but your replication setup is not working, the first thing to do is check the error log for messages. Many users have lost time by not doing this soon enough after encountering problems. If you cannot tell from ...
https://dev.mysql.com/doc/refman/5.7/en/replication-rbr-usage.html
When binary log events were written in row-based format and you want to read or recover from a replication or database failure you can use this command to read contents of the binary log. When using row-based logging, if the replica server is ...
https://dev.mysql.com/doc/refman/5.7/en/replication-solutions-unexpected-replica-halt.html
As a table, updates to the applier metadata repository are committed together with the transactions, meaning that the replica's progress information recorded in that repository is always consistent with what has been applied to the database, even in ... In order for replication to be resilient to unexpected halts of the server (sometimes described as crash-safe) it must be possible for the replica to recover its state before ...
https://dev.mysql.com/doc/refman/5.7/en/replication-solutions.html
For performance or data distribution reasons, you may want to replicate different databases to different replicas. See Section 16.3.5, “Replicating Different Databases to Different Replicas” As the number of replicas increases, the load on the ... Replication can be used in many different environments for a range of ...
https://dev.mysql.com/doc/refman/5.7/en/rewriter-query-rewrite-plugin.html
The Rewriter plugin uses a database named query_rewrite containing a table named rewrite_rules. The query_rewrite database contains a stored procedure named flush_rewrite_rules() that loads the contents of the rules table into the plugin. MySQL ...