Author: mcbrown
Date: 2007-08-29 14:08:51 +0200 (Wed, 29 Aug 2007)
New Revision: 7578
Log:
Docs Bug: #30268 (SHOW BINLOG EVENTS output)
Modified:
trunk/refman-4.1/sql-syntax.xml
trunk/refman-5.0/sql-syntax.xml
trunk/refman-5.1/sql-syntax.xml
trunk/refman-5.2/sql-syntax.xml
Modified: trunk/refman-4.1/sql-syntax.xml
===================================================================
--- trunk/refman-4.1/sql-syntax.xml 2007-08-29 11:24:33 UTC (rev 7577)
+++ trunk/refman-4.1/sql-syntax.xml 2007-08-29 12:08:51 UTC (rev 7578)
Changed blocks: 1, Lines Added: 24, Lines Deleted: 0; 1479 bytes
@@ -18527,6 +18527,30 @@
This statement is available as of MySQL 4.0.
</para>
+ <note>
+ <para>
+ Issuing a <literal>SHOW BINLOG EVENTS</literal> with no
+ <literal>LIMIT</literal> clause could start a very time- and
+ resource-consuming process because the server returns to the
+ client the complete contents of the binary log (which
+ includes all statements executed by the server that modify
+ data). As an alternative to <literal>SHOW BINLOG
+ EVENTS</literal>, use the <command>mysqlbinlog</command>
+ utility to save the binary log to a text file for later
+ examination and analysis. See <xref linkend="mysqlbinlog"/>.
+ </para>
+ </note>
+
+ <note>
+ <para>
+ Events relating to the setting of variables is not included
+ in the output generated when calling <literal>SHOW BINLOG
+ EVENTS</literal>. To get complete coverage of events within
+ a binary log, use
+ <link linkend="mysqlbinlog"><literal>mysqlbinlog</literal></link>.
+ </para>
+ </note>
+
</section>
<section id="show-binary-logs">
Modified: trunk/refman-5.0/sql-syntax.xml
===================================================================
--- trunk/refman-5.0/sql-syntax.xml 2007-08-29 11:24:33 UTC (rev 7577)
+++ trunk/refman-5.0/sql-syntax.xml 2007-08-29 12:08:51 UTC (rev 7578)
Changed blocks: 1, Lines Added: 23, Lines Deleted: 12; 2145 bytes
@@ -21523,19 +21523,30 @@
<xref linkend="select"/>.
</para>
- <para>
- <emphasis role="bold">Note</emphasis>: Issuing a <literal>SHOW
- BINLOG EVENTS</literal> with no <literal>LIMIT</literal>
- clause could start a very time- and resource-consuming process
- because the server returns to the client the complete contents
- of the binary log (which includes all statements executed by
- the server that modify data). As an alternative to
- <literal>SHOW BINLOG EVENTS</literal>, use the
- <command>mysqlbinlog</command> utility to save the binary log
- to a text file for later examination and analysis. See
- <xref linkend="mysqlbinlog"/>.
- </para>
+ <note>
+ <para>
+ Issuing a <literal>SHOW BINLOG EVENTS</literal> with no
+ <literal>LIMIT</literal> clause could start a very time- and
+ resource-consuming process because the server returns to the
+ client the complete contents of the binary log (which
+ includes all statements executed by the server that modify
+ data). As an alternative to <literal>SHOW BINLOG
+ EVENTS</literal>, use the <command>mysqlbinlog</command>
+ utility to save the binary log to a text file for later
+ examination and analysis. See <xref linkend="mysqlbinlog"/>.
+ </para>
+ </note>
+ <note>
+ <para>
+ Events relating to the setting of variables is not included
+ in the output generated when calling <literal>SHOW BINLOG
+ EVENTS</literal>. To get complete coverage of events within
+ a binary log, use
+ <link linkend="mysqlbinlog"><literal>mysqlbinlog</literal></link>.
+ </para>
+ </note>
+
</section>
<section id="show-binary-logs">
Modified: trunk/refman-5.1/sql-syntax.xml
===================================================================
--- trunk/refman-5.1/sql-syntax.xml 2007-08-29 11:24:33 UTC (rev 7577)
+++ trunk/refman-5.1/sql-syntax.xml 2007-08-29 12:08:51 UTC (rev 7578)
Changed blocks: 1, Lines Added: 23, Lines Deleted: 12; 2145 bytes
@@ -23833,19 +23833,30 @@
<xref linkend="select"/>.
</para>
- <para>
- <emphasis role="bold">Note</emphasis>: Issuing a <literal>SHOW
- BINLOG EVENTS</literal> with no <literal>LIMIT</literal>
- clause could start a very time- and resource-consuming process
- because the server returns to the client the complete contents
- of the binary log (which includes all statements executed by
- the server that modify data). As an alternative to
- <literal>SHOW BINLOG EVENTS</literal>, use the
- <command>mysqlbinlog</command> utility to save the binary log
- to a text file for later examination and analysis. See
- <xref linkend="mysqlbinlog"/>.
- </para>
+ <note>
+ <para>
+ Issuing a <literal>SHOW BINLOG EVENTS</literal> with no
+ <literal>LIMIT</literal> clause could start a very time- and
+ resource-consuming process because the server returns to the
+ client the complete contents of the binary log (which
+ includes all statements executed by the server that modify
+ data). As an alternative to <literal>SHOW BINLOG
+ EVENTS</literal>, use the <command>mysqlbinlog</command>
+ utility to save the binary log to a text file for later
+ examination and analysis. See <xref linkend="mysqlbinlog"/>.
+ </para>
+ </note>
+ <note>
+ <para>
+ Events relating to the setting of variables is not included
+ in the output generated when calling <literal>SHOW BINLOG
+ EVENTS</literal>. To get complete coverage of events within
+ a binary log, use
+ <link linkend="mysqlbinlog"><literal>mysqlbinlog</literal></link>.
+ </para>
+ </note>
+
</section>
<section id="show-binary-logs">
Modified: trunk/refman-5.2/sql-syntax.xml
===================================================================
--- trunk/refman-5.2/sql-syntax.xml 2007-08-29 11:24:33 UTC (rev 7577)
+++ trunk/refman-5.2/sql-syntax.xml 2007-08-29 12:08:51 UTC (rev 7578)
Changed blocks: 2, Lines Added: 25, Lines Deleted: 14; 2579 bytes
@@ -14385,8 +14385,8 @@
<listitem>
<para>
- If the <literal>LOCK TABLES</literal> statement must wait due
- to locks held by other threads on any of the tables, it
+ If the <literal>LOCK TABLES</literal> statement must wait
+ due to locks held by other threads on any of the tables, it
blocks until all locks can be acquired.
</para>
</listitem>
@@ -24276,19 +24276,30 @@
<xref linkend="select"/>.
</para>
- <para>
- <emphasis role="bold">Note</emphasis>: Issuing a <literal>SHOW
- BINLOG EVENTS</literal> with no <literal>LIMIT</literal>
- clause could start a very time- and resource-consuming process
- because the server returns to the client the complete contents
- of the binary log (which includes all statements executed by
- the server that modify data). As an alternative to
- <literal>SHOW BINLOG EVENTS</literal>, use the
- <command>mysqlbinlog</command> utility to save the binary log
- to a text file for later examination and analysis. See
- <xref linkend="mysqlbinlog"/>.
- </para>
+ <note>
+ <para>
+ Issuing a <literal>SHOW BINLOG EVENTS</literal> with no
+ <literal>LIMIT</literal> clause could start a very time- and
+ resource-consuming process because the server returns to the
+ client the complete contents of the binary log (which
+ includes all statements executed by the server that modify
+ data). As an alternative to <literal>SHOW BINLOG
+ EVENTS</literal>, use the <command>mysqlbinlog</command>
+ utility to save the binary log to a text file for later
+ examination and analysis. See <xref linkend="mysqlbinlog"/>.
+ </para>
+ </note>
+ <note>
+ <para>
+ Events relating to the setting of variables is not included
+ in the output generated when calling <literal>SHOW BINLOG
+ EVENTS</literal>. To get complete coverage of events within
+ a binary log, use
+ <link linkend="mysqlbinlog"><literal>mysqlbinlog</literal></link>.
+ </para>
+ </note>
+
</section>
<section id="show-binary-logs">
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r7578 - in trunk: refman-4.1 refman-5.0 refman-5.1 refman-5.2 | mcbrown | 29 Aug |
