List:Commits« Previous MessageNext Message »
From:stefan Date:March 27 2006 1:33pm
Subject:svn commit - mysqldoc@docsrva: r1683 - trunk/refman-5.1
View as plain text  
Author: shinz
Date: 2006-03-27 15:33:47 +0200 (Mon, 27 Mar 2006)
New Revision: 1683

Log:
Add dynamic slave logging format (closing WL#3171), changelog needs to be written still

Modified:
   trunk/refman-5.1/replication.xml

Modified: trunk/refman-5.1/replication.xml
===================================================================
--- trunk/refman-5.1/replication.xml	2006-03-27 13:15:07 UTC (rev 1682)
+++ trunk/refman-5.1/replication.xml	2006-03-27 13:33:47 UTC (rev 1683)
@@ -341,6 +341,21 @@
 </programlisting>
 
     <para>
+      In addition to switching the logging format manually, a slave
+      server may switch the format <emphasis>automatically</emphasis>.
+      This happens when the server is running in either
+      <literal>STATEMENT</literal> or <literal>MIXED</literal> format
+      and encounters a row in the binary log that is written in
+      <literal>ROW</literal> logging format. In that case, the slave
+      switches to row-based replication temporarily for that event, and
+      switches back to the previous format afterwards. (It does that by
+      setting its <option>binlog_format</option> option to
+      <literal>ROW</literal>; so if the row event lasts long enough, you
+      may be able to see the switched format when issuing <literal>SHOW
+      VARIABLES LIKE 'binlog_format'</literal>.)
+    </para>
+
+    <para>
       There are two reasons why you might want to set replication
       logging on a per-connection basis:
     </para>

Thread
svn commit - mysqldoc@docsrva: r1683 - trunk/refman-5.1stefan27 Mar