Bug #2120 | derived table query causes server to go 100 percent cpu | ||
---|---|---|---|
Submitted: | 15 Dec 2003 13:14 | Modified: | 20 Feb 2004 5:55 |
Reporter: | Edmund Mierzwa | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: MyISAM storage engine | Severity: | S3 (Non-critical) |
Version: | 4.1.1 alpha | OS: | Windows (winxp) |
Assigned to: | Oleksandr Byelkin | CPU Architecture: | Any |
[15 Dec 2003 13:14]
Edmund Mierzwa
[15 Dec 2003 13:23]
Dean Ellis
Verified against 4.1.2. EXPLAIN on this query forces mysqld to restart (with nothing in the error log other than mentioning that mysqld restarted). (The issue in MySQLCC is due to MySQLCC issuing an EXPLAIN against the query.)
[15 Dec 2003 16:42]
Alexander Keremidarski
Further tests revealed that bug happens only when mysqld is compiled without debug options. Debug binaries return expected result from both query and EXPLAIN
[20 Dec 2003 2:06]
Alexey Botchkov
bk commit - 4.1 tree (hf:1.1701) (20 Dec 2003)
[1 Feb 2004 5:36]
Oleksandr Byelkin
ChangeSet 1.1683 04/02/01 15:30:32 bell@sanja.is.com.ua +18 -0 now all tables of query are locked in one place (including derived tables) fixed BUG#2120 and other problem with EXPLAINing derived tables
[1 Feb 2004 10:13]
Oleksandr Byelkin
as addition: ChangeSet 1.1689 04/02/01 20:07:44 bell@sanja.is.com.ua +6 -0 make JOIN::prepare, JOIN::optimize only once for EXPLAIN of derived table (BUG#2120 sfter merge)
[20 Feb 2004 5:55]
Oleksandr Byelkin
thank you for bug report. Putch for this bug is pushed to our internal source repository and will be present in next 4.1 release