Author: paul
Date: 2007-06-26 21:23:09 +0200 (Tue, 26 Jun 2007)
New Revision: 6917
Log:
r22095@frost: paul | 2007-06-26 14:21:50 -0500
Document bugfixes:
Bug#24924
Bug#25602
Bug#27383
Bug#28984
Bug#29117
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:26621
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:22092
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:26621
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:22095
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-26 18:33:27 UTC (rev 6916)
+++ trunk/refman-4.1/news-4.1.xml 2007-06-26 19:23:09 UTC (rev 6917)
Changed blocks: 1, Lines Added: 14, Lines Deleted: 0; 876 bytes
@@ -190,6 +190,20 @@
<listitem>
<para>
+ A malformed password packet in the connection protocol could
+ cause the server to crash. (Bug #28984)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ A network structure was initialized incorrectly, leading to
+ embedded server crashes. (Bug #29117)
+ </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
Modified: trunk/refman-5.0/releasenotes-es-5.0.xml
===================================================================
--- trunk/refman-5.0/releasenotes-es-5.0.xml 2007-06-26 18:33:27 UTC (rev 6916)
+++ trunk/refman-5.0/releasenotes-es-5.0.xml 2007-06-26 19:23:09 UTC (rev 6917)
Changed blocks: 2, Lines Added: 40, Lines Deleted: 0; 1947 bytes
@@ -102,6 +102,39 @@
<listitem>
<para>
+ A query with <literal>DISTINCT</literal> in the select list to
+ which the loose-scan optimization for grouping queries was
+ applied returned an incorrect result set when the query was
+ used with the <literal>SQL_BIG_RESULT</literal> option. (Bug
+ #25602)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ A too-long <literal>shared-memory-base-name</literal> value
+ could cause a buffer overflow and crash the server or clients.
+ (Bug #24924)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fixed a case of unsafe aliasing in the source that caused a
+ client library crash when compiled with <command>gcc</command>
+ 4 at high optimization levels. (Bug #27383)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ A network structure was initialized incorrectly, leading to
+ embedded server crashes. (Bug #29117)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
A stack overrun could when storing <literal>DATETIME</literal>
values using repeated prepared statements. (Bug #27592)
</para>
@@ -347,6 +380,13 @@
<listitem>
<para>
+ A malformed password packet in the connection protocol could
+ cause the server to crash. (Bug #28984)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
<literal>INSERT .. ON DUPLICATE KEY UPDATE</literal> could
under some circumstances silently update rows when it should
not have. (Bug #28904)
Modified: trunk/refman-5.1/news-5.1.xml
===================================================================
--- trunk/refman-5.1/news-5.1.xml 2007-06-26 18:33:27 UTC (rev 6916)
+++ trunk/refman-5.1/news-5.1.xml 2007-06-26 19:23:09 UTC (rev 6917)
Changed blocks: 3, Lines Added: 218, Lines Deleted: 126; 12000 bytes
@@ -30,6 +30,83 @@
<filename>refman-common</filename> directory.
</remark>
+ <section id="news-5-1-21">
+
+ <title>Changes in release 5.1.21 (Not yet released)</title>
+
+ <para role="release-level">
+ This is a new Beta development release, fixing recently discovered
+ bugs.
+ </para>
+
+ <para role="release-non-production">
+ <emphasis role="bold">NOTE:</emphasis> This Beta release, as any
+ other pre-production release, should not be installed on
+ <emphasis>production</emphasis> level systems or systems with
+ critical data. It is good practice to back up your data before
+ installing any new version of software. Although MySQL has worked
+ very hard to ensure a high level of quality, protect your data by
+ making a backup as you would for any software beta release. Please
+ refer to our bug database at <ulink url="http://bugs.mysql.com/"/>
+ for more details about the individual bugs fixed in this version.
+ </para>
+
+ &enterprise-offering-note;
+
+<!--
+ <para>
+ Functionality added or changed:
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ </para>
+ </listitem>
+
+ </itemizedlist>
+-->
+
+ <para>
+ Bugs fixed:
+ </para>
+
+ <remark role="note">
+ Leave any security or incompatible fixes first in the list.
+ </remark>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ A query with <literal>DISTINCT</literal> in the select list to
+ which the loose-scan optimization for grouping queries was
+ applied returned an incorrect result set when the query was
+ used with the <literal>SQL_BIG_RESULT</literal> option. (Bug
+ #25602)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ A network structure was initialized incorrectly, leading to
+ embedded server crashes. (Bug #29117)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fixed a case of unsafe aliasing in the source that caused a
+ client library crash when compiled with <command>gcc</command>
+ 4 at high optimization levels. (Bug #27383)
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ </section>
+
<section id="news-5-1-20">
<title>Changes in release 5.1.20 (Not yet released)</title>
@@ -210,132 +287,6 @@
<listitem>
<para>
- On Windows, an application that called
- <literal>mysql_thread_init()</literal> but forgot to call
- <literal>mysql_thread_end()</literal> would get this error:
- <literal>Error in my_thread_global_end()</literal> (Bug
- #25621)
- </para>
- </listitem>
-
- <listitem>
- <para>
- A stack overrun could occur when storing
- <literal>DATETIME</literal> values using repeated prepared
- statements. (Bug #27592)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <literal>INSERT .. ON DUPLICATE KEY UPDATE</literal> could
- under some circumstances silently update rows when it should
- not have. (Bug #28904)
- </para>
- </listitem>
-
- <listitem>
- <para>
- Using events in replication could cause the slave to crash.
- (Bug #28953)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <literal>ALTER TABLE ... ENABLE KEYS</literal> could cause
- <command>mysqld</command> to crash when executed on a table
- containing on a <literal>MyISAM</literal> table containing
- billions of rows. (Bug #27029)
- </para>
- </listitem>
-
- <listitem>
- <para>
- A <literal>FLUSH TABLES WITH READ LOCK</literal> statement
- followed by a <literal>FLUSH LOGS</literal> statement caused a
- deadlock if the general log or the slow query log was enabled.
- (Bug #26380)
- </para>
- </listitem>
-
- <listitem>
- <para>
- The <literal>TRUNCATE</literal> statement was handled
- differently by the server when row-based logging was in
- effect, even though the binlogging format in effect does not
- effect the fact that <literal>TRUNCATE</literal> is always
- logged as a statement. (Bug #29130)
- </para>
- </listitem>
-
- <listitem>
- <para>
- When the query cache was fully used, issuing <literal>RENAME
- DATABASE</literal> or <literal>RENAME SCHEMA</literal> could
- cause the server to hang, with 100% CPU usage. (Bug #28211)
- </para>
- </listitem>
-
- <listitem>
- <para>
- Binary content <literal>0x00</literal> in a
- <literal>BLOB</literal> column sometimes became <literal>0x5C
- 0x00</literal> following a dump and reload, which could cause
- problems with data using multi-byte character sets such as
- <literal>GBK</literal> (Chinese). This was due to a problem
- with <literal>SELECT INTO OUTFILE</literal> whereby
- <literal>LOAD DATA</literal> later incorrectly interpreted
- <literal>0x5C</literal> as the second byte of a multi-byte
- sequence rather than as the <literal>SOLIDUS</literal>
- (<quote>\</quote>) character, used by MySQL as the escape
- character. (Bug #26711)
- </para>
- </listitem>
-
- <listitem>
- <para>
- If one of the queries in a <literal>UNION</literal> used the
- <literal>SQL_CACHE</literal> option and another query in the
- <literal>UNION</literal> contained a nondeterministic
- function, the result was still cached. For example, this query
- was incorrectly cached:
-
-<programlisting>
-SELECT NOW() FROM t1 UNION SELECT SQL_CACHE 1 FROM t1;
-</programlisting>
-
- (Bug #29053)
- </para>
- </listitem>
-
- <listitem>
- <para>
- Queries using UDFs or stored functions were cached. (Bug
- #28921)
- </para>
- </listitem>
-
- <listitem>
- <para>
- The modification of a table by a partially completed
- multi-column update was not recorded in the binlog, rather
- than being marked by an event and a corresponding error code.
- (Bug #27716)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <literal>SHOW ENGINES</literal> and queries on
- <literal>INFORMATION_SCHEMA.ENGINES</literal> did not use the
- same values for representing the same storage engine states.
- (Bug #27684)
- </para>
- </listitem>
-
- <listitem>
- <para>
<literal>NDB Cluster</literal> (Disk Data): When dropping a
page, the stack's bottom entry could sometime be left
<quote>cold</quote> rather than <quote>hot</quote>, violating
@@ -518,6 +469,147 @@
<listitem>
<para>
+ A malformed password packet in the connection protocol could
+ cause the server to crash. (Bug #28984)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ A too-long <literal>shared-memory-base-name</literal> value
+ could cause a buffer overflow and crash the server or clients.
+ (Bug #24924)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ On Windows, an application that called
+ <literal>mysql_thread_init()</literal> but forgot to call
+ <literal>mysql_thread_end()</literal> would get this error:
+ <literal>Error in my_thread_global_end()</literal> (Bug
+ #25621)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ A stack overrun could occur when storing
+ <literal>DATETIME</literal> values using repeated prepared
+ statements. (Bug #27592)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>INSERT .. ON DUPLICATE KEY UPDATE</literal> could
+ under some circumstances silently update rows when it should
+ not have. (Bug #28904)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Using events in replication could cause the slave to crash.
+ (Bug #28953)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>ALTER TABLE ... ENABLE KEYS</literal> could cause
+ <command>mysqld</command> to crash when executed on a table
+ containing on a <literal>MyISAM</literal> table containing
+ billions of rows. (Bug #27029)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ A <literal>FLUSH TABLES WITH READ LOCK</literal> statement
+ followed by a <literal>FLUSH LOGS</literal> statement caused a
+ deadlock if the general log or the slow query log was enabled.
+ (Bug #26380)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The <literal>TRUNCATE</literal> statement was handled
+ differently by the server when row-based logging was in
+ effect, even though the binlogging format in effect does not
+ effect the fact that <literal>TRUNCATE</literal> is always
+ logged as a statement. (Bug #29130)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ When the query cache was fully used, issuing <literal>RENAME
+ DATABASE</literal> or <literal>RENAME SCHEMA</literal> could
+ cause the server to hang, with 100% CPU usage. (Bug #28211)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Binary content <literal>0x00</literal> in a
+ <literal>BLOB</literal> column sometimes became <literal>0x5C
+ 0x00</literal> following a dump and reload, which could cause
+ problems with data using multi-byte character sets such as
+ <literal>GBK</literal> (Chinese). This was due to a problem
+ with <literal>SELECT INTO OUTFILE</literal> whereby
+ <literal>LOAD DATA</literal> later incorrectly interpreted
+ <literal>0x5C</literal> as the second byte of a multi-byte
+ sequence rather than as the <literal>SOLIDUS</literal>
+ (<quote>\</quote>) character, used by MySQL as the escape
+ character. (Bug #26711)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ If one of the queries in a <literal>UNION</literal> used the
+ <literal>SQL_CACHE</literal> option and another query in the
+ <literal>UNION</literal> contained a nondeterministic
+ function, the result was still cached. For example, this query
+ was incorrectly cached:
+
+<programlisting>
+SELECT NOW() FROM t1 UNION SELECT SQL_CACHE 1 FROM t1;
+</programlisting>
+
+ (Bug #29053)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Queries using UDFs or stored functions were cached. (Bug
+ #28921)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The modification of a table by a partially completed
+ multi-column update was not recorded in the binlog, rather
+ than being marked by an event and a corresponding error code.
+ (Bug #27716)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>SHOW ENGINES</literal> and queries on
+ <literal>INFORMATION_SCHEMA.ENGINES</literal> did not use the
+ same values for representing the same storage engine states.
+ (Bug #27684)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
Connections from one <command>mysqld</command> server to
another failed on Mac OS X, affecting replication and
<literal>FEDERATED</literal> tables. (Bug #26664)
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r6917 - in trunk: . refman-4.1 refman-5.0 refman-5.1 | paul | 26 Jun |
