Bug #36801 InnoDB should release the lock on a duplicate key under REPEATABLE READ
Submitted: 19 May 2008 15:02 Modified: 13 May 2010 16:12
Reporter: Heikki Tuuri Email Updates:
Status: Verified Impact on me:
Category:MySQL Server: InnoDB storage engine Severity:S4 (Feature request)
Version: OS:Any
Assigned to: Assigned Account CPU Architecture:Any

[19 May 2008 15:02] Heikki Tuuri
Venu noted that InnoDB does not release the lock on the duplicate key after a duplicate key error:


It would make sense for InnoDB to release it on the REPEATABLE READ level.

How to repeat:
See above.
[19 May 2008 15:29] MySQL Verification Team
Thank you for the bug report.
[19 May 2008 16:05] Heikki Tuuri
Sorry, I meant READ COMMITTED.
[19 May 2008 17:51] Venu Anuganti
Thanks Heikki for posting this. Yes, READ COMMITTED it needs to release the lock..