database/mariadb
1
0
Fork 0
mirror of https://github.com/MariaDB/server.git synced 2025-07-27 18:02:13 +03:00
Code Activity

MDEV-13256 innodb.truncate_debug fails in buildbot

Browse Source 
Ensure that no adaptive hash index exists for any system tables,
so that the blocked TRUNCATE TABLE t1 will not block the concurrent
TRUNCATE TABLE t2.
This commit is contained in:
Marko Mäkelä
2017-09-25 17:24:52 +03:00
parent 7dcb8816a1
commit 742263df4f
2 changed files with 11 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
mysql-test/suite/innodb/r/truncate_debug.result
View File

@ -1,6 +1,9 @@
#
# Bug #23070734 CONCURRENT TRUNCATE TABLES CAUSE STALLS
#
SET @ahi= @@global.innodb_adaptive_hash_index;
SET GLOBAL innodb_adaptive_hash_index=OFF;
SET GLOBAL innodb_adaptive_hash_index=ON;
Test_1 :- Check if DDL operations are possible on
table being truncated. Also check if
DDL operations on other tables succeed.
@ -81,6 +84,5 @@ connection con2;
disconnect con2;
connection default;
SET DEBUG_SYNC= 'RESET';
SET session lock_wait_timeout=default;
set global innodb_adaptive_hash_index=on;
SET GLOBAL innodb_adaptive_hash_index=@ahi;
drop table t1,t2,t3;