binlog format MIXED and temp table causes inconsistency

[Teemu Ollakka]

To reproduce, start cluster and run the following sequence of commands against one of the nodes:

use test;
drop table if exists t1;
set binlog_format=MIXED;
create temporary table t1 (a int) engine=innodb;
drop table t1;
create table t1 (a int not null, b int not null, c blob not null, d int not null, e int, primary key (a,b,c(255),d)) engine=innodb;
insert into t1 values (2,2,"b",2,2),(1,1,"a",1,1),(3,3,"ab",3,3);
drop table t1;

This causes inconsistency, table t1 is not dropped on slave nodes. By inspecting binlog it looks like the last drop table is translated to drop temporary table:

DROP TEMPORARY TABLE IF EXISTS `t1` /* generated by server */

However, if the insert is not executed, the last drop table is executed on slaves properly and no inconsistency occurs.

[Krunal Bauskar (krunal-bauskar)]

binlog_format=MIXED is not supported so using it can lead to inconsistency.
We can't warrant against unsupported feature.

[Shahriyar Rzayev (rzayev-sehriyar)]

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-513