Author: jstephens
Date: 2009-09-09 11:56:50 +0200 (Wed, 09 Sep 2009)
New Revision: 16522
Log:
Documented Replication bugfixes:
Bug #45694, Bug #46130, Bug #46864
Modified:
trunk/dynamic-docs/changelog/mysqld-1.xml
Modified: trunk/dynamic-docs/changelog/mysqld-1.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld-1.xml 2009-09-09 09:34:38 UTC (rev 16521)
+++ trunk/dynamic-docs/changelog/mysqld-1.xml 2009-09-09 09:56:50 UTC (rev 16522)
Changed blocks: 1, Lines Added: 102, Lines Deleted: 0; 3000 bytes
@@ -10,6 +10,108 @@
<tags>
<highlight type="replication"/>
+ <manual type="transactions"/>
+ <manual type="triggers"/>
+ </tags>
+
+ <bugs>
+ <fixes bugid="46864"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.1.39"/>
+ </versions>
+
+ <message>
+
+ <para>
+ Performing a multi-row update of the
+ <literal>AUTO_INCREMENT</literal> column of a transactional
+ table could result in an inconsistency between master and slave
+ when there was a trigger on the transactional table that updated
+ a non-transactional table. When such an update failed on the
+ master, no rows were updated on the master, but some rows could
+ (erroneously) be updated on the slave.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <tags>
+ <highlight type="replication"/>
+ <manual type="transactions"/>
+ <manual type="rollbacks"/>
+ </tags>
+
+ <bugs>
+ <fixes bugid="46130"/>
+ <seealsobug bugid="33864"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.1.39"/>
+ </versions>
+
+ <message>
+
+ <para>
+ When a statement that changed both transactional and
+ non-transactional tables failed, the transactional changes were
+ automatically rolled back on the master but the slave ignored
+ the error and did not roll them back, thus leading to
+ inconsistencies between master and slave.
+ </para>
+
+ <para>
+ This issue is fixed by automatically rolling back a statement
+ that fails on the slave; however, the transaction is not rolled
+ back unless a corresponding
+ <literal role="stmt">ROLLBACK</literal> statement is found in
+ the relay log file.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <tags>
+ <highlight type="replication"/>
+ <manual type="slave_transaction_retries"/>
+ </tags>
+
+ <bugs>
+ <fixes bugid="45674"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.1.39"/>
+ </versions>
+
+ <message>
+
+ <para>
+ When <literal role="sysvar">slave_transaction_retries</literal>
+ is set, a statement that replicates, but is then rolled back due
+ to a deadlock on the slave, should be retried. However, in
+ certain cases, replication was stopped with error 1213
+ (<errortext>Deadlock found when trying to get lock; try
+ restarting transaction</errortext>) instead, even when this
+ variable was set.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <tags>
+ <highlight type="replication"/>
<manual type="character sets"/>
<manual type="LOAD DATA INFILE"/>
</tags>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r16522 - trunk/dynamic-docs/changelog | jon.stephens | 9 Sep |
