svn commit - mysqldoc@docsrva: r2433 - in trunk: refman-4.1 refman-5.0 refman-5.1

[mcbrown]

Author: mcbrown
Date: 2006-06-20 15:27:52 +0200 (Tue, 20 Jun 2006)
New Revision: 2433

Log:
Documenting Docs bug 20449 (InnoDB ANALYZE tables)
Fixed InnoDB to Write Lock, added link to the InnoDB docs on Analyze Table 



Modified:
   trunk/refman-4.1/innodb.xml
   trunk/refman-4.1/sql-syntax.xml
   trunk/refman-5.0/innodb.xml
   trunk/refman-5.0/sql-syntax.xml
   trunk/refman-5.1/innodb.xml
   trunk/refman-5.1/sql-syntax.xml

Modified: trunk/refman-4.1/innodb.xml
===================================================================
--- trunk/refman-4.1/innodb.xml	2006-06-20 11:44:11 UTC (rev 2432)
+++ trunk/refman-4.1/innodb.xml	2006-06-20 13:27:52 UTC (rev 2433)
@@ -7013,7 +7013,7 @@
         <para>
           <literal>ANALYZE TABLE</literal> determines index cardinality
           (as displayed in the <literal>Cardinality</literal> column of
-          <literal>SHOW INDEX</literal> output) by doing eight random
+          <literal>SHOW INDEX</literal> output) by doing ten random
           dives to each of the index trees and updating index
           cardinality estimates accordingly. Note that because these are
           only estimates, repeated runs of <literal>ANALYZE

Modified: trunk/refman-4.1/sql-syntax.xml
===================================================================
--- trunk/refman-4.1/sql-syntax.xml	2006-06-20 11:44:11 UTC (rev 2432)
+++ trunk/refman-4.1/sql-syntax.xml	2006-06-20 13:27:52 UTC (rev 2433)
@@ -12081,7 +12081,9 @@
         <para>
           <literal>ANALYZE TABLE</literal> analyzes and stores the key
           distribution for a table. During the analysis, the table is
-          locked with a read lock. This statement works with
+          locked with a read lock for <literal>MyISAM</literal> and
+          <literal>BDB</literal>. For <literal>InnoDB</literal>
the
+          table is locked with a write lock. This statement works with
           <literal>MyISAM</literal>, <literal>BDB</literal>, and
(as of
           MySQL 4.0.13) <literal>InnoDB</literal> tables. For
           <literal>MyISAM</literal> tables, this statement is equivalent
@@ -12089,6 +12091,12 @@
         </para>
 
         <para>
+          For more information on how the analysis works
+          within<literal>InnoDB</literal>, see
+          <xref linkend="innodb-restrictions"/>.
+        </para>
+
+        <para>
           MySQL uses the stored key distribution to decide the order in
           which tables should be joined when you perform a join on
           something other than a constant.

Modified: trunk/refman-5.0/innodb.xml
===================================================================
--- trunk/refman-5.0/innodb.xml	2006-06-20 11:44:11 UTC (rev 2432)
+++ trunk/refman-5.0/innodb.xml	2006-06-20 13:27:52 UTC (rev 2433)
@@ -7080,7 +7080,7 @@
         <para>
           <literal>ANALYZE TABLE</literal> determines index cardinality
           (as displayed in the <literal>Cardinality</literal> column of
-          <literal>SHOW INDEX</literal> output) by doing eight random
+          <literal>SHOW INDEX</literal> output) by doing ten random
           dives to each of the index trees and updating index
           cardinality estimates accordingly. Note that because these are
           only estimates, repeated runs of <literal>ANALYZE

Modified: trunk/refman-5.0/sql-syntax.xml
===================================================================
--- trunk/refman-5.0/sql-syntax.xml	2006-06-20 11:44:11 UTC (rev 2432)
+++ trunk/refman-5.0/sql-syntax.xml	2006-06-20 13:27:52 UTC (rev 2433)
@@ -13549,7 +13549,9 @@
         <para>
           <literal>ANALYZE TABLE</literal> analyzes and stores the key
           distribution for a table. During the analysis, the table is
-          locked with a read lock. This statement works with
+          locked with a read lock for <literal>MyISAM</literal> and
+          <literal>BDB</literal>. For <literal>InnoDB</literal>
the
+          table is locked with a write lock. This statement works with
           <literal>MyISAM</literal>, <literal>BDB</literal>, and
           <literal>InnoDB</literal> tables. For
           <literal>MyISAM</literal> tables, this statement is equivalent
@@ -13557,6 +13559,12 @@
         </para>
 
         <para>
+          For more information on how the analysis works
+          within<literal>InnoDB</literal>, see
+          <xref linkend="innodb-restrictions"/>.
+        </para>
+
+        <para>
           MySQL uses the stored key distribution to decide the order in
           which tables should be joined when you perform a join on
           something other than a constant.

Modified: trunk/refman-5.1/innodb.xml
===================================================================
--- trunk/refman-5.1/innodb.xml	2006-06-20 11:44:11 UTC (rev 2432)
+++ trunk/refman-5.1/innodb.xml	2006-06-20 13:27:52 UTC (rev 2433)
@@ -7030,7 +7030,7 @@
         <para>
           <literal>ANALYZE TABLE</literal> determines index cardinality
           (as displayed in the <literal>Cardinality</literal> column of
-          <literal>SHOW INDEX</literal> output) by doing eight random
+          <literal>SHOW INDEX</literal> output) by doing ten random
           dives to each of the index trees and updating index
           cardinality estimates accordingly. Note that because these are
           only estimates, repeated runs of <literal>ANALYZE

Modified: trunk/refman-5.1/sql-syntax.xml
===================================================================
--- trunk/refman-5.1/sql-syntax.xml	2006-06-20 11:44:11 UTC (rev 2432)
+++ trunk/refman-5.1/sql-syntax.xml	2006-06-20 13:27:52 UTC (rev 2433)
@@ -14772,7 +14772,9 @@
         <para>
           <literal>ANALYZE TABLE</literal> analyzes and stores the key
           distribution for a table. During the analysis, the table is
-          locked with a read lock. This statement works with
+          locked with a read lock for <literal>MyISAM</literal> and
+          <literal>BDB</literal>. For <literal>InnoDB</literal>
the
+          table is locked with a write lock. This statement works with
           <literal>MyISAM</literal>, <literal>BDB</literal>, and
           <literal>InnoDB</literal> tables. For
           <literal>MyISAM</literal> tables, this statement is equivalent
@@ -14780,6 +14782,12 @@
         </para>
 
         <para>
+          For more information on how the analysis works
+          within<literal>InnoDB</literal>, see
+          <xref linkend="innodb-restrictions"/>.
+        </para>
+
+        <para>
           MySQL uses the stored key distribution to decide the order in
           which tables should be joined when you perform a join on
           something other than a constant.