Author: jstephens
Date: 2008-04-05 18:30:07 +0200 (Sat, 05 Apr 2008)
New Revision: 10422
Log:
Documented Replication bugfixes:
Bug #18199, Bug #18453
Modified:
trunk/dynamic-docs/changelog/mysqld-1.xml
trunk/refman-5.0/sql-syntax.xml
trunk/refman-5.1/sql-syntax.xml
trunk/refman-6.0/sql-syntax.xml
Modified: trunk/dynamic-docs/changelog/mysqld-1.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld-1.xml 2008-04-05 09:01:36 UTC (rev 10421)
+++ trunk/dynamic-docs/changelog/mysqld-1.xml 2008-04-05 16:30:07 UTC (rev 10422)
Changed blocks: 1, Lines Added: 28, Lines Deleted: 0; 1153 bytes
@@ -10,6 +10,34 @@
<tags>
<highlight type="replication"/>
+ <manual type="PURGE BINARY LOGS"/>
+ </tags>
+
+ <versions>
+ <version ver="5.0.60"/>
+ <version ver="5.1.24"/>
+ <version ver="6.0.5"/>
+ </versions>
+
+ <message>
+
+ <para>
+ <literal>PURGE BINARY LOGS TO</literal> and <literal>PURGE
+ BINARY LOGS BEFORE</literal> did not handle missing binary log
+ files correctly or in the same way. Now for both of these
+ statements, if any files listed in the
+ <filename>.index</filename> file are missing from the
+ filesystem, the statement fails with an error.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <tags>
+ <highlight type="replication"/>
<manual type="AUTO_INCREMENT"/>
<manual type="triggers"/>
<manual type="stored routines"/>
Modified: trunk/refman-5.0/sql-syntax.xml
===================================================================
--- trunk/refman-5.0/sql-syntax.xml 2008-04-05 09:01:36 UTC (rev 10421)
+++ trunk/refman-5.0/sql-syntax.xml 2008-04-05 16:30:07 UTC (rev 10422)
Changed blocks: 1, Lines Added: 15, Lines Deleted: 0; 1234 bytes
@@ -22010,6 +22010,21 @@
master.
</para>
+ <para>
+ Prior to MySQL 5.0.60, <literal>PURGE BINARY LOGS TO</literal>
+ and <literal>PURGE BINARY LOGS BEFORE</literal> did not behave
+ in the same way (and neither one behaved correctly) when
+ binary log files listed in the <filename>.index</filename>
+ file had been removed from the system by some other means
+ (such as using rm on Linux). Beginning with MySQL 5.0.60, both
+ variants of the statement fail with an error in such cases.
+ (Bug #18199, Bug #18453) You can handle such errors by editing
+ the <filename>.index</filename> file (which is a simple text
+ file) manually and insuring that it lists only the binlog
+ files that are actually present, then running again the
+ <literal>PURGE BINARY LOGS</literal> statement that failed.
+ </para>
+
</section>
<section id="reset-master">
Modified: trunk/refman-5.1/sql-syntax.xml
===================================================================
--- trunk/refman-5.1/sql-syntax.xml 2008-04-05 09:01:36 UTC (rev 10421)
+++ trunk/refman-5.1/sql-syntax.xml 2008-04-05 16:30:07 UTC (rev 10422)
Changed blocks: 1, Lines Added: 15, Lines Deleted: 0; 1234 bytes
@@ -24893,6 +24893,21 @@
master.
</para>
+ <para>
+ Prior to MySQL 5.1.24, <literal>PURGE BINARY LOGS TO</literal>
+ and <literal>PURGE BINARY LOGS BEFORE</literal> did not behave
+ in the same way (and neither one behaved correctly) when
+ binary log files listed in the <filename>.index</filename>
+ file had been removed from the system by some other means
+ (such as using rm on Linux). Beginning with MySQL 5.1.24, both
+ variants of the statement fail with an error in such cases.
+ (Bug #18199, Bug #18453) You can handle such errors by editing
+ the <filename>.index</filename> file (which is a simple text
+ file) manually and insuring that it lists only the binlog
+ files that are actually present, then running again the
+ <literal>PURGE BINARY LOGS</literal> statement that failed.
+ </para>
+
</section>
<section id="reset-master">
Modified: trunk/refman-6.0/sql-syntax.xml
===================================================================
--- trunk/refman-6.0/sql-syntax.xml 2008-04-05 09:01:36 UTC (rev 10421)
+++ trunk/refman-6.0/sql-syntax.xml 2008-04-05 16:30:07 UTC (rev 10422)
Changed blocks: 1, Lines Added: 15, Lines Deleted: 0; 1232 bytes
@@ -25158,6 +25158,21 @@
master.
</para>
+ <para>
+ Prior to MySQL 6.0.5, <literal>PURGE BINARY LOGS TO</literal>
+ and <literal>PURGE BINARY LOGS BEFORE</literal> did not behave
+ in the same way (and neither one behaved correctly) when
+ binary log files listed in the <filename>.index</filename>
+ file had been removed from the system by some other means
+ (such as using rm on Linux). Beginning with MySQL 6.0.5, both
+ variants of the statement fail with an error in such cases.
+ (Bug #18199, Bug #18453) You can handle such errors by editing
+ the <filename>.index</filename> file (which is a simple text
+ file) manually and insuring that it lists only the binlog
+ files that are actually present, then running again the
+ <literal>PURGE BINARY LOGS</literal> statement that failed.
+ </para>
+
</section>
<section id="reset-master">
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r10422 - in trunk: dynamic-docs/changelog refman-5.0 refman-5.1 refman-6.0 | jon | 5 Apr |
