Bug #55396 Error in concurrent_insert 5.5 documentation
Submitted: 20 Jul 2010 12:36 Modified: 20 Jul 2010 14:39
Reporter: Shlomi Noach (OCA) Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Documentation Severity:S3 (Non-critical)
Version:5.5 OS:Any
Assigned to: Paul Dubois CPU Architecture:Any
Tags: concurrent_insert
Triage: Needs Triage: D3 (Medium)

[20 Jul 2010 12:36] Shlomi Noach
Description:
On: http://dev.mysql.com/doc/refman/5.5/en/server-system-variables.html#sysvar_concurrent_inse...

A table lists the values for the new concurrent_insert NEVER, AUTO & ALWAYS new syntax.
However, the table lists AUTO twice:

AUTO (or 1) 	(Default) Enables concurrent insert for MyISAM  tables that do not have holes

AUTO (or 2) 	Enables concurrent inserts for all MyISAM tables, even those that have holes. For a table with a hole, new rows are inserted at the end of the table if it is in use by another thread. Otherwise, MySQL acquires a normal write lock and inserts the row into the hole.

How to repeat:
n/a

Suggested fix:
Fix docs to list ALWAYS.
[20 Jul 2010 12:47] Sveta Smirnova
Thank you for the report.

Verified as described.
[20 Jul 2010 14:39] 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.