innodb/innodb caused problems for wsrep-5.5 debug build in part:
create table t1 (a int not null , b int, primary key (a)) engine = innodb;
create table t2 (a int not null , b int, primary key (a)) engine = myisam;
insert into t1 VALUES (1,3) , (2,3), (3,3);
select * from t1;
insert into t2 select * from t1;
...where the insert..select from innodb table to myisam table caused debug level assert during binlog commit. Problem was that wsrep_cleanup_transaction had wiped out trx cache earlier (but not stmt cache)
innodb/innodb caused problems for wsrep-5.5 debug build in part:
create table t1 (a int not null , b int, primary key (a)) engine = innodb;
create table t2 (a int not null , b int, primary key (a)) engine = myisam;
insert into t1 VALUES (1,3) , (2,3), (3,3);
select * from t1;
insert into t2 select * from t1;
...where the insert..select from innodb table to myisam table caused debug level assert during binlog commit. Problem was that wsrep_cleanup_ transaction had wiped out trx cache earlier (but not stmt cache)
Fix was pushed in wsrep-5.5, in revision: http:// bazaar. launchpad. net/~codership/ codership- mysql/wsrep- 5.5/revision/ 3942
and, as said, wsrep-5.6 is not affected by this