Bug #47295 | Locked a record that shouldn't be such | ||
---|---|---|---|
Submitted: | 13 Sep 2009 14:00 | Modified: | 4 Jan 2010 14:29 |
Reporter: | Saverio Miroddi | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server: Locking | Severity: | S3 (Non-critical) |
Version: | 5.1.31-1ubuntu2 | OS: | Any |
Assigned to: | CPU Architecture: | Any | |
Tags: | locking innodb |
[13 Sep 2009 14:00]
Saverio Miroddi
[14 Sep 2009 4:01]
Valeriy Kravchuk
What about http://dev.mysql.com/doc/refman/5.1/en/innodb-record-level-locks.html? Doesn't it explain this situation with next-key locks?
[14 Oct 2009 23:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".
[4 Jan 2010 14:18]
Saverio Miroddi
Carefully read the article - the article generically (but appropriately, given the article subject) says "locks on the index it [mysql] encounters", and it's my problem not to have a deep enough understading of the processso - so I don't consider it a bug.