mirror of
https://github.com/MariaDB/server.git
synced 2025-01-16 20:12:31 +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.
27 lines
899 B
Text
27 lines
899 B
Text
# t/concurrent_innodb_unsafelog.test
|
|
#
|
|
# Concurrent InnoDB tests
|
|
#
|
|
# Last update:
|
|
# 2006-07-26 ML test refactored (MySQL 5.1)
|
|
# main code t/innodb_concurrent.test -> include/concurrent.inc
|
|
# new wrapper t/concurrent_innodb.test
|
|
# 2008-06-03 KP test refactored; removed name locks, added comments.
|
|
# renamed wrapper t/concurrent_innodb.test ->
|
|
# t/concurrent_innodb_unsafelog.test
|
|
# new wrapper t/concurrent_innodb_safelog.test
|
|
#
|
|
|
|
--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/concurrent.inc
|
|
|
|
SET GLOBAL innodb_lock_wait_timeout = @save_timeout;
|
|
SET GLOBAL tx_isolation = @save_isolation;
|