Bug #25974 | Server | ||
---|---|---|---|
Submitted: | 31 Jan 2007 13:19 | Modified: | 1 Mar 2007 8:50 |
Reporter: | Anthony Glen | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Server: General | Severity: | S1 (Critical) |
Version: | 4.1.14 / 5.0.27a | OS: | Linux (Linux Slackware 10) |
Assigned to: | CPU Architecture: | Any |
[31 Jan 2007 13:19]
Anthony Glen
[31 Jan 2007 13:35]
Sveta Smirnova
Thank you for the report. But version 4.1.14 is quite old. Please try with current full supported 5.0.27 version or current only has extended support 4.1.22 version and say us result.
[1 Mar 2007 0: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".
[1 Mar 2007 8:30]
Anthony Glen
Hi, Repeating this large SELECT query under MySQL version 5.0.27a does appear to correct this problem and also others whereby the linux server was grinding to a halt (i.e. running various other reports). This does look like it has been corrected in this later version of the MySQL software.
[1 Mar 2007 8:44]
Sveta Smirnova
Thank you for the comment. > Repeating this large SELECT query under MySQL version 5.0.27a does > appear to correct this problem So I'll close this report as "Can't repeat". If you not agree fill free to describe why and reopen again.
[1 Mar 2007 8:50]
Anthony Glen
Yes, please close this bug report. Thank You