Bug #26195 multi_range_count not documented
Submitted: 8 Feb 2007 20:45 Modified: 9 Feb 2007 16:24
Reporter: [ name withheld ] Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Documentation Severity:S3 (Non-critical)
Version: OS:Any
Assigned to: Paul DuBois CPU Architecture:Any
Tags: multi_range_count

[8 Feb 2007 20:45] [ name withheld ] 
Description:
The variable multi_range_count in MySQL 5.0 is not documented in http://dev.mysql.com/doc/refman/5.0/en/server-system-variables.html

root@host:/var/lib/mysql# mysqladmin variables | grep multi
| multi_range_count               | 256                                    |

How to repeat:
Go to http://dev.mysql.com/doc/refman/5.0/en/server-system-variables.html and search for multi_range_count
[8 Feb 2007 22:39] Sveta Smirnova 
Thank you for the report.

Verified as described.

multi_range_count is indicated on the http://dev.mysql.com/doc/refman/5.0/en/mysqld-option-tables.html and http://dev.mysql.com/doc/refman/5.0/en/server-parameters.html pages
[9 Feb 2007 16:24] 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.

              The maximum number of ranges to send to a table handler at
              once during range selects. The default value is 256.
              Sending multiple ranges to a handler at once can improve
              the performance of certain selects dramatically. This
              especially true for the NDB Cluster table handler, which
              needs to send the range requests to all nodes. Sending a
              batch of those requests at once reduces the communication
              costs significantly.