[MDEV-19800] Document explicitly that GTID-based replication works with all binlog_fromat values Created: 2019-06-19 Updated: 2023-12-15 |
|
| Status: | Open |
| Project: | MariaDB Server |
| Component/s: | Documentation, Replication |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major |
| Reporter: | Valerii Kravchuk | Assignee: | Joe Cotellese |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | GTID, binlog | ||
| Issue Links: |
|
||||
| Description |
|
It seems users of MySQL often assume that one must use row-based logging to use GTID-based replication. I think adding explicit section to this KB page: https://mariadb.com/kb/en/library/gtid/ explaining that in MariaDB GTID-based replication works with STATEMENT, MIXED and ROW formats (and documenting restrictions in each format, if any) would help them to get clear understanding that these features are "ortogonal" and there is no need to force ROW-based logging on master just because slaves are using GTID-based replication. |
| Comments |
| Comment by Julien Fritsch [ 2021-09-22 ] |
|
jacob.moorman from our discussion, I decided to reassign Kenneth's ticket to you? |