| Bug #47786 | Add note and/or reference to http://dev.mysql.com/doc/refman/5.1/en/blob.html | ||
|---|---|---|---|
| Submitted: | 2 Oct 2009 10:17 | Modified: | 6 Oct 2009 16:22 |
| Reporter: | Valeriy Kravchuk | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: Documentation | Severity: | S4 (Feature request) |
| Version: | 5.0+ | OS: | Any |
| Assigned to: | Paul DuBois | CPU Architecture: | Any |
[2 Oct 2009 10:17]
Valeriy Kravchuk
[2 Oct 2009 20:30]
Paul DuBois
Valeriy, before I make this change, do you have anything to say about the additional user comment posted by Kristian Köhntopp in response to Simon's comment?
[6 Oct 2009 8:28]
Valeriy Kravchuk
I'd say that his comment just explain in details when temporary table can be created on disk. Great comment to have, but still we should add a reference and small note about possible perfromance impact.
[6 Oct 2009 16:22]
Paul DuBois
Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly, and will be included in the next release of the relevant products. Instances of BLOB or TEXT columns in the result of a query that is processed using a temporary table causes the server to use a table on disk rather than in memory because the MEMORY storage engine does not support those data types (see http://dev.mysql.com/doc/refman/5.1/en/internal-temporary-tables.html). Use of disk incurs a performance penalty, so include BLOB or TEXT columns in the query result only if they are really needed. For example, avoid using SELECT *, which selects all columns.
