| Bug #83048 | PARTIALLY FAILED USER MANAGEMENT STMT FAILS TO CONSUME GTID ON BINLOGLESS SLAVE | ||
|---|---|---|---|
| Submitted: | 20 Sep 2016 7:50 | Modified: | 31 Mar 2017 16:56 |
| Reporter: | João Gramacho | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: Replication | Severity: | S3 (Non-critical) |
| Version: | 5.7 | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
[31 Mar 2017 16:56]
Paul DuBois
Posted by developer: Noted in 5.7.18, 8.0.1 changelogs. A partially failed CREATE USER, RENAME USER, or ALTER USER statement was not correctly consuming an auto-generated or specified GTID when binary logging was disabled.
Description: This bug is a follow up of BUG#21686749, fixing CREATE USER, RENAME USER and ALTER USER cases. How to repeat: Apply the attached diff file to extend an existent test case ("main.no_binlog_gtid_next_partially_failed_stmts") to cover also CREATE USER, RENAME USER and ALTER USER cases. Suggested fix: Handle partially failed CREATE USER, RENAME USER and ALTER USER statements the same way BUG#21686749 handled all other cases.