mirror of
https://github.com/MariaDB/server.git
synced 2025-11-04 04:46:15 +01:00
1a6f470464
The transaction isolation levels READ COMMITTED and READ UNCOMMITTED should behave similarly to the old deprecated setting innodb_locks_unsafe_for_binlog=1, that is, avoid acquiring gap locks. row_search_mvcc(): Reduce the scope of some variables, and clean up the initialization and use of the variable set_also_gap_locks.
24 lines
726 B
Text
24 lines
726 B
Text
# t/unsafe_binlog_innodb.test
|
|
#
|
|
# Note that this test uses at least in case of InnoDB options
|
|
# innodb_locks_unsafe_for_binlog = true
|
|
# innodb_lock_timeout = 5
|
|
#
|
|
# Last update:
|
|
# 2006-08-02 ML test refactored
|
|
# old name was innodb_unsafe_binlog.test
|
|
# main code went into include/unsafe_binlog.inc
|
|
#
|
|
|
|
--source include/have_innodb.inc
|
|
let $engine_type= InnoDB;
|
|
|
|
SET @save_timeout = @@GLOBAL.innodb_lock_wait_timeout;
|
|
SET GLOBAL innodb_lock_wait_timeout = 1;
|
|
SET @save_isolation = @@GLOBAL.tx_isolation;
|
|
SET GLOBAL TRANSACTION ISOLATION LEVEL READ COMMITTED;
|
|
|
|
--source include/unsafe_binlog.inc
|
|
|
|
SET GLOBAL innodb_lock_wait_timeout = @save_timeout;
|
|
SET GLOBAL tx_isolation = @save_isolation;
|