svn commit - mysqldoc@docsrva: r8196 - trunk/dynamic-docs/open-bugs

[mcbrown]

Author: mcbrown
Date: 2007-10-19 17:21:36 +0200 (Fri, 19 Oct 2007)
New Revision: 8196

Log:
Automatic update from openbugs

Modified:
   trunk/dynamic-docs/open-bugs/mysqld.xml


Modified: trunk/dynamic-docs/open-bugs/mysqld.xml
===================================================================
--- trunk/dynamic-docs/open-bugs/mysqld.xml	2007-10-19 15:11:56 UTC (rev 8195)
+++ trunk/dynamic-docs/open-bugs/mysqld.xml	2007-10-19 15:21:36 UTC (rev 8196)
Changed blocks: 5, Lines Added: 47, Lines Deleted: 2; 2940 bytes

@@ -622,13 +622,21 @@
     <message>
 
       <para>
-        %BUGID%: Specifying a qcache of 5GB let the server crash.
+        %BUGID%: Specifying a query cache of 5GB causes the server to
+        crash
       </para>
 
       <itemizedlist>
 
         <listitem>
           <para>
+            This problem is known to occur only on 64-bit Windows
+            pltforms. The workaround is to increase the size of the
+            Windows page file, or to decrease the amount of physical
+            memory on the machine.
+          </para>
+
+          <para>
             <emphasis role="bold">Target fix</emphasis>: 6.0
           </para>
         </listitem>

@@ -1634,7 +1642,7 @@
         <listitem>
           <para>
             RENAME DATABASE was intended only for updating names of
-            pre-5.1 databases to the new 5.1 identifier encoding. It is
+            pre-5.1 databases to the new 5.1 identifier encoding. It's
             being removed and replaced with ALTER TABLE db_name UPGRADE
             DATA DIRECTORY NAME.
           </para>

@@ -2293,6 +2301,22 @@
         %BUGID%: <literal>UPDATE</literal>, changed rows incorrect
       </para>
 
+      <itemizedlist>
+
+        <listitem>
+          <para>
+            When updating rows within an InnoDB, the 'rows changed'
+            information returned during an UPDATE statement only shows
+            the number of rows where the data was updated. If the update
+            value and the existing value are the same, then the rows
+            changed counter is not updated. One workaround is to
+            explicitly only change records that do not match the new
+            data.
+          </para>
+        </listitem>
+
+      </itemizedlist>
+
     </message>
 
   </logentry>

@@ -4200,6 +4224,20 @@
         leaves slave unstable
       </para>
 
+      <itemizedlist>
+
+        <listitem>
+          <para>
+            This issue is encountered if using transactions with MyISAM
+            and replicating to an InnoDB or NDB slave: the slave becomes
+            unstable. This is due to the commit not being recorded in
+            the binlog, so that the transactions are not completed on
+            the slave.
+          </para>
+        </listitem>
+
+      </itemizedlist>
+
     </message>
 
   </logentry>

@@ -4236,6 +4274,13 @@
 
         <listitem>
           <para>
+            When FLUSH TABLES is executed, there is a brief moment when
+            the value of Seconds_Behind_Master is calculated
+            incorrectly. This can cause false alerts for monitoring
+            services.
+          </para>
+
+          <para>
             <emphasis role="bold">Target fix</emphasis>: 5.1.23
           </para>
         </listitem>