Author: paul
Date: 2007-07-06 05:48:06 +0200 (Fri, 06 Jul 2007)
New Revision: 7029
Log:
r22448@frost: paul | 2007-07-05 22:45:37 -0500
Document bugfixes:
Bug#24795
Bug#26938
Bug#27060
Bug#28600
Bug#28752
Bug#29104
Modified:
trunk/refman-5.0/releasenotes-cs-5.0.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:27312
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:22447
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:18820
+ 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:27312
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:22448
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:18820
Modified: trunk/refman-5.0/releasenotes-cs-5.0.xml
===================================================================
--- trunk/refman-5.0/releasenotes-cs-5.0.xml 2007-07-06 03:47:48 UTC (rev 7028)
+++ trunk/refman-5.0/releasenotes-cs-5.0.xml 2007-07-06 03:48:06 UTC (rev 7029)
Changed blocks: 1, Lines Added: 70, Lines Deleted: 0; 1915 bytes
@@ -25,6 +25,76 @@
to earlier versions, see <xref linkend="news"/>.
</para>
+ <section id="releasenotes-cs-5-0-45">
+
+ <title>Release Notes for MySQL Community Server 5.0.45 (Not yet released)</title>
+
+ <para role="release-level">
+ This is a bugfix release for the current production release
+ family. It replaces MySQL 5.0.41.
+ </para>
+
+ <para>
+ Functionality added or changed:
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para></para>
+ </listitem>
+
+<!-- From 5.0.44 (begin) -->
+
+<!-- From 5.0.44 (end) -->
+
+<!-- From 5.0.42 (begin) -->
+
+<!-- From 5.0.42 (end) -->
+
+ </itemizedlist>
+
+ <para>
+ Bugs fixed:
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ Potential memory leaks in the <literal>SHOW PROFILE</literal>
+ implementation were eliminated. (Bug #24795)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Times displayed by <literal>SHOW PROFILE</literal> were
+ incorrectly associated with the profile entry one later than
+ the corrrect one. (Bug #27060)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>SHOW PROFILE</literal> hung if executed before
+ enabling the <literal>@@profiling</literal> session variable.
+ (Bug #26938)
+ </para>
+ </listitem>
+
+<!-- From 5.0.44 (begin) -->
+
+<!-- From 5.0.44 (end) -->
+
+<!-- From 5.0.42 (begin) -->
+
+<!-- From 5.0.42 (end) -->
+
+ </itemizedlist>
+
+ </section>
+
<section id="releasenotes-cs-5-0-41">
<title>Release Notes for MySQL Community Server 5.0.41 (01 May 2007)</title>
Modified: trunk/refman-5.0/releasenotes-es-5.0.xml
===================================================================
--- trunk/refman-5.0/releasenotes-es-5.0.xml 2007-07-06 03:47:48 UTC (rev 7028)
+++ trunk/refman-5.0/releasenotes-es-5.0.xml 2007-07-06 03:48:06 UTC (rev 7029)
Changed blocks: 1, Lines Added: 24, Lines Deleted: 7; 2343 bytes
@@ -94,23 +94,40 @@
<listitem>
<para>
- The server returned data from <literal>SHOW CREATE
- TABLE</literal> statement or a <literal>SELECT</literal>
- statement on an INFORMATION_SCHEMA table using the
- <literal>binary</literal> character set. (Bug #10491)
+ <literal>NDB Cluster</literal>: The management client's
+ response to <literal>START BACKUP WAIT COMPLETED</literal> did
+ not include the backup ID. (Bug #27640)
</para>
</listitem>
<listitem>
<para>
- <literal>NDB Cluster</literal>: The management client's
- response to <literal>START BACKUP WAIT COMPLETED</literal> did
- not include the backup ID. (Bug #27640)
+ An assertion failure occurred if a query contained a
+ conjunctive predicate of the form
+ <literal><replaceable>view_column</replaceable> =
+ constant</literal> in the <literal>WHERE</literal> clause and
+ the <literal>GROUP BY</literal> clause contained a reference
+ to a different view column. The fix also enables application
+ of an optimization that was being skipped if a query contained
+ a conjunctive predicate of the form
+ <literal><replaceable>view_column</replaceable> =
+ constant</literal> in the <literal>WHERE</literal> clause and
+ the <literal>GROUP BY</literal> clause contained a reference
+ to the same view column. (Bug #29104)
</para>
</listitem>
<listitem>
<para>
+ The server returned data from <literal>SHOW CREATE
+ TABLE</literal> statement or a <literal>SELECT</literal>
+ statement on an INFORMATION_SCHEMA table using the
+ <literal>binary</literal> character set. (Bug #10491)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
Mixing binary and <literal>utf8</literal> columns in a union
caused field lengths to be calculated incorrectly, resulting
in truncation. (Bug #29205)
Modified: trunk/refman-5.1/news-5.1.xml
===================================================================
--- trunk/refman-5.1/news-5.1.xml 2007-07-06 03:47:48 UTC (rev 7028)
+++ trunk/refman-5.1/news-5.1.xml 2007-07-06 03:48:06 UTC (rev 7029)
Changed blocks: 2, Lines Added: 92, Lines Deleted: 59; 9350 bytes
@@ -80,123 +80,140 @@
<listitem>
<para>
- Replication of partitioned tables using the
- <literal>InnoDB</literal> storage engine failed with
- <literal>binlog-format=ROW</literal> or
- <literal>binlog-format=MIXED</literal>. (Bug #28430)
+ <literal>NDB Cluster</literal> (Cluster Replication): When
+ executing a statement where
+ <literal>binlog_format=statement</literal>, the result of the
+ statement was logged both as a statement and as rows. (Bug
+ #29222)
</para>
</listitem>
<listitem>
<para>
- <literal>SHOW TRIGGERS</literal> did not handle non-Latin
- symbols in column names correctly;
- <command>mysqldump</command> also did not work properly with
- such triggers. Both of these issues were also related to
- improper handling of non-Latin characters sets in
- <literal>INFORMATION_SCHEMA</literal> tables. (Bug #19443)
+ <literal>NDB Cluster</literal>: Replica redo logs were
+ inconsistently handled during a system restart. (Bug #29354)
</para>
</listitem>
<listitem>
<para>
- If a storage engine has its own logging capability, then any
- statement using both this engine and some other engine not
- having its own logging could not be correctly logged, due to
- the fact that entries from one engine could be logged before
- entries from the other engine were. This did not generate any
- error messages when it occurred.
+ <literal>NDB Cluster</literal>: When restarting a data node,
+ queries could hang during that node's start phase 5, and only
+ continue once the node entered phase 6. (Bug #29364)
</para>
+ </listitem>
+ <listitem>
<para>
- Now, if multiple storage engines are used in a statement and
- at least one of them has its own logging capability, then an
- error message is generated and the statement is not executed.
- (Bug #28722)
+ <literal>NDB Cluster</literal>: When a node failed to respond
+ to a <literal>COPY_GCI</literal> signal as part of a global
+ checkpoint, the master node was killed instead instead of the
+ node that actually failed. (Bug #29331)
</para>
-
- <note>
- <para>
- Currently, the only storage engine to have its own logging
- capability is <literal>NDBCLUSTER</literal>.
- </para>
- </note>
</listitem>
<listitem>
<para>
- Using the <literal>READ COMMITTED</literal> transaction
- isolation level caused mixed and statement-based replication
- to fail. (Bug #23051)
+ <literal>NDB Cluster</literal>: An invalid comparison made
+ during <literal>REDO</literal> validation that could lead to
+ an <errortext>Error while reading REDO log</errortext>
+ condition. (Bug #29118)
</para>
</listitem>
<listitem>
<para>
- The server returned data from <literal>SHOW CREATE
- TABLE</literal> statement or a <literal>SELECT</literal>
- statement on an INFORMATION_SCHEMA table using the
- <literal>binary</literal> character set. (Bug #10491)
+ <literal>NDB Cluster</literal>: The wrong data pages were
+ sometimes invalidated following a global checkpoint. (Bug
+ #29067)
</para>
</listitem>
<listitem>
<para>
- <literal>NDB Cluster</literal> (Cluster Replication): When
- executing a statement where
- <literal>binlog_format=statement</literal>, the result of the
- statement was logged both as a statement and as rows. (Bug
- #29222)
+ <literal>NDB Cluster</literal>: If at least 2 files were
+ involved in <literal>REDO</literal> invalidation, then file 0
+ of page 0 was not updated and so pointed to an invalid part of
+ the redo log. (Bug #29057)
</para>
</listitem>
<listitem>
<para>
- <literal>NDB Cluster</literal>: Replica redo logs were
- inconsistently handled during a system restart. (Bug #29354)
+ An assertion failure occurred if a query contained a
+ conjunctive predicate of the form
+ <literal><replaceable>view_column</replaceable> =
+ constant</literal> in the <literal>WHERE</literal> clause and
+ the <literal>GROUP BY</literal> clause contained a reference
+ to a different view column. The fix also enables application
+ of an optimization that was being skipped if a query contained
+ a conjunctive predicate of the form
+ <literal><replaceable>view_column</replaceable> =
+ constant</literal> in the <literal>WHERE</literal> clause and
+ the <literal>GROUP BY</literal> clause contained a reference
+ to the same view column. (Bug #29104)
</para>
</listitem>
<listitem>
<para>
- <literal>NDB Cluster</literal>: When restarting a data node,
- queries could hang during that node's start phase 5, and only
- continue once the node entered phase 6. (Bug #29364)
+ Replication of partitioned tables using the
+ <literal>InnoDB</literal> storage engine failed with
+ <literal>binlog-format=ROW</literal> or
+ <literal>binlog-format=MIXED</literal>. (Bug #28430)
</para>
</listitem>
<listitem>
<para>
- <literal>NDB Cluster</literal>: When a node failed to respond
- to a <literal>COPY_GCI</literal> signal as part of a global
- checkpoint, the master node was killed instead instead of the
- node that actually failed. (Bug #29331)
+ <literal>SHOW TRIGGERS</literal> did not handle non-Latin
+ symbols in column names correctly;
+ <command>mysqldump</command> also did not work properly with
+ such triggers. Both of these issues were also related to
+ improper handling of non-Latin characters sets in
+ <literal>INFORMATION_SCHEMA</literal> tables. (Bug #19443)
</para>
</listitem>
<listitem>
<para>
- <literal>NDB Cluster</literal>: An invalid comparison made
- during <literal>REDO</literal> validation that could lead to
- an <errortext>Error while reading REDO log</errortext>
- condition. (Bug #29118)
+ If a storage engine has its own logging capability, then any
+ statement using both this engine and some other engine not
+ having its own logging could not be correctly logged, due to
+ the fact that entries from one engine could be logged before
+ entries from the other engine were. This did not generate any
+ error messages when it occurred.
</para>
+
+ <para>
+ Now, if multiple storage engines are used in a statement and
+ at least one of them has its own logging capability, then an
+ error message is generated and the statement is not executed.
+ (Bug #28722)
+ </para>
+
+ <note>
+ <para>
+ Currently, the only storage engine to have its own logging
+ capability is <literal>NDBCLUSTER</literal>.
+ </para>
+ </note>
</listitem>
<listitem>
<para>
- <literal>NDB Cluster</literal>: The wrong data pages were
- sometimes invalidated following a global checkpoint. (Bug
- #29067)
+ Using the <literal>READ COMMITTED</literal> transaction
+ isolation level caused mixed and statement-based replication
+ to fail. (Bug #23051)
</para>
</listitem>
<listitem>
<para>
- <literal>NDB Cluster</literal>: If at least 2 files were
- involved in <literal>REDO</literal> invalidation, then file 0
- of page 0 was not updated and so pointed to an invalid part of
- the redo log. (Bug #29057)
+ The server returned data from <literal>SHOW CREATE
+ TABLE</literal> statement or a <literal>SELECT</literal>
+ statement on an INFORMATION_SCHEMA table using the
+ <literal>binary</literal> character set. (Bug #10491)
</para>
</listitem>
@@ -803,6 +820,22 @@
<listitem>
<para>
+ The <literal>binlog_format</literal> system variable value was
+ empty if the server was started with binary logging disabled.
+ Now it is set to <literal>MIXED</literal>. (Bug #28752)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Conversion of U+00A5 YEN SIGN and U+203E OVERLINE from
+ <literal>ucs2</literal> to <literal>ujis</literal> produced
+ incorrect results. (Bug #28600)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
Some valid identifiers were not parsed correctly. (Bug #28127)
</para>
</listitem>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r7029 - in trunk: . refman-5.0 refman-5.1 | paul | 6 Jul |
