[MDEV-15783] Row-based replication did not log selectively as advertised in docs. Docs changed to reflect actual behavior. Created: 2018-04-04 Updated: 2020-08-25 Resolved: 2018-04-04 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Documentation |
| Affects Version/s: | N/A |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Trivial |
| Reporter: | Juan | Assignee: | Ian Gilfillan |
| Resolution: | Not a Bug | Votes: | 0 |
| Labels: | logging, replication | ||
| Environment: |
CentOS Linux release 7.4.1708 |
||
| Issue Links: |
|
||||||||
| Description |
|
Row-based replication documents claimed: The reality is different, with row-based replication actually logging DDL statements to every database as long as any database is in use ("use <database-name>;"), while correctly ignoring DML statements to ignored databases. When no default database has been specified (with "use <database-name>;") all statements to logged databases are logged, and all statements to ignored databases ignored, as expected. I have updated the documentation to reflect the observed server behavior. |
| Comments |
| Comment by Elena Stepanova [ 2018-04-04 ] |
|
juan.vera, you are mixing up concepts. The article talks about row-based (or statement-based) logging, not about binlog_format=row or otherwise. The text before was quite accurate. There is no "row-based logging" for DDL. DDL is always logged in statement format, regardless of the current value of binlog_format. greenman, could you please make it right? Not necessarily revert to exactly how it was before, maybe add a note more clearly explaining the difference. |
| Comment by Juan [ 2018-04-04 ] |
|
Ok. Reverted. |
| Comment by Ian Gilfillan [ 2018-04-04 ] |
|
Thanks for restoring - I can see how the confusion could arise, so will look at making it clearer. |
| Comment by Juan [ 2018-04-04 ] |
|
Thanks, Ian. |