Author: jstephens
Date: 2007-05-21 18:22:04 +0200 (Mon, 21 May 2007)
New Revision: 6554
Log:
Reformat
Modified:
trunk/refman-5.1/news-5.1.xml
Modified: trunk/refman-5.1/news-5.1.xml
===================================================================
--- trunk/refman-5.1/news-5.1.xml 2007-05-21 16:20:49 UTC (rev 6553)
+++ trunk/refman-5.1/news-5.1.xml 2007-05-21 16:22:04 UTC (rev 6554)
Changed blocks: 24, Lines Added: 150, Lines Deleted: 153; 20039 bytes
@@ -718,7 +718,7 @@
<literal>VARCHAR</literal> column. (Bug #27123)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: Under certain rare
@@ -728,7 +728,7 @@
same tuple in the lock queue. (Bug #28073)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: Under some circumstances, a
@@ -2424,28 +2424,27 @@
</listitem>
</itemizedlist>
-
+
<section id="news-5-1-18-cge">
-
+
<title>Changes in MySQL 5.1.16 Carrier Grade Edition</title>
-
+
<para>
This section contains change history information for
&mccge-series; releases based on MySQL 5.1.16.
</para>
-
+
<section id="news-5-1-18-ndb-6-2-2">
- <title>Changes in release MySQL 5.1.18-ndb-6.2.2-beta (Not yet
- released)</title>
-
+
+ <title>Changes in release MySQL 5.1.18-ndb-6.2.2-beta (Not yet released)</title>
+
<para role="release-level">
This is a new Beta development release, fixing recently
discovered bugs and incorporating improvements made since the
previous &mccge-series; release.
</para>
-
-
- <!--
+
+<!--
<para>
Like all releases for &mccge-series;, this is a
source-only release which you must compile and install using the
@@ -2466,14 +2465,15 @@
for more details about the individual bugs fixed in this version.
</para>
-->
-
+
<para>
- This Beta release incorporates all bugfixes and feature changes
- made in MySQL 5.1.18-ndb-6.2.1, which includes all bugfixes and
- feature changes which were added in the mainline 5.1.18 release;
- information about these can be found in
+ This Beta release incorporates all bugfixes and feature
+ changes made in MySQL 5.1.18-ndb-6.2.1, which includes all
+ bugfixes and feature changes which were added in the mainline
+ 5.1.18 release; information about these can be found in
<xref linkend="news-5-1-18"/>.
</para>
+
<!--
<important>
<formalpara>
@@ -2487,8 +2487,8 @@
</formalpara>
</important>
--->
-
+-->
+
<!--
<para>
Functionality added or changed:
@@ -2499,39 +2499,40 @@
<para></para>
</listitem>
</itemizedlist>
--->
-
+-->
+
<para>
This release fixes the following bugs:
</para>
-
+
<itemizedlist>
+
<listitem>
<para></para>
</listitem>
+
</itemizedlist>
+
</section>
-
-
+
<section id="news-5-1-18-ndb-6-2-1">
-
- <title>Changes in release MySQL 5.1.18-ndb-6.2.1-beta (Released
- 30 April 2007)</title>
-
+
+ <title>Changes in release MySQL 5.1.18-ndb-6.2.1-beta (Released 30 April 2007)</title>
+
<para role="release-level">
This is a new Beta development release, fixing recently
discovered bugs and incorporating improvements made since the
previous &mccge-series; release.
</para>
-
+
<warning>
<para>
This release was withdrawn after production and should no
longer be used.
</para>
</warning>
-
- <!--
+
+<!--
<para>
Like all releases for &mccge-series;, this is a
source-only release which you must compile and install using the
@@ -2552,20 +2553,20 @@
for more details about the individual bugs fixed in this version.
</para>
-->
-
+
<para>
- This Beta release incorporates all bugfixes and feature changes
- made in MySQL 5.1.18-ndb-6.2.0, which includes all bugfixes and
- feature changes which were added in the mainline 5.1.18 release;
- information about these can be found in
+ This Beta release incorporates all bugfixes and feature
+ changes made in MySQL 5.1.18-ndb-6.2.0, which includes all
+ bugfixes and feature changes which were added in the mainline
+ 5.1.18 release; information about these can be found in
<xref linkend="news-5-1-18"/>.
</para>
-
+
<important>
<formalpara>
-
+
<title>Upgrading to MySQL 5.1.18-ndb-6.2.1 from a previous release</title>
-
+
<para>
The internal specifications for columns in
<literal>NDB</literal> tables changed to allow
@@ -2576,25 +2577,25 @@
prior to MySQL 5.1.15-ndb-6.1.7, or MySQL Cluster mainline
releases prior to 5.1.18.
</para>
-
+
</formalpara>
-
+
<para>
See
<link linkend="mysql-cluster-upgrade-downgrade-compatibility-online-add-drop-column">the
- related note</link> in
+ related note</link> in
<xref linkend="mysql-cluster-upgrade-downgrade-compatibility"/>,
for important information prior to upgrading a MySQL Cluster
- to MySQL 5.1.15-ndb-6.1.7 or later from MySQL 5.1.15-ndb-6.1.6
- or an earlier ndb-6.1.x release.
+ to MySQL 5.1.15-ndb-6.1.7 or later from MySQL
+ 5.1.15-ndb-6.1.6 or an earlier ndb-6.1.x release.
</para>
-
+
<para>
See also Bug #28205.
</para>
</important>
-
- <!--
+
+<!--
<para>
Functionality added or changed:
</para>
@@ -2607,131 +2608,132 @@
</itemizedlist>
-->
-
+
<para>
This release fixes the following bugs:
</para>
-
+
<itemizedlist>
-
+
<listitem>
<para>
- Multiple operations involving deletes followed by reads were
- not handled correctly. (Bug #28276)
+ Multiple operations involving deletes followed by reads
+ were not handled correctly. (Bug #28276)
</para>
-
+
<note>
<para>
This issue could also affect MySQL Cluster Replication.
</para>
</note>
</listitem>
-
+
<listitem>
<para>
<emphasis role="bold">Cluster APIs</emphasis>: Using
- <literal>NdbBlob::writeData()</literal> to write data in the
- middle of an existing blob value (that is, updating the
- value) could overwrite some data past the end of the data to
- be changed. (Bug #27018)
+ <literal>NdbBlob::writeData()</literal> to write data in
+ the middle of an existing blob value (that is, updating
+ the value) could overwrite some data past the end of the
+ data to be changed. (Bug #27018)
</para>
</listitem>
-
+
<listitem>
<para>
- <emphasis role="bold">Cluster Replication</emphasis>: Trying
- to replicate a large number of frequent updates with a
- relatively small relay log
+ <emphasis role="bold">Cluster Replication</emphasis>:
+ Trying to replicate a large number of frequent updates
+ with a relatively small relay log
(<literal>max-relay-log-size</literal> set to 1M or less)
could cause the slave to crash. (Bug #27529)
</para>
</listitem>
-
+
<listitem>
<para>
- <emphasis role="bold">Cluster Replication</emphasis>: An SQL
- node acting as a replication master server could be a single
- point of failure; that is, if it failed, the replication
- slave had no way of knowing this, which could result in a
- mismatch of data between the master and the slave. (Bug
- #21494)
+ <emphasis role="bold">Cluster Replication</emphasis>: An
+ SQL node acting as a replication master server could be a
+ single point of failure; that is, if it failed, the
+ replication slave had no way of knowing this, which could
+ result in a mismatch of data between the master and the
+ slave. (Bug #21494)
</para>
</listitem>
-
+
<listitem>
<para>
Memory usage of a <command>mysqld</command> process grew
even while idle. (Bug #27560)
</para>
</listitem>
-
+
<listitem>
<para>
The Cluster table handler did not set bits in null bytes
correctly. (Bug #26591)
</para>
</listitem>
-
+
<listitem>
<para>
- When trying to create tables on an SQL node not connected to
- the cluster, a misleading error message <errortext>Table
- '<replaceable>tbl_name</replaceable>' already
- exists</errortext> was generated. The error now generated is
- <errortext>Could not connect to storage engine</errortext>.
- (Bug #18676)
+ When trying to create tables on an SQL node not connected
+ to the cluster, a misleading error message
+ <errortext>Table '<replaceable>tbl_name</replaceable>'
+ already exists</errortext> was generated. The error now
+ generated is <errortext>Could not connect to storage
+ engine</errortext>. (Bug #18676)
</para>
</listitem>
-
+
<listitem>
<para>
Incorrect handling of fragmentation in a node takeover
- during a restart could cause stale data to be copied to the
- starting node, leading eventually to failure of the node.
- (Bug #27434)
+ during a restart could cause stale data to be copied to
+ the starting node, leading eventually to failure of the
+ node. (Bug #27434)
</para>
</listitem>
-
+
<listitem>
<para>
Incorrect handling of fragmentation in a node takeover
- during a restart could cause stale data to be copied to the
- starting node, leading eventually to failure of the node.
- (Bug #27434)
+ during a restart could cause stale data to be copied to
+ the starting node, leading eventually to failure of the
+ node. (Bug #27434)
</para>
</listitem>
-
+
<listitem>
<para>
- After putting the cluster in single user mode from one MySQL
- server, trying to drop an NDB table from a second MySQL
- server also connected to the cluster would cause the second
- MySQL server to hang. (Bug #27254)
+ After putting the cluster in single user mode from one
+ MySQL server, trying to drop an NDB table from a second
+ MySQL server also connected to the cluster would cause the
+ second MySQL server to hang. (Bug #27254)
</para>
</listitem>
-
+
<listitem>
<para>
<command>mysqld</command> could crash shortly after a data
- node failure following certain DML operations. (Bug #27169)
+ node failure following certain DML operations. (Bug
+ #27169)
</para>
</listitem>
-
+
<listitem>
<para>
An incorrect assertion was made when sending a
<literal>TCKEYFAILREF</literal> or
- <literal>TCKEYCONF</literal> message to a failed data node.
- (Bug #26814)
+ <literal>TCKEYCONF</literal> message to a failed data
+ node. (Bug #26814)
</para>
</listitem>
-
+
</itemizedlist>
-
+
</section>
+
</section>
-
-
+
</section>
<section id="news-5-1-17">
@@ -5026,8 +5028,6 @@
&mccge-series; releases based on MySQL 5.1.16.
</para>
-
-
<section id="news-5-1-16-ndb-6-2-0">
<title>Changes in release MySQL 5.1.16-ndb-6.2.0-beta (03 March 2007)</title>
@@ -6691,18 +6691,18 @@
This section contains change history information for
&mccge-series; releases based on MySQL 5.1.15.
</para>
-
+
<section id="news-5-1-15-ndb-6-1-8">
- <title>Changes in release MySQL 5.1.15-ndb-6.1.7-beta (Released 05
- May 2007)</title>
-
+
+ <title>Changes in release MySQL 5.1.15-ndb-6.1.7-beta (Released 05 May 2007)</title>
+
<para role="release-level">
This is a new Beta development release, fixing recently
discovered bugs and incorporating improvements made since the
previous &mccge-series; release.
</para>
-
- <!--
+
+<!--
<para>
Like all releases for MySQL &mccge-series;, this is a
source-only release which you must compile and install using the
@@ -6715,7 +6715,7 @@
this directory contains the complete source archive.
</para>
-->
-
+
<para role="release-non-production">
<emphasis role="bold">NOTE</emphasis>: Although MySQL has worked
very hard to ensure a high level of quality, protect your data
@@ -6724,7 +6724,7 @@
<ulink url="http://bugs.mysql.com/"/> for more details about the
individual bugs fixed in this version.
</para>
-
+
<para>
This Beta release incorporates all bugfixes and feature changes
made in MySQL 5.1.14-ndb-6.1.0, MySQL 5.1.15-ndb-6.1.1, MySQL
@@ -6748,26 +6748,26 @@
</formalpara>
</important>
--->
-
-
+-->
+
<para>
Functionality added or changed:
</para>
-
+
<itemizedlist>
+
<listitem>
<para></para>
</listitem>
+
</itemizedlist>
-
-
+
<para>
This release fixes the following bugs:
</para>
-
+
<itemizedlist>
-
+
<listitem>
<para>
<emphasis role="bold">Disk Data</emphasis>: Extremely large
@@ -6775,7 +6775,7 @@
failure in some circumstances. (Bug #27942)
</para>
</listitem>
-
+
<listitem>
<para>
Repeated insertion of data generated by
@@ -6784,7 +6784,7 @@
#27437)
</para>
</listitem>
-
+
<listitem>
<para>
<emphasis role="bold">Cluster APIs</emphasis>: In a
@@ -6793,16 +6793,14 @@
to overwrite an existing value. (Bug #20535)
</para>
</listitem>
+
</itemizedlist>
-
-
+
</section>
-
-
+
<section id="news-5-1-15-ndb-6-1-7">
- <title>Changes in release MySQL 5.1.15-ndb-6.1.7-beta (Released 05
- May 2007)</title>
+ <title>Changes in release MySQL 5.1.15-ndb-6.1.7-beta (Released 05 May 2007)</title>
<para role="release-level">
This is a new Beta development release, fixing recently
@@ -6908,23 +6906,23 @@
</para>
<itemizedlist>
-
+
<listitem>
<para>
Under certain rare circumstances, <literal>DROP
- TABLE</literal> or <literal>TRUNCATE</literal> of an
+ TABLE</literal> or <literal>TRUNCATE</literal> of an
<literal>NDB</literal> table could cause a node failure or
forced cluster shutdown. (Bug #27581)
</para>
</listitem>
-
+
<listitem>
<para>
Memory usage of a <command>mysqld</command> process grew
even while idle. (Bug #27560)
</para>
</listitem>
-
+
<listitem>
<para>
<emphasis role="bold">Cluster APIs</emphasis>: An issue with
@@ -6934,7 +6932,7 @@
corruption. (Bug #27663)
</para>
</listitem>
-
+
<listitem>
<para>
<emphasis role="bold">Cluster Replication</emphasis>: Under
@@ -6942,7 +6940,7 @@
checkpoint indexes out of order. (Bug #27651)
</para>
</listitem>
-
+
<listitem>
<para>
<emphasis role="bold">Cluster Replication</emphasis>: It was
@@ -6951,15 +6949,14 @@
cluster. (Bug #27728)
</para>
</listitem>
-
+
<listitem>
<para>
Some queries that updated multiple tables were not backed up
or replicated correctly. (Bug #27748)
</para>
</listitem>
-
-
+
<listitem>
<para>
<emphasis role="bold">Disk Data</emphasis>: Changes to a
@@ -6968,43 +6965,43 @@
transaction had been committed. (Bug #27757)
</para>
</listitem>
-
+
<listitem>
<para>
An <literal>INSERT</literal> followed a delete
<literal>DELETE</literal> on the same <literal>NDB</literal>
table caused a memory leak. (Bug #27756)
</para>
-
+
<para>
(This bug was introduced by the fix for Bug #20612.)
</para>
</listitem>
-
-
+
<listitem>
<para>
Under some circumstances, a node restart could fail to
update the Global Checkpoint Index (GCI). (Bug #28023)
</para>
</listitem>
-
+
<listitem>
- <para>
- Under certain rare circumstances, <command>ndbd</command>
- could get caught in an infinite loop when one transaction took
- a read lock and then a second transaction attempted to obtain
- a write lock on the same tuple in the lock queue. (Bug #28073)
- </para>
+ <para>
+ Under certain rare circumstances, <command>ndbd</command>
+ could get caught in an infinite loop when one transaction
+ took a read lock and then a second transaction attempted to
+ obtain a write lock on the same tuple in the lock queue.
+ (Bug #28073)
+ </para>
</listitem>
-
+
<listitem>
<para>
The cluster waited 30 seconds instead of 30 milliseconds
before reading table statistics. (Bug #28093)
</para>
</listitem>
-
+
<listitem>
<para>
<emphasis role="bold">Disk Data</emphasis>: Changing a
@@ -7013,15 +7010,15 @@
caused the table to become an in-memory table. (Bug #24667)
</para>
</listitem>
-
+
<listitem>
<para>
Performing a delete followed by an insert during a local
checkpoint could cause a <errortext>Rowid already
- allocated</errortext> error. (Bug #27205)
+ allocated</errortext> error. (Bug #27205)
</para>
</listitem>
-
+
<listitem>
<para>
<emphasis role="bold">Disk Data</emphasis>: When restarting
@@ -7039,14 +7036,14 @@
node failure. (Bug #28161)
</para>
</listitem>
-
+
<listitem>
<para>
<command>mysqldump</command> could not dump log tables. (Bug
#26121)
</para>
</listitem>
-
+
<listitem>
<para>
The <option>--with-readline</option> option for
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r6554 - trunk/refman-5.1 | jon | 21 May |
