BUG#11763471 BUG#56184 Rolled back transaction without non-transactional table updated was binlogged
BUG#11763126 BUG#55798 Slave SQL retry on transaction inserts extra data into non-transaction table

BUG#56184
---------
The transaction modified non-transactional table will be binlogged with
ROLLBACK if it rolls back on master. It includes the case that all
statements which modified non-transactional table are binlogged outside
the transaction. Example:

  BEGIN
  INSERT INTO trans-table;
  INSERT INTO non-trans-table;
  ROLLBACK

This will be binlogged as:

  BEGIN
  INSERT INTO non-trans-table;
  COMMIT
  BEGIN
  INSERT INTO trans-table;
  ROLLBACK;

All statements in the second binlogged transaction modify only transactional
tables and are rolled back safely on master. So the second transaction should
not be binlogged.

After 5.5, there are two caches for binary logs, a transactional cache and a
statement cache. When executing a transaction, statements that modified only
transactional tables are always...