Bug #16782 Partitions: crash, REPLACE .. on table with PK, DUPLICATE KEY event
Submitted: 25 Jan 2006 15:19 Modified: 16 Feb 2006 14:20
Reporter: Matthias Leich Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Partitions Severity:S2 (Serious)
Version:5.1 OS:
Assigned to: Jim Winstead CPU Architecture:Any

[25 Jan 2006 15:19] Matthias Leich
Description:
--disable_warnings
DROP TABLE IF EXISTS t1;
--enable_warnings
SET SESSION storage_engine= MyISAM;
CREATE TABLE t1
( f_int1 INTEGER, f_int2 INTEGER, PRIMARY KEY (f_int1))
PARTITION BY HASH(f_int1) PARTITIONS 2;
INSERT INTO t1(f_int1,f_int2) VALUES(1,1),(2,2);

## REPLACE
REPLACE INTO t1 (f_int1, f_int2) VALUES(1,1),(2,2);
      <----- mysqltest: At line 13: query 'REPLACE INTO t1 
               (f_int1, f_int2) VALUES(1,1),(2,2)' failed: 
        2013: Lost connection to MySQL server during query

I get also a crash when switching from 'MyISAM' to 'BDB'.

My environment:
   - Intel PC with Linux(SuSE 9.3)
   - MySQL compiled from source
         Version 5.1 last ChangeSet@1.2076, 2006-01-23

How to repeat:
Please execute the statements above or use my attached 
testscript ml013.test
  copy it to mysql-test/t
  echo "Dummy" > r/ml013.result   # Produce a dummy file with 
                                                   # expected results
  ./mysql-test-run ml013
[25 Jan 2006 15:20] Matthias Leich
test script

Attachment: ml013.test (application/test, text), 336 bytes.

[1 Feb 2006 19:28] Bugs System
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/2022
[15 Feb 2006 19:20] Bugs System
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/2671
[16 Feb 2006 0:42] Jim Winstead
Fixed in 5.1.7.
[16 Feb 2006 14:20] Jon Stephens
Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at
    http://www.mysql.com/doc/en/Installing_source_tree.html

Additional info:

Documented bugfix in 5.1.7 changelog; closed.