Author: mcbrown
Date: 2007-10-14 19:10:06 +0200 (Sun, 14 Oct 2007)
New Revision: 8086
Log:
Fixing some admonitions
Modified:
trunk/refman-4.1/se-innodb.xml
trunk/refman-5.0/se-innodb.xml
trunk/refman-5.1/se-innodb.xml
trunk/refman-5.2/se-innodb.xml
Modified: trunk/refman-4.1/se-innodb.xml
===================================================================
--- trunk/refman-4.1/se-innodb.xml 2007-10-14 17:09:40 UTC (rev 8085)
+++ trunk/refman-4.1/se-innodb.xml 2007-10-14 17:10:06 UTC (rev 8086)
Changed blocks: 4, Lines Added: 40, Lines Deleted: 33; 4819 bytes
@@ -1402,15 +1402,21 @@
</para>
<para>
- The crash recovery mode. Warning: This variable should be set
- greater than 0 only in an emergency situation when you want to
- dump your tables from a corrupt database! Possible values are
- from 1 to 6. The meanings of these values are described in
- <xref linkend="forcing-recovery"/>. As a safety measure,
- <literal>InnoDB</literal> prevents any changes to its data
- when this variable is greater than 0. This variable is
- available starting from MySQL 3.23.44.
+ The crash recovery mode.
</para>
+
+ <warning>
+ <para>
+ This variable should be set greater than 0 only in an
+ emergency situation when you want to dump your tables from a
+ corrupt database! Possible values are from 1 to 6. The
+ meanings of these values are described in
+ <xref linkend="forcing-recovery"/>. As a safety measure,
+ <literal>InnoDB</literal> prevents any changes to its data
+ when this variable is greater than 0. This variable is
+ available starting from MySQL 3.23.44.
+ </para>
+ </warning>
</listitem>
<listitem>
@@ -7054,31 +7060,32 @@
<itemizedlist>
<listitem>
- <para>
- <indexterm>
- <primary>NFS</primary>
- <secondary>InnoDB</secondary>
- </indexterm>
-
- <indexterm>
- <primary>InnoDB</primary>
- <secondary>NFS</secondary>
- </indexterm>
-
- <emphasis role="bold">Warning:</emphasis> Do
- <emphasis>not</emphasis> convert MySQL system tables in the
- <literal>mysql</literal> database from
- <literal>MyISAM</literal> to <literal>InnoDB</literal> tables!
- This is an unsupported operation. If you do this, MySQL does
- not restart until you restore the old system tables from a
- backup or re-generate them with the
- <command>mysql_install_db</command> script.
- </para>
+ <warning>
+ <para>
+ Do <emphasis>not</emphasis> convert MySQL system tables in
+ the <literal>mysql</literal> database from
+ <literal>MyISAM</literal> to <literal>InnoDB</literal>
+ tables! This is an unsupported operation. If you do this,
+ MySQL does not restart until you restore the old system
+ tables from a backup or re-generate them with the
+ <command>mysql_install_db</command> script.
+ </para>
+ </warning>
</listitem>
<listitem>
<warning>
<para>
+ <indexterm>
+ <primary>NFS</primary>
+ <secondary>InnoDB</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>InnoDB</primary>
+ <secondary>NFS</secondary>
+ </indexterm>
+
It is not a good idea to configure <literal>InnoDB</literal>
to use datafiles or logfiles on NFS volumes. Otherwise, the
files might be locked by other processes and become
@@ -7596,9 +7603,9 @@
With <literal>innodb_table_monitor</literal> you see a table
whose name is <filename>#sql-...</filename>. Starting from MySQL
4.0.6, you can perform SQL statements also on tables whose name
- contains the character <quote><literal>#</literal></quote> if you
- enclose the name within backticks. Thus, you can drop such an
- orphaned table like any other orphaned table using the method
+ contains the character <quote><literal>#</literal></quote> if
+ you enclose the name within backticks. Thus, you can drop such
+ an orphaned table like any other orphaned table using the method
described earlier. Note that to copy or rename a file in the
Unix shell, you need to put the file name in double quotes if
the file name contains <quote><literal>#</literal></quote>.
@@ -7606,8 +7613,8 @@
<para>
Older MySQL versions did not allow accessing any table with a
- name containing <quote><literal>#</literal></quote>. The solution
- in older MySQL versions is to use a special
+ name containing <quote><literal>#</literal></quote>. The
+ solution in older MySQL versions is to use a special
<literal>InnoDB</literal> mechanism available starting from
MySQL 3.23.48. When you have an orphaned table
<filename>#sql-id</filename> inside the tablespace, you can
Modified: trunk/refman-5.0/se-innodb.xml
===================================================================
--- trunk/refman-5.0/se-innodb.xml 2007-10-14 17:09:40 UTC (rev 8085)
+++ trunk/refman-5.0/se-innodb.xml 2007-10-14 17:10:06 UTC (rev 8086)
Changed blocks: 2, Lines Added: 36, Lines Deleted: 27; 3300 bytes
@@ -1352,14 +1352,20 @@
</para>
<para>
- The crash recovery mode. Warning: This variable should be set
- greater than 0 only in an emergency situation when you want to
- dump your tables from a corrupt database! Possible values are
- from 1 to 6. The meanings of these values are described in
- <xref linkend="forcing-recovery"/>. As a safety measure,
- <literal>InnoDB</literal> prevents any changes to its data
- when this variable is greater than 0.
+ The crash recovery mode.
</para>
+
+ <warning>
+ <para>
+ This variable should be set greater than 0 only in an
+ emergency situation when you want to dump your tables from a
+ corrupt database! Possible values are from 1 to 6. The
+ meanings of these values are described in
+ <xref linkend="forcing-recovery"/>. As a safety measure,
+ <literal>InnoDB</literal> prevents any changes to its data
+ when this variable is greater than 0.
+ </para>
+ </warning>
</listitem>
<listitem>
@@ -7196,29 +7202,32 @@
<itemizedlist>
<listitem>
- <para>
- <indexterm>
- <primary>NFS</primary>
- <secondary>InnoDB</secondary>
- </indexterm>
+ <warning>
+ <para>
+ Do <emphasis>not</emphasis> convert MySQL system tables in
+ the <literal>mysql</literal> database from
+ <literal>MyISAM</literal> to <literal>InnoDB</literal>
+ tables! This is an unsupported operation. If you do this,
+ MySQL does not restart until you restore the old system
+ tables from a backup or re-generate them with the
+ <command>mysql_install_db</command> script.
+ </para>
+ </warning>
+ </listitem>
- <indexterm>
- <primary>InnoDB</primary>
- <secondary>NFS</secondary>
- </indexterm>
+ <listitem>
+ <warning>
+ <para>
+ <indexterm>
+ <primary>NFS</primary>
+ <secondary>InnoDB</secondary>
+ </indexterm>
- <emphasis role="bold">Warning:</emphasis> Do
- <emphasis>not</emphasis> convert MySQL system tables in the
- <literal>mysql</literal> database from
- <literal>MyISAM</literal> to <literal>InnoDB</literal> tables!
- This is an unsupported operation. If you do this, MySQL does
- not restart until you restore the old system tables from a
- backup or re-generate them with the
- <command>mysql_install_db</command> script.
- </para>
+ <indexterm>
+ <primary>InnoDB</primary>
+ <secondary>NFS</secondary>
+ </indexterm>
- <warning>
- <para>
It is not a good idea to configure <literal>InnoDB</literal>
to use datafiles or logfiles on NFS volumes. Otherwise, the
files might be locked by other processes and become
Modified: trunk/refman-5.1/se-innodb.xml
===================================================================
--- trunk/refman-5.1/se-innodb.xml 2007-10-14 17:09:40 UTC (rev 8085)
+++ trunk/refman-5.1/se-innodb.xml 2007-10-14 17:10:06 UTC (rev 8086)
Changed blocks: 2, Lines Added: 36, Lines Deleted: 27; 3300 bytes
@@ -1367,14 +1367,20 @@
</para>
<para>
- The crash recovery mode. Warning: This variable should be set
- greater than 0 only in an emergency situation when you want to
- dump your tables from a corrupt database! Possible values are
- from 1 to 6. The meanings of these values are described in
- <xref linkend="forcing-recovery"/>. As a safety measure,
- <literal>InnoDB</literal> prevents any changes to its data
- when this variable is greater than 0.
+ The crash recovery mode.
</para>
+
+ <warning>
+ <para>
+ This variable should be set greater than 0 only in an
+ emergency situation when you want to dump your tables from a
+ corrupt database! Possible values are from 1 to 6. The
+ meanings of these values are described in
+ <xref linkend="forcing-recovery"/>. As a safety measure,
+ <literal>InnoDB</literal> prevents any changes to its data
+ when this variable is greater than 0.
+ </para>
+ </warning>
</listitem>
<listitem>
@@ -7886,29 +7892,32 @@
<itemizedlist>
<listitem>
- <para>
- <indexterm>
- <primary>NFS</primary>
- <secondary>InnoDB</secondary>
- </indexterm>
+ <warning>
+ <para>
+ Do <emphasis>not</emphasis> convert MySQL system tables in
+ the <literal>mysql</literal> database from
+ <literal>MyISAM</literal> to <literal>InnoDB</literal>
+ tables! This is an unsupported operation. If you do this,
+ MySQL does not restart until you restore the old system
+ tables from a backup or re-generate them with the
+ <command>mysql_install_db</command> script.
+ </para>
+ </warning>
+ </listitem>
- <indexterm>
- <primary>InnoDB</primary>
- <secondary>NFS</secondary>
- </indexterm>
+ <listitem>
+ <warning>
+ <para>
+ <indexterm>
+ <primary>NFS</primary>
+ <secondary>InnoDB</secondary>
+ </indexterm>
- <emphasis role="bold">Warning:</emphasis> Do
- <emphasis>not</emphasis> convert MySQL system tables in the
- <literal>mysql</literal> database from
- <literal>MyISAM</literal> to <literal>InnoDB</literal> tables!
- This is an unsupported operation. If you do this, MySQL does
- not restart until you restore the old system tables from a
- backup or re-generate them with the
- <command>mysql_install_db</command> script.
- </para>
+ <indexterm>
+ <primary>InnoDB</primary>
+ <secondary>NFS</secondary>
+ </indexterm>
- <warning>
- <para>
It is not a good idea to configure <literal>InnoDB</literal>
to use datafiles or logfiles on NFS volumes. Otherwise, the
files might be locked by other processes and become
Modified: trunk/refman-5.2/se-innodb.xml
===================================================================
--- trunk/refman-5.2/se-innodb.xml 2007-10-14 17:09:40 UTC (rev 8085)
+++ trunk/refman-5.2/se-innodb.xml 2007-10-14 17:10:06 UTC (rev 8086)
Changed blocks: 2, Lines Added: 36, Lines Deleted: 27; 3300 bytes
@@ -1365,14 +1365,20 @@
</para>
<para>
- The crash recovery mode. Warning: This variable should be set
- greater than 0 only in an emergency situation when you want to
- dump your tables from a corrupt database! Possible values are
- from 1 to 6. The meanings of these values are described in
- <xref linkend="forcing-recovery"/>. As a safety measure,
- <literal>InnoDB</literal> prevents any changes to its data
- when this variable is greater than 0.
+ The crash recovery mode.
</para>
+
+ <warning>
+ <para>
+ This variable should be set greater than 0 only in an
+ emergency situation when you want to dump your tables from a
+ corrupt database! Possible values are from 1 to 6. The
+ meanings of these values are described in
+ <xref linkend="forcing-recovery"/>. As a safety measure,
+ <literal>InnoDB</literal> prevents any changes to its data
+ when this variable is greater than 0.
+ </para>
+ </warning>
</listitem>
<listitem>
@@ -7859,29 +7865,32 @@
<itemizedlist>
<listitem>
- <para>
- <indexterm>
- <primary>NFS</primary>
- <secondary>InnoDB</secondary>
- </indexterm>
+ <warning>
+ <para>
+ Do <emphasis>not</emphasis> convert MySQL system tables in
+ the <literal>mysql</literal> database from
+ <literal>MyISAM</literal> to <literal>InnoDB</literal>
+ tables! This is an unsupported operation. If you do this,
+ MySQL does not restart until you restore the old system
+ tables from a backup or re-generate them with the
+ <command>mysql_install_db</command> script.
+ </para>
+ </warning>
+ </listitem>
- <indexterm>
- <primary>InnoDB</primary>
- <secondary>NFS</secondary>
- </indexterm>
+ <listitem>
+ <warning>
+ <para>
+ <indexterm>
+ <primary>NFS</primary>
+ <secondary>InnoDB</secondary>
+ </indexterm>
- <emphasis role="bold">Warning:</emphasis> Do
- <emphasis>not</emphasis> convert MySQL system tables in the
- <literal>mysql</literal> database from
- <literal>MyISAM</literal> to <literal>InnoDB</literal> tables!
- This is an unsupported operation. If you do this, MySQL does
- not restart until you restore the old system tables from a
- backup or re-generate them with the
- <command>mysql_install_db</command> script.
- </para>
+ <indexterm>
+ <primary>InnoDB</primary>
+ <secondary>NFS</secondary>
+ </indexterm>
- <warning>
- <para>
It is not a good idea to configure <literal>InnoDB</literal>
to use datafiles or logfiles on NFS volumes. Otherwise, the
files might be locked by other processes and become
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r8086 - in trunk: refman-4.1 refman-5.0 refman-5.1 refman-5.2 | mcbrown | 14 Oct |
