mirror of
https://github.com/MariaDB/server.git
synced 2025-01-17 12:32:27 +01:00
d665e79c5b
for InnoDB tables" Don't use thr_lock.c locks for InnoDB tables. Below is list of changes that were needed to implement this: - HANDLER OPEN acquireis MDL_SHARED_READ instead of MDL_SHARED - HANDLER READ calls external_lock() even if SE is not going to be locked by THR_LOCK - InnoDB lock wait timeouts are now honored which are much shorter by default than server lock wait timeouts (1 year vs 50 seconds) - with @@autocommit= 1 LOCK TABLES disables autocommit implicitely, though user still sees @@autocommt= 1 - the above starts implicit transaction - transactions started by LOCK TABLES are now rolled back on disconnect (previously everything was committed due to autocommit) - transactions started by LOCK TABLES are now rolled back by ROLLBACK (previously everything was committed due to autocommit) - it is now impossible to change BINLOG_FORMAT under LOCK TABLES (at least to statement) due to running transaction - LOCK TABLES WRITE is additionally handled by MDL - ...in contrast LOCK TABLES READ protection against DML is pure InnoDB - combining transactional and non-transactional tables under LOCK TABLES may cause rolled back changes in transactional table and "committed" changes in non-transactional table - user may disable innodb_table_locks, which will cause LOCK TABLES to be noop basically Removed tests for BUG#45143 and BUG#55930 which cover InnoDB + THR_LOCK. To operate properly these tests require code flow to go through THR_LOCK debug sync points, which is not the case after this patch. These tests are removed by WL#6671 as well. An alternative is to port them to different storage engine.
56 lines
1.5 KiB
Text
56 lines
1.5 KiB
Text
SET DEBUG_SYNC='RESET';
|
|
DROP TABLE IF EXISTS t1;
|
|
#
|
|
# Bug#20667 - Truncate table fails for a write locked table
|
|
#
|
|
CREATE TABLE t1 (c1 INT);
|
|
INSERT INTO t1 VALUES (1);
|
|
connect con1, localhost, root,,;
|
|
START TRANSACTION;
|
|
INSERT INTO t1 VALUES (2);
|
|
connection default;
|
|
SET DEBUG_SYNC='mdl_acquire_lock_wait SIGNAL waiting';
|
|
TRUNCATE TABLE t1;
|
|
connection con1;
|
|
SET DEBUG_SYNC='now WAIT_FOR waiting';
|
|
KILL QUERY @id;
|
|
connection default;
|
|
ERROR 70100: Query execution was interrupted
|
|
connection con1;
|
|
# Release SW lock by committing transaction.
|
|
COMMIT;
|
|
disconnect con1;
|
|
connection default;
|
|
UNLOCK TABLES;
|
|
DROP TABLE t1;
|
|
SET DEBUG_SYNC='RESET';
|
|
#
|
|
# Bug#57659 Segfault in Query_cache::invalidate_data for TRUNCATE TABLE
|
|
#
|
|
# Note that this test case only reproduces the problem
|
|
# when it is run with valgrind.
|
|
DROP TABLE IF EXISTS t1, m1;
|
|
CREATE TABLE t1(a INT) engine=memory;
|
|
CREATE TABLE m1(a INT) engine=merge UNION(t1);
|
|
connect con2, localhost, root;
|
|
connect con1, localhost, root;
|
|
SET DEBUG_SYNC= 'open_tables_after_open_and_process_table SIGNAL opened WAIT_FOR dropped';
|
|
# Sending:
|
|
TRUNCATE TABLE m1;
|
|
connection con2;
|
|
SET DEBUG_SYNC= 'now WAIT_FOR opened';
|
|
# Sending:
|
|
FLUSH TABLES;
|
|
connection default;
|
|
# Waiting for FLUSH TABLES to be blocked.
|
|
SET DEBUG_SYNC= 'now SIGNAL dropped';
|
|
connection con1;
|
|
# Reaping: TRUNCATE TABLE m1
|
|
ERROR HY000: Unable to open underlying table which is differently defined or of non-MyISAM type or doesn't exist
|
|
disconnect con1;
|
|
connection con2;
|
|
# Reaping: FLUSH TABLES
|
|
disconnect con2;
|
|
connection default;
|
|
SET DEBUG_SYNC= 'RESET';
|
|
DROP TABLE m1, t1;
|