Author: jstephens
Date: 2008-11-18 16:58:19 +0100 (Tue, 18 Nov 2008)
New Revision: 12515
Log:
Added info regarding binary logging event groups (Thanks, Mats!)
Modified:
trunk/refman-4.1/replication-options-core.xml
trunk/refman-4.1/replication.xml
trunk/refman-4.1/sql-syntax-replication.xml
trunk/refman-5.0/Makefile.depends
trunk/refman-5.0/replication-notes.xml
trunk/refman-5.0/replication-options-core.xml
trunk/refman-5.0/sql-syntax-replication.xml
trunk/refman-5.1/Makefile.depends
trunk/refman-5.1/dba-core.xml
trunk/refman-5.1/replication-notes.xml
trunk/refman-5.1/sql-syntax-replication.xml
trunk/refman-6.0/Makefile.depends
trunk/refman-6.0/dba-core.xml
trunk/refman-6.0/replication-notes.xml
trunk/refman-6.0/sql-syntax-replication.xml
Modified: trunk/refman-4.1/replication-options-core.xml
===================================================================
--- trunk/refman-4.1/replication-options-core.xml 2008-11-18 04:48:33 UTC (rev 12514)
+++ trunk/refman-4.1/replication-options-core.xml 2008-11-18 15:58:19 UTC (rev 12515)
Changed blocks: 1, Lines Added: 13, Lines Deleted: 3; 1141 bytes
@@ -1724,10 +1724,20 @@
<para>
The number of events from the master that a slave server
- should skip. See
- <xref linkend="set-global-sql-slave-skip-counter"/>. This
- variable was added in MySQL 3.23.33.
+ should skip. This variable was added in MySQL 3.23.33.
</para>
+
+ <important>
+ <para>
+ If skipping the number of events specified by setting this
+ variable would cause the slave to begin in the middle of an
+ event group, the slave continues to skip until it finds the
+ beginning of the next event group and begins from that
+ point. See
+ <xref linkend="set-global-sql-slave-skip-counter"/>, for
+ more information.
+ </para>
+ </important>
</listitem>
</itemizedlist>
Modified: trunk/refman-4.1/replication.xml
===================================================================
--- trunk/refman-4.1/replication.xml 2008-11-18 04:48:33 UTC (rev 12514)
+++ trunk/refman-4.1/replication.xml 2008-11-18 15:58:19 UTC (rev 12515)
Changed blocks: 1, Lines Added: 5, Lines Deleted: 0; 607 bytes
@@ -3654,6 +3654,11 @@
<literal role="func">LAST_INSERT_ID()</literal> is that
they take two events in the binary log of the master.
</para>
+
+ <para>
+ See also
+ <xref linkend="set-global-sql-slave-skip-counter"/>.
+ </para>
</listitem>
<listitem>
Modified: trunk/refman-4.1/sql-syntax-replication.xml
===================================================================
--- trunk/refman-4.1/sql-syntax-replication.xml 2008-11-18 04:48:33 UTC (rev 12514)
+++ trunk/refman-4.1/sql-syntax-replication.xml 2008-11-18 15:58:19 UTC (rev 12515)
Changed blocks: 2, Lines Added: 53, Lines Deleted: 0; 2072 bytes
@@ -967,6 +967,19 @@
<primary>SET GLOBAL SQL_SLAVE_SKIP_COUNTER</primary>
</indexterm>
+ <indexterm>
+ <primary>SQL_SLAVE_SKIP_COUNTER</primary>
+ </indexterm>
+
+ <indexterm>
+ <primary>event groups</primary>
+ </indexterm>
+
+ <indexterm>
+ <primary>binary log</primary>
+ <secondary>event groups</secondary>
+ </indexterm>
+
<remark role="help-topic" condition="SET GLOBAL SQL_SLAVE_SKIP_COUNTER"/>
<remark role="help-keywords">
@@ -999,6 +1012,46 @@
<remark role="help-description-end"/>
+ <para>
+ When using this statement, it is important to understand that
+ the binary log is actually organized as a sequence of groups
+ known as <firstterm>event groups</firstterm>. Each event group
+ consists of a sequence of events.
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ For transactional tables, an event group corresponds to a
+ transaction.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ For non-transactional tables, an event group corresponds to
+ a single SQL statement.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ <note>
+ <para>
+ A single transaction can contain changes to both transactional
+ and non-transactional tables.
+ </para>
+ </note>
+
+ <para>
+ When you use <literal>SET [GLOBAL]
+ SQL_SLAVE_SKIP_COUNTER</literal> to skip events and the result
+ is in the middle of a group, the slave continues to skip events
+ until it reaches the end of the group. Execution then starts
+ with the next event group.
+ </para>
+
</section>
<section id="start-slave">
Modified: trunk/refman-5.0/Makefile.depends
===================================================================
--- trunk/refman-5.0/Makefile.depends 2008-11-18 04:48:33 UTC (rev 12514)
+++ trunk/refman-5.0/Makefile.depends 2008-11-18 15:58:19 UTC (rev 12515)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 0; 664 bytes
@@ -2905,6 +2905,7 @@
../refman-5.0/metadata/se-innodb-core.idmap \
../refman-5.0/metadata/se-memory.idmap \
../refman-5.0/metadata/sql-syntax-data-definition.idmap \
+ ../refman-5.0/metadata/sql-syntax-replication.idmap \
../refman-5.0/metadata/sql-syntax-server-administration.idmap \
../refman-5.0/metadata/sql-syntax-transactions.idmap \
../refman-5.1/metadata/replication-configuration-core.idmap \
Modified: trunk/refman-5.0/replication-notes.xml
===================================================================
--- trunk/refman-5.0/replication-notes.xml 2008-11-18 04:48:33 UTC (rev 12514)
+++ trunk/refman-5.0/replication-notes.xml 2008-11-18 15:58:19 UTC (rev 12515)
Changed blocks: 1, Lines Added: 5, Lines Deleted: 0; 625 bytes
@@ -2268,6 +2268,11 @@
<literal role="func">LAST_INSERT_ID()</literal> is that
they take two events in the binary log of the master.
</para>
+
+ <para>
+ See also
+ <xref linkend="set-global-sql-slave-skip-counter"/>.
+ </para>
</listitem>
<listitem>
Modified: trunk/refman-5.0/replication-options-core.xml
===================================================================
--- trunk/refman-5.0/replication-options-core.xml 2008-11-18 04:48:33 UTC (rev 12514)
+++ trunk/refman-5.0/replication-options-core.xml 2008-11-18 15:58:19 UTC (rev 12515)
Changed blocks: 1, Lines Added: 13, Lines Deleted: 2; 1046 bytes
@@ -2015,9 +2015,20 @@
<para>
The number of events from the master that a slave server
- should skip. See
- <xref linkend="set-global-sql-slave-skip-counter"/>.
+ should skip.
</para>
+
+ <important>
+ <para>
+ If skipping the number of events specified by setting this
+ variable would cause the slave to begin in the middle of an
+ event group, the slave continues to skip until it finds the
+ beginning of the next event group and begins from that
+ point. See
+ <xref linkend="set-global-sql-slave-skip-counter"/>, for
+ more information.
+ </para>
+ </important>
</listitem>
</itemizedlist>
Modified: trunk/refman-5.0/sql-syntax-replication.xml
===================================================================
--- trunk/refman-5.0/sql-syntax-replication.xml 2008-11-18 04:48:33 UTC (rev 12514)
+++ trunk/refman-5.0/sql-syntax-replication.xml 2008-11-18 15:58:19 UTC (rev 12515)
Changed blocks: 2, Lines Added: 53, Lines Deleted: 0; 2069 bytes
@@ -955,6 +955,19 @@
<primary>SET GLOBAL SQL_SLAVE_SKIP_COUNTER</primary>
</indexterm>
+ <indexterm>
+ <primary>SQL_SLAVE_SKIP_COUNTER</primary>
+ </indexterm>
+
+ <indexterm>
+ <primary>event groups</primary>
+ </indexterm>
+
+ <indexterm>
+ <primary>binary log</primary>
+ <secondary>event groups</secondary>
+ </indexterm>
+
<remark role="help-topic" condition="SET GLOBAL SQL_SLAVE_SKIP_COUNTER"/>
<remark role="help-keywords">
@@ -982,6 +995,46 @@
<remark role="help-description-end"/>
+ <para>
+ When using this statement, it is important to understand that
+ the binary log is actually organized as a sequence of groups
+ known as <firstterm>event groups</firstterm>. Each event group
+ consists of a sequence of events.
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ For transactional tables, an event group corresponds to a
+ transaction.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ For non-transactional tables, an event group corresponds to
+ a single SQL statement.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ <note>
+ <para>
+ A single transaction can contain changes to both transactional
+ and non-transactional tables.
+ </para>
+ </note>
+
+ <para>
+ When you use <literal>SET GLOBAL
+ SQL_SLAVE_SKIP_COUNTER</literal> to skip events and the result
+ is in the middle of a group, the slave continues to skip events
+ until it reaches the end of the group. Execution then starts
+ with the next event group.
+ </para>
+
</section>
<section id="start-slave">
Modified: trunk/refman-5.1/Makefile.depends
===================================================================
--- trunk/refman-5.1/Makefile.depends 2008-11-18 04:48:33 UTC (rev 12514)
+++ trunk/refman-5.1/Makefile.depends 2008-11-18 15:58:19 UTC (rev 12515)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 0; 650 bytes
@@ -2924,6 +2924,7 @@
../refman-5.1/metadata/replication-solutions.idmap \
../refman-5.1/metadata/se-innodb-core.idmap \
../refman-5.1/metadata/se-memory.idmap \
+ ../refman-5.1/metadata/sql-syntax-replication.idmap \
../refman-5.1/metadata/sql-syntax-server-administration.idmap \
../refman-5.1/metadata/sql-syntax-transactions.idmap \
../refman-5.1/metadata/stored-programs-views.idmap \
Modified: trunk/refman-5.1/dba-core.xml
===================================================================
--- trunk/refman-5.1/dba-core.xml 2008-11-18 04:48:33 UTC (rev 12514)
+++ trunk/refman-5.1/dba-core.xml 2008-11-18 15:58:19 UTC (rev 12515)
Changed blocks: 1, Lines Added: 13, Lines Deleted: 2; 1033 bytes
@@ -7695,9 +7695,20 @@
<para>
The number of events from the master that a slave server
- should skip. See
- <xref linkend="set-global-sql-slave-skip-counter"/>.
+ should skip.
</para>
+
+ <important>
+ <para>
+ If skipping the number of events specified by setting this
+ variable would cause the slave to begin in the middle of
+ an event group, the slave continues to skip until it finds
+ the beginning of the next event group and begins from that
+ point. See
+ <xref linkend="set-global-sql-slave-skip-counter"/>, for
+ more information.
+ </para>
+ </important>
</listitem>
<listitem>
Modified: trunk/refman-5.1/replication-notes.xml
===================================================================
--- trunk/refman-5.1/replication-notes.xml 2008-11-18 04:48:33 UTC (rev 12514)
+++ trunk/refman-5.1/replication-notes.xml 2008-11-18 15:58:19 UTC (rev 12515)
Changed blocks: 1, Lines Added: 5, Lines Deleted: 0; 625 bytes
@@ -2977,6 +2977,11 @@
<literal role="func">LAST_INSERT_ID()</literal> is that
they take two events in the binary log of the master.
</para>
+
+ <para>
+ See also
+ <xref linkend="set-global-sql-slave-skip-counter"/>.
+ </para>
</listitem>
<listitem>
Modified: trunk/refman-5.1/sql-syntax-replication.xml
===================================================================
--- trunk/refman-5.1/sql-syntax-replication.xml 2008-11-18 04:48:33 UTC (rev 12514)
+++ trunk/refman-5.1/sql-syntax-replication.xml 2008-11-18 15:58:19 UTC (rev 12515)
Changed blocks: 2, Lines Added: 53, Lines Deleted: 0; 2073 bytes
@@ -1016,6 +1016,19 @@
<primary>SET GLOBAL SQL_SLAVE_SKIP_COUNTER</primary>
</indexterm>
+ <indexterm>
+ <primary>SQL_SLAVE_SKIP_COUNTER</primary>
+ </indexterm>
+
+ <indexterm>
+ <primary>event groups</primary>
+ </indexterm>
+
+ <indexterm>
+ <primary>binary log</primary>
+ <secondary>event groups</secondary>
+ </indexterm>
+
<remark role="help-topic" condition="SET GLOBAL SQL_SLAVE_SKIP_COUNTER"/>
<remark role="help-keywords">
@@ -1043,6 +1056,46 @@
<remark role="help-description-end"/>
+ <para>
+ When using this statement, it is important to understand that
+ the binary log is actually organized as a sequence of groups
+ known as <firstterm>event groups</firstterm>. Each event group
+ consists of a sequence of events.
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ For transactional tables, an event group corresponds to a
+ transaction.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ For non-transactional tables, an event group corresponds to
+ a single SQL statement.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ <note>
+ <para>
+ A single transaction can contain changes to both transactional
+ and non-transactional tables.
+ </para>
+ </note>
+
+ <para>
+ When you use <literal>SET GLOBAL
+ SQL_SLAVE_SKIP_COUNTER</literal> to skip events and the result
+ is in the middle of a group, the slave continues to skip events
+ until it reaches the end of the group. Execution then starts
+ with the next event group.
+ </para>
+
</section>
<section id="start-slave">
Modified: trunk/refman-6.0/Makefile.depends
===================================================================
--- trunk/refman-6.0/Makefile.depends 2008-11-18 04:48:33 UTC (rev 12514)
+++ trunk/refman-6.0/Makefile.depends 2008-11-18 15:58:19 UTC (rev 12515)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 0; 650 bytes
@@ -2098,6 +2098,7 @@
../refman-6.0/metadata/replication-solutions.idmap \
../refman-6.0/metadata/se-innodb-core.idmap \
../refman-6.0/metadata/se-memory.idmap \
+ ../refman-6.0/metadata/sql-syntax-replication.idmap \
../refman-6.0/metadata/sql-syntax-server-administration.idmap \
../refman-6.0/metadata/sql-syntax-transactions.idmap \
../refman-6.0/metadata/stored-programs-views.idmap \
Modified: trunk/refman-6.0/dba-core.xml
===================================================================
--- trunk/refman-6.0/dba-core.xml 2008-11-18 04:48:33 UTC (rev 12514)
+++ trunk/refman-6.0/dba-core.xml 2008-11-18 15:58:19 UTC (rev 12515)
Changed blocks: 1, Lines Added: 13, Lines Deleted: 2; 1033 bytes
@@ -7723,9 +7723,20 @@
<para>
The number of events from the master that a slave server
- should skip. See
- <xref linkend="set-global-sql-slave-skip-counter"/>.
+ should skip.
</para>
+
+ <important>
+ <para>
+ If skipping the number of events specified by setting this
+ variable would cause the slave to begin in the middle of
+ an event group, the slave continues to skip until it finds
+ the beginning of the next event group and begins from that
+ point. See
+ <xref linkend="set-global-sql-slave-skip-counter"/>, for
+ more information.
+ </para>
+ </important>
</listitem>
<listitem>
Modified: trunk/refman-6.0/replication-notes.xml
===================================================================
--- trunk/refman-6.0/replication-notes.xml 2008-11-18 04:48:33 UTC (rev 12514)
+++ trunk/refman-6.0/replication-notes.xml 2008-11-18 15:58:19 UTC (rev 12515)
Changed blocks: 1, Lines Added: 5, Lines Deleted: 0; 625 bytes
@@ -2960,6 +2960,11 @@
<literal role="func">LAST_INSERT_ID()</literal> is that
they take two events in the binary log of the master.
</para>
+
+ <para>
+ See also
+ <xref linkend="set-global-sql-slave-skip-counter"/>.
+ </para>
</listitem>
<listitem>
Modified: trunk/refman-6.0/sql-syntax-replication.xml
===================================================================
--- trunk/refman-6.0/sql-syntax-replication.xml 2008-11-18 04:48:33 UTC (rev 12514)
+++ trunk/refman-6.0/sql-syntax-replication.xml 2008-11-18 15:58:19 UTC (rev 12515)
Changed blocks: 2, Lines Added: 53, Lines Deleted: 0; 2069 bytes
@@ -812,6 +812,19 @@
<primary>SET GLOBAL SQL_SLAVE_SKIP_COUNTER</primary>
</indexterm>
+ <indexterm>
+ <primary>SQL_SLAVE_SKIP_COUNTER</primary>
+ </indexterm>
+
+ <indexterm>
+ <primary>event groups</primary>
+ </indexterm>
+
+ <indexterm>
+ <primary>binary log</primary>
+ <secondary>event groups</secondary>
+ </indexterm>
+
<remark role="help-topic" condition="SET GLOBAL SQL_SLAVE_SKIP_COUNTER"/>
<remark role="help-keywords">
@@ -839,6 +852,46 @@
<remark role="help-description-end"/>
+ <para>
+ When using this statement, it is important to understand that
+ the binary log is actually organized as a sequence of groups
+ known as <firstterm>event groups</firstterm>. Each event group
+ consists of a sequence of events.
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ For transactional tables, an event group corresponds to a
+ transaction.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ For non-transactional tables, an event group corresponds to
+ a single SQL statement.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ <note>
+ <para>
+ A single transaction can contain changes to both transactional
+ and non-transactional tables.
+ </para>
+ </note>
+
+ <para>
+ When you use <literal>SET GLOBAL
+ SQL_SLAVE_SKIP_COUNTER</literal> to skip events and the result
+ is in the middle of a group, the slave continues to skip events
+ until it reaches the end of the group. Execution then starts
+ with the next event group.
+ </para>
+
</section>
<section id="start-slave">
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r12515 - in trunk: refman-4.1 refman-5.0 refman-5.1 refman-6.0 | jon | 18 Nov |
