List:Commits« Previous MessageNext Message »
From:paul.dubois Date:August 23 2010 2:08pm
Subject:svn commit - mysqldoc@docsrva: r22383 - in trunk: . refman-4.1 refman-5.0 refman-5.1 refman-5.5 refman-5.6 refman-6.0
View as plain text  
Author: paul
Date: 2010-08-23 16:08:51 +0200 (Mon, 23 Aug 2010)
New Revision: 22383

Log:
 r62563@frost:  paul | 2010-08-23 09:08:28 -0500
 Add mention of PURGE BINARY LOGS for log expiration (Shawn)


Modified:
   trunk/refman-4.1/dba-log-files.xml
   trunk/refman-5.0/dba-log-files.xml
   trunk/refman-5.1/dba-log-files.xml
   trunk/refman-5.5/dba-log-files.xml
   trunk/refman-5.6/dba-log-files.xml
   trunk/refman-6.0/dba-log-files.xml

Property changes on: trunk
___________________________________________________________________
Name: svk:merge
   - 07c7e7b4-24e3-4b51-89d0-6dc09fec6bec:/mysqldoc-local/mysqldoc/trunk:35498
07c7e7b4-24e3-4b51-89d0-6dc09fec6bec:/mysqldoc-local/trunk:41634
4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:43968
4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/trunk:44480
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:62560
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:39036
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/trunk:39546
   + 07c7e7b4-24e3-4b51-89d0-6dc09fec6bec:/mysqldoc-local/mysqldoc/trunk:35498
07c7e7b4-24e3-4b51-89d0-6dc09fec6bec:/mysqldoc-local/trunk:41634
4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:43968
4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/trunk:44480
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:62563
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:39036
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/trunk:39546


Modified: trunk/refman-4.1/dba-log-files.xml
===================================================================
--- trunk/refman-4.1/dba-log-files.xml	2010-08-23 14:02:42 UTC (rev 22382)
+++ trunk/refman-4.1/dba-log-files.xml	2010-08-23 14:08:51 UTC (rev 22383)
Changed blocks: 1, Lines Added: 4, Lines Deleted: 1; 817 bytes

@@ -952,7 +952,10 @@
       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.
+      maximum number of days your slaves might lag behind the master. To
+      remove binary logs on demand, use the <literal role="stmt">PURGE
+      BINARY LOGS</literal> statement (see
+      <xref linkend="purge-binary-logs"/>).
     </para>
 
     <para>


Modified: trunk/refman-5.0/dba-log-files.xml
===================================================================
--- trunk/refman-5.0/dba-log-files.xml	2010-08-23 14:02:42 UTC (rev 22382)
+++ trunk/refman-5.0/dba-log-files.xml	2010-08-23 14:08:51 UTC (rev 22383)
Changed blocks: 1, Lines Added: 4, Lines Deleted: 1; 817 bytes

@@ -900,7 +900,10 @@
       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.
+      maximum number of days your slaves might lag behind the master. To
+      remove binary logs on demand, use the <literal role="stmt">PURGE
+      BINARY LOGS</literal> statement (see
+      <xref linkend="purge-binary-logs"/>).
     </para>
 
     <para>


Modified: trunk/refman-5.1/dba-log-files.xml
===================================================================
--- trunk/refman-5.1/dba-log-files.xml	2010-08-23 14:02:42 UTC (rev 22382)
+++ trunk/refman-5.1/dba-log-files.xml	2010-08-23 14:08:51 UTC (rev 22383)
Changed blocks: 1, Lines Added: 4, Lines Deleted: 1; 819 bytes

@@ -2571,7 +2571,10 @@
       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.
+      maximum number of days your slaves might lag behind the master. To
+      remove binary logs on demand, use the <literal role="stmt">PURGE
+      BINARY LOGS</literal> statement (see
+      <xref linkend="purge-binary-logs"/>).
     </para>
 
     <para>


Modified: trunk/refman-5.5/dba-log-files.xml
===================================================================
--- trunk/refman-5.5/dba-log-files.xml	2010-08-23 14:02:42 UTC (rev 22382)
+++ trunk/refman-5.5/dba-log-files.xml	2010-08-23 14:08:51 UTC (rev 22383)
Changed blocks: 1, Lines Added: 4, Lines Deleted: 1; 819 bytes

@@ -2639,7 +2639,10 @@
       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.
+      maximum number of days your slaves might lag behind the master. To
+      remove binary logs on demand, use the <literal role="stmt">PURGE
+      BINARY LOGS</literal> statement (see
+      <xref linkend="purge-binary-logs"/>).
     </para>
 
     <para>


Modified: trunk/refman-5.6/dba-log-files.xml
===================================================================
--- trunk/refman-5.6/dba-log-files.xml	2010-08-23 14:02:42 UTC (rev 22382)
+++ trunk/refman-5.6/dba-log-files.xml	2010-08-23 14:08:51 UTC (rev 22383)
Changed blocks: 1, Lines Added: 4, Lines Deleted: 1; 819 bytes

@@ -2611,7 +2611,10 @@
       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.
+      maximum number of days your slaves might lag behind the master. To
+      remove binary logs on demand, use the <literal role="stmt">PURGE
+      BINARY LOGS</literal> statement (see
+      <xref linkend="purge-binary-logs"/>).
     </para>
 
     <para>


Modified: trunk/refman-6.0/dba-log-files.xml
===================================================================
--- trunk/refman-6.0/dba-log-files.xml	2010-08-23 14:02:42 UTC (rev 22382)
+++ trunk/refman-6.0/dba-log-files.xml	2010-08-23 14:08:51 UTC (rev 22383)
Changed blocks: 1, Lines Added: 4, Lines Deleted: 1; 819 bytes

@@ -2745,7 +2745,10 @@
       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.
+      maximum number of days your slaves might lag behind the master. To
+      remove binary logs on demand, use the <literal role="stmt">PURGE
+      BINARY LOGS</literal> statement (see
+      <xref linkend="purge-binary-logs"/>).
     </para>
 
     <para>


Thread
svn commit - mysqldoc@docsrva: r22383 - in trunk: . refman-4.1 refman-5.0 refman-5.1 refman-5.5 refman-5.6 refman-6.0paul.dubois23 Aug