Bug #28039 Falcon Crash if INSERT ON DUPLICATE KEY with two interleaving transactions
Submitted: 23 Apr 2007 19:50
Reporter: Hakan Küçükyılmaz Email Updates:
Status: Closed Impact on me:
Category:MySQL Server: Falcon storage engine Severity:S3 (Non-critical)
Version: OS:Any
Assigned to: CPU Architecture:Any

[23 Apr 2007 19:50] Hakan Küçükyılmaz
I have two connections, "T1" and "T2".
On T1, I insert a primary-key value.
On T2, I try to insert the same value, using an ON DUPLICATE KEY clause.
On T1, I commit.

Similar to Bug#22160 "REPLACE crash with two interleaving transactions",
except that the statement is INSERT instead of REPLACE, and the
COMMIT comes in a different place.

How to repeat:
On connection T1, do:
set @@autocommit=0;
create table tj16 (s1 int, primary key (s1), s2 int) engine=jstar;
insert into tj16 values (1,2);

On connection T2, do:
set @@autocommit=0;
insert into tj16 values (1,2) on duplicate key update s2 = 5;

On connection T1, do:
[23 Apr 2007 19:52] Hakan Küçükyılmaz
Test case is falcon_bug_28039.test.