Bug #97358 | The log.flush_notifier_mutex in log_sys is useless | ||
---|---|---|---|
Submitted: | 24 Oct 2019 11:59 | Modified: | 25 Oct 2019 11:53 |
Reporter: | Zongzhi Chen (OCA) | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Server: InnoDB storage engine | Severity: | S5 (Performance) |
Version: | 8.0.* | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[24 Oct 2019 11:59]
Zongzhi Chen
[24 Oct 2019 12:36]
MySQL Verification Team
Hello Mr. zongzhi, Thank you for your bug report. What you write is true, but there is one detail that you miss. That code, which you are referring to, can run in several threads. Hence, the mutex lock is necessary. Let us know if you disagree ........
[24 Oct 2019 19:06]
Zongzhi Chen
No, I am not agree. There is only one log_flush_notifier.. The log_flush_notifier thread is created in log_start_background_threads() function ``` srv_threads.m_log_flush_notifier = os_thread_create(log_flush_notifier_thread_key, log_flush_notifier, &log); ```
[25 Oct 2019 11:53]
MySQL Verification Team
Hi Mr. zongzhi, I have revisited the code and I think that you are right. Verified as a performance improvement contribution.