Author: paul
Date: 2008-03-14 03:19:37 +0100 (Fri, 14 Mar 2008)
New Revision: 10227
Log:
r29975@frost: paul | 2008-03-13 20:36:06 -0500
Remove a bunch of BACKUP DATABASE and RESTORE-related changelog entries.
None of these appeared in any released version. (They are for 6.0.5,
the first version to support these statements.)
Modified:
trunk/dynamic-docs/changelog/mysqld-1.xml
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:35828
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:29971
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:30059
+ 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:35828
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:29975
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:30059
Modified: trunk/dynamic-docs/changelog/mysqld-1.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld-1.xml 2008-03-14 00:15:08 UTC (rev 10226)
+++ trunk/dynamic-docs/changelog/mysqld-1.xml 2008-03-14 02:19:37 UTC (rev 10227)
Changed blocks: 1, Lines Added: 0, Lines Deleted: 287; 5378 bytes
@@ -10559,291 +10559,4 @@
</logentry>
- <logentry entrytype="bug">
-
- <tags>
- <manual type="BACKUP DATABASE"/>
- </tags>
-
- <bugs>
- <fixes bugid="30938"/>
- </bugs>
-
- <versions>
- <version ver="6.0.5"/>
- </versions>
-
- <message>
-
- <para>
- <literal>BACKUP DATABASE</literal> crashed if it attempted to
- backup tables for which the required storage engine was unloaded
- or otherwise unknown.
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="bug">
-
- <tags>
- <manual type="BACKUP DATABASE"/>
- </tags>
-
- <bugs>
- <fixes bugid="30947"/>
- </bugs>
-
- <versions>
- <version ver="6.0.5"/>
- </versions>
-
- <message>
-
- <para>
- <literal>BACKUP DATABASE</literal> crashed if the
- <literal>CREATE TABLE</literal> statements for the tables in a
- backed-up database exceed 4KB in size. The limit now is 2MB.
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="bug">
-
- <tags>
- <manual type="BACKUP DATABASE"/>
- </tags>
-
- <bugs>
- <fixes bugid="31383"/>
- </bugs>
-
- <versions>
- <version ver="6.0.5"/>
- </versions>
-
- <message>
-
- <para>
- The consistent snapshot driver for <literal>BACKUP
- DATABASE</literal> failed to initiate a consistent read, so that
- changes to an <literal>InnoDB</literal> table during the backup
- were included in the backup data.
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="bug">
-
- <tags>
- <manual type="BACKUP DATABASE"/>
- </tags>
-
- <bugs>
- <fixes bugid="31538"/>
- </bugs>
-
- <versions>
- <version ver="6.0.5"/>
- </versions>
-
- <message>
-
- <para>
- Output for <literal>BACKUP DATABASE</literal> was too large, in
- some cases up to 20 times larger than the raw data files for
- some storage engines.
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="bug">
-
- <tags>
- <manual type="BACKUP DATABASE"/>
- </tags>
-
- <bugs>
- <fixes bugid="32190"/>
- </bugs>
-
- <versions>
- <version ver="6.0.5"/>
- </versions>
-
- <message>
-
- <para>
- <literal>BACKUP DATABASE</literal> did not always save database
- character set and collation information in the output.
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="bug">
-
- <tags>
- <manual type="RESTORE"/>
- </tags>
-
- <bugs>
- <fixes bugid="32954"/>
- </bugs>
-
- <versions>
- <version ver="6.0.5"/>
- </versions>
-
- <message>
-
- <para>
- The MyISAM driver for <literal>RESTORE</literal> could
- incorrectly restore data.
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="bug">
-
- <tags>
- <manual type="BACKUP DATABASE"/>
- <manual type="SHOW PROCESSLIST"/>
- </tags>
-
- <bugs>
- <fixes bugid="32970"/>
- </bugs>
-
- <versions>
- <version ver="6.0.5"/>
- </versions>
-
- <message>
-
- <para>
- The <literal>BACKUP DATABASE</literal> locking thread did not
- show up in the server's process list information due to a race
- condition.
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="bug">
-
- <tags>
- <manual type="BACKUP DATABASE"/>
- </tags>
-
- <bugs>
- <fixes bugid="33119"/>
- </bugs>
-
- <versions>
- <version ver="6.0.5"/>
- </versions>
-
- <message>
-
- <para>
- <literal>BACKUP DATABASE</literal> should fail if the output
- file already exists, but was silently overwriting any existing
- file. This has been corrected. Also, any file created by the
- backup operation is deleted if any error occurs.
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="bug">
-
- <tags>
- <manual type="BACKUP DATABASE"/>
- </tags>
-
- <bugs>
- <fixes bugid="33172"/>
- </bugs>
-
- <versions>
- <version ver="6.0.5"/>
- </versions>
-
- <message>
-
- <para>
- Some performance problems with <literal>BACKUP
- DATABASE</literal> were corrected.
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="bug">
-
- <tags>
- <manual type="BACKUP DATABASE"/>
- </tags>
-
- <bugs>
- <fixes bugid="33296"/>
- </bugs>
-
- <versions>
- <version ver="6.0.5"/>
- </versions>
-
- <message>
-
- <para>
- Shutdown of the <literal>BACKUP DATABASE</literal> locking
- thread was subject to a race condition.
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="bug">
-
- <tags>
- <manual type="BACKUP DATABASE"/>
- <manual type="SHOW WARNINGS"/>
- </tags>
-
- <bugs>
- <fixes bugid="33562"/>
- </bugs>
-
- <versions>
- <version ver="6.0.5"/>
- </versions>
-
- <message>
-
- <para>
- Warnings generated during a <literal>BACKUP DATABASE</literal>
- operation were not logged properly, and thus could not be
- displayed with a subsequent <literal>SHOW WARNINGS</literal>
- statement.
- </para>
-
- </message>
-
- </logentry>
-
</changelog>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r10227 - in trunk: . dynamic-docs/changelog | paul | 14 Mar |
