Bug #41333 MySQL 5.1 crash with index merge algorithm and Merge tables
Submitted: 9 Dec 2008 16:43 Modified: 9 Dec 2008 17:14
Reporter: Tony Wynes Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Server: Optimizer Severity:S2 (Serious)
Version:5.1.30 OS:Solaris (S10 Sparc)
Assigned to: CPU Architecture:Any

[9 Dec 2008 16:43] Tony Wynes
Description:
I'm pretty sure this is a duplicate of bug #40675 "MySQL 5.1 crash with index merge algorithm and Merge tables" but don't have access to verify.  I get a "You do not have access to bug #40675." when trying to access it so perhaps there's a vulnerability too.

I've included some SQL to recreate the problem below.  I'm trying to find out the severity and the target version for resolution of this bug.

How to repeat:
mysql-5.1.30-solaris10-sparc-64bit.pkg and my-huge.cnf.

CREATE DATABASE test;

DROP TABLE IF EXISTS test.t_one;
CREATE TABLE test.t_one ( `foo` char(20) NOT NULL DEFAULT '', `bah` char(30) NOT NULL DEFAULT '', KEY `foo` (`foo`), KEY `bah` (`bah`)) ENGINE=MyISAM;

INSERT INTO test.t_one VALUES ('1234567890','1234567890'),('1234567890','1234567890'),('1234567890','1234567890'),('1234567890','1234567890'),('1234567890','1234567890'),('1234567890','1234567890'),('1234567890','1234567890'),('1234567890','1234567890'),('1234567890','1234567890'),('1234567890','1234567890');

DROP TABLE IF EXISTS test.t_two;
CREATE TABLE test.t_two ( `foo` char(20) NOT NULL DEFAULT '', `bah` char(30) NOT NULL DEFAULT '', KEY `foo` (`foo`), KEY `bah` (`bah`)) ENGINE=MRG_MyISAM INSERT_METHOD=LAST UNION=(test.t_one);

SELECT COUNT(*) FROM test.t_two WHERE foo = '12345' OR bah = '12345';

The select query results in a signal 11.

Suggested fix:
None.
[9 Dec 2008 16:52] MySQL Verification Team
Thank you for the bug report. Duplicate of bug: http://bugs.mysql.com/bug.php?id=40675
[9 Dec 2008 17:14] Tony Wynes
So can you tell me the severity and the target version for resolution of #40675?I don't have access.
[17 Dec 2008 15:47] Valeriy Kravchuk
Bug #40675 is Critical and should be fixed in 5.1.x as soon as possible.