Author: paul
Date: 2007-08-29 18:33:50 +0200 (Wed, 29 Aug 2007)
New Revision: 7586
Log:
r24367@frost: paul | 2007-08-29 10:37:19 -0500
Additional revisions to log table section.
Modified:
trunk/refman-5.1/dba-core.xml
trunk/refman-5.2/dba-core.xml
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:29523
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:24356
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:20005
+ 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:29523
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:24367
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:20005
Modified: trunk/refman-5.1/dba-core.xml
===================================================================
--- trunk/refman-5.1/dba-core.xml 2007-08-29 16:14:44 UTC (rev 7585)
+++ trunk/refman-5.1/dba-core.xml 2007-08-29 16:33:50 UTC (rev 7586)
Changed blocks: 5, Lines Added: 82, Lines Deleted: 87; 8832 bytes
@@ -28446,14 +28446,14 @@
<title>Selecting General Query and Slow Query Log Output Destinations</title>
<para>
- Before MySQL 5.1.6, the server uses log files as the destination
- for general query log and slow query log entries, if those logs
- are enabled. As of MySQL 5.1.6, the server provides more
- flexible control over the destination for log output. Log
- entries can be written to log files (as before) or to the
- <literal>general_log</literal> and <literal>slow_log</literal>
- tables in the <literal>mysql</literal> database. If logging is
- enabled, either or both destinations can be selected.
+ As of MySQL 5.1.6, the server provides flexible control over the
+ destination for log output. Log entries can be written to log
+ files to the <literal>general_log</literal> and
+ <literal>slow_log</literal> tables in the
+ <literal>mysql</literal> database. If logging is enabled, either
+ or both destinations can be selected. (Before MySQL 5.1.6, the
+ server uses only log files as the destination for general query
+ log and slow query log entries, if those logs are enabled.)
</para>
<note>
@@ -28644,72 +28644,9 @@
</itemizedlist>
<para>
- By default, the log tables use the <literal>CSV</literal>
- storage engine that writes data in comma-separated values
- format. For users who have access to the
- <filename>.CSV</filename> files that contain log table data, the
- files are easy to import into other programs such as
- spreadsheets that can process CSV input.
+ The log table implementation has the following characteristics:
</para>
- <para>
- Beginning with MySQL 5.1.12, the log tables can be altered to
- use the <literal>MyISAM</literal> storage engine. You cannot use
- <literal>ALTER TABLE</literal> to alter a log table that is in
- use. The log must be disabled first. No engines other than
- <literal>CSV</literal> or <literal>MyISAM</literal> are legal
- for the log tables.
- </para>
-
- <para>
- Log entries can be expired by using <literal>TRUNCATE
- TABLE</literal>. However, <literal>DROP TABLE</literal> cannot
- be used to drop a log table that is in use. The log must be
- disabled first.
- </para>
-
- <para>
- To disable logging so that you can modify a log table, you can
- use the following strategy. The example uses the general query
- log; the procedure for the slow query log is similar but uses
- the <literal>slow_log</literal> table and
- <literal>slow_query_log</literal> system variable.
- </para>
-
-<programlisting>
-SET @old_log_state = @@global.general_log;
-SET GLOBAL general_log = 'OFF';
-ALTER TABLE mysql.general_log ENGINE = MyISAM;
-SET GLOBAL general_log = @old_log_state;
-</programlisting>
-
- <para>
- Entries written to the log tables are not written to the binary
- log and thus are not replicated to slave servers.
- </para>
-
- <para>
- Beginning with MySQL 5.1.13, you can atomically rename a log
- table (to perform log rotation, for example) using the following
- strategy:
- </para>
-
-<programlisting>
-USE mysql;
-CREATE TABLE IF NOT EXISTS general_log2 LIKE general_log;
-RENAME TABLE general_log TO general_log_backup, general_log2 TO general_log;
-</programlisting>
-
- <para>
- It is not recommended to partition log tables, and doing so is
- not allowed beginning with MySQL 5.1.20.
- </para>
-
- <para>
- In MySQL 5.1.21, log table implementation was revised to provide
- more well-defined interface characteristics:
- </para>
-
<itemizedlist>
<listitem>
@@ -28722,41 +28659,76 @@
<listitem>
<para>
- The global read lock and the state of the global
- <literal>read_only</literal> system variable have no effect
- on log tables. The server can always write to the log
- tables.
+ <literal>CREATE TABLE</literal>, <literal>ALTER
+ TABLE</literal>, and <literal>DROP TABLE</literal> are valid
+ operations on a log table. For <literal>ALTER
+ TABLE</literal> and <literal>DROP TABLE</literal>, the log
+ table cannot be in use and must be disabled, as described
+ later.
</para>
</listitem>
<listitem>
<para>
- <literal>TRUNCATE TABLE</literal> is a valid operation on a
- log table, as previously mentioned.
+ By default, the log tables use the <literal>CSV</literal>
+ storage engine that writes data in comma-separated values
+ format. For users who have access to the
+ <filename>.CSV</filename> files that contain log table data,
+ the files are easy to import into other programs such as
+ spreadsheets that can process CSV input.
</para>
+
+ <para>
+ Beginning with MySQL 5.1.12, the log tables can be altered
+ to use the <literal>MyISAM</literal> storage engine. You
+ cannot use <literal>ALTER TABLE</literal> to alter a log
+ table that is in use. The log must be disabled first. No
+ engines other than <literal>CSV</literal> or
+ <literal>MyISAM</literal> are legal for the log tables.
+ </para>
</listitem>
<listitem>
<para>
- <literal>RENAME TABLE</literal> is a valid operation on a
- log table and can be used atomcally for log rotation, as
- previously described.
+ To disable logging so that you can alter (or drop) a log
+ table, you can use the following strategy. The example uses
+ the general query log; the procedure for the slow query log
+ is similar but uses the <literal>slow_log</literal> table
+ and <literal>slow_query_log</literal> system variable.
</para>
+
+<programlisting>
+SET @old_log_state = @@global.general_log;
+SET GLOBAL general_log = 'OFF';
+ALTER TABLE mysql.general_log ENGINE = MyISAM;
+SET GLOBAL general_log = @old_log_state;
+</programlisting>
</listitem>
<listitem>
<para>
- <literal>CREATE TABLE</literal>, <literal>ALTER
- TABLE</literal>, and <literal>DROP TABLE</literal> are valid
- operations on a log table. For <literal>ALTER
- TABLE</literal> and <literal>DROP TABLE</literal>, the log
- table cannot be in use and must be disabled, as previously
- described.
+ <literal>TRUNCATE TABLE</literal> is a valid operation on a
+ log table. It can be used to expire log entries.
</para>
</listitem>
<listitem>
<para>
+ As of MySQL 5.1.13, <literal>RENAME TABLE</literal> is a
+ valid operation on a log table. You can atomically rename a
+ log table (to perform log rotation, for example) using the
+ following strategy:
+ </para>
+
+<programlisting>
+USE mysql;
+CREATE TABLE IF NOT EXISTS general_log2 LIKE general_log;
+RENAME TABLE general_log TO general_log_backup, general_log2 TO general_log;
+</programlisting>
+ </listitem>
+
+ <listitem>
+ <para>
<literal>LOCK TABLES</literal> cannot be used on a log
table.
</para>
@@ -28773,6 +28745,22 @@
<listitem>
<para>
+ The global read lock and the state of the global
+ <literal>read_only</literal> system variable have no effect
+ on log tables. The server can always write to the log
+ tables.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Entries written to the log tables are not written to the
+ binary log and thus are not replicated to slave servers.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
To flush the log tables or log files, use <literal>FLUSH
TABLES</literal> or <literal>FLUSH LOGS</literal>,
respectively. (From MySQL 5.1.12 to 5.1.20, <literal>FLUSH
@@ -28781,6 +28769,13 @@
</para>
</listitem>
+ <listitem>
+ <para>
+ It is not recommended to partition log tables, and doing so
+ is not allowed beginning with MySQL 5.1.20.
+ </para>
+ </listitem>
+
</itemizedlist>
</section>
Modified: trunk/refman-5.2/dba-core.xml
===================================================================
--- trunk/refman-5.2/dba-core.xml 2007-08-29 16:14:44 UTC (rev 7585)
+++ trunk/refman-5.2/dba-core.xml 2007-08-29 16:33:50 UTC (rev 7586)
Changed blocks: 4, Lines Added: 76, Lines Deleted: 82; 7972 bytes
@@ -28290,11 +28290,10 @@
<para>
MySQL Server provides flexible control over the destination for
- log output. Log entries can be written to log files (as before)
- or to the <literal>general_log</literal> and
- <literal>slow_log</literal> tables in the
- <literal>mysql</literal> database. If logging is enabled, either
- or both destinations can be selected.
+ log output. Log entries can be written to log files or to the
+ <literal>general_log</literal> and <literal>slow_log</literal>
+ tables in the <literal>mysql</literal> database. If logging is
+ enabled, either or both destinations can be selected.
</para>
<note>
@@ -28484,70 +28483,9 @@
</itemizedlist>
<para>
- By default, the log tables use the <literal>CSV</literal>
- storage engine that writes data in comma-separated values
- format. For users who have access to the
- <filename>.CSV</filename> files that contain log table data, the
- files are easy to import into other programs such as
- spreadsheets that can process CSV input.
+ The log table implementation has the following characteristics:
</para>
- <para>
- The log tables can be altered to use the
- <literal>MyISAM</literal> storage engine. You cannot use
- <literal>ALTER TABLE</literal> to alter a log table that is in
- use. The log must be disabled first. No engines other than
- <literal>CSV</literal> or <literal>MyISAM</literal> are legal
- for the log tables.
- </para>
-
- <para>
- Log entries can be expired by using <literal>TRUNCATE
- TABLE</literal>. However, <literal>DROP TABLE</literal> cannot
- be used to drop a log table that is in use. The log must be
- disabled first.
- </para>
-
- <para>
- To disable logging so that you can modify a log table, you can
- use the following strategy. The example uses the general query
- log; the procedure for the slow query log is similar but uses
- the <literal>slow_log</literal> table and
- <literal>slow_query_log</literal> system variable.
- </para>
-
-<programlisting>
-SET @old_log_state = @@global.general_log;
-SET GLOBAL general_log = 'OFF';
-ALTER TABLE mysql.general_log ENGINE = MyISAM;
-SET GLOBAL general_log = @old_log_state;
-</programlisting>
-
- <para>
- Entries written to the log tables are not written to the binary
- log and thus are not replicated to slave servers.
- </para>
-
- <para>
- You can atomically rename a log table (to perform log rotation,
- for example) using the following strategy:
- </para>
-
-<programlisting>
-USE mysql;
-CREATE TABLE IF NOT EXISTS general_log2 LIKE general_log;
-RENAME TABLE general_log TO general_log_backup, general_log2 TO general_log;
-</programlisting>
-
- <para>
- It is not allowed to partition log tables.
- </para>
-
- <para>
- In MySQL 5.1.21, log table implementation was revised to provide
- more well-defined interface characteristics:
- </para>
-
<itemizedlist>
<listitem>
@@ -28560,41 +28498,75 @@
<listitem>
<para>
- The global read lock and the state of the global
- <literal>read_only</literal> system variable have no effect
- on log tables. The server can always write to the log
- tables.
+ <literal>CREATE TABLE</literal>, <literal>ALTER
+ TABLE</literal>, and <literal>DROP TABLE</literal> are valid
+ operations on a log table. For <literal>ALTER
+ TABLE</literal> and <literal>DROP TABLE</literal>, the log
+ table cannot be in use and must be disabled, as described
+ later.
</para>
</listitem>
<listitem>
<para>
- <literal>TRUNCATE TABLE</literal> is a valid operation on a
- log table, as previously mentioned.
+ By default, the log tables use the <literal>CSV</literal>
+ storage engine that writes data in comma-separated values
+ format. For users who have access to the
+ <filename>.CSV</filename> files that contain log table data,
+ the files are easy to import into other programs such as
+ spreadsheets that can process CSV input.
</para>
+
+ <para>
+ The log tables can be altered to use the
+ <literal>MyISAM</literal> storage engine. You cannot use
+ <literal>ALTER TABLE</literal> to alter a log table that is
+ in use. The log must be disabled first. No engines other
+ than <literal>CSV</literal> or <literal>MyISAM</literal> are
+ legal for the log tables.
+ </para>
</listitem>
<listitem>
<para>
- <literal>RENAME TABLE</literal> is a valid operation on a
- log table and can be used atomcally for log rotation, as
- previously described.
+ To disable logging so that you can alter (or drop) a log
+ table, you can use the following strategy. The example uses
+ the general query log; the procedure for the slow query log
+ is similar but uses the <literal>slow_log</literal> table
+ and <literal>slow_query_log</literal> system variable.
</para>
+
+<programlisting>
+SET @old_log_state = @@global.general_log;
+SET GLOBAL general_log = 'OFF';
+ALTER TABLE mysql.general_log ENGINE = MyISAM;
+SET GLOBAL general_log = @old_log_state;
+</programlisting>
</listitem>
<listitem>
<para>
- <literal>CREATE TABLE</literal>, <literal>ALTER
- TABLE</literal>, and <literal>DROP TABLE</literal> are valid
- operations on a log table. For <literal>ALTER
- TABLE</literal> and <literal>DROP TABLE</literal>, the log
- table cannot be in use and must be disabled, as previously
- described.
+ <literal>TRUNCATE TABLE</literal> is a valid operation on a
+ log table. It can be used to expire log entries.
</para>
</listitem>
<listitem>
<para>
+ <literal>RENAME TABLE</literal> is a valid operation on a
+ log table. You can atomically rename a log table (to perform
+ log rotation, for example) using the following strategy:
+ </para>
+
+<programlisting>
+USE mysql;
+CREATE TABLE IF NOT EXISTS general_log2 LIKE general_log;
+RENAME TABLE general_log TO general_log_backup, general_log2 TO general_log;
+</programlisting>
+ </listitem>
+
+ <listitem>
+ <para>
<literal>LOCK TABLES</literal> cannot be used on a log
table.
</para>
@@ -28611,12 +28583,34 @@
<listitem>
<para>
+ The global read lock and the state of the global
+ <literal>read_only</literal> system variable have no effect
+ on log tables. The server can always write to the log
+ tables.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Entries written to the log tables are not written to the
+ binary log and thus are not replicated to slave servers.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
To flush the log tables or log files, use <literal>FLUSH
TABLES</literal> or <literal>FLUSH LOGS</literal>,
respectively.
</para>
</listitem>
+ <listitem>
+ <para>
+ It is not allowed to partition log tables.
+ </para>
+ </listitem>
+
</itemizedlist>
</section>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r7586 - in trunk: . refman-5.1 refman-5.2 | paul | 29 Aug |
