mirror of
https://github.com/MariaDB/server.git
synced 2025-08-01 03:47:19 +03:00
Last part of fix for BUG#7998 "Replication should be more clever about when to replicate RELEASE_LOCK()" + fixes after merge
mysql-test/r/drop_temp_table.result: result update mysql-test/r/mix_innodb_myisam_binlog.result: result update mysql-test/r/rpl000001.result: result update mysql-test/r/rpl_change_master.result: result update mysql-test/r/rpl_deadlock.result: result update (merge) mysql-test/t/rpl000001.test: can't rely on GET_LOCK() to do slave synchro (use table lock instead) mysql-test/t/rpl_change_master.test: changing the test as we can't use GET_LOCK() for slave synchro mysql-test/t/rpl_deadlock.test: update (merge) binlog positions mysql-test/t/rpl_get_lock.test: comment
This commit is contained in:
@ -22,6 +22,13 @@ connection slave;
|
||||
sync_with_master;
|
||||
select get_lock("lock",3);
|
||||
select * from t1;
|
||||
# There is no point in testing REPLICATIION of the IS_*_LOCK
|
||||
# functions; slave does not run with the same concurrency context as
|
||||
# master (generally in slave we can't know that on master this lock
|
||||
# was already held by another connection and so that the the
|
||||
# get_lock() we're replicating timed out on master hence returned 0,
|
||||
# or that the is_free_lock() we're playing returned 0 etc.
|
||||
# But here all we do is test these functions outside of replication.
|
||||
select is_free_lock("lock"), is_used_lock("lock") = connection_id();
|
||||
explain extended select is_free_lock("lock"), is_used_lock("lock");
|
||||
# Check lock functions
|
||||
|
Reference in New Issue
Block a user