List:Commits« Previous MessageNext Message »
From:jon.stephens Date:May 11 2010 3:41pm
Subject:svn commit - mysqldoc@docsrva: r20548 - in trunk: refman-5.0 refman-5.1 refman-5.4 refman-5.5 refman-6.0
View as plain text  
Author: jstephens
Date: 2010-05-11 17:41:43 +0200 (Tue, 11 May 2010)
New Revision: 20548

Log:

Fixes Docs BUG#50078 (REPAIR TABLE changes don't replicate)



Modified:
   trunk/refman-5.0/replication-notes.xml
   trunk/refman-5.0/sql-syntax-server-administration.xml
   trunk/refman-5.1/replication-notes.xml
   trunk/refman-5.1/sql-syntax-server-administration.xml
   trunk/refman-5.4/replication-notes.xml
   trunk/refman-5.4/sql-syntax-server-administration.xml
   trunk/refman-5.5/replication-notes.xml
   trunk/refman-5.5/sql-syntax-server-administration.xml
   trunk/refman-6.0/replication-notes.xml
   trunk/refman-6.0/sql-syntax-server-administration.xml


Modified: trunk/refman-5.0/replication-notes.xml
===================================================================
--- trunk/refman-5.0/replication-notes.xml	2010-05-11 15:40:00 UTC (rev 20547)
+++ trunk/refman-5.0/replication-notes.xml	2010-05-11 15:41:43 UTC (rev 20548)
Changed blocks: 1, Lines Added: 32, Lines Deleted: 0; 1705 bytes

@@ -920,6 +920,38 @@
 
     </section>
 
+    <section id="replication-features-repair-table">
+
+      <title>Replication and <literal>REPAIR TABLE</literal></title>
+
+      <indexterm>
+        <primary>replication</primary>
+        <secondary>and REPAIR TABLE statement</secondary>
+      </indexterm>
+
+      <indexterm>
+        <primary>REPAIR TABLE</primary>
+        <secondary>and replication</secondary>
+      </indexterm>
+
+      <para>
+        When used on a corrupted or otherwise damaged table, it is
+        possible for the <literal role="stmt">REPAIR TABLE</literal>
+        statement to delete rows that cannot be recovered. However, any
+        such modifications of table data performed by this statement are
+        not replicated, which can cause master and slave to lose
+        synchronization. For this reason, in the event that a table on
+        the master becomes damaged and you use
+        <literal role="stmt">REPAIR TABLE</literal> to repair it, you
+        should first stop replication (if it is still running) before
+        using <literal role="stmt">REPAIR TABLE</literal>, then
+        afterwards compare the master&apos;s and slave&apos;s copies of
+        the table and be prepared to correct any discrepancies manually,
+        before restarting replication.
+      </para>
+
+    </section>
+
     <section id="replication-features-shutdowns">
 
       <title>Replication During Master or Slave Shutdowns</title>


Modified: trunk/refman-5.0/sql-syntax-server-administration.xml
===================================================================
--- trunk/refman-5.0/sql-syntax-server-administration.xml	2010-05-11 15:40:00 UTC (rev 20547)
+++ trunk/refman-5.0/sql-syntax-server-administration.xml	2010-05-11 15:41:43 UTC (rev 20548)
Changed blocks: 2, Lines Added: 19, Lines Deleted: 0; 1266 bytes

@@ -2886,6 +2886,16 @@
         <filename>.frm</filename> file to the current version.
       </para>
 
+      <indexterm>
+        <primary>replication</primary>
+        <secondary>and REPAIR TABLE statement</secondary>
+      </indexterm>
+
+      <indexterm>
+        <primary>REPAIR TABLE</primary>
+        <secondary>and replication</secondary>
+      </indexterm>
+
       <para>
         By default, <literal role="stmt">REPAIR TABLE</literal>
         statements are written to the binary log so that they will be

@@ -2894,6 +2904,15 @@
         its alias <literal>LOCAL</literal>.
       </para>
 
+      <important>
+        <para>
+          In the event that a table on the master becomes corrupted and
+          you run <literal>REPAIR TABLE</literal> on it, any resulting
+          changes to the original table are <emphasis>not</emphasis>
+          propagated to slaves.
+        </para>
+      </important>
+
     </section>
 
     <section id="restore-table">


Modified: trunk/refman-5.1/replication-notes.xml
===================================================================
--- trunk/refman-5.1/replication-notes.xml	2010-05-11 15:40:00 UTC (rev 20547)
+++ trunk/refman-5.1/replication-notes.xml	2010-05-11 15:41:43 UTC (rev 20548)
Changed blocks: 1, Lines Added: 32, Lines Deleted: 0; 1707 bytes

@@ -2191,6 +2191,38 @@
 
     </section>
 
+    <section id="replication-features-repair-table">
+
+      <title>Replication and <literal>REPAIR TABLE</literal></title>
+
+      <indexterm>
+        <primary>replication</primary>
+        <secondary>and REPAIR TABLE statement</secondary>
+      </indexterm>
+
+      <indexterm>
+        <primary>REPAIR TABLE</primary>
+        <secondary>and replication</secondary>
+      </indexterm>
+
+      <para>
+        When used on a corrupted or otherwise damaged table, it is
+        possible for the <literal role="stmt">REPAIR TABLE</literal>
+        statement to delete rows that cannot be recovered. However, any
+        such modifications of table data performed by this statement are
+        not replicated, which can cause master and slave to lose
+        synchronization. For this reason, in the event that a table on
+        the master becomes damaged and you use
+        <literal role="stmt">REPAIR TABLE</literal> to repair it, you
+        should first stop replication (if it is still running) before
+        using <literal role="stmt">REPAIR TABLE</literal>, then
+        afterwards compare the master&apos;s and slave&apos;s copies of
+        the table and be prepared to correct any discrepancies manually,
+        before restarting replication.
+      </para>
+
+    </section>
+
     <section id="replication-features-shutdowns">
 
       <title>Replication During Master or Slave Shutdowns</title>


Modified: trunk/refman-5.1/sql-syntax-server-administration.xml
===================================================================
--- trunk/refman-5.1/sql-syntax-server-administration.xml	2010-05-11 15:40:00 UTC (rev 20547)
+++ trunk/refman-5.1/sql-syntax-server-administration.xml	2010-05-11 15:41:43 UTC (rev 20548)
Changed blocks: 2, Lines Added: 19, Lines Deleted: 0; 1266 bytes

@@ -2918,6 +2918,16 @@
         <filename>.frm</filename> file to the current version.
       </para>
 
+      <indexterm>
+        <primary>replication</primary>
+        <secondary>and REPAIR TABLE statement</secondary>
+      </indexterm>
+
+      <indexterm>
+        <primary>REPAIR TABLE</primary>
+        <secondary>and replication</secondary>
+      </indexterm>
+
       <para>
         By default, <literal role="stmt">REPAIR TABLE</literal>
         statements are written to the binary log so that they will be

@@ -2926,6 +2936,15 @@
         its alias <literal>LOCAL</literal>.
       </para>
 
+      <important>
+        <para>
+          In the event that a table on the master becomes corrupted and
+          you run <literal>REPAIR TABLE</literal> on it, any resulting
+          changes to the original table are <emphasis>not</emphasis>
+          propagated to slaves.
+        </para>
+      </important>
+
     </section>
 
     <section id="restore-table">


Modified: trunk/refman-5.4/replication-notes.xml
===================================================================
--- trunk/refman-5.4/replication-notes.xml	2010-05-11 15:40:00 UTC (rev 20547)
+++ trunk/refman-5.4/replication-notes.xml	2010-05-11 15:41:43 UTC (rev 20548)
Changed blocks: 1, Lines Added: 32, Lines Deleted: 0; 1707 bytes

@@ -1779,6 +1779,38 @@
 
     </section>
 
+    <section id="replication-features-repair-table">
+
+      <title>Replication and <literal>REPAIR TABLE</literal></title>
+
+      <indexterm>
+        <primary>replication</primary>
+        <secondary>and REPAIR TABLE statement</secondary>
+      </indexterm>
+
+      <indexterm>
+        <primary>REPAIR TABLE</primary>
+        <secondary>and replication</secondary>
+      </indexterm>
+
+      <para>
+        When used on a corrupted or otherwise damaged table, it is
+        possible for the <literal role="stmt">REPAIR TABLE</literal>
+        statement to delete rows that cannot be recovered. However, any
+        such modifications of table data performed by this statement are
+        not replicated, which can cause master and slave to lose
+        synchronization. For this reason, in the event that a table on
+        the master becomes damaged and you use
+        <literal role="stmt">REPAIR TABLE</literal> to repair it, you
+        should first stop replication (if it is still running) before
+        using <literal role="stmt">REPAIR TABLE</literal>, then
+        afterwards compare the master&apos;s and slave&apos;s copies of
+        the table and be prepared to correct any discrepancies manually,
+        before restarting replication.
+      </para>
+
+    </section>
+
     <section id="replication-features-shutdowns">
 
       <title>Replication During Master or Slave Shutdowns</title>


Modified: trunk/refman-5.4/sql-syntax-server-administration.xml
===================================================================
--- trunk/refman-5.4/sql-syntax-server-administration.xml	2010-05-11 15:40:00 UTC (rev 20547)
+++ trunk/refman-5.4/sql-syntax-server-administration.xml	2010-05-11 15:41:43 UTC (rev 20548)
Changed blocks: 2, Lines Added: 19, Lines Deleted: 0; 1266 bytes

@@ -2857,6 +2857,16 @@
         <filename>.frm</filename> file to the current version.
       </para>
 
+      <indexterm>
+        <primary>replication</primary>
+        <secondary>and REPAIR TABLE statement</secondary>
+      </indexterm>
+
+      <indexterm>
+        <primary>REPAIR TABLE</primary>
+        <secondary>and replication</secondary>
+      </indexterm>
+
       <para>
         By default, <literal role="stmt">REPAIR TABLE</literal>
         statements are written to the binary log so that they will be

@@ -2865,6 +2875,15 @@
         its alias <literal>LOCAL</literal>.
       </para>
 
+      <important>
+        <para>
+          In the event that a table on the master becomes corrupted and
+          you run <literal>REPAIR TABLE</literal> on it, any resulting
+          changes to the original table are <emphasis>not</emphasis>
+          propagated to slaves.
+        </para>
+      </important>
+
     </section>
 
     <section id="restore-table">


Modified: trunk/refman-5.5/replication-notes.xml
===================================================================
--- trunk/refman-5.5/replication-notes.xml	2010-05-11 15:40:00 UTC (rev 20547)
+++ trunk/refman-5.5/replication-notes.xml	2010-05-11 15:41:43 UTC (rev 20548)
Changed blocks: 1, Lines Added: 32, Lines Deleted: 0; 1707 bytes

@@ -2105,6 +2105,38 @@
 
     </section>
 
+    <section id="replication-features-repair-table">
+
+      <title>Replication and <literal>REPAIR TABLE</literal></title>
+
+      <indexterm>
+        <primary>replication</primary>
+        <secondary>and REPAIR TABLE statement</secondary>
+      </indexterm>
+
+      <indexterm>
+        <primary>REPAIR TABLE</primary>
+        <secondary>and replication</secondary>
+      </indexterm>
+
+      <para>
+        When used on a corrupted or otherwise damaged table, it is
+        possible for the <literal role="stmt">REPAIR TABLE</literal>
+        statement to delete rows that cannot be recovered. However, any
+        such modifications of table data performed by this statement are
+        not replicated, which can cause master and slave to lose
+        synchronization. For this reason, in the event that a table on
+        the master becomes damaged and you use
+        <literal role="stmt">REPAIR TABLE</literal> to repair it, you
+        should first stop replication (if it is still running) before
+        using <literal role="stmt">REPAIR TABLE</literal>, then
+        afterwards compare the master&apos;s and slave&apos;s copies of
+        the table and be prepared to correct any discrepancies manually,
+        before restarting replication.
+      </para>
+
+    </section>
+
     <section id="replication-features-shutdowns">
 
       <title>Replication During Master or Slave Shutdowns</title>


Modified: trunk/refman-5.5/sql-syntax-server-administration.xml
===================================================================
--- trunk/refman-5.5/sql-syntax-server-administration.xml	2010-05-11 15:40:00 UTC (rev 20547)
+++ trunk/refman-5.5/sql-syntax-server-administration.xml	2010-05-11 15:41:43 UTC (rev 20548)
Changed blocks: 2, Lines Added: 19, Lines Deleted: 0; 1246 bytes

@@ -2767,6 +2767,16 @@
         <filename>.frm</filename> file to the current version.
       </para>
 
+      <indexterm>
+        <primary>replication</primary>
+        <secondary>and REPAIR TABLE statement</secondary>
+      </indexterm>
+
+      <indexterm>
+        <primary>REPAIR TABLE</primary>
+        <secondary>and replication</secondary>
+      </indexterm>
+
       <para>
         By default, <literal role="stmt">REPAIR TABLE</literal>
         statements are written to the binary log so that they will be

@@ -2775,6 +2785,15 @@
         its alias <literal>LOCAL</literal>.
       </para>
 
+      <important>
+        <para>
+          In the event that a table on the master becomes corrupted and
+          you run <literal>REPAIR TABLE</literal> on it, any resulting
+          changes to the original table are <emphasis>not</emphasis>
+          propagated to slaves.
+        </para>
+      </important>
+
     </section>
 
   </section>


Modified: trunk/refman-6.0/replication-notes.xml
===================================================================
--- trunk/refman-6.0/replication-notes.xml	2010-05-11 15:40:00 UTC (rev 20547)
+++ trunk/refman-6.0/replication-notes.xml	2010-05-11 15:41:43 UTC (rev 20548)
Changed blocks: 1, Lines Added: 32, Lines Deleted: 0; 1707 bytes

@@ -2003,6 +2003,38 @@
 
     </section>
 
+    <section id="replication-features-repair-table">
+
+      <title>Replication and <literal>REPAIR TABLE</literal></title>
+
+      <indexterm>
+        <primary>replication</primary>
+        <secondary>and REPAIR TABLE statement</secondary>
+      </indexterm>
+
+      <indexterm>
+        <primary>REPAIR TABLE</primary>
+        <secondary>and replication</secondary>
+      </indexterm>
+
+      <para>
+        When used on a corrupted or otherwise damaged table, it is
+        possible for the <literal role="stmt">REPAIR TABLE</literal>
+        statement to delete rows that cannot be recovered. However, any
+        such modifications of table data performed by this statement are
+        not replicated, which can cause master and slave to lose
+        synchronization. For this reason, in the event that a table on
+        the master becomes damaged and you use
+        <literal role="stmt">REPAIR TABLE</literal> to repair it, you
+        should first stop replication (if it is still running) before
+        using <literal role="stmt">REPAIR TABLE</literal>, then
+        afterwards compare the master&apos;s and slave&apos;s copies of
+        the table and be prepared to correct any discrepancies manually,
+        before restarting replication.
+      </para>
+
+    </section>
+
     <section id="replication-features-shutdowns">
 
       <title>Replication During Master or Slave Shutdowns</title>


Modified: trunk/refman-6.0/sql-syntax-server-administration.xml
===================================================================
--- trunk/refman-6.0/sql-syntax-server-administration.xml	2010-05-11 15:40:00 UTC (rev 20547)
+++ trunk/refman-6.0/sql-syntax-server-administration.xml	2010-05-11 15:41:43 UTC (rev 20548)
Changed blocks: 2, Lines Added: 19, Lines Deleted: 0; 1246 bytes

@@ -2794,6 +2794,16 @@
         <filename>.frm</filename> file to the current version.
       </para>
 
+      <indexterm>
+        <primary>replication</primary>
+        <secondary>and REPAIR TABLE statement</secondary>
+      </indexterm>
+
+      <indexterm>
+        <primary>REPAIR TABLE</primary>
+        <secondary>and replication</secondary>
+      </indexterm>
+
       <para>
         By default, <literal role="stmt">REPAIR TABLE</literal>
         statements are written to the binary log so that they will be

@@ -2802,6 +2812,15 @@
         its alias <literal>LOCAL</literal>.
       </para>
 
+      <important>
+        <para>
+          In the event that a table on the master becomes corrupted and
+          you run <literal>REPAIR TABLE</literal> on it, any resulting
+          changes to the original table are <emphasis>not</emphasis>
+          propagated to slaves.
+        </para>
+      </important>
+
     </section>
 
   </section>


Thread
svn commit - mysqldoc@docsrva: r20548 - in trunk: refman-5.0 refman-5.1 refman-5.4 refman-5.5 refman-6.0jon.stephens11 May