Author: mcbrown
Date: 2006-04-25 17:47:32 +0200 (Tue, 25 Apr 2006)
New Revision: 1935
Log:
Documenting bug #17917
Modified:
trunk/refman-common/news-4.1.xml
trunk/refman-common/news-5.0.xml
trunk/refman-common/news-5.1.xml
Modified: trunk/refman-common/news-4.1.xml
===================================================================
--- trunk/refman-common/news-4.1.xml 2006-04-25 15:43:42 UTC (rev 1934)
+++ trunk/refman-common/news-4.1.xml 2006-04-25 15:47:32 UTC (rev 1935)
@@ -219,6 +219,14 @@
<listitem>
<para>
+ Executing <literal>SELECT</literal> on a large table that had
+ been compressed within <command>myisampack</command> could
+ cause a crash. (Bug #17917)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
<literal>NDB Cluster</literal>: In a 2-node cluster with a
node failure, restarting the node with a low value for
<literal>StartPartialTimeout</literal> could cause the cluster
Modified: trunk/refman-common/news-5.0.xml
===================================================================
--- trunk/refman-common/news-5.0.xml 2006-04-25 15:43:42 UTC (rev 1934)
+++ trunk/refman-common/news-5.0.xml 2006-04-25 15:47:32 UTC (rev 1935)
@@ -248,6 +248,14 @@
<listitem>
<para>
+ Executing <literal>SELECT</literal> on a large table that had
+ been compressed within <command>myisampack</command> could
+ cause a crash. (Bug #17917)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
<literal>NDB Cluster</literal>: When attempting to create an
index on a <literal>BIT</literal> or <literal>BLOB</literal>
column, <errortext>Error 743: Unsupported character set in
Modified: trunk/refman-common/news-5.1.xml
===================================================================
--- trunk/refman-common/news-5.1.xml 2006-04-25 15:43:42 UTC (rev 1934)
+++ trunk/refman-common/news-5.1.xml 2006-04-25 15:47:32 UTC (rev 1935)
@@ -104,29 +104,29 @@
all configured data nodes first. (Bug #18606)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: It is now possible to restore
a Cluster backup between big-endian and little-endian
- machines. (Bug #19255)
+ machines. (Bug #19255)
</para>
</listitem>
-
- <listitem>
- <para>
- <literal>NDB Cluster</literal>: It is now possible to install
- MySQL with Cluster support to a non-default location and
- change the search path for font description files using
- either the <option>--basedir</option> or
- <option>--character-sets-dir</option> options. (Previously
- in MySQL 5.1, <command>ndbd</command> searched only the
- default path for character sets.)
- </para>
- </listitem>
<listitem>
<para>
+ <literal>NDB Cluster</literal>: It is now possible to install
+ MySQL with Cluster support to a non-default location and
+ change the search path for font description files using either
+ the <option>--basedir</option> or
+ <option>--character-sets-dir</option> options. (Previously in
+ MySQL 5.1, <command>ndbd</command> searched only the default
+ path for character sets.)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
In result set metadata, the
<literal>MYSQL_FIELD.length</literal> value for
<literal>BIT</literal> columns now is reported in number of
@@ -143,23 +143,31 @@
</para>
<itemizedlist>
-
+
<listitem>
<para>
+ Executing <literal>SELECT</literal> on a large table that had
+ been compressed within <command>myisampack</command> could
+ cause a crash. (Bug #17917)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
<literal>NDB Cluster</literal> (NDB API): Passing a
nonexistent index name to
<literal>NdbIndexScanOperation::setBound()</literal> caused a
segmentation fault. (Bug #19088)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>ALTER TABLE ... REBUILD PARTITION</literal> returned
an inaccurate error message. (Bug #16819)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: In rare situations with
@@ -167,25 +175,25 @@
<literal>IndexScanOperations</literal>. (Bug #19198)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>InnoDB</literal>: A <literal>DELETE</literal>
followed by an <literal>INSERT</literal> and then by an
<literal>UPDATE</literal> on a partitioned
<literal>InnoDB</literal> table caused subsequent queries to
- return incorrect results. (Bug #17992)
+ return incorrect results. (Bug #17992)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: A table insert or update of
more than 128 bytes of data in a 4-replica Cluster could cause
- a node to crash. (Bug #18622)
+ a node to crash. (Bug #18622)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal> (Disk Data): Concurrent table
@@ -194,7 +202,7 @@
node failures. (Bug #18575)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: An issue with replication
@@ -202,7 +210,7 @@
cluster to crash when entering single user mode. (Bug #18535)
</para>
</listitem>
-
+
<listitem>
<para>
Successive <literal>ALTER TABLE ... DROP PARTITION</literal>
@@ -210,18 +218,18 @@
cause the server to crash. (Bug #18962)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: When attempting to create an
- index on a <literal>BIT</literal> or
- <literal>BLOB</literal> column, <errortext>Error 743:
- Unsupported character set in table or index</errortext> was
- returned instead of <errortext>Error 906: Unsupported
- attribute type in index</errortext>.
+ index on a <literal>BIT</literal> or <literal>BLOB</literal>
+ column, <errortext>Error 743: Unsupported character set in
+ table or index</errortext> was returned instead of
+ <errortext>Error 906: Unsupported attribute type in
+ index</errortext>.
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: The Cluster binlog
@@ -230,7 +238,7 @@
from the binary log. (Bug #18932)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: Concurrent
@@ -239,7 +247,7 @@
failures. (Bug #19245)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal> (Disk Data): Running an
@@ -248,7 +256,7 @@
deadlock. (Bug #19244)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal> (Disk Data): Issuing a
@@ -257,7 +265,7 @@
corruption. (Bug #19141)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: <command>ndb_restore</command>
@@ -265,35 +273,35 @@
cluster. (Bug #18210)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: Adding an index to an unsigned
integer column did not work correctly. (Bug #18133)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: A <literal>SELECT</literal>
from an <literal>NDB</literal> table with <literal>ORDER BY
- <replaceable>indexed_column</replaceable></literal> and a
+ <replaceable>indexed_column</replaceable></literal> and a
<literal>LIMIT</literal> clause would fail following
- <literal>ALTER TABLE</literal>. (Bug #18094)
+ <literal>ALTER TABLE</literal>. (Bug #18094)
</para>
</listitem>
-
+
<listitem>
<para>
- <literal>NDB Cluster</literal>: Performing multiple <literal>ALTER
- TABLE</literal> operations on the same NDB table from
- different <command>mysqld</command> processes in the same
- cluster led to schema versioning errors when trying to access
- the table again following the restart of one of the
+ <literal>NDB Cluster</literal>: Performing multiple
+ <literal>ALTER TABLE</literal> operations on the same NDB
+ table from different <command>mysqld</command> processes in
+ the same cluster led to schema versioning errors when trying
+ to access the table again following the restart of one of the
<command>mysqld</command> processes. (Bug #16445)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: Starting
@@ -302,7 +310,7 @@
out. (Bug #19214)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: Fragment IDs were not being
@@ -319,24 +327,24 @@
digits. (Bug #17043)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal> (Replication): Delete and
update of rows in a table without a primary key failed on the
- slave. (Bug #17400)
+ slave. (Bug #17400)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: On slow networks or CPUs, the
management client <literal>SHOW</literal> command could
sometimes erroneously show all data nodes as being master
- nodes belonging to nodegroup 0. (Bug #15530)
+ nodes belonging to nodegroup 0. (Bug #15530)
</para>
</listitem>
-
+
<listitem>
<para>
The XPath <literal>string-length()</literal> function was not
@@ -696,7 +704,7 @@
</para>
<itemizedlist>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: <literal>BLOB</literal>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r1935 - trunk/refman-common | mcbrown | 25 Apr |
