Comments - Replication and Binary Log System Variables
Content reproduced on this site is the property of its respective owners,
and this content is not reviewed in advance by MariaDB. The views, information and opinions
expressed by this content do not necessarily represent those of MariaDB or any other party.
When we change auto_increment_increment and/or auto_increment_offset online with SET GLOBAL this affects only new connections. Old existing connections still work with the old values for aii and aio.
This is not really what I expected...
Hallo, Oli!
That's because this type of variables belongs to the @@global/@@session class. And its semantics was settled long time ago so the session first initializes its private instance from the current value of the overall system-wide @@global "parent". And *then* it is free to change its @@session. So if one would prefer a behavior like you did then the freedom of making changes obviously suffers a lot. In such use case the variable would had to be defined as a pure @@global. However, I don't see as impossible to merge two perceptions with introduction of a magic value to the global instance of the @@global/@@session that would turn it into the pure @@global class.
"replicate_do_table
Description: Slave threads will be restricted to replicating the specified tables, provided in comma-delimited format. ... The directive does not accept a comma-delimited list..."
That's fairly contradictory...
Thanks, fixed.
binlog_row_image parameter introduced in 10.1.6 to provide the ability to limit which rows are written to the log. On previous versions, was the default behavior to always include all columns?
Found the answer here, it does log all columns (in MySQL, and by logical extension MariaDB) before this parameter was supported:
https://dev.mysql.com/doc/refman/5.6/en/replication-options-binary-log.html#sysvar_binlog_row_image quoted below:
"The default value is full. In MySQL 5.5 and earlier, full row images are always used for both before images and after images."
It maybe obvious to some, but it took me hours of research to discover that the "name" needs to include the database, e.g. replicate_wild_ignore_table = "db1.table2%" or, replicate_wild_ignore_table = "%.table2%"
binlog-do-db is not a system variable - it isn't exposed by SHOW VARIABLES. It is documented on the list of mysqld options. But I agree, it's natural to be mentioned here as well and should be added.
missing binlog_do_db on this page