MySQL Bugs: #13517: Documentation bug for show proccesslist

Bug #13517	Documentation bug for show proccesslist
Submitted:	27 Sep 2005 9:18	Modified:	22 Nov 2005 18:51
Reporter:	Peter Volk (Basic Quality Contributor)	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Documentation	Severity:	S3 (Non-critical)
Version:	4.0.23	OS:	Any (any)
Assigned to:	Paul DuBois	CPU Architecture:	Any

Description:
When I execute the command "show proccesslist;" on the console I get several threads with the state "Copying to tmp table". According to http://dev.mysql.com/doc/mysql/en/show-processlist.html there is no such state.

How to repeat:
none

Suggested fix:
Add a description of the "Copying to tmp table" state

So, it was neither of the following states?

"- Copying to tmp table on disk 
The temporary result set was larger than tmp_table_size and the thread is changing the temporary table from in-memory to disk-based format to save memory. 

- Creating tmp table 
The thread is creating a temporary table to hold a part of the result for the query"

Simply "Copying to tmp table"?

correct

both states exist:

./sql/sql_select.cc:1162:    thd->proc_info= "Copying to tmp table";
...
./sql/sql_select.cc:5815:  thd->proc_info= (!strcmp(save_proc_info,"Copying to tmp table") ?
./sql/sql_select.cc:5816:                  "Copying to tmp table on disk" : save_proc_info);

so "Copying to tmp table" is the step where the tmp table is still a hash table in RAM
while "Copying to tmp table on disk" is shown later when the table doesn't fit into RAM
and is put on disk instead

> According to http://dev.mysql.com/doc/mysql/en/show-processlist.html there is no such state.

this is not really a bug as the page also states 

  "Some states commonly seen in the output from SHOW PROCESSLIST:"

but as this state is way more common then the "on disk" one i think it is only fair
to mention it

Oh how wonderfull....Yes I think it is a bit more often that it fits into the RAM...Thanks.....

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
product(s).