svn commit - mysqldoc@docsrva: r24929 - trunk/mysql-enterprise-backup-3.5

[john.russell]

Author: jrussell
Date: 2011-01-28 19:43:16 +0100 (Fri, 28 Jan 2011)
New Revision: 24929

Log:
Added limitation per bug #57335.


Modified:
   trunk/mysql-enterprise-backup-3.5/manual.xml


Modified: trunk/mysql-enterprise-backup-3.5/manual.xml
===================================================================
--- trunk/mysql-enterprise-backup-3.5/manual.xml	2011-01-28 16:37:59 UTC (rev 24928)
+++ trunk/mysql-enterprise-backup-3.5/manual.xml	2011-01-28 18:43:16 UTC (rev 24929)
Changed blocks: 1, Lines Added: 37, Lines Deleted: 14; 3044 bytes

@@ -5141,21 +5141,44 @@
       <title>Limitations of <literal>mysqlbackup</literal> and
         <literal>ibbackup</literal> Commands</title>
 
-      <para>
-        In some cases, backups of non-transactional tables such as
-        <literal role="se">MyISAM</literal> tables could contain
-        additional uncommitted data. If
-        <link linkend="glos_autocommit">autocommit</link> is turned off,
-        and both <literal role="se">InnoDB</literal> tables and
-        non-transactional tables are modified within the same
-        transaction, data can be written to the non-transactional table
-        before the binlog position is updated. The binlog position is
-        updated when the transaction is committed, but the
-        non-transactional data is written immediately. If the backup
-        occurs while such a transaction is open, the backup data
-        contains the updates made to the non-transactional table.
-      </para>
+      <itemizedlist>
 
+        <listitem>
+          <para>
+            In some cases, backups of non-transactional tables such as
+            <literal role="se">MyISAM</literal> tables could contain
+            additional uncommitted data. If
+            <link linkend="glos_autocommit">autocommit</link> is turned
+            off, and both <literal role="se">InnoDB</literal> tables and
+            non-transactional tables are modified within the same
+            transaction, data can be written to the non-transactional
+            table before the binlog position is updated. The binlog
+            position is updated when the transaction is committed, but
+            the non-transactional data is written immediately. If the
+            backup occurs while such a transaction is open, the backup
+            data contains the updates made to the non-transactional
+            table.
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            If the <literal>mysqlbackup</literal> process is
+            interrupted, such as by a Unix <literal>kill -9</literal>
+            command, a <literal>FLUSH TABLES WITH READ LOCK</literal>
+            operation might remain running. In this case, use the
+            <literal>KILL QUERY</literal> command from the
+            <literal>mysql</literal> command line to kill the
+            <literal>FLUSH TABLES WITH READ LOCK</literal> statement.
+            This issue is more likely to occur if the <literal>FLUSH
+            TABLES</literal> operation is stalled by a long-running
+            query or transaction. Refer to <xref linkend="mysqlbackup"/>
+            for guidelines about backup timing and performance.
+          </para>
+        </listitem>
+
+      </itemizedlist>
+
     </section>
 
     <section remap="h2" id="bugs.linux">