svn commit - mysqldoc@docsrva: r2860 - in trunk: . refman-common

[paul]

Author: paul
Date: 2006-07-28 06:57:36 +0200 (Fri, 28 Jul 2006)
New Revision: 2860

Log:
 r9268@kite-hub:  paul | 2006-07-27 23:46:30 -0500
 Document bugfixes:
 Bug#18014
 Bug#19630
 Bug#20783
 Bug#20850
 Bug#21188
 Bug#21206


Modified:
   trunk/refman-common/news-4.1.xml
   trunk/refman-common/news-5.0.xml
   trunk/refman-common/news-5.1.xml

Property changes on: trunk
___________________________________________________________________
Name: svk:merge
   - 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:12204
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:12816
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:8441
   + 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:12204
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:12816
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:9268


Modified: trunk/refman-common/news-4.1.xml
===================================================================
--- trunk/refman-common/news-4.1.xml	2006-07-28 01:47:37 UTC (rev 2859)
+++ trunk/refman-common/news-4.1.xml	2006-07-28 04:57:36 UTC (rev 2860)
Changed blocks: 1, Lines Added: 9, Lines Deleted: 0; 774 bytes

@@ -190,6 +190,15 @@
 
       <listitem>
         <para>
+          Under heavy load (executing more than 1024 simultaneous
+          complex queries), a problem in the code that handles internal
+          temporary tables could lead to writing beyond allocated space
+          and memory corruption. (Bug #21206)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           Multiple invocations of the <literal>REVERSE()</literal>
           function could return different results. (Bug #18243)
         </para>


Modified: trunk/refman-common/news-5.0.xml
===================================================================
--- trunk/refman-common/news-5.0.xml	2006-07-28 01:47:37 UTC (rev 2859)
+++ trunk/refman-common/news-5.0.xml	2006-07-28 04:57:36 UTC (rev 2860)
Changed blocks: 1, Lines Added: 19, Lines Deleted: 0; 1138 bytes

@@ -670,6 +670,25 @@
 
       <listitem>
         <para>
+          Under heavy load (executing more than 1024 simultaneous
+          complex queries), a problem in the code that handles internal
+          temporary tables could lead to writing beyond allocated space
+          and memory corruption. Use of more than 1024 simultaneous
+          cursors server wide also could lead to memory corruption.
+          (This applies both to stored procedure and C API cursors.)
+          (Bug #21206)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          A race condition during slave server shutdown caused an assert
+          failure. (Bug #20850)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           <command>mysqldump</command> produced a malformed dump file
           when dumping multiple databases that contained views. (Bug
           #20221)


Modified: trunk/refman-common/news-5.1.xml
===================================================================
--- trunk/refman-common/news-5.1.xml	2006-07-28 01:47:37 UTC (rev 2859)
+++ trunk/refman-common/news-5.1.xml	2006-07-28 04:57:36 UTC (rev 2860)
Changed blocks: 3, Lines Added: 47, Lines Deleted: 10; 3241 bytes

@@ -316,7 +316,7 @@
 <programlisting>
 REPAIR TABLE <replaceable>tbl_name</replaceable> QUICK;
 </programlisting>
-        
+
         <para>
           The same trigger error message was produced under two
           conditions: The trigger duplicated an existing trigger name,

@@ -325,18 +325,54 @@
           conditions so as to be more informative. (Bug #10946)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
+          When run with the <option>--use-threads</option> option,
+          <command>mysqlimport</command> returned a random exit code.
+          (Bug #21188)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          The effect of a stored function or trigger that caused
+          <literal>AUTO_INCREMENT</literal> values to be generated for
+          multiple tables was not logged properly if statement-based
+          logging was used. Only the first table's value was logged,
+          causing replication to fail. Under mixed logging format, this
+          is dealt with by switching to row-based logging for the
+          function or trigger. For statement-based logging, this remains
+          a problem. (Bug #19630)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Changing the definition of a <literal>DECIMAL</literal> column
+          with <literal>ALTER TABLE</literal> caused loss of column
+          values. (Bug #18014)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          A race condition during slave server shutdown caused an assert
+          failure. (Bug #20850)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           Partitions were represented internally as the wrong data type,
-          which led in some cases to failures of queries such as <literal>SELECT
-          COUNT(*) FROM INFORMATION_SCHEMA.PARTITIONS WHERE
-          PARTITION_NAME =
-            '<replaceable>partition_name</replaceable>'</literal>. (Bug
+          which led in some cases to failures of queries such as
+          <literal>SELECT COUNT(*) FROM INFORMATION_SCHEMA.PARTITIONS
+          WHERE PARTITION_NAME =
+          '<replaceable>partition_name</replaceable>'</literal>. (Bug
           #20340)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           Searches against a <literal>ZEROFILL</literal> column of a

@@ -1481,9 +1517,10 @@
       <listitem>
         <para>
           For <command>mysqld</command>, Valgrind revealed problems that
-          were corrected: Memory corruption in replication slaves when
-          switching databases (Bug #19022); syscall write parameter
-          pointing to uninitialized byte (Bug #20579).
+          were corrected: Possible uninitialized data in a string
+          comparison (Bug #20783); memory corruption in replication
+          slaves when switching databases (Bug #19022); syscall write
+          parameter pointing to uninitialized byte (Bug #20579).
         </para>
       </listitem>