Author: paul
Date: 2010-09-07 21:11:26 +0200 (Tue, 07 Sep 2010)
New Revision: 22609
Log:
r63007@frost: paul | 2010-09-07 14:11:02 -0500
FLUSH LOGS no longer renames error log file (Bug#29751)
Modified:
trunk/refman-5.1/dba-log-files.xml
trunk/refman-5.1/sql-syntax-server-administration.xml
trunk/refman-5.5/dba-log-files.xml
trunk/refman-5.5/sql-syntax-server-administration.xml
trunk/refman-5.6/dba-log-files.xml
trunk/refman-5.6/sql-syntax-server-administration.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:42090
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:63005
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:42090
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:63007
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-5.1/dba-log-files.xml
===================================================================
--- trunk/refman-5.1/dba-log-files.xml 2010-09-07 19:01:31 UTC (rev 22608)
+++ trunk/refman-5.1/dba-log-files.xml 2010-09-07 19:11:26 UTC (rev 22609)
Changed blocks: 1, Lines Added: 12, Lines Deleted: 5; 1682 bytes
@@ -527,16 +527,23 @@
</para>
<para>
- If you execute <literal role="stmt" condition="flush">FLUSH
- LOGS</literal> and <command>mysqld</command> is writing the error
- log to a file (for example, if it was started with the
+ Prior to MySQL 5.1.51, if you execute
+ <literal role="stmt" condition="flush">FLUSH LOGS</literal> and
+ <command>mysqld</command> is writing the error log to a file (for
+ example, if it was started with the
<option role="mysqld">--log-error</option> option), it renames the
current log file with the suffix <literal>-old</literal>, then
creates a new empty log file. Be aware that a second
<literal role="stmt" condition="flush">FLUSH LOGS</literal>
statement thus causes the original error log file to be lost
- unless you save it under a different name. No renaming occurs if
- the server is not writing to a named file.
+ unless you save it under a different name. To avoid this problem,
+ no renaming occurs as of MySQL 5.1.51; the server merely closes
+ and reopens the log file. To rename the file, you can do so
+ maually before flushing and then
+ <literal role="stmt" condition="flush">FLUSH LOGS</literal> will
+ reopen a new file with the original file name. No renaming occurs
+ even before MySQL 5.1.51 if the server is not writing to a named
+ file.
</para>
<para>
Modified: trunk/refman-5.1/sql-syntax-server-administration.xml
===================================================================
--- trunk/refman-5.1/sql-syntax-server-administration.xml 2010-09-07 19:01:31 UTC (rev 22608)
+++ trunk/refman-5.1/sql-syntax-server-administration.xml 2010-09-07 19:11:26 UTC (rev 22609)
Changed blocks: 1, Lines Added: 12, Lines Deleted: 5; 1914 bytes
@@ -10550,17 +10550,24 @@
</para>
<para>
- If you execute <literal role="stmt" condition="flush">FLUSH
- LOGS</literal> and <command>mysqld</command> is writing the
- error log to a file (for example, if it was started with the
+ Prior to MySQL 5.1.51, if you execute
+ <literal role="stmt" condition="flush">FLUSH LOGS</literal>
+ and <command>mysqld</command> is writing the error log to a
+ file (for example, if it was started with the
<option role="mysqld">--log-error</option> option), it
renames the current log file with the suffix
<literal>-old</literal>, then creates a new empty log file.
Be aware that a second
<literal role="stmt" condition="flush">FLUSH LOGS</literal>
statement thus causes the original error log file to be lost
- unless you save it under a different name. No renaming
- occurs if the server is not writing to a named file.
+ unless you save it under a different name. To avoid this
+ problem, no renaming occurs as of MySQL 5.1.51; the server
+ merely closes and reopens the log file. To rename the file,
+ you can do so maually before flushing and then
+ <literal role="stmt" condition="flush">FLUSH LOGS</literal>
+ will reopen a new file with the original file name. No
+ renaming occurs even before MySQL 5.1.51 if the server is
+ not writing to a named file.
</para>
</listitem>
Modified: trunk/refman-5.5/dba-log-files.xml
===================================================================
--- trunk/refman-5.5/dba-log-files.xml 2010-09-07 19:01:31 UTC (rev 22608)
+++ trunk/refman-5.5/dba-log-files.xml 2010-09-07 19:11:26 UTC (rev 22609)
Changed blocks: 1, Lines Added: 12, Lines Deleted: 5; 1679 bytes
@@ -496,16 +496,23 @@
</para>
<para>
- If you execute <literal role="stmt" condition="flush">FLUSH
- LOGS</literal> and <command>mysqld</command> is writing the error
- log to a file (for example, if it was started with the
+ Prior to MySQL 5.5.7, if you execute
+ <literal role="stmt" condition="flush">FLUSH LOGS</literal> and
+ <command>mysqld</command> is writing the error log to a file (for
+ example, if it was started with the
<option role="mysqld">--log-error</option> option), it renames the
current log file with the suffix <literal>-old</literal>, then
creates a new empty log file. Be aware that a second
<literal role="stmt" condition="flush">FLUSH LOGS</literal>
statement thus causes the original error log file to be lost
- unless you save it under a different name. No renaming occurs if
- the server is not writing to a named file.
+ unless you save it under a different name. To avoid this problem,
+ no renaming occurs as of MySQL 5.5.7; the server merely closes and
+ reopens the log file. To rename the file, you can do so maually
+ before flushing and then
+ <literal role="stmt" condition="flush">FLUSH LOGS</literal> will
+ reopen a new file with the original file name. No renaming occurs
+ even before MySQL 5.5.7 if the server is not writing to a named
+ file.
</para>
<para>
Modified: trunk/refman-5.5/sql-syntax-server-administration.xml
===================================================================
--- trunk/refman-5.5/sql-syntax-server-administration.xml 2010-09-07 19:01:31 UTC (rev 22608)
+++ trunk/refman-5.5/sql-syntax-server-administration.xml 2010-09-07 19:11:26 UTC (rev 22609)
Changed blocks: 1, Lines Added: 12, Lines Deleted: 5; 1908 bytes
@@ -10044,17 +10044,24 @@
</para>
<para>
- If you execute <literal role="stmt" condition="flush">FLUSH
- LOGS</literal> and <command>mysqld</command> is writing the
- error log to a file (for example, if it was started with the
+ Prior to MySQL 5.5.7, if you execute
+ <literal role="stmt" condition="flush">FLUSH LOGS</literal>
+ and <command>mysqld</command> is writing the error log to a
+ file (for example, if it was started with the
<option role="mysqld">--log-error</option> option), it
renames the current log file with the suffix
<literal>-old</literal>, then creates a new empty log file.
Be aware that a second
<literal role="stmt" condition="flush">FLUSH LOGS</literal>
statement thus causes the original error log file to be lost
- unless you save it under a different name. No renaming
- occurs if the server is not writing to a named file.
+ unless you save it under a different name. To avoid this
+ problem, no renaming occurs as of MySQL 5.5.7; the server
+ merely closes and reopens the log file. To rename the file,
+ you can do so maually before flushing and then
+ <literal role="stmt" condition="flush">FLUSH LOGS</literal>
+ will reopen a new file with the original file name. No
+ renaming occurs even before MySQL 5.5.7 if the server is not
+ writing to a named file.
</para>
<para>
Modified: trunk/refman-5.6/dba-log-files.xml
===================================================================
--- trunk/refman-5.6/dba-log-files.xml 2010-09-07 19:01:31 UTC (rev 22608)
+++ trunk/refman-5.6/dba-log-files.xml 2010-09-07 19:11:26 UTC (rev 22609)
Changed blocks: 1, Lines Added: 12, Lines Deleted: 5; 1679 bytes
@@ -496,16 +496,23 @@
</para>
<para>
- If you execute <literal role="stmt" condition="flush">FLUSH
- LOGS</literal> and <command>mysqld</command> is writing the error
- log to a file (for example, if it was started with the
+ Prior to MySQL 5.6.1, if you execute
+ <literal role="stmt" condition="flush">FLUSH LOGS</literal> and
+ <command>mysqld</command> is writing the error log to a file (for
+ example, if it was started with the
<option role="mysqld">--log-error</option> option), it renames the
current log file with the suffix <literal>-old</literal>, then
creates a new empty log file. Be aware that a second
<literal role="stmt" condition="flush">FLUSH LOGS</literal>
statement thus causes the original error log file to be lost
- unless you save it under a different name. No renaming occurs if
- the server is not writing to a named file.
+ unless you save it under a different name. To avoid this problem,
+ no renaming occurs as of MySQL 5.6.1; the server merely closes and
+ reopens the log file. To rename the file, you can do so maually
+ before flushing and then
+ <literal role="stmt" condition="flush">FLUSH LOGS</literal> will
+ reopen a new file with the original file name. No renaming occurs
+ even before MySQL 5.6.1 if the server is not writing to a named
+ file.
</para>
<para>
Modified: trunk/refman-5.6/sql-syntax-server-administration.xml
===================================================================
--- trunk/refman-5.6/sql-syntax-server-administration.xml 2010-09-07 19:01:31 UTC (rev 22608)
+++ trunk/refman-5.6/sql-syntax-server-administration.xml 2010-09-07 19:11:26 UTC (rev 22609)
Changed blocks: 1, Lines Added: 12, Lines Deleted: 5; 1908 bytes
@@ -10100,17 +10100,24 @@
</para>
<para>
- If you execute <literal role="stmt" condition="flush">FLUSH
- LOGS</literal> and <command>mysqld</command> is writing the
- error log to a file (for example, if it was started with the
+ Prior to MySQL 5.6.1, if you execute
+ <literal role="stmt" condition="flush">FLUSH LOGS</literal>
+ and <command>mysqld</command> is writing the error log to a
+ file (for example, if it was started with the
<option role="mysqld">--log-error</option> option), it
renames the current log file with the suffix
<literal>-old</literal>, then creates a new empty log file.
Be aware that a second
<literal role="stmt" condition="flush">FLUSH LOGS</literal>
statement thus causes the original error log file to be lost
- unless you save it under a different name. No renaming
- occurs if the server is not writing to a named file.
+ unless you save it under a different name. To avoid this
+ problem, no renaming occurs as of MySQL 5.6.1; the server
+ merely closes and reopens the log file. To rename the file,
+ you can do so maually before flushing and then
+ <literal role="stmt" condition="flush">FLUSH LOGS</literal>
+ will reopen a new file with the original file name. No
+ renaming occurs even before MySQL 5.6.1 if the server is not
+ writing to a named file.
</para>
<para>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r22609 - in trunk: . refman-5.1 refman-5.5 refman-5.6 | paul.dubois | 7 Sep |
