Author: paul
Date: 2010-12-08 04:22:25 +0100 (Wed, 08 Dec 2010)
New Revision: 24315
Log:
r36894@dhcp-215: paul | 2010-12-07 21:22:17 -0500
Fix docs bug:
- Bug#58551: Optimize table after load or insert into ... select gives 25% speed increase
Modified:
trunk/refman-4.1/sql-syntax-server-administration.xml
trunk/refman-5.0/sql-syntax-server-administration.xml
trunk/refman-5.1/sql-syntax-server-administration.xml
trunk/refman-5.5/sql-syntax-server-administration.xml
trunk/refman-5.6/sql-syntax-server-administration.xml
trunk/refman-6.0/sql-syntax-server-administration.xml
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- 07c7e7b4-24e3-4b51-89d0-6dc09fec6bec:/mysqldoc-local/mysqldoc/trunk:35498
07c7e7b4-24e3-4b51-89d0-6dc09fec6bec:/mysqldoc-local/trunk:45180
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:66486
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
ebeeeee4-b232-4669-a521-231442eced53:/mysqldoc-local/mysqldoc/trunk:36892
+ 07c7e7b4-24e3-4b51-89d0-6dc09fec6bec:/mysqldoc-local/mysqldoc/trunk:35498
07c7e7b4-24e3-4b51-89d0-6dc09fec6bec:/mysqldoc-local/trunk:45180
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:66486
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
ebeeeee4-b232-4669-a521-231442eced53:/mysqldoc-local/mysqldoc/trunk:36894
Modified: trunk/refman-4.1/sql-syntax-server-administration.xml
===================================================================
--- trunk/refman-4.1/sql-syntax-server-administration.xml 2010-12-08 03:16:18 UTC (rev 24314)
+++ trunk/refman-4.1/sql-syntax-server-administration.xml 2010-12-08 03:22:25 UTC (rev 24315)
Changed blocks: 2, Lines Added: 3, Lines Deleted: 8; 1351 bytes
@@ -2249,7 +2249,9 @@
<literal role="stmt">INSERT</literal> operations reuse old row
positions. You can use <literal role="stmt">OPTIMIZE
TABLE</literal> to reclaim the unused space and to defragment
- the data file.
+ the data file. After extensive changes to a table, this
+ statement may also improve performance of statements that use
+ the table, sometimes significantly.
</para>
<para>
@@ -2261,13 +2263,6 @@
<remark role="help-description-end"/>
<para>
- In most setups, you need not run <literal role="stmt">OPTIMIZE
- TABLE</literal> at all. Even if you do a lot of updates to
- variable-length rows, it is not likely that you need to do this
- more than once a week or month and only on certain tables.
- </para>
-
- <para>
<literal role="stmt">OPTIMIZE TABLE</literal> works
<emphasis>only</emphasis> for <literal>MyISAM</literal>,
<literal>BDB</literal>, and <literal>InnoDB</literal> tables. It
Modified: trunk/refman-5.0/sql-syntax-server-administration.xml
===================================================================
--- trunk/refman-5.0/sql-syntax-server-administration.xml 2010-12-08 03:16:18 UTC (rev 24314)
+++ trunk/refman-5.0/sql-syntax-server-administration.xml 2010-12-08 03:22:25 UTC (rev 24315)
Changed blocks: 2, Lines Added: 3, Lines Deleted: 8; 1338 bytes
@@ -2674,7 +2674,9 @@
<literal role="stmt">INSERT</literal> operations reuse old row
positions. You can use <literal role="stmt">OPTIMIZE
TABLE</literal> to reclaim the unused space and to defragment
- the data file.
+ the data file. After extensive changes to a table, this
+ statement may also improve performance of statements that use
+ the table, sometimes significantly.
</para>
<para>
@@ -2686,13 +2688,6 @@
<remark role="help-description-end"/>
<para>
- In most setups, you need not run <literal role="stmt">OPTIMIZE
- TABLE</literal> at all. Even if you do a lot of updates to
- variable-length rows, it is not likely that you need to do this
- more than once a week or month and only on certain tables.
- </para>
-
- <para>
<literal role="stmt">OPTIMIZE TABLE</literal> works
<emphasis>only</emphasis> for <literal>MyISAM</literal>,
<literal>InnoDB</literal>, and (as of MySQL 5.0.16)
Modified: trunk/refman-5.1/sql-syntax-server-administration.xml
===================================================================
--- trunk/refman-5.1/sql-syntax-server-administration.xml 2010-12-08 03:16:18 UTC (rev 24314)
+++ trunk/refman-5.1/sql-syntax-server-administration.xml 2010-12-08 03:22:25 UTC (rev 24315)
Changed blocks: 2, Lines Added: 3, Lines Deleted: 8; 1326 bytes
@@ -2631,7 +2631,9 @@
<literal role="stmt">INSERT</literal> operations reuse old row
positions. You can use <literal role="stmt">OPTIMIZE
TABLE</literal> to reclaim the unused space and to defragment
- the data file.
+ the data file. After extensive changes to a table, this
+ statement may also improve performance of statements that use
+ the table, sometimes significantly.
</para>
<para>
@@ -2653,13 +2655,6 @@
<remark role="help-description-end"/>
<para>
- In most setups, you need not run <literal role="stmt">OPTIMIZE
- TABLE</literal> at all. Even if you do a lot of updates to
- variable-length rows, it is not likely that you need to do this
- more than once a week or month and only on certain tables.
- </para>
-
- <para>
<literal role="stmt">OPTIMIZE TABLE</literal> works for
<literal>MyISAM</literal>, <literal>InnoDB</literal>, and
<literal>ARCHIVE</literal> tables.
Modified: trunk/refman-5.5/sql-syntax-server-administration.xml
===================================================================
--- trunk/refman-5.5/sql-syntax-server-administration.xml 2010-12-08 03:16:18 UTC (rev 24314)
+++ trunk/refman-5.5/sql-syntax-server-administration.xml 2010-12-08 03:22:25 UTC (rev 24315)
Changed blocks: 2, Lines Added: 3, Lines Deleted: 8; 1344 bytes
@@ -2655,7 +2655,9 @@
<literal role="stmt">INSERT</literal> operations reuse old row
positions. You can use <literal role="stmt">OPTIMIZE
TABLE</literal> to reclaim the unused space and to defragment
- the data file.
+ the data file. After extensive changes to a table, this
+ statement may also improve performance of statements that use
+ the table, sometimes significantly.
</para>
<para>
@@ -2675,13 +2677,6 @@
<remark role="help-description-end"/>
<para>
- In most setups, you need not run <literal role="stmt">OPTIMIZE
- TABLE</literal> at all. Even if you do a lot of updates to
- variable-length rows, it is not likely that you need to do this
- more than once a week or month and only on certain tables.
- </para>
-
- <para>
<literal role="stmt">OPTIMIZE TABLE</literal> works
<emphasis>only</emphasis> for <literal>MyISAM</literal>,
<literal>InnoDB</literal>, and <literal>ARCHIVE</literal>
Modified: trunk/refman-5.6/sql-syntax-server-administration.xml
===================================================================
--- trunk/refman-5.6/sql-syntax-server-administration.xml 2010-12-08 03:16:18 UTC (rev 24314)
+++ trunk/refman-5.6/sql-syntax-server-administration.xml 2010-12-08 03:22:25 UTC (rev 24315)
Changed blocks: 2, Lines Added: 3, Lines Deleted: 8; 1344 bytes
@@ -2649,7 +2649,9 @@
<literal role="stmt">INSERT</literal> operations reuse old row
positions. You can use <literal role="stmt">OPTIMIZE
TABLE</literal> to reclaim the unused space and to defragment
- the data file.
+ the data file. After extensive changes to a table, this
+ statement may also improve performance of statements that use
+ the table, sometimes significantly.
</para>
<para>
@@ -2669,13 +2671,6 @@
<remark role="help-description-end"/>
<para>
- In most setups, you need not run <literal role="stmt">OPTIMIZE
- TABLE</literal> at all. Even if you do a lot of updates to
- variable-length rows, it is not likely that you need to do this
- more than once a week or month and only on certain tables.
- </para>
-
- <para>
<literal role="stmt">OPTIMIZE TABLE</literal> works
<emphasis>only</emphasis> for <literal>MyISAM</literal>,
<literal>InnoDB</literal>, and <literal>ARCHIVE</literal>
Modified: trunk/refman-6.0/sql-syntax-server-administration.xml
===================================================================
--- trunk/refman-6.0/sql-syntax-server-administration.xml 2010-12-08 03:16:18 UTC (rev 24314)
+++ trunk/refman-6.0/sql-syntax-server-administration.xml 2010-12-08 03:22:25 UTC (rev 24315)
Changed blocks: 2, Lines Added: 3, Lines Deleted: 8; 1344 bytes
@@ -2533,7 +2533,9 @@
<literal role="stmt">INSERT</literal> operations reuse old row
positions. You can use <literal role="stmt">OPTIMIZE
TABLE</literal> to reclaim the unused space and to defragment
- the data file.
+ the data file. After extensive changes to a table, this
+ statement may also improve performance of statements that use
+ the table, sometimes significantly.
</para>
<para>
@@ -2554,13 +2556,6 @@
<remark role="help-description-end"/>
<para>
- In most setups, you need not run <literal role="stmt">OPTIMIZE
- TABLE</literal> at all. Even if you do a lot of updates to
- variable-length rows, it is not likely that you need to do this
- more than once a week or month and only on certain tables.
- </para>
-
- <para>
<literal role="stmt">OPTIMIZE TABLE</literal> works
<emphasis>only</emphasis> for <literal>MyISAM</literal>,
<literal>InnoDB</literal>, and <literal>ARCHIVE</literal>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r24315 - in trunk: . refman-4.1 refman-5.0 refman-5.1 refman-5.5 refman-5.6 refman-6.0 | paul.dubois | 8 Dec |
