svn commit - mysqldoc@docsrva: r8391 - in trunk: refman-4.1 refman-5.0 refman-5.1 refman-5.2

[jon]

Author: jstephens
Date: 2007-10-29 19:43:49 +0100 (Mon, 29 Oct 2007)
New Revision: 8391

Log:

4.0 -> 5.1 replication: known issue with LOAD DATA

Fixes Docs Bug #31240.



Modified:
   trunk/refman-4.1/replication.xml
   trunk/refman-5.0/replication-notes.xml
   trunk/refman-5.1/replication-notes.xml
   trunk/refman-5.2/replication-notes.xml


Modified: trunk/refman-4.1/replication.xml
===================================================================
--- trunk/refman-4.1/replication.xml	2007-10-29 18:28:29 UTC (rev 8390)
+++ trunk/refman-4.1/replication.xml	2007-10-29 18:43:49 UTC (rev 8391)
Changed blocks: 2, Lines Added: 14, Lines Deleted: 8; 1777 bytes

@@ -1184,9 +1184,10 @@
       binary log format is the same for 4.0 and 4.1, there are other
       constraints, such as SQL-level compatibility issues. For example,
       a 4.1 master cannot replicate to a 4.0 slave if the replicated
-      statements use SQL features available in 4.1 but not 4.0. These
-      and other issues are discussed in
-      <xref linkend="replication-features"/>.
+      statements use SQL features available in 4.1 but not 4.0. In
+      addition, there are known issues with trying to replicate from a
+      4.0 master to a 5.1 slave (Bug #31240). These and other issues are
+      discussed in <xref linkend="replication-features"/>.
     </para>
 
     <para>

@@ -1710,14 +1711,19 @@
           being interrupted, these modifications are
           <emphasis>not</emphasis> replicated to the slave.
         </para>
-      </listitem>
 
-      <listitem>
         <para>
-          <literal>LOAD DATA INFILE</literal> does not replicate
-          correctly when <option>--binlog-do-db</option> is used. (Bug
-          #19662)
+          In addition, <literal>LOAD DATA INFILE</literal> does not
+          replicate correctly when <option>--binlog-do-db</option> is
+          used. (Bug #19662)
         </para>
+
+        <para>
+          <literal>LOAD DATA INFILE</literal> also does not replicate
+          well from 4.0 and earlier masters to 5.1 or later slaves. In
+          such cases, it is best to upgrade the master to 5.0 or later.
+          (Bug #31240)
+        </para>
       </listitem>
 
       <listitem>


Modified: trunk/refman-5.0/replication-notes.xml
===================================================================
--- trunk/refman-5.0/replication-notes.xml	2007-10-29 18:28:29 UTC (rev 8390)
+++ trunk/refman-5.0/replication-notes.xml	2007-10-29 18:43:49 UTC (rev 8391)
Changed blocks: 1, Lines Added: 7, Lines Deleted: 4; 1054 bytes

@@ -954,10 +954,13 @@
       slave. We recommend upgrading masters and slaves running alpha or
       beta versions to new (production) versions. Replication from a
       5.0.3 master to a 5.0.2 slave will fail; from a 5.0.4 master to a
-      5.0.3 slave will also fail. In general, slaves running MySQL
-      &current-series;.x may be used with older masters (even those
-      running MySQL 3.23, 4.0, or 4.1), but not the reverse. For more
-      information on potential issues, see
+      5.0.3 slave will also fail.
+    </para>
+
+    <para>
+      In general (but not always), slaves running MySQL
+      &current-series;.x may be used with older masters, but not the
+      reverse. For more information on potential issues, see
       <xref linkend="replication-features"/>.
     </para>
 


Modified: trunk/refman-5.1/replication-notes.xml
===================================================================
--- trunk/refman-5.1/replication-notes.xml	2007-10-29 18:28:29 UTC (rev 8390)
+++ trunk/refman-5.1/replication-notes.xml	2007-10-29 18:43:49 UTC (rev 8391)
Changed blocks: 3, Lines Added: 24, Lines Deleted: 6; 2350 bytes

@@ -898,6 +898,18 @@
 
     </section>
 
+    <section id="replication-features-load-data">
+
+      <title>Replication and <literal>LOAD DATA</literal></title>
+
+      <para>
+        The <literal>LOAD DATA</literal> statement is not replicated
+        correctly to a slave running MySQL 5.1 or later from a master
+        running MySQL 4.0 or earlier.
+      </para>
+
+    </section>
+
     <section id="replication-features-mastercrash">
 
       <title>Replication During a Master Crash</title>

@@ -1471,12 +1483,12 @@
     </para>
 
     <para>
-      As a general rule, you should setup replication only between
+      As a general rule, you should set up replication only between
       masters and slaves running the same major versions (5.1, 5.0 or
       4.1) of MySQL. If you must execute replication between different
       major versions, ensure that your client is at a version equal to
       or higher than that of the master. For example, a master of 4.1.23
-      and a slave of 5.0.24.
+      and a slave of 5.0.24 should work together.
     </para>
 
     <para>

@@ -1485,12 +1497,18 @@
       recommend using the same version for both the master and the
       slave. We recommend upgrading masters and slaves running alpha or
       beta versions to new (production) versions. In many cases,
-      replication from a newer master to an older slave will fail. In
-      general, slaves running MySQL &current-series;.x can be used with
-      older masters (even those running MySQL 3.23, 4.0, or 4.1), but
-      not the reverse.
+      replication from a newer master to an older slave will fail.
     </para>
 
+    <para>
+      In general (but not always), slaves running MySQL
+      &current-series;.x can be used with older masters, but not the
+      reverse. However, there are known issues with trying to replicate
+      from a 4.0 or earlier master to a 5.1 or later slave (Bug #31240).
+      For more information on potential issues, see
+      <xref linkend="replication-features"/>.
+    </para>
+
     <note>
       <para>
         You <emphasis>cannot</emphasis> replicate from a master that


Modified: trunk/refman-5.2/replication-notes.xml
===================================================================
--- trunk/refman-5.2/replication-notes.xml	2007-10-29 18:28:29 UTC (rev 8390)
+++ trunk/refman-5.2/replication-notes.xml	2007-10-29 18:43:49 UTC (rev 8391)
Changed blocks: 3, Lines Added: 25, Lines Deleted: 7; 2682 bytes

@@ -898,6 +898,18 @@
 
     </section>
 
+    <section id="replication-features-load-data">
+
+      <title>Replication and <literal>LOAD DATA</literal></title>
+
+      <para>
+        The <literal>LOAD DATA</literal> statement is not replicated
+        correctly to a slave running MySQL 5.1 or later from a master
+        running MySQL 4.0 or earlier.
+      </para>
+
+    </section>
+
     <section id="replication-features-mastercrash">
 
       <title>Replication During a Master Crash</title>

@@ -1461,18 +1473,18 @@
 
     <para>
       The binary log format as implemented in MySQL &current-series; is
-      considerably different from that used in previous versions,
+      considerably different from that used in older versions,
       especially with regard to handling of character sets,
       <literal>LOAD DATA INFILE</literal>, and time zones.
     </para>
 
     <para>
-      As a general rule, you should setup replication only between
+      As a general rule, you should set up replication only between
       masters and slaves running the same major versions (5.1, 5.0 or
       4.1) of MySQL. If you must execute replication between different
       major versions, ensure that your client is at a version equal to
       or higher than that of the master. For example, a master of 4.1.23
-      and a slave of 5.0.24.
+      and a slave of 5.0.24 should work together.
     </para>
 
     <para>

@@ -1481,12 +1493,18 @@
       recommend using the same version for both the master and the
       slave. We recommend upgrading masters and slaves running alpha or
       beta versions to new (production) versions. In many cases,
-      replication from a newer master to an older slave will fail. In
-      general, slaves running MySQL &current-series;.x can be used with
-      older masters (even those running MySQL 3.23, 4.0, or 4.1), but
-      not the reverse.
+      replication from a newer master to an older slave will fail.
     </para>
 
+    <para>
+      In general (but not always), slaves running MySQL
+      &current-series;.x can be used with older masters, but not the
+      reverse. However, there are known issues with trying to replicate
+      from a 4.0 or earlier master to a 5.1 or later slave (Bug #31240).
+      For more information on potential issues, see
+      <xref linkend="replication-features"/>.
+    </para>
+
     <note>
       <para>
         You <emphasis>cannot</emphasis> replicate from a master that