Author: paul
Date: 2007-04-23 19:15:28 +0200 (Mon, 23 Apr 2007)
New Revision: 6065
Log:
r23886@polar: paul | 2007-04-23 12:02:21 -0500
Add some cautions about REPAIR TABLE, CHECK TABLE. (James)
Modified:
trunk/refman-4.1/client-utility-programs.xml
trunk/refman-4.1/sql-syntax.xml
trunk/refman-5.0/client-utility-programs.xml
trunk/refman-5.0/sql-syntax.xml
trunk/refman-5.1/client-utility-programs.xml
trunk/refman-5.1/sql-syntax.xml
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:23770
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:19497
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:14593
+ 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:23886
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:19497
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:14593
Modified: trunk/refman-4.1/client-utility-programs.xml
===================================================================
--- trunk/refman-4.1/client-utility-programs.xml 2007-04-23 16:41:49 UTC (rev 6064)
+++ trunk/refman-4.1/client-utility-programs.xml 2007-04-23 17:15:28 UTC (rev 6065)
Changed blocks: 2, Lines Added: 18, Lines Deleted: 0; 1363 bytes
@@ -1165,6 +1165,15 @@
<filename>.ISM</filename> files for storing data and indexes).
</para>
+ <caution>
+ <para>
+ It is best to make a backup of a table before performing a
+ table repair operation; under some circumstances the
+ operation might cause data loss. Possible causes include but
+ are not limited to filesystem errors.
+ </para>
+ </caution>
+
<para>
Invoke <command>myisamchk</command> like this:
</para>
@@ -9020,6 +9029,15 @@
note : The storage engine for the table doesn't support check
</programlisting>
+ <caution>
+ <para>
+ It is best to make a backup of a table before performing a
+ table repair operation; under some circumstances the
+ operation might cause data loss. Possible causes include but
+ are not limited to filesystem errors.
+ </para>
+ </caution>
+
<para>
There are three general ways to invoke
<command>mysqlcheck</command>:
Modified: trunk/refman-4.1/sql-syntax.xml
===================================================================
--- trunk/refman-4.1/sql-syntax.xml 2007-04-23 16:41:49 UTC (rev 6064)
+++ trunk/refman-4.1/sql-syntax.xml 2007-04-23 17:15:28 UTC (rev 6065)
Changed blocks: 2, Lines Added: 31, Lines Deleted: 12; 2616 bytes
@@ -13316,19 +13316,29 @@
<xref linkend="myisam-table-problems"/>.
</para>
- <para>
- <emphasis role="bold">Warning:</emphasis> If the server dies
- during a <literal>REPAIR TABLE</literal> operation, it is
- essential after restarting it that you immediately execute
- another <literal>REPAIR TABLE</literal> statement for the
- table before performing any other operations on it. (It is
- always a good idea to start by making a backup.) In the worst
- case, you might have a new clean index file without
- information about the data file, and then the next operation
- you perform could overwrite the data file. This is an unlikely
- but possible scenario.
- </para>
+ <caution>
+ <para>
+ It is best to make a backup of a table before performing a
+ table repair operation; under some circumstances the
+ operation might cause data loss. Possible causes include but
+ are not limited to filesystem errors.
+ </para>
+ </caution>
+ <warning>
+ <para>
+ If the server dies during a <literal>REPAIR TABLE</literal>
+ operation, it is essential after restarting it that you
+ immediately execute another <literal>REPAIR TABLE</literal>
+ statement for the table before performing any other
+ operations on it. (It is always a good idea to start by
+ making a backup.) In the worst case, you might have a new
+ clean index file without information about the data file,
+ and then the next operation you perform could overwrite the
+ data file. This is an unlikely but possible scenario.
+ </para>
+ </warning>
+
<para>
<literal>REPAIR TABLE</literal> returns a result set with the
following columns:
@@ -18156,6 +18166,15 @@
</para>
</listitem>
+ <listitem>
+ <para>
+ If <literal>CHECK TABLE</literal> finds a problem for an
+ <literal>InnoDB</literal> table, the server shuts down to
+ prevent error propagation. Details of the error will be
+ written to the error log.
+ </para>
+ </listitem>
+
</itemizedlist>
</section>
Modified: trunk/refman-5.0/client-utility-programs.xml
===================================================================
--- trunk/refman-5.0/client-utility-programs.xml 2007-04-23 16:41:49 UTC (rev 6064)
+++ trunk/refman-5.0/client-utility-programs.xml 2007-04-23 17:15:28 UTC (rev 6065)
Changed blocks: 2, Lines Added: 18, Lines Deleted: 0; 1331 bytes
@@ -1259,6 +1259,15 @@
for storing data and indexes).
</para>
+ <caution>
+ <para>
+ It is best to make a backup of a table before performing a
+ table repair operation; under some circumstances the
+ operation might cause data loss. Possible causes include but
+ are not limited to filesystem errors.
+ </para>
+ </caution>
+
<para>
Invoke <command>myisamchk</command> like this:
</para>
@@ -9374,6 +9383,15 @@
note : The storage engine for the table doesn't support check
</programlisting>
+ <caution>
+ <para>
+ It is best to make a backup of a table before performing a
+ table repair operation; under some circumstances the
+ operation might cause data loss. Possible causes include but
+ are not limited to filesystem errors.
+ </para>
+ </caution>
+
<para>
There are three general ways to invoke
<command>mysqlcheck</command>:
Modified: trunk/refman-5.0/sql-syntax.xml
===================================================================
--- trunk/refman-5.0/sql-syntax.xml 2007-04-23 16:41:49 UTC (rev 6064)
+++ trunk/refman-5.0/sql-syntax.xml 2007-04-23 17:15:28 UTC (rev 6065)
Changed blocks: 2, Lines Added: 31, Lines Deleted: 12; 2616 bytes
@@ -14679,6 +14679,15 @@
</para>
</listitem>
+ <listitem>
+ <para>
+ If <literal>CHECK TABLE</literal> finds a problem for an
+ <literal>InnoDB</literal> table, the server shuts down to
+ prevent error propagation. Details of the error will be
+ written to the error log.
+ </para>
+ </listitem>
+
</itemizedlist>
</section>
@@ -14978,19 +14987,29 @@
<xref linkend="myisam-table-problems"/>.
</para>
- <para>
- <emphasis role="bold">Warning:</emphasis> If the server dies
- during a <literal>REPAIR TABLE</literal> operation, it is
- essential after restarting it that you immediately execute
- another <literal>REPAIR TABLE</literal> statement for the
- table before performing any other operations on it. (It is
- always a good idea to start by making a backup.) In the worst
- case, you might have a new clean index file without
- information about the data file, and then the next operation
- you perform could overwrite the data file. This is an unlikely
- but possible scenario.
- </para>
+ <caution>
+ <para>
+ It is best to make a backup of a table before performing a
+ table repair operation; under some circumstances the
+ operation might cause data loss. Possible causes include but
+ are not limited to filesystem errors.
+ </para>
+ </caution>
+ <warning>
+ <para>
+ If the server dies during a <literal>REPAIR TABLE</literal>
+ operation, it is essential after restarting it that you
+ immediately execute another <literal>REPAIR TABLE</literal>
+ statement for the table before performing any other
+ operations on it. (It is always a good idea to start by
+ making a backup.) In the worst case, you might have a new
+ clean index file without information about the data file,
+ and then the next operation you perform could overwrite the
+ data file. This is an unlikely but possible scenario.
+ </para>
+ </warning>
+
<para>
<literal>REPAIR TABLE</literal> returns a result set with the
following columns:
Modified: trunk/refman-5.1/client-utility-programs.xml
===================================================================
--- trunk/refman-5.1/client-utility-programs.xml 2007-04-23 16:41:49 UTC (rev 6064)
+++ trunk/refman-5.1/client-utility-programs.xml 2007-04-23 17:15:28 UTC (rev 6065)
Changed blocks: 2, Lines Added: 18, Lines Deleted: 0; 1331 bytes
@@ -1245,6 +1245,15 @@
for storing data and indexes).
</para>
+ <caution>
+ <para>
+ It is best to make a backup of a table before performing a
+ table repair operation; under some circumstances the
+ operation might cause data loss. Possible causes include but
+ are not limited to filesystem errors.
+ </para>
+ </caution>
+
<para>
Invoke <command>myisamchk</command> like this:
</para>
@@ -9422,6 +9431,15 @@
note : The storage engine for the table doesn't support check
</programlisting>
+ <caution>
+ <para>
+ It is best to make a backup of a table before performing a
+ table repair operation; under some circumstances the
+ operation might cause data loss. Possible causes include but
+ are not limited to filesystem errors.
+ </para>
+ </caution>
+
<para>
There are three general ways to invoke
<command>mysqlcheck</command>:
Modified: trunk/refman-5.1/sql-syntax.xml
===================================================================
--- trunk/refman-5.1/sql-syntax.xml 2007-04-23 16:41:49 UTC (rev 6064)
+++ trunk/refman-5.1/sql-syntax.xml 2007-04-23 17:15:28 UTC (rev 6065)
Changed blocks: 2, Lines Added: 31, Lines Deleted: 12; 2616 bytes
@@ -16542,6 +16542,15 @@
</para>
</listitem>
+ <listitem>
+ <para>
+ If <literal>CHECK TABLE</literal> finds a problem for an
+ <literal>InnoDB</literal> table, the server shuts down to
+ prevent error propagation. Details of the error will be
+ written to the error log.
+ </para>
+ </listitem>
+
</itemizedlist>
</section>
@@ -16837,19 +16846,29 @@
<xref linkend="myisam-table-problems"/>.
</para>
- <para>
- <emphasis role="bold">Warning:</emphasis> If the server dies
- during a <literal>REPAIR TABLE</literal> operation, it is
- essential after restarting it that you immediately execute
- another <literal>REPAIR TABLE</literal> statement for the
- table before performing any other operations on it. (It is
- always a good idea to start by making a backup.) In the worst
- case, you might have a new clean index file without
- information about the data file, and then the next operation
- you perform could overwrite the data file. This is an unlikely
- but possible scenario.
- </para>
+ <caution>
+ <para>
+ It is best to make a backup of a table before performing a
+ table repair operation; under some circumstances the
+ operation might cause data loss. Possible causes include but
+ are not limited to filesystem errors.
+ </para>
+ </caution>
+ <warning>
+ <para>
+ If the server dies during a <literal>REPAIR TABLE</literal>
+ operation, it is essential after restarting it that you
+ immediately execute another <literal>REPAIR TABLE</literal>
+ statement for the table before performing any other
+ operations on it. (It is always a good idea to start by
+ making a backup.) In the worst case, you might have a new
+ clean index file without information about the data file,
+ and then the next operation you perform could overwrite the
+ data file. This is an unlikely but possible scenario.
+ </para>
+ </warning>
+
<para>
<literal>REPAIR TABLE</literal> returns a result set with the
following columns:
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r6065 - in trunk: . refman-4.1 refman-5.0 refman-5.1 | paul | 23 Apr |
