Bug #102100 DCL commands are not replicated witch certain replication filters
| Submitted: | 31 Dec 2020 10:58 | Modified: | 31 Dec 2020 12:01 |
|---|---|---|---|
| Reporter: | Sveta Smirnova (OCA) | Email Updates: | |
| Status: | Verified | Impact on me: | |
| Category: | MySQL Server: Replication | Severity: | S3 (Non-critical) |
| Version: | 5.7.31, 8.0.22, 5.7.32 | OS: | Any |
| Assigned to: | CPU Architecture: | Any |
[31 Dec 2020 10:58]
Sveta Smirnova
[31 Dec 2020 10:59]
Sveta Smirnova
Test case for MTR
Attachment: bug102100.test (application/octet-stream, text), 731 bytes.
[31 Dec 2020 12:01]
MySQL Verification Team
Hello Sveta, Thank you for the report and feedback. Verified as described. regards, Umesh
[7 Jun 2024 18:20]
Aditya Prasad
As best I can tell, DCL works like DDL with respect to replication. It is logged in statement form, which means that db-level filters depend on the default db but table-level filters depend on the table/schema name -- in this case, mysql.user. Is this understanding correct?
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.054 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.