mirror of
https://github.com/MariaDB/server.git
synced 2025-08-26 01:44:06 +03:00
b76c277a8f
Problem: MYSQL_BIN_LOG::reset_logs acquires mutexes in wrong order. The correct order is first LOCK_thread_count and then LOCK_log. This function does it the other way around. This leads to deadlock when run in parallel with a thread that takes the two locks in correct order. For example, a thread that disconnects will take the locks in the correct order. Fix: change order of the locks in MYSQL_BIN_LOG::reset_logs: first LOCK_thread_count and then LOCK_log.
27 lines
998 B
Plaintext
27 lines
998 B
Plaintext
# ==== Purpose ====
|
|
#
|
|
# Test bugs in RESET MASTER.
|
|
|
|
--source include/have_debug.inc
|
|
--source include/have_log_bin.inc
|
|
|
|
#######################################################################
|
|
# BUG#12574820: binlog.binlog_tmp_table timing out in daily and weekly trunk run
|
|
# Problem: MYSQL_BIN_LOG::reset_logs acquired LOCK_thread_count and
|
|
# LOCK_log in the wrong order. This could cause a deadlock when
|
|
# RESET MASTER was run concurrently with a disconnecting thread.
|
|
#######################################################################
|
|
|
|
# We use sleep, not debug_sync, because the sync point needs to be in
|
|
# the thread shut down code after the debug sync facility has been
|
|
# shut down.
|
|
--let $write_var= SET DEBUG="+d,sleep_after_lock_thread_count_before_delete_thd"; CREATE TEMPORARY TABLE test.t1 (a INT);
|
|
--let $write_to_file= GENERATE
|
|
--disable_query_log
|
|
--source include/write_var_to_file.inc
|
|
--enable_query_log
|
|
|
|
--exec $MYSQL < $write_to_file
|
|
RESET MASTER;
|
|
--remove_file $write_to_file
|