Author: jdrussel
Date: 2011-06-13 05:54:22 +0200 (Mon, 13 Jun 2011)
New Revision: 26491
Log:
Clarified which parts of forcing-innodb-recovery happen automatically rather than the user
doing them.
Modified:
trunk/refman-5.6/se-innodb-core.xml
Modified: trunk/refman-5.6/se-innodb-core.xml
===================================================================
--- trunk/refman-5.6/se-innodb-core.xml 2011-06-10 18:21:06 UTC (rev 26490)
+++ trunk/refman-5.6/se-innodb-core.xml 2011-06-13 03:54:22 UTC (rev 26491)
Changed blocks: 8, Lines Added: 16, Lines Deleted: 17; 4107 bytes
@@ -3886,15 +3886,14 @@
</indexterm>
<para>
- If there is database page corruption, you may want to dump
- your tables from the database with <literal>SELECT INTO ...
+ To investigate database page corruption, you might dump your
+ tables from the database with <literal>SELECT INTO ...
OUTFILE</literal>. Usually, most of the data obtained in this
- way is intact. However, it is possible that the corruption
- might cause <literal>SELECT * FROM
- <replaceable>tbl_name</replaceable></literal> statements or
- <literal>InnoDB</literal> background operations to crash or
- assert, or even cause <literal>InnoDB</literal> roll-forward
- recovery to crash. In such cases, you can use the
+ way is intact. Serious corruption might cause <literal>SELECT
+ * FROM <replaceable>tbl_name</replaceable></literal>
+ statements or <literal>InnoDB</literal> background operations
+ to crash or assert, or even cause <literal>InnoDB</literal>
+ roll-forward recovery to crash. In such cases, use the
<literal role="sysvar">innodb_force_recovery</literal> option
to force the <literal>InnoDB</literal> storage engine to start
up while preventing background operations from running, so
@@ -3910,7 +3909,7 @@
<para>
<literal role="sysvar">innodb_force_recovery</literal> is 0 by
- default (normal startup without forced recovery) The
+ default (normal startup without forced recovery). The
permissible nonzero values for
<literal role="sysvar">innodb_force_recovery</literal> follow.
A larger number includes all precautions of smaller numbers.
@@ -3931,8 +3930,8 @@
</para>
<para>
- Let the server run even if it detects a corrupt page. Try
- to make <literal>SELECT * FROM
+ Lets the server run even if it detects a corrupt page.
+ Tries to make <literal>SELECT * FROM
<replaceable>tbl_name</replaceable></literal> jump over
corrupt index records and pages, which helps in dumping
tables.
@@ -3948,7 +3947,7 @@
<!-- JDR: question posed to the InnoDB team: does separate purge thread(s) mean a change in operation for the '2' value? -->
<para>
- Prevent the main thread from running. If a crash would
+ Prevents the main thread from running. If a crash would
occur during the purge operation, this recovery value
prevents it.
</para>
@@ -3961,7 +3960,7 @@
</para>
<para>
- Do not run transaction rollbacks after recovery.
+ Does not run transaction rollbacks after recovery.
</para>
</listitem>
@@ -3972,8 +3971,8 @@
</para>
<para>
- Prevent insert buffer merge operations. If they would
- cause a crash, do not do them. Do not calculate table
+ Prevents insert buffer merge operations. If they would
+ cause a crash, does not do them. Does not calculate table
statistics.
</para>
</listitem>
@@ -3985,7 +3984,7 @@
</para>
<para>
- Do not look at undo logs when starting the database:
+ Does not look at undo logs when starting the database:
<literal>InnoDB</literal> treats even incomplete
transactions as committed.
</para>
@@ -3998,7 +3997,7 @@
</para>
<para>
- Do not do the log roll-forward in connection with
+ Does not do the log roll-forward in connection with
recovery.
</para>
| Thread |
|---|
| • svn commit - mysqldoc@oter02: r26491 - trunk/refman-5.6 | john.russell | 13 Jun |
