List:Commits« Previous MessageNext Message »
From:paul.dubois Date:March 7 2010 8:26pm
Subject:svn commit - mysqldoc@docsrva: r19443 - in trunk: . dynamic-docs/changelog mysql-backup
View as plain text  
Author: paul
Date: 2010-03-07 21:26:42 +0100 (Sun, 07 Mar 2010)
New Revision: 19443

Log:
 r56609@frost:  paul | 2010-03-07 14:26:28 -0500
 Document bug fixes:
 Bug#45587: Backup of tables using a non-existent storage engine does not give warning/error
 Bug#47281: BML may not block all it should
 Bug#47386: Backup fails to backup objects with case sensitive names on case sensitive OS
 Bug#47484: Online Backup: Restore does not set the auto_increment value correctly
 Bug#47879: Backup of partitioned tables with subpartitions can crash server
 Bug#47905: stored procedures with multiple statements not being logged to slow query log
 Bug#48315: Metadata lock is not taken for merged views that use an INFORMATION_SCHEMA table
 Bug#48923: The backup_datatypes and backup_dbname_lctns fail in PB2. Possible lock issue.
 Bug#48929: Error in Accept() if using many file descriptors
 Bug#48930: Backup: Lock thread race condition for default backup driver
 Bug#49025: mysqld-debug: missing DBUG_RETURN or DBUG_VOID_RETURN macro in function "?func"
 Bug#49146: RESTORE:Server crashes when attempt to restore PBXT table while pbxt is disabled
 Bug#49342: backup locking thread: trying to destroy a mutex LOCK_thd_data that was locked
 Bug#50351: ft_min_word_len=2 Causes query to hang
 Bug#50362: comp_err crashes during compilation on FreeBSD
 Bug#50780: 'show binary logs' debug assertion when binary logging is disabled
 Bug#51468: mysqld_multi is broken in 5.1.44


Modified:
   trunk/dynamic-docs/changelog/mysqld-2.xml
   trunk/mysql-backup/backup.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:37300
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:56607
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:37300
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:56609
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/dynamic-docs/changelog/mysqld-2.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld-2.xml	2010-03-07 18:55:13 UTC (rev 19442)
+++ trunk/dynamic-docs/changelog/mysqld-2.xml	2010-03-07 20:26:42 UTC (rev 19443)
Changed blocks: 1, Lines Added: 461, Lines Deleted: 0; 8925 bytes

@@ -7342,4 +7342,465 @@
 
   </logentry>
 
+  <logentry entrytype="bug">
+
+    <tags>
+      <manual type="BACKUP DATABASE"/>
+      <manual type="locking"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="49343"/>
+    </bugs>
+
+    <versions>
+      <version ver="6.0.14"/>
+    </versions>
+
+    <message>
+
+      <para>
+        The <literal role="se">MyISAM</literal> backup driver did not
+        protect acquire a mutex for a structure that it was destroying,
+        causing a crash if another thread attempted to access the
+        structure.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <manual type="RESTORE"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="49146"/>
+    </bugs>
+
+    <versions>
+      <version ver="6.0.14"/>
+    </versions>
+
+    <message>
+
+      <para>
+        <literal role="stmt">RESTORE</literal> crashed if a native
+        backup driver required a storage engine that was not loaded.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <manual type="BACKUP DATABASE"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="48930"/>
+    </bugs>
+
+    <versions>
+      <version ver="6.0.14"/>
+    </versions>
+
+    <message>
+
+      <para>
+        For <literal role="stmt">BACKUP DATABASE</literal>, there was a
+        race condition between the backup thread and the locking thread
+        for the default backup driver.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <manual type="BACKUP DATABASE"/>
+      <manual type="RESTORE"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="48923"/>
+    </bugs>
+
+    <versions>
+      <version ver="6.0.14"/>
+    </versions>
+
+    <message>
+
+      <para>
+        A <literal role="stmt">BACKUP DATABASE</literal> and
+        <literal role="stmt">RESTORE</literal> cycle could fail to
+        handle database and table lettercase on systems with
+        <literal role="sysvar">lower_case_table_names</literal> set to
+        2.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <manual type="BACKUP DATABASE"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="45587"/>
+    </bugs>
+
+    <versions>
+      <version ver="6.0.14"/>
+    </versions>
+
+    <message>
+
+      <para>
+        <literal role="stmt">BACKUP DATABASE</literal> failed to produce
+        an error if a table to be backed up required a storage engine
+        that was not loaded.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <manual type="RESTORE"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="47484"/>
+    </bugs>
+
+    <versions>
+      <version ver="6.0.14"/>
+    </versions>
+
+    <message>
+
+      <para>
+        <literal role="stmt">RESTORE</literal> did not restore table
+        <literal>AUTO_INCREMENT</literal> values properly.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <manual type="MySQL Backup"/>
+      <manual type="CHECK TABLE"/>
+      <manual type="ANALYZE TABLE"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="47281"/>
+    </bugs>
+
+    <versions>
+      <version ver="6.0.14"/>
+    </versions>
+
+    <message>
+
+      <para>
+        <literal role="stmt">ANALYZE TABLE</literal> and
+        <literal role="stmt">CHECK TABLE</literal> are now included in
+        the set of statements blocked by the backup metadata lock
+        because under some conditions these statements can modify
+        tables.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <manual type="BACKUP DATABASE"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="47386"/>
+    </bugs>
+
+    <versions>
+      <version ver="6.0.14"/>
+    </versions>
+
+    <message>
+
+      <para>
+        Previously, <literal role="stmt">BACKUP DATABASE</literal>
+        failed if there were two databases whose names differed in
+        lettercase only and when one database contained an object that
+        was missing in the other. Now <literal role="stmt">BACKUP
+        DATABASE</literal> correctly determines which objects are in
+        which database even when database names differ only in
+        lettercase.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <manual type="BACKUP DATABASE"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="47879"/>
+    </bugs>
+
+    <versions>
+      <version ver="6.0.14"/>
+    </versions>
+
+    <message>
+
+      <para>
+        Attempts to use <literal role="stmt">BACKUP DATABASE</literal>
+        for partitioned tables with subpartitions caused a server crash.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <manual type="locking"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="48315"/>
+    </bugs>
+
+    <versions>
+      <version ver="5.5.3"/>
+      <version ver="6.0.14"/>
+    </versions>
+
+    <message>
+
+      <para>
+        If a prepared statement using a merged view referencing an
+        <literal>INFORMATION_SCHEMA</literal> table was executed, no
+        metadata lock of the view was taken. Consequently, it was
+        possible for concurrent DDL statements on the view to execute
+        and cause statements to be written in the wrong order to the
+        binary log.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <manual type="mysqld_multi"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="51468"/>
+    </bugs>
+
+    <versions>
+      <version ver="5.1.45"/>
+      <version ver="5.5.3"/>
+      <version ver="6.0.14"/>
+    </versions>
+
+    <message>
+
+      <para>
+        <command>mysqld_multi</command> failed due to a syntax error in
+        the script.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="48929"/>
+    </bugs>
+
+    <versions>
+      <version ver="5.5.3"/>
+      <version ver="6.0.14"/>
+    </versions>
+
+    <message>
+
+      <para>
+        On POSIX systems, calls to <literal>select()</literal> with a
+        file descriptor set larger than <literal>FD_SETSIZE</literal>
+        resulted in unpredictable I/O errors; for example, when a large
+        number of tables required repair.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <manual type="SHOW BINARY LOGS"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="50780"/>
+    </bugs>
+
+    <versions>
+      <version ver="5.1.45"/>
+      <version ver="5.5.3"/>
+      <version ver="6.0.14"/>
+    </versions>
+
+    <message>
+
+      <para>
+        For debug builds, <literal role="stmt">SHOW BINARY
+        LOGS</literal> caused an assertion to be raised if binary
+        logging was not enabled.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <manual type="full-text"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="50351"/>
+    </bugs>
+
+    <versions>
+      <version ver="5.1.45"/>
+      <version ver="5.5.3"/>
+      <version ver="6.0.14"/>
+    </versions>
+
+    <message>
+
+      <para>
+        Full-text queries that used the truncation operator
+        (<literal>*</literal>) could enter an infinite loop.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <manual type="Windows"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="49025"/>
+    </bugs>
+
+    <versions>
+      <version ver="5.1.45"/>
+      <version ver="5.5.3"/>
+      <version ver="6.0.14"/>
+    </versions>
+
+    <message>
+
+      <para>
+        For debug builds on Windows, warnings about incorrect use of
+        debugging directives were written to the error log. The
+        directives were rewritten to eliminate these messages.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <manual type="logging"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="47905"/>
+    </bugs>
+
+    <versions>
+      <version ver="5.1.45"/>
+      <version ver="5.5.3"/>
+      <version ver="6.0.14"/>
+    </versions>
+
+    <message>
+
+      <para>
+        Slow <literal>CALL</literal> statements were not always logged
+        to the slow query log because execution time for
+        multiple-statement stored procedures was assessed incorrectly.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <manual type="comp_err"/>
+      <manual type="FreeBSD"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="50362"/>
+    </bugs>
+
+    <versions>
+      <version ver="5.5.3"/>
+    </versions>
+
+    <message>
+
+      <para>
+        <command>comp_err</command> did not build on FreeBSD.
+      </para>
+
+    </message>
+
+  </logentry>
+
 </changelog>


Modified: trunk/mysql-backup/backup.xml
===================================================================
--- trunk/mysql-backup/backup.xml	2010-03-07 18:55:13 UTC (rev 19442)
+++ trunk/mysql-backup/backup.xml	2010-03-07 20:26:42 UTC (rev 19443)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 463 bytes

@@ -763,7 +763,7 @@
 ALTER  DATABASE/TABLE/VIEW/FUNCTION/PROCEDURE/EVENT/TABLESPACE
 RENAME TABLE/USER
 GRANT/REVOKE
-TRUNCATE/OPTIMIZE/REPAIR TABLE
+ANALYZE/CHECK/TRUNCATE/OPTIMIZE/REPAIR TABLE
 </programlisting>
 
     <para>


Thread
svn commit - mysqldoc@docsrva: r19443 - in trunk: . dynamic-docs/changelog mysql-backuppaul.dubois7 Mar