Re: mysql crash - Sasha Pachev - com.mysql.lists.bugs

6 messages in com.mysql.lists.bugsRe: mysql crash

From	Sent On	Attachments
Jakub Formela	27 Jun 2001 12:21
Timothy Smith	27 Jun 2001 16:03
Sasha Pachev	27 Jun 2001 18:11
Sinisa Milivojevic	28 Jun 2001 04:17
Jakub Formela	30 Jun 2001 03:09
Sinisa Milivojevic	30 Jun 2001 05:12

Subject:	Re: mysql crash
From:	Sasha Pachev (sas...@mysql.com)
Date:	06/27/2001 06:11:02 PM
List:	com.mysql.lists.bugs

On Wednesday 27 June 2001 13:21, Jakub Formela wrote:

Hi! Hope U can help me, because I got to finish site in few days, and this can't be done, when I'll be gettin' errors like this. I got a lot of errors with signal 11, but they come when mySQL was running very different queries. The numeric codes are always the same below - example message from error log, and results returned by resolve_stack_dump

pleaaaaaseee.....

There is away to get priority help in a hurry - visit https://order.mysql.com and get a support contract. However, it looks like in this case you will not need it. The stack trace indicates that you are hitting an ORDER BY bug introduced in 3.23.34 and promptly fixed in 3.23.35, which had another bad bug with UPDATE, which in turn was fixed in 3.23.36 - this ended the ugly dark window of critical bugs in a stable release. So the fix is to upgrade to the latest version - 3.23.39.