Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Critical
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 5.5.21
-
Component/s: None
-
Labels:None
Description
https://bugs.launchpad.net/maria/+bug/922146
bzr version-info
revision-id: wlad@montyprogram.com-20120120213231-r6jatdnysflmkhdm
date: 2012-01-20 22:32:31 +0100
build-date: 2012-01-26 19:31:32 +0400
revno: 3228
branch-nick: maria-5.5
Couldn't reproduce on maria-5.3, mysql-5.5.20, 5.6.4, percona-server-5.5.19; however the testcases are not deterministic, so there is no guarantee that the bug isn't there.
Gliffy Diagrams
Attachments
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
If you are not able to reproduce it in the shared environment as described above, please let me know, I will see what else I can do.
As an MTR test case, please try this one (I tried both linux 32 bit and 64 bit, failed on every attempt. Revno 3272)
--source include/have_innodb.inc
SET GLOBAL innodb_lock_wait_timeout=3;
CREATE TABLE t1 (
col_int_key INT,
KEY (col_int_key)
) ENGINE=InnoDB
PARTITION BY KEY(col_int_key) PARTITIONS 2;
INSERT INTO t1 VALUES (6);
--connect (con1,127.0.0.1,root,,test)
SET SESSION TRANSACTION ISOLATION LEVEL SERIALIZABLE;
SET AUTOCOMMIT=OFF;
SELECT col_int_key FROM t1;
--connection default
--send
DELETE IGNORE FROM t1;
--connection con1
DELETE FROM t1 WHERE col_int_key IN (1, 40000000);
--connection default
--reap
- End of test case
cannot repeat either with mtr or with rqg in both debug and optimizer builds