svn commit - mysqldoc@docsrva: r17516 - in trunk: . dynamic-docs/command-optvars refman-4.1 refman-5.0 refman-5.1 refman-5.4 refman-5.5

[paul.dubois]

Author: paul
Date: 2009-11-07 18:41:51 +0100 (Sat, 07 Nov 2009)
New Revision: 17516

Log:
 r46244@frost:  paul | 2009-11-07 11:40:26 -0500
 Fix docs bug:
 Bug#48519: InnoDB does 8 random dives, not 10 AFAIK


Modified:
   trunk/dynamic-docs/command-optvars/mysqld.xml
   trunk/refman-4.1/se-innodb-core.xml
   trunk/refman-5.0/se-innodb-core.xml
   trunk/refman-5.1/se-innodb-core.xml
   trunk/refman-5.4/se-innodb-core.xml
   trunk/refman-5.5/se-innodb-core.xml

Property changes on: trunk
___________________________________________________________________
Name: svk:merge
   - 07c7e7b4-24e3-4b51-89d0-6dc09fec6bec:/mysqldoc-local/mysqldoc/trunk:27680
07c7e7b4-24e3-4b51-89d0-6dc09fec6bec:/mysqldoc-local/trunk:25547
4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:43968
4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/trunk:44480
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:46243
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:39036
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/trunk:39546
   + 07c7e7b4-24e3-4b51-89d0-6dc09fec6bec:/mysqldoc-local/mysqldoc/trunk:27680
07c7e7b4-24e3-4b51-89d0-6dc09fec6bec:/mysqldoc-local/trunk:25547
4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:43968
4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/trunk:44480
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:46244
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:39036
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/trunk:39546


Modified: trunk/dynamic-docs/command-optvars/mysqld.xml
===================================================================
--- trunk/dynamic-docs/command-optvars/mysqld.xml	2009-11-07 17:41:41 UTC (rev 17515)
+++ trunk/dynamic-docs/command-optvars/mysqld.xml	2009-11-07 17:41:51 UTC (rev 17516)
Changed blocks: 1, Lines Added: 2, Lines Deleted: 1; 566 bytes

@@ -11349,7 +11349,8 @@
     <name>innodb_stats_sample_pages</name>
 
     <shortdescription>
-      How many index pages to sample for statistics calculations
+      The number of index pages to sample for index distribution
+      statistics
     </shortdescription>
 
     <types>


Modified: trunk/refman-4.1/se-innodb-core.xml
===================================================================
--- trunk/refman-4.1/se-innodb-core.xml	2009-11-07 17:41:41 UTC (rev 17515)
+++ trunk/refman-4.1/se-innodb-core.xml	2009-11-07 17:41:51 UTC (rev 17516)
Changed blocks: 1, Lines Added: 4, Lines Deleted: 4; 1211 bytes

@@ -9381,10 +9381,10 @@
           <literal role="stmt">ANALYZE TABLE</literal> determines index
           cardinality (as displayed in the
           <literal>Cardinality</literal> column of
-          <literal role="stmt">SHOW INDEX</literal> output) by doing ten
-          random dives to each of the index trees and updating index
-          cardinality estimates accordingly. Because these are only
-          estimates, repeated runs of <literal role="stmt">ANALYZE
+          <literal role="stmt">SHOW INDEX</literal> output) by doing
+          eight random dives to each of the index trees and updating
+          index cardinality estimates accordingly. Because these are
+          only estimates, repeated runs of <literal role="stmt">ANALYZE
           TABLE</literal> may produce different numbers. This makes
           <literal role="stmt">ANALYZE TABLE</literal> fast on
           <literal>InnoDB</literal> tables but not 100% accurate because


Modified: trunk/refman-5.0/se-innodb-core.xml
===================================================================
--- trunk/refman-5.0/se-innodb-core.xml	2009-11-07 17:41:41 UTC (rev 17515)
+++ trunk/refman-5.0/se-innodb-core.xml	2009-11-07 17:41:51 UTC (rev 17516)
Changed blocks: 1, Lines Added: 4, Lines Deleted: 4; 1211 bytes

@@ -9367,10 +9367,10 @@
           <literal role="stmt">ANALYZE TABLE</literal> determines index
           cardinality (as displayed in the
           <literal>Cardinality</literal> column of
-          <literal role="stmt">SHOW INDEX</literal> output) by doing ten
-          random dives to each of the index trees and updating index
-          cardinality estimates accordingly. Because these are only
-          estimates, repeated runs of <literal role="stmt">ANALYZE
+          <literal role="stmt">SHOW INDEX</literal> output) by doing
+          eight random dives to each of the index trees and updating
+          index cardinality estimates accordingly. Because these are
+          only estimates, repeated runs of <literal role="stmt">ANALYZE
           TABLE</literal> may produce different numbers. This makes
           <literal role="stmt">ANALYZE TABLE</literal> fast on
           <literal>InnoDB</literal> tables but not 100% accurate because


Modified: trunk/refman-5.1/se-innodb-core.xml
===================================================================
--- trunk/refman-5.1/se-innodb-core.xml	2009-11-07 17:41:41 UTC (rev 17515)
+++ trunk/refman-5.1/se-innodb-core.xml	2009-11-07 17:41:51 UTC (rev 17516)
Changed blocks: 4, Lines Added: 35, Lines Deleted: 6; 3020 bytes

@@ -2687,6 +2687,25 @@
       </listitem>
 
       <listitem>
+        <para id="sysvar_innodb_stats_sample_pages">
+          <literal role="sysvar">innodb_stats_sample_pages</literal>
+        </para>
+
+        <para condition="dynamic:optvar:item"
role="5.1:mysqld:innodb_stats_sample_pages"/>
+
+        <para>
+          (<literal>InnoDB Plugin</literal> only) The number of index
+          pages to sample for index distribution statistics such as are
+          calculated by <literal role="stmt">ANALYZE TABLE</literal>.
+          The default value is 8.
+        </para>
+
+        <para>
+          This variable was added in MySQL 5.1.38.
+        </para>
+      </listitem>
+
+      <listitem>
         <para id="sysvar_innodb_support_xa">
           <literal role="sysvar">innodb_support_xa</literal>
         </para>

@@ -2820,8 +2839,11 @@
         </para>
 
         <para>
-          This variable is not used in &next-series; because the
-          improved algorithm is used by default.
+          This variable is not used in <literal>InnoDB Plugin</literal>
+          because the improved algorithm is used by default. Also, the
+          number of random dives can be changed by modifying the
+          <literal role="sysvar">innodb_stats_sample_pages</literal>
+          system variable.
         </para>
       </listitem>
 

@@ -10521,10 +10543,10 @@
           <literal role="stmt">ANALYZE TABLE</literal> determines index
           cardinality (as displayed in the
           <literal>Cardinality</literal> column of
-          <literal role="stmt">SHOW INDEX</literal> output) by doing ten
-          random dives to each of the index trees and updating index
-          cardinality estimates accordingly. Because these are only
-          estimates, repeated runs of <literal role="stmt">ANALYZE
+          <literal role="stmt">SHOW INDEX</literal> output) by doing
+          eight random dives to each of the index trees and updating
+          index cardinality estimates accordingly. Because these are
+          only estimates, repeated runs of <literal role="stmt">ANALYZE
           TABLE</literal> may produce different numbers. This makes
           <literal role="stmt">ANALYZE TABLE</literal> fast on
           <literal>InnoDB</literal> tables but not 100% accurate because

@@ -10532,6 +10554,13 @@
         </para>
 
         <para>
+          For <literal>InnoDB Plugin</literal>, the number of random
+          dives can be changed by modifying the
+          <literal role="sysvar">innodb_stats_sample_pages</literal>
+          system variable.
+        </para>
+
+        <para>
           MySQL uses index cardinality estimates only in join
           optimization. If some join is not optimized in the right way,
           you can try using <literal role="stmt">ANALYZE


Modified: trunk/refman-5.4/se-innodb-core.xml
===================================================================
--- trunk/refman-5.4/se-innodb-core.xml	2009-11-07 17:41:41 UTC (rev 17515)
+++ trunk/refman-5.4/se-innodb-core.xml	2009-11-07 17:41:51 UTC (rev 17516)
Changed blocks: 3, Lines Added: 29, Lines Deleted: 4; 2424 bytes

@@ -2416,6 +2416,25 @@
       </listitem>
 
       <listitem>
+        <para id="sysvar_innodb_stats_sample_pages">
+          <literal role="sysvar">innodb_stats_sample_pages</literal>
+        </para>
+
+        <para condition="dynamic:optvar:item"
role="5.4:mysqld:innodb_stats_sample_pages"/>
+
+        <para>
+          The number of index pages to sample for index distribution
+          statistics such as are calculated by
+          <literal role="stmt">ANALYZE TABLE</literal>. The default
+          value is 8.
+        </para>
+
+        <para>
+          This variable was added in MySQL 5.4.2.
+        </para>
+      </listitem>
+
+      <listitem>
         <para id="sysvar_innodb_support_xa">
           <literal role="sysvar">innodb_support_xa</literal>
         </para>

@@ -10226,10 +10245,10 @@
           <literal role="stmt">ANALYZE TABLE</literal> determines index
           cardinality (as displayed in the
           <literal>Cardinality</literal> column of
-          <literal role="stmt">SHOW INDEX</literal> output) by doing ten
-          random dives to each of the index trees and updating index
-          cardinality estimates accordingly. Because these are only
-          estimates, repeated runs of <literal role="stmt">ANALYZE
+          <literal role="stmt">SHOW INDEX</literal> output) by doing
+          eight random dives to each of the index trees and updating
+          index cardinality estimates accordingly. Because these are
+          only estimates, repeated runs of <literal role="stmt">ANALYZE
           TABLE</literal> may produce different numbers. This makes
           <literal role="stmt">ANALYZE TABLE</literal> fast on
           <literal>InnoDB</literal> tables but not 100% accurate because

@@ -10237,6 +10256,12 @@
         </para>
 
         <para>
+          The number of random dives can be changed by modifying the
+          <literal role="sysvar">innodb_stats_sample_pages</literal>
+          system variable.
+        </para>
+
+        <para>
           MySQL uses index cardinality estimates only in join
           optimization. If some join is not optimized in the right way,
           you can try using <literal role="stmt">ANALYZE


Modified: trunk/refman-5.5/se-innodb-core.xml
===================================================================
--- trunk/refman-5.5/se-innodb-core.xml	2009-11-07 17:41:41 UTC (rev 17515)
+++ trunk/refman-5.5/se-innodb-core.xml	2009-11-07 17:41:51 UTC (rev 17516)
Changed blocks: 3, Lines Added: 25, Lines Deleted: 4; 2342 bytes

@@ -2405,6 +2405,21 @@
       </listitem>
 
       <listitem>
+        <para id="sysvar_innodb_stats_sample_pages">
+          <literal role="sysvar">innodb_stats_sample_pages</literal>
+        </para>
+
+        <para condition="dynamic:optvar:item"
role="5.5:mysqld:innodb_stats_sample_pages"/>
+
+        <para>
+          The number of index pages to sample for index distribution
+          statistics such as are calculated by
+          <literal role="stmt">ANALYZE TABLE</literal>. The default
+          value is 8.
+        </para>
+      </listitem>
+
+      <listitem>
         <para id="sysvar_innodb_support_xa">
           <literal role="sysvar">innodb_support_xa</literal>
         </para>

@@ -10197,10 +10212,10 @@
           <literal role="stmt">ANALYZE TABLE</literal> determines index
           cardinality (as displayed in the
           <literal>Cardinality</literal> column of
-          <literal role="stmt">SHOW INDEX</literal> output) by doing ten
-          random dives to each of the index trees and updating index
-          cardinality estimates accordingly. Because these are only
-          estimates, repeated runs of <literal role="stmt">ANALYZE
+          <literal role="stmt">SHOW INDEX</literal> output) by doing
+          eight random dives to each of the index trees and updating
+          index cardinality estimates accordingly. Because these are
+          only estimates, repeated runs of <literal role="stmt">ANALYZE
           TABLE</literal> may produce different numbers. This makes
           <literal role="stmt">ANALYZE TABLE</literal> fast on
           <literal>InnoDB</literal> tables but not 100% accurate because

@@ -10208,6 +10223,12 @@
         </para>
 
         <para>
+          The number of random dives can be changed by modifying the
+          <literal role="sysvar">innodb_stats_sample_pages</literal>
+          system variable.
+        </para>
+
+        <para>
           MySQL uses index cardinality estimates only in join
           optimization. If some join is not optimized in the right way,
           you can try using <literal role="stmt">ANALYZE