| List: | General Discussion | « Previous MessageNext Message » | |
| From: | Dan Nelson | Date: | June 17 2001 1:00am |
| Subject: | Re: What does tmp_table_size *really* do? | ||
| View as plain text | |||
In the last episode (Jun 16), Jeremy Zawodny said: > Err, I forgot to mention that there's a "Using filesort" in the > output as well. That makes me believe it wants to write to disk (even > if there may be sufficient RAM). I'm not sure "Using filesort" actually means it is going to create a file. The code seems to print "filesort" whenever an ORDER BY is requested (sql_select.cc:536). Even the manual simply says "extra pass". Maybe it required a file-based table in an earlier version, but not anymore? -- Dan Nelson dnelson@stripped
| Thread | ||
|---|---|---|
| • What does tmp_table_size *really* do? | Jeremy Zawodny | 16 Jun |
| • Re: What does tmp_table_size *really* do? | Dan Nelson | 16 Jun |
| • Re: What does tmp_table_size *really* do? | Jeremy Zawodny | 16 Jun |
| • Re: What does tmp_table_size *really* do? | Dan Nelson | 16 Jun |
| • Re: What does tmp_table_size *really* do? | Jeremy Zawodny | 16 Jun |
| • Re: What does tmp_table_size *really* do? | Dan Nelson | 17 Jun |
| • Re: What does tmp_table_size *really* do? | Jeremy Zawodny | 17 Jun |
| • Re: What does tmp_table_size *really* do? | jaab | 16 Jun |
| • Re: What does tmp_table_size *really* do? | Kevin Whitney | 16 Jun |
| • RE: What does tmp_table_size *really* do? | Sander Pilon | 16 Jun |
