Author: paul
Date: 2007-07-26 19:54:13 +0200 (Thu, 26 Jul 2007)
New Revision: 7240
Log:
r27975@polar: paul | 2007-07-26 12:30:30 -0500
Add cross reference.
Modified:
trunk/refman-4.1/dba-core.xml
trunk/refman-5.0/dba-core.xml
trunk/refman-5.1/dba-core.xml
trunk/refman-5.2/dba-core.xml
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:27974
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:23051
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:18941
+ 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:27975
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:23051
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:18941
Modified: trunk/refman-4.1/dba-core.xml
===================================================================
--- trunk/refman-4.1/dba-core.xml 2007-07-26 17:52:53 UTC (rev 7239)
+++ trunk/refman-4.1/dba-core.xml 2007-07-26 17:54:13 UTC (rev 7240)
Changed blocks: 1, Lines Added: 7, Lines Deleted: 6; 1345 bytes
@@ -6003,12 +6003,13 @@
<para>
When reading rows in sorted order following a key-sorting
operation, the rows are read through this buffer to avoid
- disk seeks. Setting the variable to a large value can
- improve <literal>ORDER BY</literal> performance by a lot.
- However, this is a buffer allocated for each client, so
- you should not set the global variable to a large value.
- Instead, change the session variable only from within
- those clients that need to run large queries.
+ disk seeks. See <xref linkend="order-by-optimization"/>.
+ Setting the variable to a large value can improve
+ <literal>ORDER BY</literal> performance by a lot. However,
+ this is a buffer allocated for each client, so you should
+ not set the global variable to a large value. Instead,
+ change the session variable only from within those clients
+ that need to run large queries.
</para>
<para>
Modified: trunk/refman-5.0/dba-core.xml
===================================================================
--- trunk/refman-5.0/dba-core.xml 2007-07-26 17:52:53 UTC (rev 7239)
+++ trunk/refman-5.0/dba-core.xml 2007-07-26 17:54:13 UTC (rev 7240)
Changed blocks: 1, Lines Added: 7, Lines Deleted: 6; 1345 bytes
@@ -6554,12 +6554,13 @@
<para>
When reading rows in sorted order following a key-sorting
operation, the rows are read through this buffer to avoid
- disk seeks. Setting the variable to a large value can
- improve <literal>ORDER BY</literal> performance by a lot.
- However, this is a buffer allocated for each client, so
- you should not set the global variable to a large value.
- Instead, change the session variable only from within
- those clients that need to run large queries.
+ disk seeks. See <xref linkend="order-by-optimization"/>.
+ Setting the variable to a large value can improve
+ <literal>ORDER BY</literal> performance by a lot. However,
+ this is a buffer allocated for each client, so you should
+ not set the global variable to a large value. Instead,
+ change the session variable only from within those clients
+ that need to run large queries.
</para>
<para>
Modified: trunk/refman-5.1/dba-core.xml
===================================================================
--- trunk/refman-5.1/dba-core.xml 2007-07-26 17:52:53 UTC (rev 7239)
+++ trunk/refman-5.1/dba-core.xml 2007-07-26 17:54:13 UTC (rev 7240)
Changed blocks: 1, Lines Added: 7, Lines Deleted: 6; 1345 bytes
@@ -6848,12 +6848,13 @@
<para>
When reading rows in sorted order following a key-sorting
operation, the rows are read through this buffer to avoid
- disk seeks. Setting the variable to a large value can
- improve <literal>ORDER BY</literal> performance by a lot.
- However, this is a buffer allocated for each client, so
- you should not set the global variable to a large value.
- Instead, change the session variable only from within
- those clients that need to run large queries.
+ disk seeks. See <xref linkend="order-by-optimization"/>.
+ Setting the variable to a large value can improve
+ <literal>ORDER BY</literal> performance by a lot. However,
+ this is a buffer allocated for each client, so you should
+ not set the global variable to a large value. Instead,
+ change the session variable only from within those clients
+ that need to run large queries.
</para>
<para>
Modified: trunk/refman-5.2/dba-core.xml
===================================================================
--- trunk/refman-5.2/dba-core.xml 2007-07-26 17:52:53 UTC (rev 7239)
+++ trunk/refman-5.2/dba-core.xml 2007-07-26 17:54:13 UTC (rev 7240)
Changed blocks: 1, Lines Added: 7, Lines Deleted: 6; 1345 bytes
@@ -6783,12 +6783,13 @@
<para>
When reading rows in sorted order following a key-sorting
operation, the rows are read through this buffer to avoid
- disk seeks. Setting the variable to a large value can
- improve <literal>ORDER BY</literal> performance by a lot.
- However, this is a buffer allocated for each client, so
- you should not set the global variable to a large value.
- Instead, change the session variable only from within
- those clients that need to run large queries.
+ disk seeks. See <xref linkend="order-by-optimization"/>.
+ Setting the variable to a large value can improve
+ <literal>ORDER BY</literal> performance by a lot. However,
+ this is a buffer allocated for each client, so you should
+ not set the global variable to a large value. Instead,
+ change the session variable only from within those clients
+ that need to run large queries.
</para>
<para>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r7240 - in trunk: . refman-4.1 refman-5.0 refman-5.1 refman-5.2 | paul | 26 Jul |
