Bug #114389 | A non-existent row has appeared which happens in Repeatable Read Level | ||
---|---|---|---|
Submitted: | 18 Mar 2024 11:48 | Modified: | 19 Mar 2024 12:54 |
Reporter: | Hongyu Yang | Email Updates: | |
Status: | Duplicate | Impact on me: | |
Category: | MySQL Server: InnoDB storage engine | Severity: | S2 (Serious) |
Version: | 8.0, 8.2 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[18 Mar 2024 11:48]
Hongyu Yang
[19 Mar 2024 12:54]
MySQL Verification Team
HI Mr. Yang, Thank you for your bug report. This is truly a serious bug. However, it has been reported in dozen of bug reports. The original bug is the following one: https://bugs.mysql.com/bug.php?id=100328 It has many, many duplicates, which you can find in that bug report. Since this bug is very hard to fix, it has been properly documented: "15.7.2.3 Consistent Nonlocking Reads” https://dev.mysql.com/doc/refman/8.0/en/innodb-consistent-read.html Duplicate.