Author: jstephens
Date: 2006-01-20 12:29:33 +0100 (Fri, 20 Jan 2006)
New Revision: 945
Log:
Documented Partitioning bugs:
13435, 13437, 13438, 13439, 13440,
13441, 13442, 13445, 13446, 13447,
13644, 14365, 15968
Minor Partitioning chapter fixes.
Started new Partitioning Limitations section.
Modified:
trunk/refman-5.1/partitioning.xml
trunk/refman-common/news-5.1.xml
trunk/refman-common/titles.en.ent
Modified: trunk/refman-5.1/partitioning.xml
===================================================================
--- trunk/refman-5.1/partitioning.xml 2006-01-20 04:33:42 UTC (rev 944)
+++ trunk/refman-5.1/partitioning.xml 2006-01-20 11:29:33 UTC (rev 945)
@@ -35,19 +35,26 @@
commands for use with partitioned tables are discussed in
<xref linkend="partitioning-maintenance"/>.
</para>
+
+ <para>
+ <emphasis role="bold">Important</emphasis>: Partitioned tables
+ created with MySQL versions prior to 5.1.6 cannot be read by a 5.1.6
+ or later MySQL Server. If you have partitioned tables created in
+ MySQL 5.1.5 or earlier, be sure to see <xref linkend="news-5-1-6"/>
+ for suggested workarounds <emphasis>before</emphasis> upgrading to
+ MySQL 5.1.6 or later.
+ </para>
<para>
- <emphasis role="bold">Please Note</emphasis>: The partitioning
- implementation in MySQL 5.1 is still very new (pre-alpha quality)
- and is <emphasis>not</emphasis> production-ready at this time. Much
- the same is true of this chapter: Some of the features described
- herein are not yet actually implemented (partitioning maintenance
- and repartitioning commands), and others might not yet function
- exactly as described (for example, the <literal>DATA
- DIRECTORY</literal> and <literal>INDEX DIRECTORY</literal> options
- for partitions are adversely affected by Bug #13520). We have
- attempted to note these discrepancies in this chapter. Before filing
- bug reports, we encourage you to check the following resources:
+ The partitioning implementation in MySQL 5.1 is still undergoing
+ development and is not yet production-ready. Much the same is true
+ of this chapter: Some of the features described herein are not yet
+ actually implemented, and others might not yet function exactly as
+ described (for example, the <literal>DATA DIRECTORY</literal> and
+ <literal>INDEX DIRECTORY</literal> options for partitions are
+ adversely affected by Bug #13520). We have attempted to note these
+ discrepancies in this chapter. Before filing bug reports, we
+ encourage you to check the following resources:
</para>
<itemizedlist>
@@ -117,7 +124,7 @@
</itemizedlist>
<para>
- MySQL 5.1 alpha binaries are now available from
+ MySQL 5.1-alpha binaries are now available from
<ulink url="http://dev.mysql.com/downloads/mysql/5.1.html"/>.
However, for the latest partitioning bugfixes and feature additions,
you can obtain the source from our BitKeeper repository. To enable
@@ -142,6 +149,11 @@
This section provides a conceptual overview of partitioning in
MySQL ¤t-series;.
</para>
+
+ <para>
+ For information on partitioning restrictions and feature
+ limitations, see <xref linkend="partitioning-limitations"/>.
+ </para>
<para>
The SQL standard does not provide much in the way of guidance
@@ -1883,9 +1895,18 @@
<programlisting>
/var/lib/mysql/test> <userinput>ls *.MYD -l</userinput>
--rw-rw---- 1 mysql mysql 0 2005-11-04 18:41 tnhash_p0.MYD
--rw-rw---- 1 mysql mysql 0 2005-11-04 18:41 tnhash_p1.MYD
+-rw-rw---- 1 mysql mysql 0 2005-11-04 18:41 tnhash#P#p0.MYD
+-rw-rw---- 1 mysql mysql 0 2005-11-04 18:41 tnhash#P#p1.MYD
</programlisting>
+
+ <para>
+ (<emphasis role="bold">Note</emphasis>: Prior to MySQL 5.1.5,
+ thes files would have been named
+ <filename>tnhash_p0.MYD</filename> and
+ <filename>tnhash_p1.MYD</filename>. See
+ <xref linkend="news-5-1-6"/> and Bug #13437 for information
+ regarding how this change impacts upgrades.)
+ </para>
<para>
Note that the size of each file is 0 bytes. Now insert a row
@@ -1921,8 +1942,8 @@
<programlisting>
var/lib/mysql/test> <userinput>ls *.MYD -l</userinput>
--rw-rw---- 1 mysql mysql 20 2005-11-04 18:44 tnhash_p0.MYD
--rw-rw---- 1 mysql mysql 0 2005-11-04 18:41 tnhash_p1.MYD
+-rw-rw---- 1 mysql mysql 20 2005-11-04 18:44 tnhash#P#p0.MYD
+-rw-rw---- 1 mysql mysql 0 2005-11-04 18:41 tnhash#P#p1.MYD
</programlisting>
<para>
@@ -3195,7 +3216,7 @@
<para>
You should take note of the following restrictions and
- limitations:
+ limitations on <literal>EXPLAIN PARTITIONS</literal>:
</para>
<itemizedlist>
@@ -3241,5 +3262,24 @@
</section>
</section>
-
+
+ <section id="partitioning-limitations">
+ <title>&title-partitioning-limitations;</title>
+
+ <para>
+ This section discusses current restricitons and limitations on
+ MySQL partitioning support, as listed here:
+ </para>
+
+ <itemizedlist>
+ <listitem>
+ <para>
+ Partitioned tables do not support foreign keys.
+ </para>
+ </listitem>
+ </itemizedlist>
+
+ </section>
+
+
</chapter>
Modified: trunk/refman-common/news-5.1.xml
===================================================================
--- trunk/refman-common/news-5.1.xml 2006-01-20 04:33:42 UTC (rev 944)
+++ trunk/refman-common/news-5.1.xml 2006-01-20 11:29:33 UTC (rev 945)
@@ -57,23 +57,25 @@
<listitem>
<para>
- Partition support is not an <quote>engine</quote>, but it was
- included in the output of <literal>SHOW ENGINES</literal>. Now
- it does not. (Bug #14355)
+ <emphasis role="bold">Incompatible change</emphasis>: Due to a
+ change in the naming scheme for partitioning and
+ subpartitioning files, it is not possible for the server to
+ read partitioned tables created in previous MySQL versions. A
+ suggested workaround is (1) to create a non-partitioned table
+ with the same table schema using a standard <literal>CREATE
+ TABLE</literal> statement (that is, with no partitioning
+ clauses) and then (2) to issue a<literal>SELECT INTO</literal>
+ to copy the data into the non-partitioned table before the
+ upgrade; following the upgrade, you can partition the new
+ table using <literal>ALTER TABLE ... PARTITION BY
+ ...</literal>. Alternatively, you can dump the table using
+ <command>mysqldump</command> prior to upgrading and reload it
+ afterwards with <literal>LOAD DATA</literal>. (Bug #13437)
</para>
</listitem>
<listitem>
<para>
- <literal>SHOW CREATE TABLE</literal> did not display the
- <literal>PARTITIONS</literal> clause for tables partitioned by
- <literal>HASH</literal> or <literal>KEY</literal>. (Bug
- #14327)
- </para>
- </listitem>
-
- <listitem>
- <para>
<emphasis role="bold">Incompatible change</emphasis>: Words
with apostrophes are now matched in a FULLTEXT search against
non-apostrophe words (for example, a search for
@@ -84,6 +86,21 @@
#14194)
</para>
</listitem>
+
+ <listitem>
+ <para>
+ Partition support is not an <quote>engine</quote>, but it was
+ included in the output of <literal>SHOW ENGINES</literal>. Now
+ it does not. (Bug #14355)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>ANALYZE TABLE</literal> is now supported for
+ partitioned tables. (Bug #13441)
+ </para>
+ </listitem>
<listitem>
<para>
@@ -131,6 +148,116 @@
<listitem>
<para>
+ <literal>SHOW CREATE TABLE</literal> did not display the
+ <literal>PARTITIONS</literal> clause for tables partitioned by
+ <literal>HASH</literal> or <literal>KEY</literal>. (Bug
+ #14327)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Inserting a negative value into an integer column used as the
+ partitioning key for a table partitioned by
+ <literal>HASH</literal> could cause the server to crash. (Bug
+ #15968)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ With a table partitioned by <literal>LIST</literal>, inserting
+ a value which was smaller than any value shown in the
+ partitioning value-lists could cause the server to crash. (Bug
+ #14365)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>ALTER TABLE ... DROP PARTITION</literal> would
+ truncate all <literal>DATE</literal> column values in the
+ table's remaining partitions to <literal>NULL</literal>. (Bug
+ #13644)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>ALTER TABLE ... ADD PARTITION</literal> could crash
+ the server or cause an <errortext>Out of memory</errortext>
+ error in some circumstances. (Bug #13447)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The server would allow foreign keys to be declared in the
+ definition of a partitioned table despite the fact that
+ partitioned tables do not support foreign keys (see
+ <xref linkend="partitioning-limitations"/>). (Bug #13446)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ A <literal>SELECT</literal> from a key-partitioned table with
+ a multi-column key could cause the server to crash. (Bug
+ #13445)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Issuing a <literal>TRUNCATE</literal> statement twice in
+ succession on the same partitioned table would cause the
+ server to crash. (Bug #13442)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Using a <literal>REPLACE</literal> statement on a partitioned
+ table caused the server to crash. (Bug #13440)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Using an identifier rather than a literal integer value in the
+ <literal>LESS THAN</literal> clause of a range-partitioned
+ table could cause the server to crash and corruption of
+ tables. (Bug #13439)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Using <literal>ENGINE=...</literal> within a
+ <literal>PARTITION</literal> clause could cause the server to
+ crash. (Bug #13438)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>CREATE TABLE ... LIKE</literal> did not work if the
+ table whose schema was to be copied was a partitoned table.
+ (Bug #13435)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>SHOW CREATE TABLE</literal> did not display the
+ <literal>PARTITIONS</literal> clause for tables partitioned by
+ <literal>HASH</literal> or <literal>KEY</literal>. (Bug
+ #14327)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
Certain permission management statements could create a
<literal>NULL</literal> hostname for a user, resulting in a
server crash. (Bug #15598)
Modified: trunk/refman-common/titles.en.ent
===================================================================
--- trunk/refman-common/titles.en.ent 2006-01-20 04:33:42 UTC (rev 944)
+++ trunk/refman-common/titles.en.ent 2006-01-20 11:29:33 UTC (rev 945)
@@ -1305,6 +1305,7 @@
<!ENTITY title-partitioning-hash "<literal>HASH</literal> Partitioning">
<!ENTITY title-partitioning-info "Obtaining Information About Partitions">
<!ENTITY title-partitioning-key "<literal>KEY</literal> Partitioning">
+<!ENTITY title-partitioning-limitations "Restrictions and Limitations on Partitioning">
<!ENTITY title-partitioning-linear-hash "<literal>LINEAR HASH</literal> Partitioning">
<!ENTITY title-partitioning-list "<literal>LIST</literal> Partitioning">
<!ENTITY title-partitioning-maintenance "Maintenance of Partitions">
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r945 - in trunk: refman-5.1 refman-common | jon | 20 Jan |
