From: jon Date: July 10 2008 2:50pm Subject: svn commit - mysqldoc@docsrva: r11177 - in trunk: refman-5.1 refman-6.0 List-Archive: http://lists.mysql.com/commits/49464 Message-Id: <200807101450.m6AEoI0Q020340@docsrva.mysql.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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 hidden primary key - generated by the NDB storage engine for - each Cluster table is used as the partitioning key. + generated by the NDBCLUSTER storage + engine for each MySQL Cluster table is used as the + partitioning key. @@ -2370,8 +2371,8 @@ design tables so as not to allow nulls, usually by declaring columns NOT NULL.) If you have a RANGE 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) @@ -2751,10 +2752,10 @@ In MySQL 5.1.7 and earlier MySQL 5.1 releases, ALTER TABLE ... ENGINE = ... 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 ALTER - TABLE ... REMOVE PARTITIONING to remove a table's - partitioning. See . + only the storage engine used by the table, and leaves the + table's partitioning scheme intact. As of MySQL 5.1.8, use + ALTER TABLE ... REMOVE PARTITIONING to remove a + table's partitioning. See . @@ -2869,14 +2870,15 @@ Query OK, 0 rows affected (0.03 sec) - - Note: In MySQL ¤t-series;, the - NDBCLUSTER storage engine does not support - ALTER TABLE ... DROP PARTITION. It does, - however, support the other partitioning-related extensions to - ALTER TABLE that are described in this - chapter. - + + + The NDBCLUSTER storage engine does not + support ALTER TABLE ... DROP PARTITION. It + does, however, support the other partitioning-related + extensions to ALTER TABLE that are + described in this chapter. + + It is very important to remember that, when you drop a @@ -3541,23 +3543,23 @@ causes partition files to be rebuilt. - - The statements ANALYZE PARTITION, - CHECK PARTITION, OPTIMIZE - PARTITION, and REPAIR PARTITION - 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) - + + + The statements ANALYZE PARTITION, + CHECK PARTITION, OPTIMIZE + PARTITION, and REPAIR PARTITION + — 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) + - - To accomplish these tasks, you can use - mysqlcheck or, with partitioned - MyISAM tables, you can use - myisamchk. See , - and , for more information. - + + The use of mysqlcheck or + myisamchk is also not supported with + partitioned tables. + + @@ -3842,12 +3844,12 @@ - This section discusses partition pruning, - 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 Do not scan - partitions where there can be no matching values. For - example, suppose you have a partitioned table + This section discusses an optimization known as + partition pruning, 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 + Do not scan partitions where there can be no matching + values. For example, suppose you have a partitioned table t1 defined by this statement: @@ -4753,6 +4755,29 @@ + + + + Repairing and rebuilding partitioned tables + + + The statements CHECK TABLE, + OPTIMIZE TABLE, ANALYZE + TABLE, and REPAIR TABLE are not + supported for partitioned tables. + mysqlcheck and + myisamchk are also not supported for + partitioned tables. However, you can use ALTER + TABLE ... REBUILD PARTITION to rebuild one or more + partitions of a partitioned table; ALTER TABLE ... + REORGANIZE PARTITION also causes partitions to be + rebuilt. See , for more + information about these two statements. + + + + +
@@ -5163,9 +5188,9 @@ Partitioning by KEY (or LINEAR KEY) is the only type of partitioning supported for - the NDB storage engine. Beginning with - MySQL 5.1.12, it is not possible to create a Cluster table - using any partitioning type other than + the NDBCLUSTER storage engine. Beginning + with MySQL 5.1.12, it is not possible to create a MySQL + Cluster table using any partitioning type other than [LINEAR] KEY, and attempting to do so fails with an error. 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). + + The use of myisamchk with partitioned tables + is not supported. + + 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 + + The use of mysqlcheck with partitioned tables + is not supported. + + 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 @@ INSERT privileges for the table. + + ANALYZE TABLE is not supported for + partitioned tables. + + @@ -18266,6 +18271,11 @@ definition that no longer exist. + + CHECK TABLE is not supported for + partitioned tables. + + @@ -18673,6 +18683,13 @@ INSERT privileges for the table. + + OPTIMIZE TABLE is not supported for + partitioned tables. See + , for information + about alternatives. + + @@ -18856,6 +18873,13 @@ INSERT privileges for the table. + + REPAIR TABLE is not supported for + partitioned tables. See + , for information + about alternatives. + + 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 hidden primary key generated by the - NDB storage engine for each Cluster - table is used as the partitioning key. + NDBCLUSTER storage engine for each + MySQL Cluster table is used as the partitioning key. @@ -2686,9 +2686,9 @@ ALTER TABLE ... ENGINE = ... 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 ALTER TABLE ... REMOVE - PARTITIONING to remove a table's partitioning. See + PARTITIONING to remove a table's partitioning. See . @@ -2804,14 +2804,15 @@ Query OK, 0 rows affected (0.03 sec) - - Note: In MySQL ¤t-series;, the - NDBCLUSTER storage engine does not support - ALTER TABLE ... DROP PARTITION. It does, - however, support the other partitioning-related extensions to - ALTER TABLE that are described in this - chapter. - + + + The NDBCLUSTER storage engine does not + support ALTER TABLE ... DROP PARTITION. It + does, however, support the other partitioning-related + extensions to ALTER TABLE that are + described in this chapter. + + It is very important to remember that, when you drop a @@ -3464,183 +3465,24 @@ causes partition files to be rebuilt. - - The statements ANALYZE PARTITION, - CHECK PARTITION, OPTIMIZE - PARTITION, and REPAIR PARTITION - 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) - + + + The statements ANALYZE PARTITION, + CHECK PARTITION, OPTIMIZE + PARTITION, and REPAIR PARTITION + — 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) + - - To accomplish these tasks, you can use - mysqlcheck or, with partitioned - MyISAM tables, you can use - myisamchk. See , - and , for more information. - + + The use of mysqlcheck or + myisamchk is also not supported with + partitioned tables. + + - - [js] Commenting out the following due to fix for Bug #20129 and - pending the completion of WL#4176. - - - -
@@ -4489,10 +4331,12 @@ Performance with <literal>LOAD DATA</literal> - LOAD DATA 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, LOAD DATA + 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) @@ -4770,22 +4614,6 @@ - Performance with <literal>LOAD DATA</literal> - - - Prior to MySQL 6.0.4, LOAD DATA 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) - - - - - - - - <literal>DELAYED</literal> option not supported @@ -4833,6 +4661,29 @@ + + + + Repairing and rebuilding partitioned tables + + + The statements CHECK TABLE, + OPTIMIZE TABLE, ANALYZE + TABLE, and REPAIR TABLE are not + supported for partitioned tables. + mysqlcheck and + myisamchk are also not supported for + partitioned tables. However, you can use ALTER + TABLE ... REBUILD PARTITION to rebuild one or more + partitions of a partitioned table; ALTER TABLE ... + REORGANIZE PARTITION also causes partitions to be + rebuilt. See , for more + information about these two statements. + + + + +
@@ -5229,10 +5080,11 @@ Partitioning by KEY (or LINEAR KEY) is the only type of partitioning supported for - the NDB storage engine. It is not possible - to create a Cluster table using any partitioning type other - than [LINEAR] KEY, and - attempting to do so fails with an error. + the NDBCLUSTER storage engine. It is not + possible to create a MySQL Cluster table using any + partitioning type other than [LINEAR] + KEY, and attempting to do so fails with an + error. 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). + + The use of myisamchk with partitioned tables + is not supported. + + 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 + + The use of mysqlcheck with partitioned tables + is not supported. + + 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 @@ INSERT privileges for the table. + + ANALYZE TABLE is not supported for + partitioned tables. + + @@ -19243,6 +19248,11 @@ definition that no longer exist. + + CHECK TABLE is not supported for + partitioned tables. + + @@ -19652,6 +19662,13 @@ INSERT privileges for the table. + + OPTIMIZE TABLE is not supported for + partitioned tables. See + , for information + about alternatives. + + @@ -19812,6 +19829,13 @@ INSERT privileges for the table. + + REPAIR TABLE is not supported for + partitioned tables. See + , for information + about alternatives. + +