mysql binlog_row_image的选择

其含义为

The default value is full. In MySQL 5.5 and earlier, full row images are always used for both before images and after images. If you need to replicate from a MySQL 5.6 (or later) master to a slave running a previous version of MySQL, the master should always use this value.

When using minimal or noblob, deletes and updates are guaranteed to work correctly for a given table if and only if the following conditions are true for both the source and destination tables:

• All columns must be present and in the same order; each column must use the same data type as its counterpart in the other table.

• The tables must have identical primary key definitions.

(In other words, the tables must be identical with the possible exception of indexes that are not part of the tables' primary keys.)

If these conditions are not met, it is possible that the primary key column values in the destination table may prove insufficient to provide a unique match for a delete or update. In this event, no warning or error is issued; the master and slave silently diverge, thus breaking consistency.

Setting this variable has no effect when the binary logging format is STATEMENT. When binlog_format is MIXED, the setting for binlog_row_image is applied to changes that are logged using row-based format, but this setting no effect on changes logged as statements.

Setting binlog_row_image on either the global or session level does not cause an implicit commit; this means that this variable can be changed while a transaction is in progress without affecting the transaction.

一般来说，我们认为主从配置的时候，表结构一定是相同的，否则肯定就借助第三方的逻辑复制工具了。所以，对于某些update很频繁的系统，尤其是金融行业大量宽表设计的时候，这个值应该设置为minimal以最大化性能。

最近因为风控剥离到备库，使用了replicate-rewrite-db和replicate-wild-do-table（因为某些规范的原因）被搞死了，每天有异常数据，看来这特征还是不够稳定，而且5.6好像就不生效。