| Bug #19310 | Partitions: crash when adding a partition to InnoDB table | ||
|---|---|---|---|
| Submitted: | 24 Apr 2006 20:29 | Modified: | 27 May 2006 18:54 |
| Reporter: | Matthias Leich | Email Updates: | |
| Status: | Duplicate | Impact on me: | |
| Category: | MySQL Server: Partitions | Severity: | S1 (Critical) |
| Version: | 5.1 | OS: | |
| Assigned to: | Assigned Account | CPU Architecture: | Any |
[24 Apr 2006 20:29]
Matthias Leich
testcase
Attachment: ml014.test (application/test, text), 433 bytes.
[24 Apr 2006 20:30]
Matthias Leich
stacktrace
Attachment: stacktrace (application/octet-stream, text), 4.94 KiB.
[27 May 2006 18:54]
Mikael Ronström
Patch for Bug#19122 fixes this one as well
Description: # MyISAM would be harmless SET SESSION storage_engine='InnoDB'; DROP TABLE IF EXISTS t1; CREATE TABLE t1 (f_date DATE, f_varchar VARCHAR(30)) PARTITION BY HASH(CAST(YEAR(f_date) AS SIGNED INTEGER)); # This statement crashes the server. # CREATE partitioned table with three partitions in one step # would be harmless. ALTER TABLE t1 ADD PARTITION PARTITIONS 1; ---> At line 14: query 'ALTER TABLE t1 ADD PARTITION PARTITIONS 1' failed: 2013: Lost connection to MySQL server during query My environment: - Intel PC with Linux(SuSE 9.3) - MySQL compiled from source Version 5.1 last ChangeSet@1.2353.1.4, 2006-04-23 How to repeat: Please use my attached testscript ml014.test copy it to mysql-test/t echo "Dummy" > r/ml014.result # Produce a dummy file with # expected results ./mysql-test-run ml014