Author: paul
Date: 2007-06-18 15:54:28 +0200 (Mon, 18 Jun 2007)
New Revision: 6842
Log:
r21756@frost: paul | 2007-06-18 08:52:37 -0500
Documented bugfixes:
Bug#26402
Bug#28574
Bug#28748
Modified:
trunk/refman-4.1/news-4.1.xml
trunk/refman-5.0/releasenotes-es-5.0.xml
trunk/refman-5.1/news-5.1.xml
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:26606
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:21734
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:18307
+ 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:26606
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:21756
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:18307
Modified: trunk/refman-4.1/news-4.1.xml
===================================================================
--- trunk/refman-4.1/news-4.1.xml 2007-06-18 13:25:57 UTC (rev 6841)
+++ trunk/refman-4.1/news-4.1.xml 2007-06-18 13:54:28 UTC (rev 6842)
Changed blocks: 1, Lines Added: 12, Lines Deleted: 0; 977 bytes
@@ -190,6 +190,18 @@
<listitem>
<para>
+ When one thread attempts to lock two (or more) tables and
+ another thread executes a statement that aborts these locks
+ (such as <literal>REPAIR TABLE</literal>, <literal>OPTIMIZE
+ TABLE</literal>, or <literal>CHECK TABLE</literal>), the
+ thread might get a table object with an incorrect lock type in
+ the table cache. The result is table corruption or a server
+ crash. (Bug #28574)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
<literal>PURGE MASTER LOGS BEFORE
(<replaceable>subquery</replaceable>)</literal> caused a
server crash. Subqueries are forbidden in the
Modified: trunk/refman-5.0/releasenotes-es-5.0.xml
===================================================================
--- trunk/refman-5.0/releasenotes-es-5.0.xml 2007-06-18 13:25:57 UTC (rev 6841)
+++ trunk/refman-5.0/releasenotes-es-5.0.xml 2007-06-18 13:54:28 UTC (rev 6842)
Changed blocks: 2, Lines Added: 36, Lines Deleted: 17; 2544 bytes
@@ -99,23 +99,6 @@
<listitem>
<para>
- An error occurred trying to connect to <command>mysqld-debug.exe</command>.
- (Bug #27597)
- </para>
- </listitem>
-
- <listitem>
- <para>
- Using an <literal>INTEGER</literal> column from a table to
- <literal>ROUND()</literal> a number produced different
- results than using a constant with the same value
- as the <literal>INTEGER</literal> column.
- (Bug# 28980)
- </para>
- </listitem>
-
- <listitem>
- <para>
<literal>NDB Cluster</literal>: The actual value of
<literal>MaxNoOfOpenFiles</literal> as used by the cluster was
offset by 1 from the value set in
@@ -176,6 +159,42 @@
<listitem>
<para>
+ <literal>SELECT</literal> statements involving comparison of
+ doubles to longlong or unsigned longlong values could return
+ one too few rows. (Bug #28748)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ When one thread attempts to lock two (or more) tables and
+ another thread executes a statement that aborts these locks
+ (such as <literal>REPAIR TABLE</literal>, <literal>OPTIMIZE
+ TABLE</literal>, or <literal>CHECK TABLE</literal>), the
+ thread might get a table object with an incorrect lock type in
+ the table cache. The result is table corruption or a server
+ crash. (Bug #28574)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ An error occurred trying to connect to
+ <command>mysqld-debug.exe</command>. (Bug #27597)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Using an <literal>INTEGER</literal> column from a table to
+ <literal>ROUND()</literal> a number produced different results
+ than using a constant with the same value as the
+ <literal>INTEGER</literal> column. (Bug# 28980)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
InnoDB tables using an indexed <literal>CHAR</literal> column
with <literal>utf8</literal> as the default character set
could fail to return the right rows. (Bug #28878)
Modified: trunk/refman-5.1/news-5.1.xml
===================================================================
--- trunk/refman-5.1/news-5.1.xml 2007-06-18 13:25:57 UTC (rev 6841)
+++ trunk/refman-5.1/news-5.1.xml 2007-06-18 13:54:28 UTC (rev 6842)
Changed blocks: 2, Lines Added: 73, Lines Deleted: 42; 4762 bytes
@@ -167,48 +167,6 @@
<listitem>
<para>
- Running <literal>SHOW TABLE STATUS</literal> while performing
- a high number of inserts on partitioned tables with a great
- many partitions could cause the server to crash. (Bug #28806)
- </para>
- </listitem>
-
- <listitem>
- <para>
- An error occurred trying to connect to
- <command>mysqld-debug.exe</command>. (Bug #27597)
- </para>
- </listitem>
-
- <listitem>
- <para>
- Using an <literal>INTEGER</literal> column from a table to
- <literal>ROUND()</literal> a number produced different results
- than using a constant with the same value as the
- <literal>INTEGER</literal> column. (Bug# 28980)
- </para>
- </listitem>
-
- <listitem>
- <para>
- The <literal>PARTITION_COMMENT</literal> column of the
- <literal>INFORMATION_SCHEMA.PARTITIONS</literal> table had the
- wrong default value. (Bug #28007)
- </para>
- </listitem>
-
- <listitem>
- <para>
- Performing <literal>ALTER TABLE ... ADD PARTITION</literal> or
- <literal>ALTER TABLE DROP PARTITION</literal> could result in
- inconcsistent data, or cause the server to crash, if done
- concurrently with other accesses to the table. (Bug #28477,
- Bug #28488)
- </para>
- </listitem>
-
- <listitem>
- <para>
<literal>NDB Cluster</literal>: A regression in the heartbeat
monitoring code could lead to node failure under high load.
This issue affected MySQL 5.1.19 only. (Bug #28783)
@@ -303,6 +261,79 @@
<listitem>
<para>
+ <literal>SELECT</literal> statements involving comparison of
+ doubles to longlong or unsigned longlong values could return
+ one too few rows. (Bug #28748)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ When one thread attempts to lock two (or more) tables and
+ another thread executes a statement that aborts these locks
+ (such as <literal>REPAIR TABLE</literal>, <literal>OPTIMIZE
+ TABLE</literal>, or <literal>CHECK TABLE</literal>), the
+ thread might get a table object with an incorrect lock type in
+ the table cache. The result is table corruption or a server
+ crash. (Bug #28574)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The server crashed when attempting to open a table having a
+ <literal>#mysql50#</literal> prefix in the database or table
+ name. The server now will not open such tables. (This prefix
+ is reserved by <command>mysql_upgrade</command> for accessing
+ 5.0 tables that have names not yet encoded for 5.1.) (Bug
+ #26402)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Running <literal>SHOW TABLE STATUS</literal> while performing
+ a high number of inserts on partitioned tables with a great
+ many partitions could cause the server to crash. (Bug #28806)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ An error occurred trying to connect to
+ <command>mysqld-debug.exe</command>. (Bug #27597)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Using an <literal>INTEGER</literal> column from a table to
+ <literal>ROUND()</literal> a number produced different results
+ than using a constant with the same value as the
+ <literal>INTEGER</literal> column. (Bug# 28980)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The <literal>PARTITION_COMMENT</literal> column of the
+ <literal>INFORMATION_SCHEMA.PARTITIONS</literal> table had the
+ wrong default value. (Bug #28007)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Performing <literal>ALTER TABLE ... ADD PARTITION</literal> or
+ <literal>ALTER TABLE DROP PARTITION</literal> could result in
+ inconcsistent data, or cause the server to crash, if done
+ concurrently with other accesses to the table. (Bug #28477,
+ Bug #28488)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
InnoDB tables using an indexed <literal>CHAR</literal> column
with <literal>utf8</literal> as the default character set
could fail to return the right rows. (Bug #28878)
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r6842 - in trunk: . refman-4.1 refman-5.0 refman-5.1 | paul | 18 Jun |
