Bug #28042 Falcon Partitions: crash after a few alters

• Submitted: 23 Apr 2007 20:45
• Reporter: Hakan Küçükyılmaz
• Status: Closed
• Category: MySQL Server: Falcon storage engine
• Severity: S3 (Non-critical)
• Version: 6.0.0-alpha
• OS: Any
• CPU Architecture: Any

[23 Apr 2007 20:45] Hakan Küçükyılmaz

Description:
I create a procedure with a short loop that removes partitioning and puts it back again. It crashes and the database can't be read when I restart.

This is minor because the same procedure fails with engine=myisam. But with engine=myisam the result is failure, not crash and corruption.

How to repeat:
mysql> create database falcon4//
Query OK, 1 row affected (0.13 sec)

mysql> use falcon4//
Database changed
mysql> create table tf3 (s1 int, s2 varchar(200)) engine=falcon//
Query OK, 0 rows affected (0.19 sec)

mysql> create procedure pf3 () begin declare v int default 0; while v < 2 do alter table tf3 remove partitioning; alter table tf3 partition by range (s1) (partition p4 values less than maxvalue); set v = v + 1; end while; end//
Query OK, 0 rows affected (0.03 sec)

mysql> call pf3()//
ERROR 2013 (HY000): Lost connection to MySQL server during query

[23 Apr 2007 20:46] Hakan Küçükyılmaz

Test case is falcon_bug_28042.test