List:Commits« Previous MessageNext Message »
From:jon Date:September 30 2008 10:38pm
Subject:svn commit - mysqldoc@docsrva: r11928 - trunk/dynamic-docs/changelog
View as plain text  
Author: jstephens
Date: 2008-09-30 22:38:42 +0200 (Tue, 30 Sep 2008)
New Revision: 11928

Log:

Documented Falcon bugfixes:

  Bug #22165, Bug #35322, Bug #35982, Bug #36403, Bug #36745,
  Bug #37343, Bug #37344, Bug #38041, Bug #38043, Bug #38933



Modified:
   trunk/dynamic-docs/changelog/mysqld-1.xml
   trunk/dynamic-docs/changelog/mysqld.xml


Modified: trunk/dynamic-docs/changelog/mysqld-1.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld-1.xml	2008-09-30 18:39:02 UTC (rev 11927)
+++ trunk/dynamic-docs/changelog/mysqld-1.xml	2008-09-30 20:38:42 UTC (rev 11928)
Changed blocks: 1, Lines Added: 262, Lines Deleted: 0; 5497 bytes

@@ -9,6 +9,268 @@
   <logentry entrytype="bug">
 
     <tags>
+      <manual type="Falcon"/>
+      <manual type="ALTER TABLE"/>
+      <manual type="DML"/>
+      <manual type="deadlock"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="38043"/>
+    </bugs>
+
+    <versions>
+      <version ver="6.0.6"/>
+    </versions>
+
+    <message>
+
+      <para>
+        Executing <literal>ALTER TABLE</literal> and DML statements
+        concurrently on <literal>Falcon</literal> tables could cause the
+        server to hang.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <manual type="Falcon"/>
+      <manual type="ALTER TABLE"/>
+      <manual type="ADD KEY"/>
+      <manual type="DROP KEY"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="38041"/>
+    </bugs>
+
+    <versions>
+      <version ver="6.0.6"/>
+    </versions>
+
+    <message>
+
+      <para>
+        <literal>ALTER TABLE ... ADD KEY</literal> and <literal>ALTER
+        TABLE ... DROP KEY</literal> were not always handled correctly
+        for <literal>Falcon</literal> tables, resulting in spurious
+        duplicate key and other errors.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <manual type="Falcon"/>
+      <manual type="SELECT"/>
+      <manual type="AVG()"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="37344"/>
+    </bugs>
+
+    <versions>
+      <version ver="6.0.6"/>
+    </versions>
+
+    <message>
+
+      <para>
+        A large number of updates on a <literal>Falcon</literal> table
+        followed by a query of the form <literal>SELECT
+        AVG(<replaceable>int_non_key_column</replaceable>) FROM
+        <replaceable>table</replaceable> WHERE
+        <replaceable>int_non_key_column</replaceable> &lt;
+        <replaceable>constant</replaceable> GROUP BY
+        <replaceable>int_key_column</replaceable> LIMIT
+        <replaceable>limit</replaceable></literal> could crash the
+        server.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <manual type="Falcon"/>
+      <manual type="falcon_page_size"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="37343"/>
+    </bugs>
+
+    <versions>
+      <version ver="6.0.6"/>
+    </versions>
+
+    <message>
+
+      <para>
+        Queries with complex conditions in the <literal>WHERE</literal>
+        clause on <literal>Falcon</literal> tables when
+        <literal>falcon_page_size</literal> was set to a low value could
+        cause the server to crash.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <manual type="Falcon"/>
+      <manual type="Solaris"/>
+      <manual type="mysql_install_db"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="36745"/>
+    </bugs>
+
+    <versions>
+      <version ver="6.0.6"/>
+    </versions>
+
+    <message>
+
+      <para>
+        <command>mysql_install_db</command> from a
+        <literal>Falcon</literal>-enabled build crashed on
+        Solaris/SPARC.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <manual type="Falcon"/>
+      <manual type="compiling"/>
+      <manual type="DTrace"/>
+      <manual type="Solaris"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="36403"/>
+    </bugs>
+
+    <versions>
+      <version ver="6.0.6"/>
+    </versions>
+
+    <message>
+
+      <para>
+        Compiling the server with <literal>Falcon</literal> support
+        failed on Solaris 10 due to problems with DTrace. This occurred
+        even when the build was configured using
+        <option>--disable-dtrace</option>.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <manual type="Falcon"/>
+      <manual type="LOAD DATA INFILE"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="35982"/>
+    </bugs>
+
+    <versions>
+      <version ver="6.0.5"/>
+    </versions>
+
+    <message>
+
+      <para>
+        Concurrent <literal>LOAD DATA INFILE</literal> statements
+        inserting data into <literal>Falcon</literal> tables could crash
+        the server.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <manual type="Falcon"/>
+      <manual type="views"/>
+      <manual type="updates"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="35322"/>
+    </bugs>
+
+    <versions>
+      <version ver="6.0.6"/>
+    </versions>
+
+    <message>
+
+      <para>
+        Simultaneous inserts and updates on an updateable view
+        referencing a <literal>Falcon</literal> table could sometimes
+        cause duplicate key errors.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <manual type="Falcon"/>
+      <manual type="rollback"/>
+      <manual type="DDL"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="38933"/>
+    </bugs>
+
+    <versions>
+      <version ver="6.0.6"/>
+    </versions>
+
+    <message>
+
+      <para>
+        Trying to execute a DDL statement on a <literal>Falcon</literal>
+        table while a transaction was being rolled back could cause the
+        server to crash.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
       <highlight type="clusterreplication"/>
       <manual type="DROP DATABASE"/>
     </tags>


Modified: trunk/dynamic-docs/changelog/mysqld.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld.xml	2008-09-30 18:39:02 UTC (rev 11927)
+++ trunk/dynamic-docs/changelog/mysqld.xml	2008-09-30 20:38:42 UTC (rev 11928)
Changed blocks: 1, Lines Added: 17, Lines Deleted: 2; 1073 bytes

@@ -3400,17 +3400,32 @@
 
     <versions>
       <version ver="6.0.0"/>
+      <version ver="6.0.7"/>
     </versions>
 
     <message>
 
       <para>
-        Using <literal>ALTER</literal> with interleaving transactions
-        triggers <literal>mysqld</literal> to crash.
+        Using <literal>ALTER TABLE</literal> with interleaving
+        transactions could cause <command>mysqld</command> to crash.
       </para>
 
     </message>
 
+    <message ver="6.0.6">
+
+      <para>
+        Using <literal>ALTER TABLE</literal> with interleaving
+        transactions could cause <command>mysqld</command> to crash.
+      </para>
+
+      <para>
+        This fix supersedes an earlier one for this issue that appeared
+        in MySQL 6.0.0.
+      </para>
+
+    </message>
+
   </logentry>
 
   <logentry entrytype="bug">


Thread
svn commit - mysqldoc@docsrva: r11928 - trunk/dynamic-docs/changelogjon30 Sep