List:Commits« Previous MessageNext Message »
From:jon.stephens Date:February 23 2011 6:26pm
Subject:svn commit - mysqldoc@oter02: r25141 - in trunk: dynamic-docs/changelog dynamic-docs/command-optvars refman-5.6
View as plain text  
Author: js221926
Date: 2011-02-23 19:26:00 +0100 (Wed, 23 Feb 2011)
New Revision: 25141

Log:

WL#4033, WL#5404: Documented --binlog-rows-query-log-events



Modified:
   trunk/dynamic-docs/changelog/mysqld-2.xml
   trunk/dynamic-docs/command-optvars/mysqld.xml
   trunk/refman-5.6/replication-options-core.xml


Modified: trunk/dynamic-docs/changelog/mysqld-2.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld-2.xml	2011-02-23 12:03:55 UTC (rev 25140)
+++ trunk/dynamic-docs/changelog/mysqld-2.xml	2011-02-23 18:26:00 UTC (rev 25141)
Changed blocks: 1, Lines Added: 43, Lines Deleted: 0; 1841 bytes

@@ -9,6 +9,49 @@
   <logentry entrytype="feature">
 
     <tags>
+      <highlight type="replication"/>
+      <highlight type="importantchange"/>
+      <manual type="--binlog-rows-query-log-events"/>
+      <manual type="RBR"/>
+    </tags>
+
+    <bugs>
+      <fixes wlid="4033"/>
+      <fixes wlid="5404"/>
+      <fixes bugid=""/>
+    </bugs>
+
+    <versions>
+      <version ver="5.6.2"/>
+    </versions>
+
+    <message>
+
+      <para>
+        Added the
+        <option role="mysqld">--binlog-rows-query-log-events</option>
+        option for <command>mysqld</command>. Using this option causes a
+        server logging in row-based mode to write informational
+        <firstterm>rows query log</firstterm> events (SQL statements,
+        for debugging and other purposes) to the binary log. MySQL
+        server and MySQL programs from MySQL 5.6.2 and later normally
+        ignore such events, so that they do not pose an issue when
+        reading the binary log. <command>mysqld</command> and
+        <command>mysqlbinlog</command> from previous MySQL releases
+        cannot read such events in the binary log, and fail if they
+        attempt to do so. For this reason, you should never prepare logs
+        for a MySQL 5.6.1 or earlier replication slave server (or other
+        reader such as <command>mysqlbinlog</command>) with this option
+        enabled on the master.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="feature">
+
+    <tags>
       <highlight type="cluster"/>
       <manual type="backup"/>
       <manual type="ndb_restore"/>


Modified: trunk/dynamic-docs/command-optvars/mysqld.xml
===================================================================
--- trunk/dynamic-docs/command-optvars/mysqld.xml	2011-02-23 12:03:55 UTC (rev 25140)
+++ trunk/dynamic-docs/command-optvars/mysqld.xml	2011-02-23 18:26:00 UTC (rev 25141)
Changed blocks: 2, Lines Added: 55, Lines Deleted: 0; 2150 bytes

@@ -127,6 +127,33 @@
 
   </mysqloption>
 
+  <mysqloption section="binlog" id="binlog_rows_query_log_events">
+
+    <xrefto id="sysvar_binlog_rows_query_log_events"/>
+
+    <name>binlog_rows_query_log_events</name>
+
+    <shortdescription>
+      When TRUE, enables logging of rows query log events in row-based
+      logging mode. FALSE by default. Do not enable when producing logs
+      for pre-5.6.2 replication slaves or other readers.
+    </shortdescription>
+
+    <types>
+      <vartype isdynamic="yes" class="status" scope="both"/>
+    </types>
+
+    <values vartype="boolean" platform="all">
+      <value default="FALSE"/>
+    </values>
+
+    <versions>
+      <manual version="5.6"/>
+      <introduced version="5.6.2"/>
+    </versions>
+
+  </mysqloption>
+
   <mysqloption section="binlog" id="Binlog_stmt_cache_disk_use">
 
     <xrefto id="statvar_Binlog_stmt_cache_disk_use"/>

@@ -9023,6 +9050,34 @@
 
   </mysqloption>
 
+  <mysqloption section="binlog" id="binlog-rows-query-log-events">
+
+    <xrefto id="option_mysqld_binlog_rows_query_log_events"/>
+
+    <name>binlog-rows-query-log-events</name>
+
+    <shortdescription>
+      Enables logging of rows query log events when using row-based
+      logging. Disabled by default. Do not enable when producing logs
+      for pre-5.6.2 slaves/readers.
+    </shortdescription>
+
+    <types>
+      <optype class="cmdline" format="--binlog-rows-query-log-events" setvar="binlog_rows_query_log_events"/>
+      <optype class="mycnf"/>
+    </types>
+
+    <values vartype="boolean" platform="all">
+      <value default="FALSE"/>
+    </values>
+
+    <versions>
+      <manual version="5.6"/>
+      <introduced version="5.6.2"/>
+    </versions>
+
+  </mysqloption>
+
   <mysqloption id="binlog_direct_non_transactional_updates" section="binlog" subsection="replication">
 
     <xrefto id="sysvar_binlog_direct_non_transactional_updates"/>


Modified: trunk/refman-5.6/replication-options-core.xml
===================================================================
--- trunk/refman-5.6/replication-options-core.xml	2011-02-23 12:03:55 UTC (rev 25140)
+++ trunk/refman-5.6/replication-options-core.xml	2011-02-23 18:26:00 UTC (rev 25141)
Changed blocks: 2, Lines Added: 68, Lines Deleted: 0; 3343 bytes

@@ -3162,6 +3162,32 @@
         </para>
       </listitem>
 
+      <listitem>
+        <para id="option_mysqld_binlog-rows-query-log-events">
+          <indexterm>
+            <primary>mysqld</primary>
+            <secondary>binlog-rows-query-log-events option</secondary>
+          </indexterm>
+
+          <indexterm>
+            <primary>binlog-rows-query-log-events option</primary>
+            <secondary>mysqld</secondary>
+          </indexterm>
+
+          <option role="mysqld">--binlog-rows-query-log-events</option>
+        </para>
+
+        <para condition="dynamic:optvar:item" role="5.6:mysqld:binlog-rows-query-log-events"/>
+
+        <para>
+          Added in MySQL 5.6.2, this option enables
+          <literal role="sysvar">binlog_rows_query_log_events</literal>.
+          Must be set to <literal>OFF</literal> (the default) when
+          generating logs for a MySQL 5.6.1 or earlier slave server or
+          version of <command>mysqlbinlog</command>.
+        </para>
+      </listitem>
+
     </itemizedlist>
 
     <formalpara id="replication-sysvars-binlog">

@@ -3602,6 +3628,48 @@
         </para>
       </listitem>
 
+      <listitem>
+        <para id="sysvar_binlog_rows_query_log_events">
+          <indexterm>
+            <primary>binlog_rows_query_log_events system variable</primary>
+          </indexterm>
+
+          <indexterm>
+            <primary>system variable</primary>
+            <secondary>binlog_rows_query_log_events</secondary>
+          </indexterm>
+
+          <literal>binlog_rows_query_log_events</literal>
+        </para>
+
+        <para condition="dynamic:optvar:item" role="5.6:mysqld:sysvar_binlog_rows_query_log_events"/>
+
+        <para>
+          The <literal>sysvar_binlog_rows_query_log_events</literal>
+          system variable affects row-based logging only. When enabled,
+          it causes a MySQL 5.6.2 or later server to write informational
+          log events such as row query log events into its binary log.
+          This information can be used for debugging and related
+          purposes; such as obtaining the original query issued on the
+          master when it cannot be reconstructed from the row updates.
+        </para>
+
+        <para>
+          These events are normally ignored by MySQL 5.6.2 and later
+          programs reading the binary log and so cause no issues when
+          replicating or restoring from backup. This is not true for a
+          <command>mysqld</command> or <command>mysqlbinlog</command>
+          from MySQL 5.6.1 or earlier: When the older version of the
+          program reading the log encounters an informational log event,
+          it fails, and stops reading at that point. To make the binary
+          log readable by slave replication MySQL servers and other
+          readers (for example, <command>mysqlbinlog</command>) from a
+          MySQL 5.6.1 or earlier distribution,
+          <literal>sysvar_binlog_rows_query_log_events</literal> must be
+          disabled during logging.
+        </para>
+      </listitem>
+
     </itemizedlist>
 
   </section>


Thread
svn commit - mysqldoc@oter02: r25141 - in trunk: dynamic-docs/changelog dynamic-docs/command-optvars refman-5.6jon.stephens23 Feb