Bug #6720 | alter table engine=innodb crashes the server | ||
---|---|---|---|
Submitted: | 19 Nov 2004 12:59 | Modified: | 19 Nov 2004 13:38 |
Reporter: | Sergey Petrunya | Email Updates: | |
Status: | Duplicate | Impact on me: | |
Category: | MySQL Server: InnoDB storage engine | Severity: | S2 (Serious) |
Version: | 5.0-bk | OS: | Linux (Linux and win32) |
Assigned to: | CPU Architecture: | Any |
[19 Nov 2004 12:59]
Sergey Petrunya
[19 Nov 2004 13:15]
Sergey Petrunya
No need to send table data file, here is the complete test case in mysql-test language: drop table if exists t0; create table t0 ( key1 int not null, index i1(key1) ); --disable_query_log insert into t0 values (1),(2),(3),(4),(5),(6),(7),(8); let $1=16; set @d=8; while ($1) { eval insert into t0 select key1+@d from t0; eval set @d=@d*2; dec $1; } --enable_query_log alter table t0 add key2 int not null; alter table t0 add key3 int not null; update t0 set key2=key1,key3=key1; alter table t0 add index i2(key2); alter table t0 add primary key(key3); flush tables; alter table t0 engine=innodb;
[19 Nov 2004 13:38]
Marko Mäkelä
Please do not submit the same bug more than once. An existing bug report already describes this very problem. Even if you feel that your issue is somewhat different, the resolution is likely to be the same. Because of this, we hope you add your comments to the original bug instead. Thank you for your interest in MySQL. Additional info: See bug #6633.