MySQL Bugs: #64074: MySQL crash with invalid pointers while parsing

Bug #64074	MySQL crash with invalid pointers while parsing
Submitted:	19 Jan 2012 18:25	Modified:	21 Jan 2012 4:09
Reporter:	kris dba	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Server	Severity:	S1 (Critical)
Version:	5.1.32	OS:	Linux (CentOS 5, 64bit)
Assigned to:		CPU Architecture:	Any
Tags:	crash, invalid pointers, parse

Description:
MySQL crashed frequently while trying to parse a SQL.
Backtrace generated was of not much help.
The query involved seems to be an insert into select operations.Iam trying to get hold of the query.
Please let me know if there is any open issues related to crash. 

 

How to repeat:
crashes every 2-3hours based on the query.

Please, check if the same problem still happens with a newer version, 5.1.61.

Based on stack trace and partitioning engine use, I'd still suggest to upgrade. Bug #50939 is one of the reasons.

If you can not upgrade, I need complete, repeatable and minimal test case, ideally with data in the tables involved.

Thank you..we did some more testing and observed that the issue is mainly with the Merge_MyISAM tables.
Querying the merge table is resulting in MySQL crash where as directly querying the underlying MyISAM table survived.
recreating the merge table was of not much help.I believe internally merge and partitioning use mostly similar functionality. so,not quite sure if it is most likely related to partition engine(Bug#50939)

Does EXPLAIN SELECT... say index merge is used?

http://bugs.mysql.com/bug.php?id=40675
(MySQL 5.1 crash with index merge algorithm and Merge tables)
"Noted in 5.1.33 changelog" and you're on 5.1.32..

Thank you Shane. you got it.
yes, optimizer was using "index_merge intersection" sometimes which is causing mysql to crash.
A simple "using where" condition resulted out without any issues.
will do abit more testing and let you the results. appreciate your help.