Bug #20005 | Crash while creating temp table | ||
---|---|---|---|
Submitted: | 22 May 2006 17:39 | Modified: | 26 Sep 2006 13:27 |
Reporter: | Matthias Urlichs | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Server | Severity: | S2 (Serious) |
Version: | 4.1.20, 4.1.11 | OS: | Linux (Debian Sarge) |
Assigned to: | CPU Architecture: | Any |
[22 May 2006 17:39]
Matthias Urlichs
[22 May 2006 17:41]
Matthias Urlichs
SQL statement triggering the bug
Attachment: sql (application/octet-stream, text), 9.81 KiB.
[22 May 2006 17:59]
MySQL Verification Team
Thank you for the bug report. I was unable to repeat testing against the 4.1.19 source server. Anyway you are reporting a version which is very older, could you please test against the newest release 4.1.XX server? Thanks in advance.
[22 Jun 2006 23:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".
[16 Aug 2006 19:25]
Sveta Smirnova
Bug #21458 duplicates this one
[16 Aug 2006 19:39]
Lukas Jelinek
The bug I reported #21458 (and which was found as a duplicate of this) occurred on the version 4.1.20. Please look there for more information.
[16 Aug 2006 20:11]
Sveta Smirnova
Lukas, thank you for the feedback. Please, accurate indicate your platform, version of package you use and indicate if you use NPTL threads.
[16 Aug 2006 20:43]
Lukas Jelinek
Platform (uname -a): Linux localhost 2.6.11-1.1369_FC4 #1 Thu Jun 2 22:55:56 EDT 2005 i686 athlon i386 GNU/Linux Package: mysql-server-4.1.20-1.FC4.1 NPTL: yes
[26 Aug 2006 13:27]
Valeriy Kravchuk
Please, try to repeat with a newer version, 4.1.21, and inform about the results.
[26 Sep 2006 23:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".
[27 Sep 2006 18:49]
Lukas Jelinek
After I had upgraded to 4.1.21 (RPM package MySQL-server-4.1.21-0.glibc23) the server has been working with no error occurred (and is still working OK). But I think that there is only low probability the error occurs again because the server processes hundreds of similar queries a day. And the original problem (as I reported) came after many weeks of trouble-free operation.