Bug #76803 | InnoDB: Unlock row could not find a 2 mode lock on the record | ||
---|---|---|---|
Submitted: | 23 Apr 2015 8:42 | Modified: | 25 Jan 2019 1:21 |
Reporter: | zhai weixiang (OCA) | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: InnoDB storage engine | Severity: | S3 (Non-critical) |
Version: | 5.1, 5.5, 5.6, 5.7, 8.0 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[23 Apr 2015 8:42]
zhai weixiang
[23 Apr 2015 9:05]
MySQL Verification Team
Affects 5.1, 5.5, 5.6, 5.7, 5.8 Did not affect 5.0
[23 Apr 2015 9:05]
MySQL Verification Team
Thanks for the report! start server with --transaction-isolation=read-committed to repeat.
[18 Jun 2016 21:26]
Omer Barnir
Posted by developer: Reported version value updated to reflect release name change from 5.8 to 8.0
[25 Jan 2019 1:21]
Jon Stephens
Documented fix as follows in the MySQL 5.7.26 and 8.0.15 changelogs as follows: When the method used to access a joined table was const, InnoDB attempted to unlock the matching row multiple times. Closed.