MySQL半一致性读导致语句级Binlog复制错误1111

MySQL事务的隔离级别为read committed(或以下)，或者设置了innodb_locks_unsafe_for_binlog参数会启用半一致性读特性。

半一致性读参考: http://www.linuxidc.com/Linux/2017-02/140844.htm

MySQL官方文档refman-5.6-en.a4.pdf 1833页 关于innodb_locks_unsafe_for_binlog参数

对于半一致性读，我感觉一个是违反两阶段锁，将不符合条件记录的行级锁提前释放。另一个是Update的行如果被锁定，则返回一个最近提交的版本。

官方文档原文如下：
Enabling innodb_locks_unsafe_for_binlog has additional effects:
? For UPDATE or DELETE statements, InnoDB holds locks only for rows that it updates or deletes.
Record locks for nonmatching rows are released after MySQL has evaluated the WHERE condition.
This greatly reduces the probability of deadlocks, but they can still happen.

? For UPDATE statements, if a row is already locked, InnoDB performs a “semi-consistent” read,
returning the latest committed version to MySQL so that MySQL can determine whether the row
matches the WHERE condition of the UPDATE. If the row matches (must be updat