Author: paul
Date: 2007-05-02 20:10:57 +0200 (Wed, 02 May 2007)
New Revision: 6301
Log:
r19936@frost: paul | 2007-05-02 13:08:17 -0500
Mention expire_logs_days for log maintenance. (Bug#27889)
Modified:
trunk/refman-4.1/dba-core.xml
trunk/refman-5.0/dba-core.xml
trunk/refman-5.1/dba-core.xml
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:24397
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:19935
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:17229
+ 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:24397
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:19936
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:17229
Modified: trunk/refman-4.1/dba-core.xml
===================================================================
--- trunk/refman-4.1/dba-core.xml 2007-05-02 18:10:27 UTC (rev 6300)
+++ trunk/refman-4.1/dba-core.xml 2007-05-02 18:10:57 UTC (rev 6301)
Changed blocks: 1, Lines Added: 9, Lines Deleted: 0; 920 bytes
@@ -25027,6 +25027,15 @@
</para>
<para>
+ For the binary log, you can set the
+ <literal>expire_logs_days</literal> system variable to expire
+ binary log files automatically after a given number of days (see
+ <xref linkend="server-system-variables"/>). If you are using
+ replication, you should set the variable no lower than the
+ maximum number of days your slaves might lag behind the master.
+ </para>
+
+ <para>
You can force MySQL to start using new log files by issuing a
<literal>FLUSH LOGS</literal> statement or executing
<command>mysqladmin flush-logs</command> or <command>mysqladmin
Modified: trunk/refman-5.0/dba-core.xml
===================================================================
--- trunk/refman-5.0/dba-core.xml 2007-05-02 18:10:27 UTC (rev 6300)
+++ trunk/refman-5.0/dba-core.xml 2007-05-02 18:10:57 UTC (rev 6301)
Changed blocks: 1, Lines Added: 9, Lines Deleted: 0; 920 bytes
@@ -28426,6 +28426,15 @@
</para>
<para>
+ For the binary log, you can set the
+ <literal>expire_logs_days</literal> system variable to expire
+ binary log files automatically after a given number of days (see
+ <xref linkend="server-system-variables"/>). If you are using
+ replication, you should set the variable no lower than the
+ maximum number of days your slaves might lag behind the master.
+ </para>
+
+ <para>
You can force MySQL to start using new log files by issuing a
<literal>FLUSH LOGS</literal> statement or executing
<command>mysqladmin flush-logs</command> or <command>mysqladmin
Modified: trunk/refman-5.1/dba-core.xml
===================================================================
--- trunk/refman-5.1/dba-core.xml 2007-05-02 18:10:27 UTC (rev 6300)
+++ trunk/refman-5.1/dba-core.xml 2007-05-02 18:10:57 UTC (rev 6301)
Changed blocks: 1, Lines Added: 9, Lines Deleted: 0; 920 bytes
@@ -29474,6 +29474,15 @@
</para>
<para>
+ For the binary log, you can set the
+ <literal>expire_logs_days</literal> system variable to expire
+ binary log files automatically after a given number of days (see
+ <xref linkend="server-system-variables"/>). If you are using
+ replication, you should set the variable no lower than the
+ maximum number of days your slaves might lag behind the master.
+ </para>
+
+ <para>
You can force MySQL to start using new log files by issuing a
<literal>FLUSH LOGS</literal> statement or executing
<command>mysqladmin flush-logs</command> or <command>mysqladmin
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r6301 - in trunk: . refman-4.1 refman-5.0 refman-5.1 | paul | 2 May |
