Author: paul
Date: 2007-08-25 18:30:20 +0200 (Sat, 25 Aug 2007)
New Revision: 7555
Log:
r24294@frost: paul | 2007-08-25 11:27:15 -0500
Documented bugfixes:
Bug#20090: InnoDB: Error: trying to declare trx to enter InnoDB
Bug#21281: Pending write lock is incorrectly removed when its statement being
KILLed
Bug#23710: crash_commit_before fails if innodb_file_per_table=1
Bug#27501: 5.0 significantly more sys ("kernel") time than 4.1 due to
getrusage() calls
Bug#27562: ascii.xml invalid?
Bug#28875: A conversion between ASCII and LATIN1 charsets does not function
Bug#29097: fsp_get_available_space_in_free_extents() is capped at 4TB
Bug#29155: Innodb "Parallel recovery" is not prevented
Bug#29306: Truncated data in MS Access with decimal (3,1) columns in a VIEW
Bug#29536: timestamp inconsistent in replication around 1970
Bug#30201: crash with query cache when killing a select
Bug#30219: GROUP BY with DISTINCT broken with BIT type in MyISAM in many cases
Bug#30287: tmpdir not respected on GROUP BY
Bug#30396: memory overrun during EXPLAIN EXTENDED
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:29492
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:24195
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:19696
+ 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:29492
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:24294
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:19696
Modified: trunk/refman-5.0/releasenotes-cs-5.0.xml
===================================================================
--- trunk/refman-5.0/releasenotes-cs-5.0.xml 2007-08-25 15:40:43 UTC (rev 7554)
+++ trunk/refman-5.0/releasenotes-cs-5.0.xml 2007-08-25 16:30:20 UTC (rev 7555)
Changed blocks: 1, Lines Added: 15, Lines Deleted: 0; 612 bytes
@@ -1918,6 +1918,21 @@
<!-- From 5.0.38 (end) -->
+ <para>
+ Bugs fixed:
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ Profiling overhead was incurred even with profiling disabled.
+ (Bug #27501)
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
<!-- From 5.0.40 (begin) -->
<para>
Modified: trunk/refman-5.0/releasenotes-es-5.0.xml
===================================================================
--- trunk/refman-5.0/releasenotes-es-5.0.xml 2007-08-25 15:40:43 UTC (rev 7554)
+++ trunk/refman-5.0/releasenotes-es-5.0.xml 2007-08-25 16:30:20 UTC (rev 7555)
Changed blocks: 4, Lines Added: 118, Lines Deleted: 30; 6009 bytes
@@ -83,6 +83,97 @@
<listitem>
<para>
+ <literal>NDB Cluster</literal>: The server would not compile
+ with <literal>NDB</literal> support on AIX 5.2. (Bug #10776)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal>: The output from
+ <command>ndb_config</command>
+ <option>--config-file=<replaceable>file</replaceable></option>
+ was sent to <literal>stdout</literal> rather than
+ <literal>stderr</literal>. (Bug #25941)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Some character mappings in the <filename>ascii.xml</filename>
+ file were incorrect. (Bug #27562)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>GROUP BY</literal> on <literal>BIT</literal> columns
+ produced incorrect results. (Bug #30219)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The <literal>mysql_list_fields()</literal> C API function
+ incorrectly set <literal>MYSQL_FIELD::decimals</literal> for
+ some view columns. (Bug #29306)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Read lock requests that were blocked by a pending write lock
+ request were not allowed to proceed if the statement
+ requesting the write lock was killed. (Bug #21281)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>InnoDB</literal> produced an unnecessary (and
+ harmless) warning: <literal>InnoDB: Error: trying to declare
+ trx to enter InnoDB, but InnoDB: it already is
+ declared</literal>. (Bug #20090)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Memory corruption occurred for some queries with a top-level
+ <literal>OR</literal> operation in the
+ <literal>WHERE</literal> condition if they contained equality
+ predicates and other sargable predicates in disjunctive parts
+ of the condition. (Bug #30396)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The server created temporary tables for filesort operations in
+ the working directory, not in the directory specified by the
+ <literal>tmpdir</literal> system variable. (Bug #30287)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Using <literal>KILL QUERY</literal> or <literal>KILL
+ CONNECTION</literal> to kill a <literal>SELECT</literal>
+ statement caused a server crash if the query cache was
+ enabled. (Bug #30201)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Operations that used the time zone replicated the time zone
+ only for successful operations, but did not replicate the time
+ zone for errors that need to know it. (Bug #29536)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
If one thread was performing concurrent inserts, other threads
reading from the same table using equality key searches could
see the index values for new rows before the data values had
@@ -125,23 +216,6 @@
<listitem>
<para>
- <literal>NDB Cluster</literal>: The server would not compile
- with <literal>NDB</literal> support on AIX 5.2. (Bug #10776)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <literal>NDB Cluster</literal>: The output from
- <command>ndb_config</command>
- <option>--config-file=<replaceable>file</replaceable></option>
- was sent to <literal>stdout</literal> rather than
- <literal>stderr</literal>. (Bug #25941)
- </para>
- </listitem>
-
- <listitem>
- <para>
On Windows, client libraries lacked symbols required for
linking. (Bug #30118)
</para>
@@ -156,19 +230,6 @@
expression attribute (see
<xref linkend="charset-repertoire"/>). (Bug #28875)
</para>
-
- <para>
- This patch results in an outstanding problem that remains to
- be fixed, illustrated by the following example that results in
- an <errortext>illegal mix of collations</errortext> error:
- </para>
-
-<programlisting>
-CREATE TABLE t1 (a CHAR(1) CHARACTER SET latin1);
-INSERT INTO t1 VALUES ('a');
-SET NAMES ascii;
-SELECT * FROM t1 WHERE a='a';
-</programlisting>
</listitem>
<listitem>
@@ -276,6 +337,33 @@
<listitem>
<para>
+ If MySQL/<literal>InnoDB</literal> crashed very quickly after
+ starting up, it would not force a checkpoint. In this case,
+ <literal>InnoDB</literal> would skip crash recovery at next
+ startup, and the database would become corrupt. Fix: If the
+ redo log scan at <literal>InnoDB</literal> startup goes past
+ the last checkpoint, force crash recovery. (Bug #23710)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ A maximum of 4TB <literal>InnoDB</literal> free space was
+ reported by <literal>SHOW TABLE STATUS,</literal> which is
+ incorrect on systems with more than 4TB space. (Bug #29097)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>InnoDB</literal> refused to start on some versions of
+ FreeBSD with LinuxThreads. This is fixed by enabling file
+ locking on FreeBSD. (Bug #29155)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
Certain statements with unions, subqueries, and joins could
result in huge memory consumption. (Bug #29582)
</para>
Modified: trunk/refman-5.1/news-5.1.xml
===================================================================
--- trunk/refman-5.1/news-5.1.xml 2007-08-25 15:40:43 UTC (rev 7554)
+++ trunk/refman-5.1/news-5.1.xml 2007-08-25 16:30:20 UTC (rev 7555)
Changed blocks: 5, Lines Added: 102, Lines Deleted: 29; 5643 bytes
@@ -83,6 +83,90 @@
<listitem>
<para>
+ <literal>NDB Cluster</literal>: Backups of
+ <literal>TIMESTAMP</literal> columns made with
+ <command>ndb_restore</command> on a MySQL Cluster using data
+ nodes hosts of one endian could not be used to restore the
+ cluster's data to data node hosts of the other endian.
+ (Bug #30134)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal> (Replication): Multi-master
+ replication setups did not handle
+ <option>--log-slave-updates</option> correctly. (Bug #30017)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Some character mappings in the <filename>ascii.xml</filename>
+ file were incorrect. (Bug #27562)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>GROUP BY</literal> on <literal>BIT</literal> columns
+ produced incorrect results. (Bug #30219)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The <literal>mysql_list_fields()</literal> C API function
+ incorrectly set <literal>MYSQL_FIELD::decimals</literal> for
+ some view columns. (Bug #29306)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Read lock requests that were blocked by a pending write lock
+ request were not allowed to proceed if the statement
+ requesting the write lock was killed. (Bug #21281)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Memory corruption occurred for some queries with a top-level
+ <literal>OR</literal> operation in the
+ <literal>WHERE</literal> condition if they contained equality
+ predicates and other sargable predicates in disjunctive parts
+ of the condition. (Bug #30396)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The server created temporary tables for filesort operations in
+ the working directory, not in the directory specified by the
+ <literal>tmpdir</literal> system variable. (Bug #30287)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Using <literal>KILL QUERY</literal> or <literal>KILL
+ CONNECTION</literal> to kill a <literal>SELECT</literal>
+ statement caused a server crash if the query cache was
+ enabled. (Bug #30201)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Operations that used the time zone replicated the time zone
+ only for successful operations, but did not replicate the time
+ zone for errors that need to know it. (Bug #29536)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
<command>mysqldump</command> from the MySQL 5.1.21
distribution could not be used to create a dump from a MySQL
5.1.20 or older server. (Bug #30123)
@@ -109,25 +193,6 @@
</para>
</listitem>
- <listitem>
- <para>
- <literal>NDB Cluster</literal>: Backups of
- <literal>TIMESTAMP</literal> columns made with
- <command>ndb_restore</command> on a MySQL Cluster using data
- nodes hosts of one endian could not be used to restore the
- cluster's data to data node hosts of the other endian.
- (Bug #30134)
- </para>
- </listitem>
-
- <listitem>
- <para>
- <literal>NDB Cluster</literal> (Replication): Multi-master
- replication setups did not handle
- <option>--log-slave-updates</option> correctly. (Bug #30017)
- </para>
- </listitem>
-
</itemizedlist>
</section>
@@ -780,6 +845,22 @@
<listitem>
<para>
+ A maximum of 4TB <literal>InnoDB</literal> free space was
+ reported by <literal>SHOW TABLE STATUS,</literal> which is
+ incorrect on systems with more than 4TB space. (Bug #29097)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>InnoDB</literal> refused to start on some versions of
+ FreeBSD with LinuxThreads. This is fixed by enabling file
+ locking on FreeBSD. (Bug #29155)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
Certain statements with unions, subqueries, and joins could
result in huge memory consumption. (Bug #29582)
</para>
@@ -831,14 +912,6 @@
<listitem>
<para>
- A maximum of 4TB <literal>InnoDB</literal> free space was
- reported by <literal>SHOW TABLE STATUS,</literal> which is
- incorrect on systems with more than 4TB space. (Bug #29097)
- </para>
- </listitem>
-
- <listitem>
- <para>
On Windows, the server used 10MB of memory for each connection
thread, resulting in memory exhaustion. Now each thread uses
1MB. (Bug #20815)
@@ -1285,9 +1358,9 @@
<listitem>
<para>
<literal>InnoDB</literal> produced an unnecessary (and
- harmless) warning: <errortext>InnoDB: Error: trying to declare
+ harmless) warning: <literal>InnoDB: Error: trying to declare
trx to enter InnoDB, but InnoDB: it already is
- declared</errortext>. (Bug #20090)
+ declared</literal>. (Bug #20090)
</para>
</listitem>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r7555 - in trunk: . refman-5.0 refman-5.1 | paul | 25 Aug |
