MySQL Bugs: #67924: Row lock isn't released after evaluating WHERE condition in READ COMMITTED

Bug #67924	Row lock isn't released after evaluating WHERE condition in READ COMMITTED
Submitted:	17 Dec 2012 15:01	Modified:	17 Dec 2012 18:39
Reporter:	Vitaly Litvak	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL Server: Locking	Severity:	S2 (Serious)
Version:	5.1.59, 5.5.24	OS:	Linux
Assigned to:		CPU Architecture:	Any
Tags:	innodb, lock, read committed, row

View
Add Comment
Files
Developer
Edit Submission
View Progress Log
Contributions

File:	Maximum allowed size is 50MB.
Description:
Privacy:

If the data you need to attach is more than 50MB, you should create a compressed archive of the data, split it to 50MB chunks, and upload each of them as a separate attachment.

To split a large file:

On *nix platforms use the split command e.g. split -b 50MB <my_large_archive> <my_split_archive_prefix>
On windows use WinZip or a similar utility to split the large file

Data for three tables, where issue always reproduces

Attachment: _20121212_1939.sql (text/x-sql), 52.92 KiB.

test case for MTR

Attachment: bug67924.test (application/octet-stream, text), 52.17 KiB.