mirror of
https://github.com/MariaDB/server.git
synced 2025-01-17 20:42:30 +01:00
c5f9a412ce
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. sql/lock.cc: If a connection has done FLUSH TABLES WITH READ LOCK and now is doing COMMIT, don't give error (applies only if it's the same connection; others' COMMITs are still blocked).
17 lines
337 B
Text
17 lines
337 B
Text
source include/master-slave.inc;
|
|
source include/have_innodb.inc;
|
|
create table t1 (a int) type=innodb;
|
|
begin;
|
|
insert into t1 values(1);
|
|
flush tables with read lock;
|
|
commit;
|
|
save_master_pos;
|
|
connection slave;
|
|
sync_with_master;
|
|
# cleanup
|
|
connection master;
|
|
unlock tables;
|
|
drop table t1;
|
|
save_master_pos;
|
|
connection slave;
|
|
sync_with_master;
|