Author: shinz
Date: 2006-09-15 16:32:04 +0200 (Fri, 15 Sep 2006)
New Revision: 3367
Log:
Move paragraph that had slipped to wrong bullet item
Modified:
trunk/refman-5.0/se-innodb.xml
trunk/refman-5.1/se-innodb.xml
Modified: trunk/refman-5.0/se-innodb.xml
===================================================================
--- trunk/refman-5.0/se-innodb.xml 2006-09-15 14:04:22 UTC (rev 3366)
+++ trunk/refman-5.0/se-innodb.xml 2006-09-15 14:32:04 UTC (rev 3367)
Changed blocks: 2, Lines Added: 11, Lines Deleted: 11; 1638 bytes
@@ -1247,6 +1247,17 @@
disable the caching of disk writes in hardware caches, or use
some other command specific to the hardware vendor.
</para>
+ <para>
+ Note: For the greatest possible durability and consistency in
+ a replication setup using <literal>InnoDB</literal> with
+ transactions, you should use
+ <literal>innodb_flush_log_at_trx_commit=1</literal>,
+ <literal>sync_binlog=1</literal>, and, before MySQL 5.0.3,
+ <literal>innodb_safe_binlog</literal> in your master server
+ <filename>my.cnf</filename> file.
+ (<literal>innodb_safe_binlog</literal> is not needed from
+ 5.0.3 on.)
+ </para>
</listitem>
<listitem>
@@ -1316,17 +1327,6 @@
50 seconds.
</para>
- <para>
- Note: For the greatest possible durability and consistency in
- a replication setup using <literal>InnoDB</literal> with
- transactions, you should use
- <literal>innodb_flush_log_at_trx_commit=1</literal>,
- <literal>sync_binlog=1</literal>, and, before MySQL 5.0.3,
- <literal>innodb_safe_binlog</literal> in your master server
- <filename>my.cnf</filename> file.
- (<literal>innodb_safe_binlog</literal> is not needed from
- 5.0.3 on.)
- </para>
</listitem>
<listitem>
Modified: trunk/refman-5.1/se-innodb.xml
===================================================================
--- trunk/refman-5.1/se-innodb.xml 2006-09-15 14:04:22 UTC (rev 3366)
+++ trunk/refman-5.1/se-innodb.xml 2006-09-15 14:32:04 UTC (rev 3367)
Changed blocks: 2, Lines Added: 8, Lines Deleted: 8; 1318 bytes
@@ -1243,6 +1243,14 @@
disable the caching of disk writes in hardware caches, or use
some other command specific to the hardware vendor.
</para>
+ <para>
+ Note: For the greatest possible durability and consistency in
+ a replication setup using <literal>InnoDB</literal> with
+ transactions, you should use
+ <literal>innodb_flush_log_at_trx_commit=1</literal> and
+ <literal>sync_binlog=1</literal> in your master server
+ <filename>my.cnf</filename> file.
+ </para>
</listitem>
<listitem>
@@ -1312,14 +1320,6 @@
50 seconds.
</para>
- <para>
- Note: For the greatest possible durability and consistency in
- a replication setup using <literal>InnoDB</literal> with
- transactions, you should use
- <literal>innodb_flush_log_at_trx_commit=1</literal> and
- <literal>sync_binlog=1</literal> in your master server
- <filename>my.cnf</filename> file.
- </para>
</listitem>
<listitem>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r3367 - in trunk: refman-5.0 refman-5.1 | stefan | 15 Sep |