Bug #109388 | two client can both grant "RECORD X supremum pseudo-record lock " | ||
---|---|---|---|
Submitted: | 15 Dec 2022 6:59 | Modified: | 15 Dec 2022 12:48 |
Reporter: | b a | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server: Locking | Severity: | S3 (Non-critical) |
Version: | 8.0.28 | OS: | CentOS |
Assigned to: | CPU Architecture: | x86 | |
Tags: | lock, pseudo-record |
[15 Dec 2022 6:59]
b a
[15 Dec 2022 12:48]
MySQL Verification Team
Hi Mr. a, Thank you for your bug report. However, it is not a bug. That is how ACID standard prescribes that locking should be performed. When you are inserting a row at the end or deleting the one that does not exist, but has to be searched at the end of the index, then supremum record has to be locked. This has all been described in our Reference Manual. Not a bug.