Author: jstephens
Date: 2008-02-15 12:14:01 +0100 (Fri, 15 Feb 2008)
New Revision: 9847
Log:
Removed references to phantom multi_read_range variable
Modified:
trunk/it/refman-5.1/dba-core.xml
trunk/pt/refman-5.1/dba-core.xml
Modified: trunk/it/refman-5.1/dba-core.xml
===================================================================
--- trunk/it/refman-5.1/dba-core.xml 2008-02-15 10:42:01 UTC (rev 9846)
+++ trunk/it/refman-5.1/dba-core.xml 2008-02-15 11:14:01 UTC (rev 9847)
Changed blocks: 4, Lines Added: 7, Lines Deleted: 27; 3002 bytes
@@ -6293,25 +6293,6 @@
</listitem>
<listitem>
- <para id="option_mysqld_multi_read_range">
- <literal>multi_read_range</literal>
- </para>
-
- <para condition="dynamic:optvar:item"
role="5.1:mysqld:multi_read_range"/>
-
- <para>
- Specifies the maximum number of ranges to send to a storage
- engine during range selects. The default value is 256.
- Sending multiple ranges to an engine is a feature that can
- improve the performance of certain selects dramatically,
- particularly for <literal>NDBCLUSTER</literal>. This engine
- needs to send the range requests to all nodes, and sending
- many of those requests at once reduces the communication
- costs significantly.
- </para>
- </listitem>
-
- <listitem>
<para id="option_mysqld_named_pipe">
<literal>named_pipe</literal>
</para>
@@ -6934,9 +6915,9 @@
<para>
The current number of prepared statements. (The maximum
number of statements is given by the
- <literal>max_prepared_stmt_count</literal> system
- variable.) This variable was added in MySQL 5.1.10. In MySQL
- 5.1.14, it was converted to the global
+ <literal>max_prepared_stmt_count</literal> system variable.)
+ This variable was added in MySQL 5.1.10. In MySQL 5.1.14, it
+ was converted to the global
<literal>Prepared_stmt_count</literal> status variable.
</para>
</listitem>
@@ -9207,9 +9188,8 @@
command set used in the network layer. In other words, their
values increase whenever prepared statement API calls such
as <command>mysql_stmt_prepare()</command>,
- <command>mysql_stmt_execute()</command>, and so forth
- are executed. However,
- <literal>Com_stmt_prepare</literal>,
+ <command>mysql_stmt_execute()</command>, and so forth are
+ executed. However, <literal>Com_stmt_prepare</literal>,
<literal>Com_stmt_execute</literal> and
<literal>Com_stmt_close</literal> also increase for
<literal>PREPARE</literal>,
<literal>EXECUTE</literal>, or
@@ -10247,8 +10227,8 @@
<para>
The current number of prepared statements. (The maximum
number of statements is given by the
- <literal>max_prepared_stmt_count</literal> system
- variable.) This variable was added in MySQL 5.1.14.
+ <literal>max_prepared_stmt_count</literal> system variable.)
+ This variable was added in MySQL 5.1.14.
</para>
</listitem>
Modified: trunk/pt/refman-5.1/dba-core.xml
===================================================================
--- trunk/pt/refman-5.1/dba-core.xml 2008-02-15 10:42:01 UTC (rev 9846)
+++ trunk/pt/refman-5.1/dba-core.xml 2008-02-15 11:14:01 UTC (rev 9847)
Changed blocks: 4, Lines Added: 7, Lines Deleted: 27; 3002 bytes
@@ -6293,25 +6293,6 @@
</listitem>
<listitem>
- <para id="option_mysqld_multi_read_range">
- <literal>multi_read_range</literal>
- </para>
-
- <para condition="dynamic:optvar:item"
role="5.1:mysqld:multi_read_range"/>
-
- <para>
- Specifies the maximum number of ranges to send to a storage
- engine during range selects. The default value is 256.
- Sending multiple ranges to an engine is a feature that can
- improve the performance of certain selects dramatically,
- particularly for <literal>NDBCLUSTER</literal>. This engine
- needs to send the range requests to all nodes, and sending
- many of those requests at once reduces the communication
- costs significantly.
- </para>
- </listitem>
-
- <listitem>
<para id="option_mysqld_named_pipe">
<literal>named_pipe</literal>
</para>
@@ -6934,9 +6915,9 @@
<para>
The current number of prepared statements. (The maximum
number of statements is given by the
- <literal>max_prepared_stmt_count</literal> system
- variable.) This variable was added in MySQL 5.1.10. In MySQL
- 5.1.14, it was converted to the global
+ <literal>max_prepared_stmt_count</literal> system variable.)
+ This variable was added in MySQL 5.1.10. In MySQL 5.1.14, it
+ was converted to the global
<literal>Prepared_stmt_count</literal> status variable.
</para>
</listitem>
@@ -9207,9 +9188,8 @@
command set used in the network layer. In other words, their
values increase whenever prepared statement API calls such
as <command>mysql_stmt_prepare()</command>,
- <command>mysql_stmt_execute()</command>, and so forth
- are executed. However,
- <literal>Com_stmt_prepare</literal>,
+ <command>mysql_stmt_execute()</command>, and so forth are
+ executed. However, <literal>Com_stmt_prepare</literal>,
<literal>Com_stmt_execute</literal> and
<literal>Com_stmt_close</literal> also increase for
<literal>PREPARE</literal>,
<literal>EXECUTE</literal>, or
@@ -10247,8 +10227,8 @@
<para>
The current number of prepared statements. (The maximum
number of statements is given by the
- <literal>max_prepared_stmt_count</literal> system
- variable.) This variable was added in MySQL 5.1.14.
+ <literal>max_prepared_stmt_count</literal> system variable.)
+ This variable was added in MySQL 5.1.14.
</para>
</listitem>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r9847 - in trunk: it/refman-5.1 pt/refman-5.1 | jon | 15 Feb |