Author: jstephens
Date: 2007-04-30 11:56:59 +0200 (Mon, 30 Apr 2007)
New Revision: 6262
Log:
Merging recent non-Cluster bugfixes to MCCGE merge changelog file.
Modified:
trunk/refman-5.1/news-5.1-merged.xml
Modified: trunk/refman-5.1/news-5.1-merged.xml
===================================================================
--- trunk/refman-5.1/news-5.1-merged.xml 2007-04-30 09:53:05 UTC (rev 6261)
+++ trunk/refman-5.1/news-5.1-merged.xml 2007-04-30 09:56:59 UTC (rev 6262)
Changed blocks: 4, Lines Added: 169, Lines Deleted: 16; 7282 bytes
@@ -165,6 +165,33 @@
detailed information. (Bug #25688, Bug #17095)
</para>
</listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: The following changes were
+ made for the <command>ndb_size.pl</command> utility:
+
+ <itemizedlist>
+ <listitem>
+ <para>
+ When <command>ndb_size.pl</command> calculates a value
+ for a given configuration parameter that is less than
+ the default value, it now suggests the default value
+ instead. (Bug #24227)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The dependency on <literal>HTML::Template</literal> was
+ removed. (Bug #24228)
+ </para>
+ </listitem>
+
+
+ </itemizedlist>
+ </para>
+ </listitem>
</itemizedlist>
@@ -205,9 +232,135 @@
The patches for Bug #19370 and Bug #21789 were reverted.
</para>
</listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal> (APIs): For
+ <literal>BLOB</literal> reads on operations with lock mode
+ <literal>LM_CommittedRead</literal>, the lock mode was not
+ upgraded to <literal>LM_Read</literal> before the state of the
+ <literal>BLOB</literal> had already been calculated. The
+ <literal>NDB</literal> API methods affected by this problem
+ included the following:
+
+ <itemizedlist>
+ <listitem>
+ <para>
+ <literal>NdbOperation::readTuple()</literal>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <literal>NdbScanOperation::readTuples()</literal>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <literal>NdbIndexScanOperation::readTuples()</literal>
+ </para>
+ </listitem>
+ </itemizedlist>
+
+ (Bug #27320)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal> (Disk Data): Setting the value
+ of the <literal>UNDO BUFFER SIZE</literal> to 64K or less in
+ a <literal>CREATE LOGFILE GROUP</literal> statement led to
+ failure of cluster data nodes. (Bug #24560)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: The cluster waited 30 seconds
+ instead of 30 milliseconds before reading table statistics.
+ (Bug #28093)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: It was not possible to add a
+ unique index to an <literal>NDB</literal> table while in
+ single user mode. (Bug #27710)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: Performing a delete followed
+ by an insert during a local checkpoint could cause a
+ <errortext>Rowid already allocated</errortext> error. (Bug
+ #27205)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal> (Disk Data): When restarting a
+ data node following the creation of a large number (~200) of
+ Disk Data objects, the cluster could not assign a node ID to
+ the restarting node. (Bug #25741)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: Adding of indexes online
+ failed for <literal>NDB</literal> tables having
+ <literal>BLOB</literal> or <literal>TEXT</literal> columns.
+ (Bug #25431)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: The
+ <command>ndb_resize.pl</command> utility did not calculate
+ memory usage for indexes correctly. (Bug #24229)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: While a data node was stopped,
+ dropping a table then creating an index on a different table
+ caused that node to fail during restart. This was due to the
+ re-use of the dropped table's internal ID for the index
+ without verifying that the index now referred to a different
+ database object. (Bug #21755)
+ </para>
+ </listitem>
<listitem>
<para>
+ <literal>NDB Cluster</literal> (Disk Data): When in single
+ user mode, it was possible to create log file groups and
+ tablespaces from any SQL node connected to the cluster. (Bug
+ #27712)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal> (Disk Data): Changing a column
+ specification or issuing a <literal>TRUNCATE</literal>
+ statement on a Disk Data table caused the table to become an
+ in-memory table. (Bug #24667, Bug #25296)
+ </para>
+
+ <para>
+ This fix supersedes an incomplete fix that was made for this
+ issue in MySQL 5.1.15.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
<literal>NDB Cluster</literal> (Replication): Setting
<literal>SQL_LOG_BIN</literal> to zero did not disable binary
logging. (Bug #27076)
@@ -503,6 +656,22 @@
<listitem>
<para>
+ An interaction between <literal>SHOW TABLE STATUS</literal>
+ and other concurrent statements that modify the table could
+ result in a divide-by-zero error and a server crash. (Bug
+ #27516)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The <filename>decimal.h</filename> header file was incorrectly
+ omitted from binary distributions. (Bug #27456)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
<command>mysqldump</command> could not connect using SSL. (Bug
#27669)
</para>
@@ -5148,22 +5317,6 @@
<listitem>
<para>
- <literal>NDB Cluster</literal> (Disk Data): Issuing a
- <literal>TRUNCATE</literal> statement on a Disk Data table
- caused the table to become an in-memory table. (Bug #25296)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <literal>NDB Cluster</literal> (Disk Data): Changing a column
- specification on a Disk Data table caused the table to become
- an in-memory table. (Bug #24667)
- </para>
- </listitem>
-
- <listitem>
- <para>
<literal>NDB Cluster</literal>: It was not possible to create
an <literal>NDB</literal> table with a key on two
<literal>VARCHAR</literal> columns where both columns had a
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r6262 - trunk/refman-5.1 | jon | 30 Apr |
