Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
10.3(EOL), (15)
10.4(EOL), 10.5, 10.6, 10.7(EOL), 10.8(EOL), 10.9(EOL), 10.10(EOL), 10.11, 11.0(EOL), 11.1(EOL), 11.2(EOL), 11.3(EOL), 11.4, 11.6(EOL), 11.7(EOL)
Description
# mysqld options required for replay: --log-bin |
SET GLOBAL max_binlog_size=98304; # A valid and arbritary setting |
START TRANSACTION WITH CONSISTENT SNAPSHOT; |
Leads to:
|
10.11.0 6ebdd3013a18b01dbecec76b870810329eb76586 (Debug) |
safe_mutex: Found wrong usage of mutex 'LOCK_commit_ordered' and 'LOCK_global_system_variables'
|
And
# mysqld options required for replay: --log-bin |
START TRANSACTION WITH CONSISTENT SNAPSHOT; |
SET GLOBAL max_binlog_size=98304; # A valid and arbritary setting |
Leads to:
|
10.11.0 6ebdd3013a18b01dbecec76b870810329eb76586 (Debug) |
safe_mutex: Found wrong usage of mutex 'LOCK_global_system_variables' and 'LOCK_log'
|
Bug confirmed present in:
MariaDB: 10.3.37 (dbg), 10.4.27 (dbg), 10.5.18 (dbg), 10.6.10 (dbg), 10.7.6 (dbg), 10.8.5 (dbg), 10.9.3 (dbg), 10.10.2 (dbg), 10.11.0 (dbg)
Attachments
Issue Links
- is duplicated by
-
-
- Closed
-
- relates to
-
-
- Closed
-
Activity
I was going to review it in about 2-3 weeks (note that the release is planned for the end of Jan)
sergLet me know if you're going to review this week, otherwise I'll just take it back and push it with your suggestion to use mysql_mutex_record_order()
knielsen Hi! Thank you for working on this. I see you put this in review but I cannot see an attached patch?
Pushed to 10.6.
Requires another patch when merged to 11.4, see here: https://lists.mariadb.org/hyperkitty/list/developers@lists.mariadb.org/thread/LN35WETUEUHYUQNZXAKXLVU5EGSCQSVX/