mirror of
https://github.com/MariaDB/server.git
synced 2025-01-18 04:53:01 +01:00
13af58aab6
when one connection had done FLUSH TABLES WITH READ LOCK, some updates, and then COMMIT, it was accepted but my_error() was called and so, while client got no error, error was logged in binlog. We now don't call my_error() in this case; we assume the connection know what it does. This problem was specific to 4.0.21. The change is needed to make replication work with existing versions of innobackup.
13 lines
287 B
Text
13 lines
287 B
Text
slave stop;
|
|
drop table if exists t1,t2,t3,t4,t5,t6,t7,t8,t9;
|
|
reset master;
|
|
reset slave;
|
|
drop table if exists t1,t2,t3,t4,t5,t6,t7,t8,t9;
|
|
slave start;
|
|
create table t1 (a int) type=innodb;
|
|
begin;
|
|
insert into t1 values(1);
|
|
flush tables with read lock;
|
|
commit;
|
|
unlock tables;
|
|
drop table t1;
|