bk commit - mysqldoc@docsrva tree (marko:1.2801)

[Marko Mäkelä]

Below is the list of changes that have just been committed into a local
mysqldoc repository of marko. When marko does a push these changes will
be propagated to the main repository and, within 24 hours after the
push, to the public repository.
For information on how to access the public repository
see http://www.mysql.com/doc/I/n/Installing_source_tree.html

ChangeSet
  1.2801 05/06/16 14:21:17 marko@stripped +1 -0
  innodb.xml:
    innodb-start: Update the documentation of innodb_flush_method=fdatasync

  refman/innodb.xml
    1.2 05/06/16 14:19:23 marko@stripped +5 -4
    innodb-start: Update the documentation of innodb_flush_method=fdatasync

# This is a BitKeeper patch.  What follows are the unified diffs for the
# set of deltas contained in the patch.  The rest of the patch, the part
# that BitKeeper cares about, is below these diffs.
# User:	marko
# Host:	hundin.mysql.fi
# Root:	/home/marko/k/mysqldoc

--- 1.1/refman/innodb.xml	Thu Jun 16 02:46:57 2005
+++ 1.2/refman/innodb.xml	Thu Jun 16 14:19:23 2005
@@ -638,7 +638,6 @@
 set-variable = innodb_lock_wait_timeout=50
 #
 # Uncomment the next lines if you want to use them
-#innodb_flush_method=fdatasync
 #set-variable = innodb_thread_concurrency=5
 </programlisting>
 
@@ -944,7 +943,7 @@
 
    <para>
     This option is relevant only on Unix systems. If set to
-    <literal>fdatasync</literal>, <literal>InnoDB</literal> uses
+    <literal>fdatasync</literal> (the default), <literal>InnoDB</literal> uses
     <literal>fsync()</literal> to flush both the data and log files. If
     set to <literal>O_DSYNC</literal>, <literal>InnoDB</literal> uses
     <literal>O_SYNC</literal> to open and flush the log files, but uses
@@ -953,8 +952,10 @@
     GNU/Linux versions starting from MySQL 4.0.14),
     <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> does not
-    use <literal>fdatasync</literal> or <literal>O_DSYNC</literal> by
+    the data and log files. Note that starting from MySQL 3.23.41,
+    <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 problems with them on many Unix
     flavors. This option is available as of MySQL 3.23.40.
    </para></listitem>