MySQL Lists are EOL. Please join:

List:Commits« Previous MessageNext Message »
From:paul Date:March 7 2008 6:12pm
Subject:svn commit - mysqldoc@docsrva: r10161 - in trunk: . dynamic-docs/changelog
View as plain text  
Author: paul
Date: 2008-03-07 19:12:40 +0100 (Fri, 07 Mar 2008)
New Revision: 10161

Log:
 r29799@frost:  paul | 2008-03-07 11:48:28 -0600
 Add BACKUP DATABASE/RESTORE changelog entries.


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:29798
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:29889
   + 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:35828
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:29799
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:29889


Modified: trunk/dynamic-docs/changelog/mysqld-1.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld-1.xml	2008-03-07 18:12:30 UTC (rev 10160)
+++ trunk/dynamic-docs/changelog/mysqld-1.xml	2008-03-07 18:12:40 UTC (rev 10161)
Changed blocks: 1, Lines Added: 287, Lines Deleted: 0; 5378 bytes

@@ -10468,4 +10468,291 @@
 
   </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: r10161 - in trunk: . dynamic-docs/changelogpaul7 Mar