Red Hat Bugzilla – Bug 152911
mysql v4.1.10 has serious UNION/DATETIME crash bug
Last modified: 2013-07-02 23:04:34 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Description of problem:
The recent errata release of mysql-server contains MySQL bug 8660. In short, this bug causes the mysql server to SIGSEGV whenever two UNION'd queries contain a DATE() cast.
Please note that I have reproduced this bug on a i386 machine as well as the x86_64 machine.
More information can be found at:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Update a RHES4 system's mysql-server package to 4.1.10a as per errata
2. Run the following queries in mysql:
create table a ( f datetime);
create table b ( f datetime);
select DATE(f) from a UNION select DATE(f) from b;
Actual Results: mysql client software reported that the connection went away before the query was complete. The mysql-server error log reported a SIGSEGV and reload.
Expected Results: Query should have completed successfully.
This is a very serious, open and recognized bug in the upstream mysql project and I expect better release engineering from an enterprise level product. What I installed as a trusted and essential security fix resulted in nearly two hours of downtime as we diagnosed the problem and implimented a workaround.
A fix for this is pending for RHEL4 QU1.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.