Bug #85733 | CREATE USER IF NOT EXISTS should always be written to the binlogs | ||
---|---|---|---|
Submitted: | 31 Mar 2017 8:50 | Modified: | 3 Oct 2017 22:19 |
Reporter: | Simon Mudd (OCA) | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Replication | Severity: | S3 (Non-critical) |
Version: | 5.7.17 | OS: | Any |
Assigned to: | CPU Architecture: | Any | |
Tags: | binlogs, CREATE USER IF NOT EXISTS, replication |
[31 Mar 2017 8:50]
Simon Mudd
[31 Mar 2017 11:14]
MySQL Verification Team
Hello Simon, Thank you for the report and feedback! Thanks, Umesh
[31 Mar 2017 11:14]
MySQL Verification Team
test results
Attachment: 85733_5.7.17.results (application/octet-stream, text), 10.13 KiB.
[2 Apr 2017 8:40]
MySQL Verification Team
on 5.7 this also affects ALTER USER IF EXISTS ..... it doesn't get written to the binlog if the user didn't exist. MySQL 8.0 seems to behave as we expect, and writes to binlog.
[3 Oct 2017 22:19]
Paul DuBois
Posted by developer: Fixed in 5.7.21, 8.0.4. CREATE USER IF NOT EXISTS was not written to the binary log if the user existed. This could result in inconsistent replication behavior if the user did not exist on slave servers. A similar issue occurred for ALTER USER IF EXISTS. To avoid inconsistencies, these statements now are written to the binary log.