svn commit - mysqldoc@docsrva: r23109 - trunk/dynamic-docs/changelog

[jon.stephens]

Author: jstephens
Date: 2010-10-13 09:44:13 +0200 (Wed, 13 Oct 2010)
New Revision: 23109

Log:




Changelog entries for Replication bugfixes:

  BUG#54144, BUG#55375






Modified:
   trunk/dynamic-docs/changelog/mysqld-2.xml


Modified: trunk/dynamic-docs/changelog/mysqld-2.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld-2.xml	2010-10-12 19:49:39 UTC (rev 23108)
+++ trunk/dynamic-docs/changelog/mysqld-2.xml	2010-10-13 07:44:13 UTC (rev 23109)
Changed blocks: 1, Lines Added: 119, Lines Deleted: 0; 3369 bytes

@@ -9,6 +9,125 @@
   <logentry entrytype="bug">
 
     <tags>
+      <highlight type="replication"/>
+      <manual type="max_binlog_cache_size"/>
+      <manual type="ER_TRANS_CACHE_FULL"/>
+      <manual type="transactions"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="55375"/>
+    </bugs>
+
+    <versions>
+      <version ver="5.5.7"/>
+    </versions>
+
+    <message>
+
+      <para>
+        When slave tried to execute a transaction larger than the
+        slave&apos;s value for
+        <literal role="sysvar">max_binlog_cache_size</literal>, it
+        crashed. This was caused by an assertion that the server should
+        roll back only the statement but not the entire transaction when
+        the error <errorname>ER_TRANS_CACHE_FULL</errorname> occurred.
+        However, the slave SQL thread always rolled back the entire
+        transaction whenever any error occurred, regardless of the type
+        of error.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <highlight type="replication"/>
+      <manual type="error messages"/>
+      <manual type="ER_SLAVE_HEARTBEAT_VALUE_OUT_OF_RANGE"/>
+      <manual type="internationalization"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="54144"/>
+    </bugs>
+
+    <versions>
+      <version ver="5.5.7"/>
+    </versions>
+
+    <message>
+
+      <para>
+        The error message for
+        <errorname>ER_SLAVE_HEARTBEAT_VALUE_OUT_OF_RANGE</errorname> was
+        hard coded in English in <filename>sql_yacc.yy</filename>, so
+        that it could not be translated in
+        <filename>errmsg.txt</filename> for other languages.
+      </para>
+
+      <para>
+        Additionally, this same error message was used for three
+        separate error conditions:
+      </para>
+
+      <orderedlist>
+
+        <listitem>
+          <para>
+            When the heartbeat period exceeded the value of
+            slave_net_timeout.
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            When the heartbeat period was nonnegative but shorter than 1
+            millisecond.
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            When the value for the heartbeat period was either negative
+            or greater than the maximum allowed.
+          </para>
+        </listitem>
+
+      </orderedlist>
+
+      <para>
+        These issues have been addressed as follows:
+      </para>
+
+      <itemizedlist>
+
+        <listitem>
+          <para>
+            By using three distinct error messages for each of the
+            conditions listed previously.
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            By moving the sources for these error messages into the
+            <filename>errmsg-utf8.txt</filename> file to facilitate
+            translations into languages other than English.
+          </para>
+        </listitem>
+
+      </itemizedlist>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
       <highlight type="cluster"/>
       <manual type="MAX_ROWS"/>
       <manual type="CREATE TABLE"/>