MySQL Lists are EOL. Please join:

List:Commits« Previous MessageNext Message »
From:jon Date:March 18 2008 10:19am
Subject:svn commit - mysqldoc@docsrva: r10289 - in trunk: refman-4.1 refman-5.0 refman-5.1 refman-6.0
View as plain text  
Author: jstephens
Date: 2008-03-18 11:19:54 +0100 (Tue, 18 Mar 2008)
New Revision: 10289

Log:

Fixed Docs Bug #20226



Modified:
   trunk/refman-4.1/backup.xml
   trunk/refman-5.0/backup.xml
   trunk/refman-5.1/backup.xml
   trunk/refman-6.0/backup.xml


Modified: trunk/refman-4.1/backup.xml
===================================================================
--- trunk/refman-4.1/backup.xml	2008-03-18 00:15:08 UTC (rev 10288)
+++ trunk/refman-4.1/backup.xml	2008-03-18 10:19:54 UTC (rev 10289)
Changed blocks: 2, Lines Added: 17, Lines Deleted: 7; 1523 bytes

@@ -1921,13 +1921,15 @@
 
       </orderedlist>
 
-      <para>
-        Note: If you want a repair operation to go much faster, you
-        should set the values of the <literal>sort_buffer_size</literal>
-        and <literal>key_buffer_size</literal> variables each to about
-        25% of your available memory when running
-        <command>myisamchk</command> or <command>isamchk</command>.
-      </para>
+      <note>
+        <para>
+          If you want a repair operation to go much faster, you should
+          set the values of the <literal>sort_buffer_size</literal> and
+          <literal>key_buffer_size</literal> variables each to about 25%
+          of your available memory when running
+          <command>myisamchk</command>.
+        </para>
+      </note>
 
       <para>
         If you get unexpected errors when repairing (such as

@@ -1984,6 +1986,14 @@
 
       </orderedlist>
 
+      <important>
+        <para>
+          If you are using replication, you should stop it prior to
+          performing the above procedure, since it involves filesystem
+          operations, and these are not logged by MySQL.
+        </para>
+      </important>
+
       <para>
         Go back to Stage 2. <command>myisamchk -r -q</command> should
         work. (This should not be an endless loop.)


Modified: trunk/refman-5.0/backup.xml
===================================================================
--- trunk/refman-5.0/backup.xml	2008-03-18 00:15:08 UTC (rev 10288)
+++ trunk/refman-5.0/backup.xml	2008-03-18 10:19:54 UTC (rev 10289)
Changed blocks: 2, Lines Added: 17, Lines Deleted: 7; 1493 bytes

@@ -1904,13 +1904,15 @@
 
       </orderedlist>
 
-      <para>
-        Note: If you want a repair operation to go much faster, you
-        should set the values of the <literal>sort_buffer_size</literal>
-        and <literal>key_buffer_size</literal> variables each to about
-        25% of your available memory when running
-        <command>myisamchk</command>.
-      </para>
+      <note>
+        <para>
+          If you want a repair operation to go much faster, you should
+          set the values of the <literal>sort_buffer_size</literal> and
+          <literal>key_buffer_size</literal> variables each to about 25%
+          of your available memory when running
+          <command>myisamchk</command>.
+        </para>
+      </note>
 
       <para>
         If you get unexpected errors when repairing (such as

@@ -1961,6 +1963,14 @@
 
       </orderedlist>
 
+      <important>
+        <para>
+          If you are using replication, you should stop it prior to
+          performing the above procedure, since it involves filesystem
+          operations, and these are not logged by MySQL.
+        </para>
+      </important>
+
       <para>
         Go back to Stage 2. <command>myisamchk -r -q</command> should
         work. (This should not be an endless loop.)


Modified: trunk/refman-5.1/backup.xml
===================================================================
--- trunk/refman-5.1/backup.xml	2008-03-18 00:15:08 UTC (rev 10288)
+++ trunk/refman-5.1/backup.xml	2008-03-18 10:19:54 UTC (rev 10289)
Changed blocks: 2, Lines Added: 17, Lines Deleted: 7; 1493 bytes

@@ -1913,13 +1913,15 @@
 
       </orderedlist>
 
-      <para>
-        Note: If you want a repair operation to go much faster, you
-        should set the values of the <literal>sort_buffer_size</literal>
-        and <literal>key_buffer_size</literal> variables each to about
-        25% of your available memory when running
-        <command>myisamchk</command>.
-      </para>
+      <note>
+        <para>
+          If you want a repair operation to go much faster, you should
+          set the values of the <literal>sort_buffer_size</literal> and
+          <literal>key_buffer_size</literal> variables each to about 25%
+          of your available memory when running
+          <command>myisamchk</command>.
+        </para>
+      </note>
 
       <para>
         If you get unexpected errors when repairing (such as

@@ -1970,6 +1972,14 @@
 
       </orderedlist>
 
+      <important>
+        <para>
+          If you are using replication, you should stop it prior to
+          performing the above procedure, since it involves filesystem
+          operations, and these are not logged by MySQL.
+        </para>
+      </important>
+
       <para>
         Go back to Stage 2. <command>myisamchk -r -q</command> should
         work. (This should not be an endless loop.)


Modified: trunk/refman-6.0/backup.xml
===================================================================
--- trunk/refman-6.0/backup.xml	2008-03-18 00:15:08 UTC (rev 10288)
+++ trunk/refman-6.0/backup.xml	2008-03-18 10:19:54 UTC (rev 10289)
Changed blocks: 2, Lines Added: 17, Lines Deleted: 7; 1493 bytes

@@ -2804,13 +2804,15 @@
 
       </orderedlist>
 
-      <para>
-        Note: If you want a repair operation to go much faster, you
-        should set the values of the <literal>sort_buffer_size</literal>
-        and <literal>key_buffer_size</literal> variables each to about
-        25% of your available memory when running
-        <command>myisamchk</command>.
-      </para>
+      <note>
+        <para>
+          If you want a repair operation to go much faster, you should
+          set the values of the <literal>sort_buffer_size</literal> and
+          <literal>key_buffer_size</literal> variables each to about 25%
+          of your available memory when running
+          <command>myisamchk</command>.
+        </para>
+      </note>
 
       <para>
         If you get unexpected errors when repairing (such as

@@ -2861,6 +2863,14 @@
 
       </orderedlist>
 
+      <important>
+        <para>
+          If you are using replication, you should stop it prior to
+          performing the above procedure, since it involves filesystem
+          operations, and these are not logged by MySQL.
+        </para>
+      </important>
+
       <para>
         Go back to Stage 2. <command>myisamchk -r -q</command> should
         work. (This should not be an endless loop.)


Thread
svn commit - mysqldoc@docsrva: r10289 - in trunk: refman-4.1 refman-5.0 refman-5.1 refman-6.0jon18 Mar