Bug #95439 | FLUSH LOGS is not added to binlog | ||
---|---|---|---|
Submitted: | 21 May 2019 1:41 | Modified: | 21 May 2019 17:56 |
Reporter: | Dieter Adriaenssens | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server: Replication | Severity: | S3 (Non-critical) |
Version: | 5.7.26 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[21 May 2019 1:41]
Dieter Adriaenssens
[21 May 2019 4:55]
MySQL Verification Team
Hello Dieter, Thank you for the report. This is documented behavior, quoting from manual "FLUSH LOGS, FLUSH BINARY LOGS, FLUSH TABLES WITH READ LOCK (with or without a table list), and FLUSH TABLES tbl_name ... FOR EXPORT are not written to the binary log in any case because they would cause problems if replicated to a slave. " - https://dev.mysql.com/doc/refman/5.7/en/flush.html regards, Umesh
[21 May 2019 17:56]
Dieter Adriaenssens
Thanks for clarifying, I guess I missed this remark when reading the documentation.