Author: paul
Date: 2006-10-04 22:52:52 +0200 (Wed, 04 Oct 2006)
New Revision: 3545
Log:
r10128@frost: paul | 2006-10-04 15:50:58 -0500
Document bugfixes:
Bug#14807
Bug#18888
Bug#21459
Bug#21638
Bug#22326
Bug#22384
Bug#22393
Modified:
trunk/refman-4.1/news-4.0.xml
trunk/refman-4.1/news-4.1.xml
trunk/refman-5.0/news-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:14161
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:10126
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:10466
+ 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:14161
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:10128
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:10466
Modified: trunk/refman-4.1/news-4.0.xml
===================================================================
--- trunk/refman-4.1/news-4.0.xml 2006-10-04 19:36:17 UTC (rev 3544)
+++ trunk/refman-4.1/news-4.0.xml 2006-10-04 20:52:52 UTC (rev 3545)
Changed blocks: 1, Lines Added: 7, Lines Deleted: 0; 678 bytes
@@ -173,6 +173,13 @@
<listitem>
<para>
+ Deleting from a large index could cause index corruption when
+ it needed to shrink. (Bug #22384)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
<command>mysqlhotcopy</command> did not copy
<literal>RAID</literal> directories with names that contained
non-decimal hex digits. (It copied only directories containing
Modified: trunk/refman-4.1/news-4.1.xml
===================================================================
--- trunk/refman-4.1/news-4.1.xml 2006-10-04 19:36:17 UTC (rev 3544)
+++ trunk/refman-4.1/news-4.1.xml 2006-10-04 20:52:52 UTC (rev 3545)
Changed blocks: 1, Lines Added: 16, Lines Deleted: 0; 1010 bytes
@@ -209,6 +209,22 @@
<listitem>
<para>
+ Deleting from a large index could cause index corruption when
+ it needed to shrink. (Bug #22384)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The build process incorrectly tried to overwrite
+ <filename>sql/lex_hash.h</filename>. This caused the build to
+ fail when using a shadow link tree pointing to original
+ sources that were owned by another account. (Bug #18888)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
Execution of a prepared statement that uses an
<literal>IN</literal> subquery with aggregate functions in the
<literal>HAVING</literal> clause could cause a server crash.
Modified: trunk/refman-5.0/news-5.0.xml
===================================================================
--- trunk/refman-5.0/news-5.0.xml 2006-10-04 19:36:17 UTC (rev 3544)
+++ trunk/refman-5.0/news-5.0.xml 2006-10-04 20:52:52 UTC (rev 3545)
Changed blocks: 2, Lines Added: 54, Lines Deleted: 0; 2606 bytes
@@ -306,6 +306,51 @@
<listitem>
<para>
+ Deleting from a large index could cause index corruption when
+ it needed to shrink. (Bug #22384)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The build process incorrectly tried to overwrite
+ <filename>sql/lex_hash.h</filename>. This caused the build to
+ fail when using a shadow link tree pointing to original
+ sources that were owned by another account. (Bug #18888)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <command>mysql_ftdump</command> produced bad counts for common
+ words. (Bug #22326)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ yaSSL had a conflicting definition for
+ <literal>socklen_t</literal> on hurd-i386 systems. (Bug
+ #22326)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ When records are merged from the insert buffer and the page
+ needs to be reorganized, <literal>InnoDB</literal> used
+ incorrect column length information when interpreting the
+ records of the page. This caused a server crash due to
+ apparent corruption of secondary indexes in
+ <literal>ROW_FORMAT=COMPACT</literal> that contain prefix
+ indexes of fixed-length columns. Data files should not be
+ corrupted, but the crash was likely to repeat every time the
+ server was restarted. (Bug #21638)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
Using <literal>GROUP_CONCAT()</literal> on the result of a
subquery in the <literal>FROM</literal> clause that itself
used <literal>GROUP_CONCAT()</literal> could cause a server
@@ -808,6 +853,15 @@
<listitem>
<para>
+ <literal>CREATE TABLE ... SELECT</literal> statements that
+ selected <literal>GEOMETRY</literal> values resulted in a
+ table that contained <literal>BLOB</literal> columns, not
+ <literal>GEOMETRY</literal> columns. (Bug #14807)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
A <literal>DATE</literal> can be represented as an integer
(such as <literal>20060101</literal>) or as a string (such as
<literal>'2006.01.01'</literal>). When a
Modified: trunk/refman-5.1/news-5.1.xml
===================================================================
--- trunk/refman-5.1/news-5.1.xml 2006-10-04 19:36:17 UTC (rev 3544)
+++ trunk/refman-5.1/news-5.1.xml 2006-10-04 20:52:52 UTC (rev 3545)
Changed blocks: 1, Lines Added: 44, Lines Deleted: 0; 2011 bytes
@@ -788,6 +788,50 @@
<listitem>
<para>
+ Deleting from a large index could cause index corruption when
+ it needed to shrink. (Bug #22384)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The build process incorrectly tried to overwrite
+ <filename>sql/lex_hash.h</filename>. This caused the build to
+ fail when using a shadow link tree pointing to original
+ sources that were owned by another account. (Bug #18888)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <command>mysql_ftdump</command> produced bad counts for common
+ words. (Bug #22326)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The optimizer could make an incorrect index choice for indexes
+ with a skewed key distribution. (Bug #22393)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ When records are merged from the insert buffer and the page
+ needs to be reorganized, <literal>InnoDB</literal> used
+ incorrect column length information when interpreting the
+ records of the page. This caused a server crash due to
+ apparent corruption of secondary indexes in
+ <literal>ROW_FORMAT=COMPACT</literal> that contain prefix
+ indexes of fixed-length columns. Data files should not be
+ corrupted, but the crash was likely to repeat every time the
+ server was restarted. (Bug #21638)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
Instance Manager didn't close the client socket file when
starting a new <command>mysqld</command> instance.
<command>mysqld</command> inherited the socket, causing
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r3545 - in trunk: . refman-4.1 refman-5.0 refman-5.1 | paul | 4 Oct |
