mariadb/mysql-test/suite/binlog/r/binlog_reset_master.result at 9e91f479d253052e4514cffd0699ef72bcce82a6 - mirror/mariadb - May the force be without you: git.fucktheforce.de

mirror/mariadb

mirror of https://github.com/MariaDB/server.git synced 2026-05-15 19:37:16 +02:00

Sven Sandberg b76c277a8f BUG#12574820: binlog.binlog_tmp_table timing out in daily and weekly trunk run

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.

2011-05-26 12:50:43 +02:00

1 line

14 B

Text

Raw Blame History

RESET MASTER;