Author: jstephens
Date: 2005-11-23 12:35:12 +0100 (Wed, 23 Nov 2005)
New Revision: 397
Log:
InnoDB chapter (5.0/5.1):
Change SHOW INNODB STATUS to SHOW ENGINE INNODB STATUS (Hartmut)
Modified:
trunk/refman-5.0/innodb.xml
trunk/refman-5.1/innodb.xml
Modified: trunk/refman-5.0/innodb.xml
===================================================================
--- trunk/refman-5.0/innodb.xml 2005-11-23 11:06:53 UTC (rev 396)
+++ trunk/refman-5.0/innodb.xml 2005-11-23 11:35:12 UTC (rev 397)
@@ -1376,7 +1376,7 @@
<para>
This option causes <literal>InnoDB</literal> to create a file
<filename><replaceable><datadir></replaceable>/innodb_status.<replaceable><pid></replaceable></filename>
- for periodical <literal>SHOW INNODB STATUS</literal> output.
+ for periodical <literal>SHOW ENGINE INNODB STATUS</literal> output.
</para>
</listitem>
@@ -2749,7 +2749,7 @@
<listitem>
<para>
- Wait until <literal>SHOW INNODB STATUS</literal> shows that
+ Wait until <literal>SHOW ENGINE INNODB STATUS</literal> shows that
there are no active transactions in the database, and the
main thread status of <literal>InnoDB</literal> is
<literal>Waiting for server activity</literal>. Then you can
@@ -4468,7 +4468,7 @@
<listitem>
<para>
- Use <literal>SHOW INNODB STATUS</literal> to determine the
+ Use <literal>SHOW ENGINE INNODB STATUS</literal> to determine the
cause of the latest deadlock. That can help you to tune your
application to avoid deadlocks.
</para>
@@ -4836,7 +4836,7 @@
<literal>InnoDB</literal> includes <literal>InnoDB</literal>
Monitors that print information about the
<literal>InnoDB</literal> internal state. You can use the SQL
- statement <literal>SHOW INNODB STATUS</literal> to fetch the
+ statement <literal>SHOW ENGINE INNODB STATUS</literal> to fetch the
output of the standard <literal>InnoDB</literal> Monitor to your
SQL client. This information is useful in performance tuning.
(If you are using the <command>mysql</command> interactive SQL
@@ -4847,7 +4847,7 @@
</para>
<programlisting>
-mysql> <userinput>SHOW INNODB STATUS\G</userinput>
+mysql> <userinput>SHOW ENGINE INNODB STATUS\G</userinput>
</programlisting>
<para>
@@ -4959,7 +4959,7 @@
</para>
<programlisting>
-mysql> <userinput>SHOW INNODB STATUS\G</userinput>
+mysql> <userinput>SHOW ENGINE INNODB STATUS\G</userinput>
*************************** 1. row ***************************
Status:
=====================================
@@ -5189,7 +5189,7 @@
<literal>stderr</literal> or to files rather than to
<literal>stdout</literal> or fixed-size memory buffers, in order
to avoid potential buffer overflows. As a side effect, the
- output of <literal>SHOW INNODB STATUS</literal> is written to a
+ output of <literal>SHOW ENGINE INNODB STATUS</literal> is written to a
status file every fifteen seconds. The name of the file is
<filename>innodb_status.<replaceable>pid</replaceable></filename>,
where <replaceable>pid</replaceable> is the server process ID.
Modified: trunk/refman-5.1/innodb.xml
===================================================================
--- trunk/refman-5.1/innodb.xml 2005-11-23 11:06:53 UTC (rev 396)
+++ trunk/refman-5.1/innodb.xml 2005-11-23 11:35:12 UTC (rev 397)
@@ -1354,7 +1354,7 @@
<para>
This option causes <literal>InnoDB</literal> to create a file
<filename><replaceable><datadir></replaceable>/innodb_status.<replaceable><pid></replaceable></filename>
- for periodical <literal>SHOW INNODB STATUS</literal> output.
+ for periodical <literal>SHOW ENGINE INNODB STATUS</literal> output.
</para>
</listitem>
@@ -1417,7 +1417,7 @@
operating system threads concurrently inside
<literal>InnoDB</literal> less than or equal to the limit
given by this parameter. If you have performance issues, and
- <literal>SHOW INNODB STATUS</literal> reveals many threads
+ <literal>SHOW ENGINE INNODB STATUS</literal> reveals many threads
waiting for semaphores, you may have thread
<quote>thrashing</quote> and should try setting this parameter
lower or higher. If you have a computer with many processors
@@ -2724,7 +2724,7 @@
<listitem>
<para>
- Wait until <literal>SHOW INNODB STATUS</literal> shows that
+ Wait until <literal>SHOW ENGINE INNODB STATUS</literal> shows that
there are no active transactions in the database, and the
main thread status of <literal>InnoDB</literal> is
<literal>Waiting for server activity</literal>. Then you can
@@ -4428,7 +4428,7 @@
<listitem>
<para>
- Use <literal>SHOW INNODB STATUS</literal> to determine the
+ Use <literal>SHOW ENGINE INNODB STATUS</literal> to determine the
cause of the latest deadlock. That can help you to tune your
application to avoid deadlocks.
</para>
@@ -4796,7 +4796,7 @@
<literal>InnoDB</literal> includes <literal>InnoDB</literal>
Monitors that print information about the
<literal>InnoDB</literal> internal state. You can use the SQL
- statement <literal>SHOW INNODB STATUS</literal> to fetch the
+ statement <literal>SHOW ENGINE INNODB STATUS</literal> to fetch the
output of the standard <literal>InnoDB</literal> Monitor to your
SQL client. This information is useful in performance tuning.
(If you are using the <command>mysql</command> interactive SQL
@@ -4807,7 +4807,7 @@
</para>
<programlisting>
-mysql> <userinput>SHOW INNODB STATUS\G</userinput>
+mysql> <userinput>SHOW ENGINE INNODB STATUS\G</userinput>
</programlisting>
<para>
@@ -4919,7 +4919,7 @@
</para>
<programlisting>
-mysql> <userinput>SHOW INNODB STATUS\G</userinput>
+mysql> <userinput>SHOW ENGINE INNODB STATUS\G</userinput>
*************************** 1. row ***************************
Status:
=====================================
@@ -5149,7 +5149,7 @@
<literal>stderr</literal> or to files rather than to
<literal>stdout</literal> or fixed-size memory buffers, in order
to avoid potential buffer overflows. As a side effect, the
- output of <literal>SHOW INNODB STATUS</literal> is written to a
+ output of <literal>SHOW ENGINE INNODB STATUS</literal> is written to a
status file every fifteen seconds. The name of the file is
<filename>innodb_status.<replaceable>pid</replaceable></filename>,
where <replaceable>pid</replaceable> is the server process ID.
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r397 - in trunk: refman-5.0 refman-5.1 | jstephens | 23 Nov |
