Author: jstephens
Date: 2008-07-10 16:50:18 +0200 (Thu, 10 Jul 2008)
New Revision: 11177
Log:
Fixing Docs Bug #37999 (mysqlcheck/myisamchk doesn't work with
partitioned tables)
Modified:
trunk/refman-5.1/Makefile.depends
trunk/refman-5.1/partitioning.xml
trunk/refman-5.1/programs-admin-util-core.xml
trunk/refman-5.1/programs-client-core.xml
trunk/refman-5.1/sql-syntax.xml
trunk/refman-6.0/Makefile.depends
trunk/refman-6.0/partitioning.xml
trunk/refman-6.0/programs-admin-util-core.xml
trunk/refman-6.0/programs-client-core.xml
trunk/refman-6.0/sql-syntax.xml
Modified: trunk/refman-5.1/Makefile.depends
===================================================================
--- trunk/refman-5.1/Makefile.depends 2008-07-10 14:27:30 UTC (rev 11176)
+++ trunk/refman-5.1/Makefile.depends 2008-07-10 14:50:18 UTC (rev 11177)
Changed blocks: 1, Lines Added: 0, Lines Deleted: 2; 657 bytes
@@ -2492,8 +2492,6 @@
../refman-5.1/metadata/news-5.1-core.idmap \
../refman-5.1/metadata/optimization.idmap \
../refman-5.1/metadata/partitioning.idmap \
- ../refman-5.1/metadata/programs-admin-util-core.idmap \
- ../refman-5.1/metadata/programs-client-core.idmap \
../refman-5.1/metadata/sql-syntax.idmap
partitioning.validpure: $(partitioning_SOURCES)
partitioning.titles: $(partitioning_SOURCES)
Modified: trunk/refman-5.1/partitioning.xml
===================================================================
--- trunk/refman-5.1/partitioning.xml 2008-07-10 14:27:30 UTC (rev 11176)
+++ trunk/refman-5.1/partitioning.xml 2008-07-10 14:50:18 UTC (rev 11177)
Changed blocks: 8, Lines Added: 66, Lines Deleted: 41; 7325 bytes
@@ -1774,8 +1774,9 @@
using the table's primary key as the partitioning
key. In the event that the Cluster table has no explicit
primary key, the <quote>hidden</quote> primary key
- generated by the <literal>NDB</literal> storage engine for
- each Cluster table is used as the partitioning key.
+ generated by the <literal>NDBCLUSTER</literal> storage
+ engine for each MySQL Cluster table is used as the
+ partitioning key.
</para>
</note>
@@ -2370,8 +2371,8 @@
design tables so as not to allow nulls, usually by declaring
columns <literal>NOT NULL</literal>.) If you have a
<literal>RANGE</literal> partitioning scheme that depends on
- this earlier behavior, you will need to re-implement it when
- upgrading to MySQL 5.1.8 or later. (Bug #15447)
+ this earlier behavior, you must re-implement it when upgrading
+ to MySQL 5.1.8 or later. (Bug #15447)
</para>
</important>
@@ -2751,10 +2752,10 @@
In MySQL 5.1.7 and earlier MySQL 5.1 releases, <literal>ALTER
TABLE ... ENGINE = ...</literal> removed all partitioning from the
affected table. Beginning with MySQL 5.1.8, this statement changes
- only the storage engine used by the table, and leaves the table's
- partitioning scheme intact. As of MySQL 5.1.8, use <literal>ALTER
- TABLE ... REMOVE PARTITIONING</literal> to remove a table's
- partitioning. See <xref linkend="alter-table"/>.
+ only the storage engine used by the table, and leaves the
+ table's partitioning scheme intact. As of MySQL 5.1.8, use
+ <literal>ALTER TABLE ... REMOVE PARTITIONING</literal> to remove a
+ table's partitioning. See <xref linkend="alter-table"/>.
</para>
<important>
@@ -2869,14 +2870,15 @@
Query OK, 0 rows affected (0.03 sec)
</programlisting>
- <para>
- Note: In MySQL ¤t-series;, the
- <literal>NDBCLUSTER</literal> storage engine does not support
- <literal>ALTER TABLE ... DROP PARTITION</literal>. It does,
- however, support the other partitioning-related extensions to
- <literal>ALTER TABLE</literal> that are described in this
- chapter.
- </para>
+ <note>
+ <para>
+ The <literal>NDBCLUSTER</literal> storage engine does not
+ support <literal>ALTER TABLE ... DROP PARTITION</literal>. It
+ does, however, support the other partitioning-related
+ extensions to <literal>ALTER TABLE</literal> that are
+ described in this chapter.
+ </para>
+ </note>
<para>
It is very important to remember that, <emphasis>when you drop a
@@ -3541,23 +3543,23 @@
causes partition files to be rebuilt.
</para>
- <para>
- The statements <literal>ANALYZE PARTITION</literal>,
- <literal>CHECK PARTITION</literal>, <literal>OPTIMIZE
- PARTITION</literal>, and <literal>REPAIR PARTITION</literal>
- were also introduced in MySQL 5.1.5 for the purpose of,
- respectively, analyzing, checking, optimizing, and repairing
- individual or multiple partitions. Support for these statements
- was removed in MySQL 5.1.24. (Bug #20129)
- </para>
+ <note>
+ <para>
+ The statements <literal>ANALYZE PARTITION</literal>,
+ <literal>CHECK PARTITION</literal>, <literal>OPTIMIZE
+ PARTITION</literal>, and <literal>REPAIR PARTITION</literal>
+ — intended to, respectively, analyze, check, optimize,
+ and repair individual or multiple partitions — were
+ supported beginning with MySQL 5.1.5 and then removed in MySQL
+ 5.1.24. (Bug #20129)
+ </para>
- <para>
- To accomplish these tasks, you can use
- <command>mysqlcheck</command> or, with partitioned
- <literal>MyISAM</literal> tables, you can use
- <command>myisamchk</command>. See <xref linkend="mysqlcheck"/>,
- and <xref linkend="myisamchk"/>, for more information.
- </para>
+ <para>
+ The use of <command>mysqlcheck</command> or
+ <command>myisamchk</command> is also not supported with
+ partitioned tables.
+ </para>
+ </note>
</section>
@@ -3842,12 +3844,12 @@
</indexterm>
<para>
- This section discusses <firstterm>partition pruning</firstterm>,
- an optimization which was implemented for partitioned tables in
- MySQL 5.1.6. The core concept behind partition pruning is
- relatively simple, and can be described as <quote>Do not scan
- partitions where there can be no matching values</quote>. For
- example, suppose you have a partitioned table
+ This section discusses an optimization known as
+ <firstterm>partition pruning</firstterm>, which was implemented
+ for partitioned tables in MySQL 5.1.6. The core concept behind
+ partition pruning is relatively simple, and can be described as
+ <quote>Do not scan partitions where there can be no matching
+ values</quote>. For example, suppose you have a partitioned table
<literal>t1</literal> defined by this statement:
</para>
@@ -4753,6 +4755,29 @@
</formalpara>
</listitem>
+ <listitem>
+ <formalpara>
+
+ <title>Repairing and rebuilding partitioned tables</title>
+
+ <para>
+ The statements <literal>CHECK TABLE</literal>,
+ <literal>OPTIMIZE TABLE</literal>, <literal>ANALYZE
+ TABLE</literal>, and <literal>REPAIR TABLE</literal> are not
+ supported for partitioned tables.
+ <command>mysqlcheck</command> and
+ <command>myisamchk</command> are also not supported for
+ partitioned tables. However, you can use <literal>ALTER
+ TABLE ... REBUILD PARTITION</literal> to rebuild one or more
+ partitions of a partitioned table; <literal>ALTER TABLE ...
+ REORGANIZE PARTITION</literal> also causes partitions to be
+ rebuilt. See <xref linkend="alter-table"/>, for more
+ information about these two statements.
+ </para>
+
+ </formalpara>
+ </listitem>
+
</itemizedlist>
<section id="partitioning-limitations-partitioning-keys-unique-keys">
@@ -5163,9 +5188,9 @@
<para>
Partitioning by <literal>KEY</literal> (or <literal>LINEAR
KEY</literal>) is the only type of partitioning supported for
- the <literal>NDB</literal> storage engine. Beginning with
- MySQL 5.1.12, it is not possible to create a Cluster table
- using any partitioning type other than
+ the <literal>NDBCLUSTER</literal> storage engine. Beginning
+ with MySQL 5.1.12, it is not possible to create a MySQL
+ Cluster table using any partitioning type other than
[<literal>LINEAR</literal>] <literal>KEY</literal>, and
attempting to do so fails with an error.
</para>
Modified: trunk/refman-5.1/programs-admin-util-core.xml
===================================================================
--- trunk/refman-5.1/programs-admin-util-core.xml 2008-07-10 14:27:30 UTC (rev 11176)
+++ trunk/refman-5.1/programs-admin-util-core.xml 2008-07-10 14:50:18 UTC (rev 11177)
Changed blocks: 1, Lines Added: 5, Lines Deleted: 0; 592 bytes
@@ -403,6 +403,11 @@
for storing data and indexes).
</para>
+ <para>
+ The use of <command>myisamchk</command> with partitioned tables
+ is not supported.
+ </para>
+
<caution>
<para>
It is best to make a backup of a table before performing a
Modified: trunk/refman-5.1/programs-client-core.xml
===================================================================
--- trunk/refman-5.1/programs-client-core.xml 2008-07-10 14:27:30 UTC (rev 11176)
+++ trunk/refman-5.1/programs-client-core.xml 2008-07-10 14:50:18 UTC (rev 11177)
Changed blocks: 1, Lines Added: 5, Lines Deleted: 0; 614 bytes
@@ -4469,6 +4469,11 @@
note : The storage engine for the table doesn't support check
</programlisting>
+ <para>
+ The use of <command>mysqlcheck</command> with partitioned tables
+ is not supported.
+ </para>
+
<caution>
<para>
It is best to make a backup of a table before performing a
Modified: trunk/refman-5.1/sql-syntax.xml
===================================================================
--- trunk/refman-5.1/sql-syntax.xml 2008-07-10 14:27:30 UTC (rev 11176)
+++ trunk/refman-5.1/sql-syntax.xml 2008-07-10 14:50:18 UTC (rev 11177)
Changed blocks: 4, Lines Added: 24, Lines Deleted: 0; 1601 bytes
@@ -18068,6 +18068,11 @@
<literal>INSERT</literal> privileges for the table.
</para>
+ <para>
+ <literal>ANALYZE TABLE</literal> is not supported for
+ partitioned tables.
+ </para>
+
<remark role="help-description-end"/>
<para>
@@ -18266,6 +18271,11 @@
definition that no longer exist.
</para>
+ <para>
+ <literal>CHECK TABLE</literal> is not supported for
+ partitioned tables.
+ </para>
+
<remark role="help-description-end"/>
<para>
@@ -18673,6 +18683,13 @@
<literal>INSERT</literal> privileges for the table.
</para>
+ <para>
+ <literal>OPTIMIZE TABLE</literal> is not supported for
+ partitioned tables. See
+ <xref linkend="partitioning-maintenance"/>, for information
+ about alternatives.
+ </para>
+
<remark role="help-description-end"/>
<para>
@@ -18856,6 +18873,13 @@
<literal>INSERT</literal> privileges for the table.
</para>
+ <para>
+ <literal>REPAIR TABLE</literal> is not supported for
+ partitioned tables. See
+ <xref linkend="partitioning-maintenance"/>, for information
+ about alternatives.
+ </para>
+
<remark role="help-description-end"/>
<para>
Modified: trunk/refman-6.0/Makefile.depends
===================================================================
--- trunk/refman-6.0/Makefile.depends 2008-07-10 14:27:30 UTC (rev 11176)
+++ trunk/refman-6.0/Makefile.depends 2008-07-10 14:50:18 UTC (rev 11177)
Changed blocks: 1, Lines Added: 0, Lines Deleted: 2; 659 bytes
@@ -1670,8 +1670,6 @@
../refman-6.0/metadata/installing-core.idmap \
../refman-6.0/metadata/optimization.idmap \
../refman-6.0/metadata/partitioning.idmap \
- ../refman-6.0/metadata/programs-admin-util-core.idmap \
- ../refman-6.0/metadata/programs-client-core.idmap \
../refman-6.0/metadata/sql-syntax.idmap
partitioning.validpure: $(partitioning_SOURCES)
partitioning.titles: $(partitioning_SOURCES)
Modified: trunk/refman-6.0/partitioning.xml
===================================================================
--- trunk/refman-6.0/partitioning.xml 2008-07-10 14:27:30 UTC (rev 11176)
+++ trunk/refman-6.0/partitioning.xml 2008-07-10 14:50:18 UTC (rev 11177)
Changed blocks: 8, Lines Added: 63, Lines Deleted: 211; 11520 bytes
@@ -1740,8 +1740,8 @@
primary key as the partitioning key. In the event that the
Cluster table has no explicit primary key, the
<quote>hidden</quote> primary key generated by the
- <literal>NDB</literal> storage engine for each Cluster
- table is used as the partitioning key.
+ <literal>NDBCLUSTER</literal> storage engine for each
+ MySQL Cluster table is used as the partitioning key.
</para>
</note>
@@ -2686,9 +2686,9 @@
<para>
<literal>ALTER TABLE ... ENGINE = ...</literal> changes only the
- storage engine used by the table, and leaves the table's
+ storage engine used by the table, and leaves the table's
partitioning scheme intact. Use <literal>ALTER TABLE ... REMOVE
- PARTITIONING</literal> to remove a table's partitioning. See
+ PARTITIONING</literal> to remove a table's partitioning. See
<xref linkend="alter-table"/>.
</para>
@@ -2804,14 +2804,15 @@
Query OK, 0 rows affected (0.03 sec)
</programlisting>
- <para>
- Note: In MySQL ¤t-series;, the
- <literal>NDBCLUSTER</literal> storage engine does not support
- <literal>ALTER TABLE ... DROP PARTITION</literal>. It does,
- however, support the other partitioning-related extensions to
- <literal>ALTER TABLE</literal> that are described in this
- chapter.
- </para>
+ <note>
+ <para>
+ The <literal>NDBCLUSTER</literal> storage engine does not
+ support <literal>ALTER TABLE ... DROP PARTITION</literal>. It
+ does, however, support the other partitioning-related
+ extensions to <literal>ALTER TABLE</literal> that are
+ described in this chapter.
+ </para>
+ </note>
<para>
It is very important to remember that, <emphasis>when you drop a
@@ -3464,183 +3465,24 @@
causes partition files to be rebuilt.
</para>
- <para>
- The statements <literal>ANALYZE PARTITION</literal>,
- <literal>CHECK PARTITION</literal>, <literal>OPTIMIZE
- PARTITION</literal>, and <literal>REPAIR PARTITION</literal>
- were available in early MySQL 6.0 releases for the purpose of,
- respectively, analyzing, checking, optimizing, and repairing
- individual or multiple partitions. Support for these statements
- was removed in MySQL 6.0.5. We intend to reintroduce these
- statements or close equivalents in a future MySQL release. (Bug
- #20129)
- </para>
+ <note>
+ <para>
+ The statements <literal>ANALYZE PARTITION</literal>,
+ <literal>CHECK PARTITION</literal>, <literal>OPTIMIZE
+ PARTITION</literal>, and <literal>REPAIR PARTITION</literal>
+ — intended to, respectively, analyze, check, optimize,
+ and repair individual or multiple partitions — were
+ supported beginning with MySQL 5.1.5 and then removed in MySQL
+ 5.1.24. (Bug #20129)
+ </para>
- <para>
- To accomplish these tasks, you can use
- <command>mysqlcheck</command> or, with partitioned
- <literal>MyISAM</literal> tables, you can use
- <command>myisamchk</command>. See <xref linkend="mysqlcheck"/>,
- and <xref linkend="myisamchk"/>, for more information.
- </para>
+ <para>
+ The use of <command>mysqlcheck</command> or
+ <command>myisamchk</command> is also not supported with
+ partitioned tables.
+ </para>
+ </note>
- <remark role="NOTE">
- [js] Commenting out the following due to fix for Bug #20129 and
- pending the completion of WL#4176.
- </remark>
-
-<!--
- <para>
- A number of partitioning maintenance tasks can be carried out in
- MySQL ¤t-series;. MySQL does not support the commands
- <literal>CHECK TABLE</literal>, <literal>OPTIMIZE
- TABLE</literal>, <literal>ANALYZE TABLE</literal>, or
- <literal>REPAIR TABLE</literal> for partitioned tables. Instead,
- a number of extensions to <literal>ALTER TABLE</literal> can be
- used for performing operations of this type on one or more
- partitions directly, as described in the following list:
- </para>
-
- <itemizedlist>
-
- <listitem>
- <formalpara>
-
- <title>Rebuilding partitions</title>
-
- <para>
- Rebuilds the partition; this has the same effect as
- dropping all records stored in the partition, then
- reinserting them. This can be useful for purposes of
- defragmentation.
- </para>
-
- </formalpara>
-
- <para>
- Example:
- </para>
-
-<programlisting>
-ALTER TABLE t1 REBUILD PARTITION p0, p1;
-</programlisting>
- </listitem>
-
- <listitem>
- <formalpara>
-
- <title>Optimizing partitions</title>
-
- <para>
- If you have deleted a large number of rows from a
- partition or if you have made many changes to a
- partitioned table with variable-length rows (that is,
- having <literal>VARCHAR</literal>,
- <literal>BLOB</literal>, or <literal>TEXT</literal>
- columns), you can use <literal>ALTER TABLE ... OPTIMIZE
- PARTITION</literal> to reclaim any unused space and to
- defragment the partition data file.
- </para>
-
- </formalpara>
-
- <para>
- Example:
- </para>
-
-<programlisting>
-ALTER TABLE t1 OPTIMIZE PARTITION p0, p1;
-</programlisting>
-
- <para>
- Using <literal>OPTIMIZE PARTITION</literal> on a given
- partition is equivalent to running <literal>CHECK
- PARTITION</literal>, <literal>ANALYZE PARTITION</literal>,
- and <literal>REPAIR PARTITION</literal> on that partition.
- </para>
- </listitem>
-
- <listitem>
- <formalpara>
-
- <title>Analyzing partitions</title>
-
- <para>
- This reads and stores the key distributions for
- partitions.
- </para>
-
- </formalpara>
-
- <para>
- Example:
- </para>
-
-<programlisting>
-ALTER TABLE t1 ANALYZE PARTITION p3;</programlisting>
- </listitem>
-
- <listitem>
- <formalpara>
-
- <title>Repairing partitions</title>
-
- <para>
- This repairs corrupted partitions.
- </para>
-
- </formalpara>
-
- <para>
- Example:
- </para>
-
-<programlisting>
-ALTER TABLE t1 REPAIR PARTITION p0,p1;
-</programlisting>
- </listitem>
-
- <listitem>
- <formalpara>
-
- <title>Checking partitions</title>
-
- <para>
- You can check partitions for errors in much the same way
- that you can use <literal>CHECK TABLE</literal> with
- non-partitioned tables.
- </para>
-
- </formalpara>
-
- <para>
- Example:
- </para>
-
-<programlisting>
-ALTER TABLE trb3 CHECK PARTITION p1;
-</programlisting>
-
- <para>
- This command will tell you if the data or indexes in
- partition <literal>p1</literal> of table
- <literal>t1</literal> are corrupted. If this is the case,
- use <literal>ALTER TABLE ... REPAIR PARTITION</literal> to
- repair the partition.
- </para>
- </listitem>
-
- </itemizedlist>
-
- <para>
- You can also use the <command>mysqlcheck</command> or
- <command>myisamchk</command> utility to accomplish these tasks,
- operating on the separate <filename>.MYI</filename> files
- generated by partitioning a table. See
- <xref linkend="mysqlcheck"/>.
- </para>
--->
-
</section>
<section id="partitioning-info">
@@ -4489,10 +4331,12 @@
<title>Performance with <literal>LOAD DATA</literal></title>
<para>
- <literal>LOAD DATA</literal> uses buffering to
- improve performance with partitioned tables;
- however, this buffer uses 130 KB memory per
- partition. (Bug #26527)
+ Prior to MySQL 6.0.4, <literal>LOAD DATA</literal>
+ performed very poorly when importing into
+ partitioned tables. The statement now uses buffering
+ to improve performance; however, the buffer uses 130
+ KB memory per partition to achieve this. (Bug
+ #26527)
</para>
</formalpara>
@@ -4770,22 +4614,6 @@
<listitem>
<formalpara>
- <title>Performance with <literal>LOAD DATA</literal></title>
-
- <para>
- Prior to MySQL 6.0.4, <literal>LOAD DATA</literal> performed
- very poorly when importing into partitioned tables. The
- statement now uses buffering to improve performance;
- however, the buffer uses 130 KB memory per partition to
- achieve this. (Bug #26527)
- </para>
-
- </formalpara>
- </listitem>
-
- <listitem>
- <formalpara>
-
<title><literal>DELAYED</literal> option not supported</title>
<para>
@@ -4833,6 +4661,29 @@
</formalpara>
</listitem>
+ <listitem>
+ <formalpara>
+
+ <title>Repairing and rebuilding partitioned tables</title>
+
+ <para>
+ The statements <literal>CHECK TABLE</literal>,
+ <literal>OPTIMIZE TABLE</literal>, <literal>ANALYZE
+ TABLE</literal>, and <literal>REPAIR TABLE</literal> are not
+ supported for partitioned tables.
+ <command>mysqlcheck</command> and
+ <command>myisamchk</command> are also not supported for
+ partitioned tables. However, you can use <literal>ALTER
+ TABLE ... REBUILD PARTITION</literal> to rebuild one or more
+ partitions of a partitioned table; <literal>ALTER TABLE ...
+ REORGANIZE PARTITION</literal> also causes partitions to be
+ rebuilt. See <xref linkend="alter-table"/>, for more
+ information about these two statements.
+ </para>
+
+ </formalpara>
+ </listitem>
+
</itemizedlist>
<section id="partitioning-limitations-partitioning-keys-unique-keys">
@@ -5229,10 +5080,11 @@
<para>
Partitioning by <literal>KEY</literal> (or <literal>LINEAR
KEY</literal>) is the only type of partitioning supported for
- the <literal>NDB</literal> storage engine. It is not possible
- to create a Cluster table using any partitioning type other
- than [<literal>LINEAR</literal>] <literal>KEY</literal>, and
- attempting to do so fails with an error.
+ the <literal>NDBCLUSTER</literal> storage engine. It is not
+ possible to create a MySQL Cluster table using any
+ partitioning type other than [<literal>LINEAR</literal>]
+ <literal>KEY</literal>, and attempting to do so fails with an
+ error.
</para>
</formalpara>
Modified: trunk/refman-6.0/programs-admin-util-core.xml
===================================================================
--- trunk/refman-6.0/programs-admin-util-core.xml 2008-07-10 14:27:30 UTC (rev 11176)
+++ trunk/refman-6.0/programs-admin-util-core.xml 2008-07-10 14:50:18 UTC (rev 11177)
Changed blocks: 1, Lines Added: 5, Lines Deleted: 0; 592 bytes
@@ -403,6 +403,11 @@
for storing data and indexes).
</para>
+ <para>
+ The use of <command>myisamchk</command> with partitioned tables
+ is not supported.
+ </para>
+
<caution>
<para>
It is best to make a backup of a table before performing a
Modified: trunk/refman-6.0/programs-client-core.xml
===================================================================
--- trunk/refman-6.0/programs-client-core.xml 2008-07-10 14:27:30 UTC (rev 11176)
+++ trunk/refman-6.0/programs-client-core.xml 2008-07-10 14:50:18 UTC (rev 11177)
Changed blocks: 1, Lines Added: 5, Lines Deleted: 0; 614 bytes
@@ -4465,6 +4465,11 @@
note : The storage engine for the table doesn't support check
</programlisting>
+ <para>
+ The use of <command>mysqlcheck</command> with partitioned tables
+ is not supported.
+ </para>
+
<caution>
<para>
It is best to make a backup of a table before performing a
Modified: trunk/refman-6.0/sql-syntax.xml
===================================================================
--- trunk/refman-6.0/sql-syntax.xml 2008-07-10 14:27:30 UTC (rev 11176)
+++ trunk/refman-6.0/sql-syntax.xml 2008-07-10 14:50:18 UTC (rev 11177)
Changed blocks: 4, Lines Added: 24, Lines Deleted: 0; 1601 bytes
@@ -19141,6 +19141,11 @@
<literal>INSERT</literal> privileges for the table.
</para>
+ <para>
+ <literal>ANALYZE TABLE</literal> is not supported for
+ partitioned tables.
+ </para>
+
<remark role="help-description-end"/>
<para>
@@ -19243,6 +19248,11 @@
definition that no longer exist.
</para>
+ <para>
+ <literal>CHECK TABLE</literal> is not supported for
+ partitioned tables.
+ </para>
+
<remark role="help-description-end"/>
<para>
@@ -19652,6 +19662,13 @@
<literal>INSERT</literal> privileges for the table.
</para>
+ <para>
+ <literal>OPTIMIZE TABLE</literal> is not supported for
+ partitioned tables. See
+ <xref linkend="partitioning-maintenance"/>, for information
+ about alternatives.
+ </para>
+
<remark role="help-description-end"/>
<para>
@@ -19812,6 +19829,13 @@
<literal>INSERT</literal> privileges for the table.
</para>
+ <para>
+ <literal>REPAIR TABLE</literal> is not supported for
+ partitioned tables. See
+ <xref linkend="partitioning-maintenance"/>, for information
+ about alternatives.
+ </para>
+
<remark role="help-description-end"/>
<para>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r11177 - in trunk: refman-5.1 refman-6.0 | jon | 10 Jul |
