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

[jon]

Author: jstephens
Date: 2008-02-06 23:20:45 +0100 (Wed, 06 Feb 2008)
New Revision: 9724

Log:

Documented replication bugfixes:

  Bug #26395, Bug #32407, Bug #33862, Bug #33413



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


Modified: trunk/dynamic-docs/changelog/mysqld-1.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld-1.xml	2008-02-06 20:56:45 UTC (rev 9723)
+++ trunk/dynamic-docs/changelog/mysqld-1.xml	2008-02-06 22:20:45 UTC (rev 9724)
Changed blocks: 1, Lines Added: 96, Lines Deleted: 0; 2572 bytes

@@ -10,6 +10,102 @@
 
     <tags>
       <highlight type="replication"/>
+      <manual type="DROP USER"/>
+      <manual type="CREATE USER"/>
+      <manual type="binlog"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="33862"/>
+      <seealsobug bugid="29749"/>
+    </bugs>
+
+    <versions>
+      <version ver="5.0.56"/>
+      <version ver="5.1.24"/>
+      <version ver="6.0.5"/>
+    </versions>
+
+    <message>
+
+      <para>
+        A <literal>DROP USER</literal> statement that failed on the
+        master were written to the binlog, as was a duplicate
+        <literal>CREATE USER</literal> statement; either of these
+        occurrences could cause the slave to fail.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <highlight type="replication"/>
+      <manual type="--base64-output"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="32407"/>
+    </bugs>
+
+    <versions>
+      <version ver="5.1.24"/>
+      <version ver="6.0.5"/>
+    </versions>
+
+    <message>
+
+      <para>
+        The <option>--base64-output</option> option for
+        <command>mysqlbinlog</command> was not honored for all types of
+        events. This interfered in some cases with performing
+        point-in-time recovery.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <highlight type="replication"/>
+      <highlight type="importantchange"/>
+      <manual type="AUTOCOMMIT"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="26395"/>
+    </bugs>
+
+    <versions>
+      <version ver="5.0.56"/>
+      <version ver="5.1.24"/>
+      <version ver="6.0.5"/>
+    </versions>
+
+    <message>
+
+      <para>
+        When the master crashed during an update on a transactional
+        table while in <literal>AUTOCOMMIT</literal> mode, the slave
+        failed. This fix causes every transaction (including
+        <literal>AUTOCOMMIT</literal> transactions) to be recorded in
+        the binlog as starting with a <literal>BEGIN</literal> and
+        ending with a <literal>COMMIT</literal> or
+        <literal>ROLLBACK</literal>.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <highlight type="replication"/>
       <manual type="SHOW BINLOG EVENTS"/>
       <manual type="max_allowed_packet"/>
     </tags>