Bug #20934 Using partitions with innodb caused a crash.

• Submitted: 10 Jul 2006 7:23
• Modified: 12 Sep 2006 11:46
• Reporter: Horst Hunger
• Status: Duplicate
• Category: MySQL Server: Partitions
• Severity: S1 (Critical)
• Version: 5.1.12
• OS: Linux (Suse 10.1)
• CPU Architecture: Any

[10 Jul 2006 7:23] Horst Hunger

Description:
executing the following sql statement
"delete from tb3_eng1 where f1=@tmp_num"
the application lost the connection.
The table definition:
create table tb3_eng1 (
i1 int NOT NULL auto_increment, primary key (i1),
f1 int,
f2 char (15),
f3 decimal (5,3),
f4 datetime
) engine=innodb
PARTITION BY KEY (i1) PARTITIONS 4
(PARTITION part1 DATA DIRECTORY =
'/data0/mysql/mysql-5.1-clone/mysql-test/var/master-data/tmpdata' INDEX DIRECTORY =
'/data0/mysql/mysql-5.1-clone/mysql-test/var/master-data/tmpindex',
PARTITION part2 DATA DIRECTORY =
'/data0/mysql/mysql-5.1-clone/mysql-test/var/master-data/tmpdata' INDEX DIRECTORY =
'/data0/mysql/mysql-5.1-clone/mysql-test/var/master-data/tmpindex',
PARTITION part3 DATA DIRECTORY =
'/data0/mysql/mysql-5.1-clone/mysql-test/var/master-data/tmpdata' INDEX DIRECTORY =
'/data0/mysql/mysql-5.1-clone/mysql-test/var/master-data/tmpindex',
PARTITION part4 DATA DIRECTORY =
'/data0/mysql/mysql-5.1-clone/mysql-test/var/master-data/tmpdata' INDEX DIRECTORY =
'/data0/mysql/mysql-5.1-clone/mysql-test/var/master-data/tmpindex');

You can find all in attached files.

How to repeat:
As the application executes the sql statements in an arbitraty order, it was not possible to reproduce the error. But, perhaps the backtrace together with the other infos allow to find the reason for that crash.

[10 Jul 2006 7:53] Horst Hunger

master.err

Attachment: master.err.20934.tar.gz (application/x-gzip, text), 9.09 KiB.

[8 Sep 2006 17:18] Mikael Ronström

This is most likely a variant of the same bug as #21210

[12 Sep 2006 11:46] Valeriy Kravchuk

Possible duplicate of bug #21210. At least, application should be checked again with version that will include fix to bug #21210.