PDF (A4) - 35.2Mb
Man Pages (TGZ) - 256.4Kb
Man Pages (Zip) - 361.2Kb
Info (Gzip) - 3.4Mb
Info (Zip) - 3.4Mb
MySQL Globalization
MySQL Information Schema
MySQL Installation Guide
MySQL and Linux/Unix
MySQL and macOS
MySQL Partitioning
MySQL Performance Schema
MySQL Replication
Using the MySQL Yum Repository
MySQL Restrictions and Limitations
Security in MySQL
MySQL and Solaris
Building MySQL from Source
Starting and Stopping MySQL
MySQL Tutorial
MySQL and Windows
MySQL NDB Cluster 7.5
Some forms of theFLUSH statement are not logged because they could cause problems if replicated to a replica:FLUSH LOGS andFLUSH TABLES WITH READ LOCK. For a syntax example, seeSection 13.7.6.3, “FLUSH Statement”. TheFLUSH TABLES,ANALYZE TABLE,OPTIMIZE TABLE, andREPAIR TABLE statements are written to the binary log and thus replicated to replicas. This is not normally a problem because these statements do not modify table data.
However, this behavior can cause difficulties under certain circumstances. If you replicate the privilege tables in themysql database and update those tables directly without usingGRANT, you must issue aFLUSH PRIVILEGES on the replicas to put the new privileges into effect. In addition, if you useFLUSH TABLES when renaming aMyISAM table that is part of aMERGE table, you must issueFLUSH TABLES manually on the replicas. These statements are written to the binary log unless you specifyNO_WRITE_TO_BINLOG or its aliasLOCAL.
PDF (A4) - 35.2Mb
Man Pages (TGZ) - 256.4Kb
Man Pages (Zip) - 361.2Kb
Info (Gzip) - 3.4Mb
Info (Zip) - 3.4Mb
MySQL Globalization
MySQL Information Schema
MySQL Installation Guide
MySQL and Linux/Unix
MySQL and macOS
MySQL Partitioning
MySQL Performance Schema
MySQL Replication
Using the MySQL Yum Repository
MySQL Restrictions and Limitations
Security in MySQL
MySQL and Solaris
Building MySQL from Source
Starting and Stopping MySQL
MySQL Tutorial
MySQL and Windows
MySQL NDB Cluster 7.5