Bug #15130 | CREATE TABLE ... SELECT SQL_BIG_RESULT looses filesort optimization | ||
---|---|---|---|
Submitted: | 22 Nov 2005 11:19 | Modified: | 27 Jul 2007 16:23 |
Reporter: | Domas Mituzas | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Optimizer | Severity: | S5 (Performance) |
Version: | 5.0.16, 4.1.15 | OS: | Linux (Linux) |
Assigned to: | Evgeny Potemkin | CPU Architecture: | Any |
[22 Nov 2005 11:19]
Domas Mituzas
[24 Jul 2007 14:19]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/commits/31477 ChangeSet@1.2485, 2007-07-24 18:15:44+04:00, evgen@moonbone.local +3 -0 Bug#15130: CREATE .. SELECT was denied to use advantages of the SQL_BIG_RESULT. When the SQL_BIG_RESULT flag is specified SELECT should store items from the select list in the filesort data and use them when sending to a client. The get_addon_fields function is responsible for creating necessary structures for that. But this function was allowed to do so only for SELECT and INSERT .. SELECT queries. This makes the SQL_BIG_RESULT useless for the CREATE .. SELECT queries. Now the get_addon_fields allows storing select list items in the filesort data for the CREATE .. SELECT queries.
[26 Jul 2007 5:55]
Bugs System
Pushed into 5.1.21-beta
[26 Jul 2007 5:56]
Bugs System
Pushed into 5.0.48
[27 Jul 2007 16:23]
Paul DuBois
Noted in 5.0.48, 5.1.21 changelogs. SQL_BIG_RESULT had no effect for CREATE TABLE ... SELECT SQL_BIG_RESULT ... statements.