Bug #15134 Partitions: crash when creating InnoDB/BDB/NDB table with named partitions
Submitted: 22 Nov 2005 13:52 Modified: 22 Nov 2005 17:13
Reporter: Matthias Leich Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Server: Partitions Severity:S1 (Critical)
Version:5.1 OS:
Assigned to: CPU Architecture:Any

[22 Nov 2005 13:52] Matthias Leich
Description:
Create partitioned table with explicit assigned partition names, 
lead to crash when using InnoDB, BDB and NDB.

--disable_warnings
DROP TABLE IF EXISTS t1;
--enable_warnings

let $engine= InnoDB;  # BDB and NDB give the same bad result

# no crash
eval CREATE TABLE t1 ( f1 BIGINT, f2 char(20)) ENGINE = $engine
PARTITION BY HASH(f1) PARTITIONS 2;
DROP TABLE t1;

# no crash
eval CREATE TABLE t1 ( f1 BIGINT, f2 char(20)) ENGINE = $engine
PARTITION BY HASH(f1) PARTITIONS 2 ( PARTITION part1 , PARTITION part2 );
DROP TABLE t1;

# This statement crashes the server     !!!!
eval CREATE TABLE t1 ( f1 BIGINT, f2 char(20))
PARTITION BY HASH(f1)
PARTITIONS 2
( PARTITION part1 STORAGE ENGINE = $engine,
  PARTITION part2 STORAGE ENGINE = $engine);

SELECT f1, f2 FROM t2;

My environment:
   - Intel PC with Linux(SuSE 9.3)
   - MySQL compiled from source
        Version 5.1 ChangeSet@1.1968, 2005-11-21

Attention: If you set $engine to MyISAM, the server will not crash.

How to repeat:
Please execute the statements above.
[22 Nov 2005 13:55] Matthias Leich
master.err when using InnoDB

Attachment: master.err (application/octet-stream, text), 3.14 KiB.

[22 Nov 2005 13:56] Matthias Leich
testcase

Attachment: ml004.test (application/test, text), 580 bytes.

[22 Nov 2005 16:28] Matthias Leich
1. The same problem occurs with the storage engines: 
          CSV, ARCHIVE, MEMORY and BLACKHOLE.
    Currently I know only one storage engine which does not show this effect: MyISAM .
2. The results were better (CSV, ARCHIVE and MEMORY do not cause a crash)
    before my last       "bk pull"  (22-11-2005)
    That means one of the Changesets between 15. Nov. and 
    ChangeSet@1.1968, 2005-11-21 caused the increased troubles.
[22 Nov 2005 17:14] Mikael Ronström
Duplicate with Bug #13438 that is in patch pending