mirror of
https://github.com/MariaDB/server.git
synced 2026-05-15 11:27:39 +02:00
Simplified THD::current_linfo locking
LOG_INFO::lock was useless. It could've only protect against concurrent iterators execution, which was already protected by LOCK_thread_count. Use LOCK_thd_data instead of LOCK_thread_count as a protection against THD::current_linfo reset. Aim is to reduce usage of LOCK_thread_count and COND_thread_count. Part of MDEV-15135.
This commit is contained in:
parent
c88fd54d17
commit
891be49a36
5 changed files with 10 additions and 26 deletions
|
|
@ -25,7 +25,6 @@ WHERE name IN (
|
|||
AND enabled = 'yes' AND timed = 'yes'
|
||||
ORDER BY name;
|
||||
NAME ENABLED TIMED
|
||||
wait/synch/mutex/sql/LOG_INFO::lock YES YES
|
||||
wait/synch/mutex/sql/THD::LOCK_thd_data YES YES
|
||||
SELECT * FROM performance_schema.setup_instruments
|
||||
WHERE name = 'wait/synch/mutex/sql/hash_filo::lock'
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue