Bug #95181 | The bugfix for Bug#28511326 seems incorrect | ||
---|---|---|---|
Submitted: | 29 Apr 2019 10:02 | Modified: | 20 May 2020 13:40 |
Reporter: | Jie Zhou | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Logging | Severity: | S3 (Non-critical) |
Version: | 5.7, 8.0 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[29 Apr 2019 10:02]
Jie Zhou
[2 May 2019 14:20]
MySQL Verification Team
Hi Jie, I fully agree with your code analysis. Verified as reported.
[24 Oct 2019 11:19]
MySQL Verification Team
Bug # 96192 is a duplicate of this report.
[20 May 2020 13:40]
Margaret Fisher
Posted by developer: Changelog entry added for MySQL 8.0.21 and 5.7.31: A fix made in MySQL 8.0.14 and MySQL 5.7.25 for a deadlock scenario involving the system variables binlog_transaction_dependency_tracking and binlog_transaction_dependency_history_size had the side effect of leaving the writeset history used for transaction dependency tracking unprotected from concurrent update. The writeset history and tracking mode are now locked correctly whenever they are accessed.