Bug #43766 | unnecessary locking on update even with tx_isolation=READ-COMMITTED or | ||
---|---|---|---|
Submitted: | 20 Mar 2009 10:19 | Modified: | 20 Mar 2009 17:47 |
Reporter: | Nishant Deshpande | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Server: Locking | Severity: | S3 (Non-critical) |
Version: | 5.1.25, 5.1.31, 4.1, 5.0, 5.1, 6.0 bzr | OS: | Linux |
Assigned to: | CPU Architecture: | Any | |
Tags: | innodb_locks_unsafe_for_binlog, lock, READ-COMMITTED, unnecessary, UPDATE |
[20 Mar 2009 10:19]
Nishant Deshpande
[20 Mar 2009 17:47]
Sveta Smirnova
Thank you for the report. Verified as described. Falcon storage engine allows such UPDATE. Test case for MySQL test suite: --source include/have_innodb.inc set global transaction isolation level read uncommitted; create table tmp_n1 (x int) engine=innodb; create table tmp_n2 (x int, y int) engine=innodb; insert into tmp_n1 values (1),(2); insert into tmp_n2 values (1,null),(2,null); begin; update tmp_n1 set x=3; connect (addconroot, localhost, root,,); connection addconroot; begin; update tmp_n2, tmp_n1 set tmp_n2.y=1 where tmp_n2.x = tmp_n1.x;