List:Commits« Previous MessageNext Message »
From:mcbrown Date:August 21 2008 10:25am
Subject:svn commit - mysqldoc@docsrva: r11587 - in trunk: refman-4.1 refman-5.0 refman-5.1 refman-6.0
View as plain text  
Author: mcbrown
Date: 2008-08-21 12:25:30 +0200 (Thu, 21 Aug 2008)
New Revision: 11587

Log:
Log file size is 32-bits on InnoDB regardless of host bit size
Maria fixes



Modified:
   trunk/refman-4.1/se-innodb-core.xml
   trunk/refman-5.0/se-innodb-core.xml
   trunk/refman-5.1/se-innodb-core.xml
   trunk/refman-6.0/se-innodb-core.xml
   trunk/refman-6.0/se-maria-core.xml


Modified: trunk/refman-4.1/se-innodb-core.xml
===================================================================
--- trunk/refman-4.1/se-innodb-core.xml	2008-08-21 09:48:26 UTC (rev 11586)
+++ trunk/refman-4.1/se-innodb-core.xml	2008-08-21 10:25:30 UTC (rev 11587)
Changed blocks: 1, Lines Added: 3, Lines Deleted: 3; 988 bytes

@@ -1604,9 +1604,9 @@
 
         <para>
           The size in bytes of each log file in a log group. The
-          combined size of log files must be less than 4GB on 32-bit
-          computers. The default is 5MB. Sensible values range from 1MB
-          to 1/<replaceable>N</replaceable>-th of the size of the buffer
+          combined size of log files must be less than 4GB. The default
+          is 5MB. Sensible values range from 1MB to
+          1/<replaceable>N</replaceable>-th of the size of the buffer
           pool, where <replaceable>N</replaceable> is the number of log
           files in the group. The larger the value, the less checkpoint
           flush activity is needed in the buffer pool, saving disk I/O.


Modified: trunk/refman-5.0/se-innodb-core.xml
===================================================================
--- trunk/refman-5.0/se-innodb-core.xml	2008-08-21 09:48:26 UTC (rev 11586)
+++ trunk/refman-5.0/se-innodb-core.xml	2008-08-21 10:25:30 UTC (rev 11587)
Changed blocks: 1, Lines Added: 3, Lines Deleted: 3; 988 bytes

@@ -1655,9 +1655,9 @@
 
         <para>
           The size in bytes of each log file in a log group. The
-          combined size of log files must be less than 4GB on 32-bit
-          computers. The default is 5MB. Sensible values range from 1MB
-          to 1/<replaceable>N</replaceable>-th of the size of the buffer
+          combined size of log files must be less than 4GB. The default
+          is 5MB. Sensible values range from 1MB to
+          1/<replaceable>N</replaceable>-th of the size of the buffer
           pool, where <replaceable>N</replaceable> is the number of log
           files in the group. The larger the value, the less checkpoint
           flush activity is needed in the buffer pool, saving disk I/O.


Modified: trunk/refman-5.1/se-innodb-core.xml
===================================================================
--- trunk/refman-5.1/se-innodb-core.xml	2008-08-21 09:48:26 UTC (rev 11586)
+++ trunk/refman-5.1/se-innodb-core.xml	2008-08-21 10:25:30 UTC (rev 11587)
Changed blocks: 2, Lines Added: 6, Lines Deleted: 6; 1686 bytes

@@ -1690,9 +1690,9 @@
 
         <para>
           The size in bytes of each log file in a log group. The
-          combined size of log files must be less than 4GB on 32-bit
-          computers. The default is 5MB. Sensible values range from 1MB
-          to 1/<replaceable>N</replaceable>-th of the size of the buffer
+          combined size of log files must be less than 4GB. The default
+          is 5MB. Sensible values range from 1MB to
+          1/<replaceable>N</replaceable>-th of the size of the buffer
           pool, where <replaceable>N</replaceable> is the number of log
           files in the group. The larger the value, the less checkpoint
           flush activity is needed in the buffer pool, saving disk I/O.

@@ -2532,9 +2532,9 @@
 
         <para>
           In the case of statement-based replication, this means that
-          when an SQL statement is replicated on a slave server, the same
-          values are used for the auto-increment column as on the master
-          server. The result of execution of multiple
+          when an SQL statement is replicated on a slave server, the
+          same values are used for the auto-increment column as on the
+          master server. The result of execution of multiple
           <literal>INSERT</literal> statements is deterministic, and the
           slave reproduces the same data as on the master. If
           auto-increment values generated by multiple


Modified: trunk/refman-6.0/se-innodb-core.xml
===================================================================
--- trunk/refman-6.0/se-innodb-core.xml	2008-08-21 09:48:26 UTC (rev 11586)
+++ trunk/refman-6.0/se-innodb-core.xml	2008-08-21 10:25:30 UTC (rev 11587)
Changed blocks: 2, Lines Added: 6, Lines Deleted: 6; 1686 bytes

@@ -1603,9 +1603,9 @@
 
         <para>
           The size in bytes of each log file in a log group. The
-          combined size of log files must be less than 4GB on 32-bit
-          computers. The default is 5MB. Sensible values range from 1MB
-          to 1/<replaceable>N</replaceable>-th of the size of the buffer
+          combined size of log files must be less than 4GB. The default
+          is 5MB. Sensible values range from 1MB to
+          1/<replaceable>N</replaceable>-th of the size of the buffer
           pool, where <replaceable>N</replaceable> is the number of log
           files in the group. The larger the value, the less checkpoint
           flush activity is needed in the buffer pool, saving disk I/O.

@@ -2437,9 +2437,9 @@
 
         <para>
           In the case of statement-based replication, this means that
-          when an SQL statement is replicated on a slave server, the same
-          values are used for the auto-increment column as on the master
-          server. The result of execution of multiple
+          when an SQL statement is replicated on a slave server, the
+          same values are used for the auto-increment column as on the
+          master server. The result of execution of multiple
           <literal>INSERT</literal> statements is deterministic, and the
           slave reproduces the same data as on the master. If
           auto-increment values generated by multiple


Modified: trunk/refman-6.0/se-maria-core.xml
===================================================================
--- trunk/refman-6.0/se-maria-core.xml	2008-08-21 09:48:26 UTC (rev 11586)
+++ trunk/refman-6.0/se-maria-core.xml	2008-08-21 10:25:30 UTC (rev 11587)
Changed blocks: 1, Lines Added: 3, Lines Deleted: 3; 946 bytes

@@ -522,15 +522,15 @@
       </listitem>
 
       <listitem>
-        <para id="option_mysqld_maria-recovery">
-          <literal>maria_recovery</literal>
+        <para id="option_mysqld_maria-recover">
+          <literal>maria_recover</literal>
         </para>
 
         <para>
           Forces recovery of corrupted <literal>Maria</literal> tables
           without using the log files. Unlike the automatic recovery
           supported by <literal>Maria</literal> on transactional tables,
-          <literal>maria-recovery</literal> will work for all
+          <literal>maria-recover</literal> will work for all
           <literal>Maria</literal> tables.
         </para>
       </listitem>


Thread
svn commit - mysqldoc@docsrva: r11587 - in trunk: refman-4.1 refman-5.0 refman-5.1 refman-6.0mcbrown21 Aug