svn commit - mysqldoc@docsrva: r6272 - in trunk: refman-5.0 refman-5.1

[mcbrown]

Author: mcbrown
Date: 2007-04-30 16:51:21 +0200 (Mon, 30 Apr 2007)
New Revision: 6272

Log:
Documenting dev bugs: Bug #23313, Bug #26662



Modified:
   trunk/refman-5.0/releasenotes-es-5.0.xml
   trunk/refman-5.0/se-innodb.xml
   trunk/refman-5.1/news-5.1.xml
   trunk/refman-5.1/se-innodb.xml


Modified: trunk/refman-5.0/releasenotes-es-5.0.xml
===================================================================
--- trunk/refman-5.0/releasenotes-es-5.0.xml	2007-04-30 14:24:37 UTC (rev 6271)
+++ trunk/refman-5.0/releasenotes-es-5.0.xml	2007-04-30 14:51:21 UTC (rev 6272)
Changed blocks: 1, Lines Added: 20, Lines Deleted: 0; 1295 bytes

@@ -156,6 +156,26 @@
 
       <listitem>
         <para>
+          The <literal>AUTO_INCREMENT</literal> value would not be
+          correctly reported for InnoDB tables when using <literal>SHOW
+            CREATE TABLE</literal> statement or
+          <command>mysqldump</command> command. (Bug #23313)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          Creating a temporary table with InnoDB when using the
+          one-file-per-table setting, when the host filesystem for
+          temporary tables is <literal>tmpfs</literal> would cause
+          <literal>mysqld</literal> to crash. This was due to the use of
+          <literal>O_DIRECT</literal> when opening the temporary table
+          file. (Bug #26662)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           An interaction between <literal>SHOW TABLE STATUS</literal>
           and other concurrent statements that modify the table could
           result in a divide-by-zero error and a server crash. (Bug


Modified: trunk/refman-5.0/se-innodb.xml
===================================================================
--- trunk/refman-5.0/se-innodb.xml	2007-04-30 14:24:37 UTC (rev 6271)
+++ trunk/refman-5.0/se-innodb.xml	2007-04-30 14:51:21 UTC (rev 6272)
Changed blocks: 1, Lines Added: 5, Lines Deleted: 4; 1258 bytes

@@ -1308,10 +1308,11 @@
           <literal>O_SYNC</literal> to open and flush the log files, but
           uses <literal>fsync()</literal> to flush the data files. If
           <literal>O_DIRECT</literal> is specified (available on some
-          GNU/Linux versions), <literal>InnoDB</literal> uses
-          <literal>O_DIRECT</literal> to open the data files, and uses
-          <literal>fsync()</literal> to flush both the data and log
-          files. Note that <literal>InnoDB</literal> uses
+          GNU/Linux versions, FreeBSD and Solaris),
+          <literal>InnoDB</literal> uses
<literal>O_DIRECT</literal> (or
+          <literal>directio()</literal> on Solaris) to open the data
+          files, and uses <literal>fsync()</literal> to flush both the
+          data and log files. Note that <literal>InnoDB</literal> uses
           <literal>fsync()</literal> instead of
           <literal>fdatasync()</literal>, and it does not use
           <literal>O_DSYNC</literal> by default because there have been


Modified: trunk/refman-5.1/news-5.1.xml
===================================================================
--- trunk/refman-5.1/news-5.1.xml	2007-04-30 14:24:37 UTC (rev 6271)
+++ trunk/refman-5.1/news-5.1.xml	2007-04-30 14:51:21 UTC (rev 6272)
Changed blocks: 1, Lines Added: 20, Lines Deleted: 0; 1254 bytes

@@ -656,6 +656,26 @@
 
       <listitem>
         <para>
+          The <literal>AUTO_INCREMENT</literal> value would not be
+          correctly reported for InnoDB tables when using <literal>SHOW
+          CREATE TABLE</literal> statement or
+          <command>mysqldump</command> command. (Bug #23313)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Creating a temporary table with InnoDB when using the
+          one-file-per-table setting, when the host filesystem for
+          temporary tables is <literal>tmpfs</literal> would cause
+          <literal>mysqld</literal> to crash. This was due to the use of
+          <literal>O_DIRECT</literal> when opening the temporary table
+          file. (Bug #26662)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           An interaction between <literal>SHOW TABLE STATUS</literal>
           and other concurrent statements that modify the table could
           result in a divide-by-zero error and a server crash. (Bug


Modified: trunk/refman-5.1/se-innodb.xml
===================================================================
--- trunk/refman-5.1/se-innodb.xml	2007-04-30 14:24:37 UTC (rev 6271)
+++ trunk/refman-5.1/se-innodb.xml	2007-04-30 14:51:21 UTC (rev 6272)
Changed blocks: 1, Lines Added: 5, Lines Deleted: 4; 1258 bytes

@@ -1301,10 +1301,11 @@
           <literal>O_SYNC</literal> to open and flush the log files, but
           uses <literal>fsync()</literal> to flush the data files. If
           <literal>O_DIRECT</literal> is specified (available on some
-          GNU/Linux versions), <literal>InnoDB</literal> uses
-          <literal>O_DIRECT</literal> to open the data files, and uses
-          <literal>fsync()</literal> to flush both the data and log
-          files. Note that <literal>InnoDB</literal> uses
+          GNU/Linux versions, FreeBSD and Solaris),
+          <literal>InnoDB</literal> uses
<literal>O_DIRECT</literal> (or
+          <literal>directio()</literal> on Solaris) to open the data
+          files, and uses <literal>fsync()</literal> to flush both the
+          data and log files. Note that <literal>InnoDB</literal> uses
           <literal>fsync()</literal> instead of
           <literal>fdatasync()</literal>, and it does not use
           <literal>O_DSYNC</literal> by default because there have been