Rechercher dans le manuel MySQL
17.4.1.13 Replication and FLUSH
Some forms of the FLUSH statement
are not logged because they could cause problems if replicated
to a slave: FLUSH LOGS and
FLUSH TABLES WITH READ LOCK. For
a syntax example, see Section 13.7.7.3, “FLUSH Syntax”. The
FLUSH TABLES,
ANALYZE TABLE,
OPTIMIZE TABLE, and
REPAIR TABLE statements are
written to the binary log and thus replicated to slaves. 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 the
mysql database and update those tables
directly without using GRANT, you
must issue a FLUSH PRIVILEGES on
the slaves to put the new privileges into effect. In addition,
if you use FLUSH TABLES when
renaming a MyISAM table that is part of a
MERGE table, you must issue
FLUSH TABLES manually on the
slaves. These statements are written to the binary log unless
you specify NO_WRITE_TO_BINLOG or its alias
LOCAL.
Document created the 26/06/2006, last modified the 26/10/2018
Source of the printed document:https://www.gaudry.be/en/mysql-rf-replication-features-flush.html
The infobrol is a personal site whose content is my sole responsibility. The text is available under CreativeCommons license (BY-NC-SA). More info on the terms of use and the author.
References
These references and links indicate documents consulted during the writing of this page, or which may provide additional information, but the authors of these sources can not be held responsible for the content of this page.
The author This site is solely responsible for the way in which the various concepts, and the freedoms that are taken with the reference works, are presented here. Remember that you must cross multiple source information to reduce the risk of errors.
