MySQL Bugs: #44173: Documentation for system variable 'thread-handling' is not correct

Bug #44173	Documentation for system variable 'thread-handling' is not correct
Submitted:	9 Apr 2009 0:47	Modified:	9 Apr 2009 20:03
Reporter:	Patrick Crews	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Documentation	Severity:	S3 (Non-critical)
Version:	6.0	OS:	Any
Assigned to:	Paul DuBois	CPU Architecture:	Any
Tags:	documentation, thread-handling

Description:
The documentation for thread-handling is inconsistent:
From the manual: (http://dev.mysql.com/doc/refman/6.0/en/server-system-variables.html#sysvar_thread_handling)

As you see, the docs list the valid values as no-threads, one-thread-per-connection, and pool-of-threads.  

However, the expanded discussion lists the valid values as one-thread, one-thread-per-connection, and pool-of-threads.

 thread_handling

Command Line Format	--thread_handling=name
<snip>
Valid Values	no-threads, one-thread-per-connection, pool-of-threads
The thread-handling model. The allowable values are one-thread (the server uses one thread), one-thread-per-connection (the server uses one thread to handle each client connection), pool-of-threads (the server does not create a thread per client connection, but uses a pool of threads for processing statements). one-thread is useful for debugging under Linux; see MySQL Internals: Porting. pool-of-threads is available as of MySQL 6.0.4. To use thread pooling, MySQL must be configured with the --with-libevent option when you run ./configure.

How to repeat:
Examine the documentation here:
http://dev.mysql.com/doc/refman/6.0/en/server-system-variables.html#sysvar_thread_handling

Suggested fix:
Determine which is correct no-threads or one-thread and update the documentation correctly.

This is likely tied to Bug#34239- Server: Thread pool options are obsolete or badly described

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.

It's no-threads, not one-threads.  The confusion (on my part) likely resulted from the fact that there is a --one-thread option, which is now deprecated in favor of --thread_handling=no-threads.