Author: jstephens
Date: 2006-07-19 06:36:22 +0200 (Wed, 19 Jul 2006)
New Revision: 2769
Log:
Documented Partitioning bugfixes:
Bug #20389, Bug #20766, Bug #20767,
Bug #20770, Bug #20852, Bug #20893
Modified:
trunk/refman-common/news-5.1.xml
Modified: trunk/refman-common/news-5.1.xml
===================================================================
--- trunk/refman-common/news-5.1.xml 2006-07-18 20:41:19 UTC (rev 2768)
+++ trunk/refman-common/news-5.1.xml 2006-07-19 04:36:22 UTC (rev 2769)
Changed blocks: 1, Lines Added: 36, Lines Deleted: 0; 1653 bytes
@@ -323,6 +323,42 @@
(Bug #17371)
</para>
</listitem>
+
+ <listitem>
+ <para>
+ <literal>InnoDB</literal> (Partitioning): Updating an
+ <literal>InnoDB</literal> table using <literal>HASH</literal>
+ partitioning with a composite primary key would cause the
+ server to hang. (Bug #20852)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Old partition and subpartition files were not always removed
+ following <literal>ALTER TABLE ... REORGANIZE
+ PARTITION</literal> statements. (Bug #20770)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Merging multiple partitions having subpartitions into a single
+ partition with subpartitions, or splitting a single partition
+ having subpartitions into multiple partitions with
+ subpartitions, could sometimes crash the server. These issues
+ were associated with a failure reported in the
+ <literal>partition_range</literal> test. (Bug #20766, Bug
+ #20767, Bug #20893)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Some queries using <literal>ORDER BY ... DESC</literal> on
+ subpartitioned tables could crash the server. (Bug #20389)
+ </para>
+ </listitem>
<listitem>
<para>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r2769 - trunk/refman-common | jstephens | 19 Jul |
