Author: paul
Date: 2008-05-14 19:18:21 +0200 (Wed, 14 May 2008)
New Revision: 10735
Log:
r31370@frost: paul | 2008-05-14 12:06:13 -0500
Revise description of effect of server restart on MEMORY tables. (Kolbe)
Modified:
trunk/it/refman-5.1/dba-core.xml
trunk/it/refman-5.1/se-memory.xml
trunk/pt/refman-5.1/dba-core.xml
trunk/pt/refman-5.1/se-memory.xml
trunk/refman-4.1/dba-core.xml
trunk/refman-4.1/storage-engines.xml
trunk/refman-5.0/dba-core.xml
trunk/refman-5.0/se-memory.xml
trunk/refman-5.1/dba-core.xml
trunk/refman-5.1/se-memory.xml
trunk/refman-6.0/dba-core.xml
trunk/refman-6.0/se-memory.xml
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:35828
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:31369
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:31263
+ 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:35828
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:31370
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:31263
Modified: trunk/it/refman-5.1/dba-core.xml
===================================================================
--- trunk/it/refman-5.1/dba-core.xml 2008-05-14 17:18:08 UTC (rev 10734)
+++ trunk/it/refman-5.1/dba-core.xml 2008-05-14 17:18:21 UTC (rev 10735)
Changed blocks: 1, Lines Added: 3, Lines Deleted: 3; 877 bytes
@@ -5824,9 +5824,9 @@
re-created with a statement such as <literal>CREATE
TABLE</literal> or altered with <literal>ALTER
TABLE</literal> or <literal>TRUNCATE TABLE</literal>. A
- server restart also affects <literal>MEMORY</literal> tables
- because that is equivalent to a <literal>TRUNCATE
- TABLE</literal> operation.
+ server restart also sets the maximum size of existing
+ <literal>MEMORY</literal> tables to the global
+ <literal>max_heap_table_size</literal> value.
</para>
<formalpara role="mnmas">
Modified: trunk/it/refman-5.1/se-memory.xml
===================================================================
--- trunk/it/refman-5.1/se-memory.xml 2008-05-14 17:18:08 UTC (rev 10734)
+++ trunk/it/refman-5.1/se-memory.xml 2008-05-14 17:18:21 UTC (rev 10735)
Changed blocks: 2, Lines Added: 4, Lines Deleted: 6; 1353 bytes
@@ -231,9 +231,9 @@
<literal>ALTER TABLE</literal> or <literal>TRUNCATE
TABLE</literal>, the value in effect at that time becomes
the new maximum size for the table. A server restart also
- affects existing <literal>MEMORY</literal> tables because
- that is equivalent to a <literal>TRUNCATE TABLE</literal>
- operation.) You can set the size for individual tables as
+ sets the maximum size of existing <literal>MEMORY</literal>
+ tables to the global <literal>max_heap_table_size</literal>
+ value.) You can set the size for individual tables as
described later in this section.
</para>
</listitem>
@@ -358,9 +358,7 @@
<para>
Both tables will revert to the server's global
- <literal>max_heap_table_size</literal> value if the server restarts
- because that is equivalent to a <literal>TRUNCATE TABLE</literal>
- operation for all <literal>MEMORY</literal> tables.
+ <literal>max_heap_table_size</literal> value if the server restarts.
</para>
<para>
Modified: trunk/pt/refman-5.1/dba-core.xml
===================================================================
--- trunk/pt/refman-5.1/dba-core.xml 2008-05-14 17:18:08 UTC (rev 10734)
+++ trunk/pt/refman-5.1/dba-core.xml 2008-05-14 17:18:21 UTC (rev 10735)
Changed blocks: 1, Lines Added: 3, Lines Deleted: 3; 877 bytes
@@ -5824,9 +5824,9 @@
re-created with a statement such as <literal>CREATE
TABLE</literal> or altered with <literal>ALTER
TABLE</literal> or <literal>TRUNCATE TABLE</literal>. A
- server restart also affects <literal>MEMORY</literal> tables
- because that is equivalent to a <literal>TRUNCATE
- TABLE</literal> operation.
+ server restart also sets the maximum size of existing
+ <literal>MEMORY</literal> tables to the global
+ <literal>max_heap_table_size</literal> value.
</para>
<formalpara role="mnmas">
Modified: trunk/pt/refman-5.1/se-memory.xml
===================================================================
--- trunk/pt/refman-5.1/se-memory.xml 2008-05-14 17:18:08 UTC (rev 10734)
+++ trunk/pt/refman-5.1/se-memory.xml 2008-05-14 17:18:21 UTC (rev 10735)
Changed blocks: 2, Lines Added: 4, Lines Deleted: 6; 1353 bytes
@@ -231,9 +231,9 @@
<literal>ALTER TABLE</literal> or <literal>TRUNCATE
TABLE</literal>, the value in effect at that time becomes
the new maximum size for the table. A server restart also
- affects existing <literal>MEMORY</literal> tables because
- that is equivalent to a <literal>TRUNCATE TABLE</literal>
- operation.) You can set the size for individual tables as
+ sets the maximum size of existing <literal>MEMORY</literal>
+ tables to the global <literal>max_heap_table_size</literal>
+ value.) You can set the size for individual tables as
described later in this section.
</para>
</listitem>
@@ -358,9 +358,7 @@
<para>
Both tables will revert to the server's global
- <literal>max_heap_table_size</literal> value if the server restarts
- because that is equivalent to a <literal>TRUNCATE TABLE</literal>
- operation for all <literal>MEMORY</literal> tables.
+ <literal>max_heap_table_size</literal> value if the server restarts.
</para>
<para>
Modified: trunk/refman-4.1/dba-core.xml
===================================================================
--- trunk/refman-4.1/dba-core.xml 2008-05-14 17:18:08 UTC (rev 10734)
+++ trunk/refman-4.1/dba-core.xml 2008-05-14 17:18:21 UTC (rev 10735)
Changed blocks: 1, Lines Added: 4, Lines Deleted: 4; 1023 bytes
@@ -4693,10 +4693,10 @@
table, unless the table is re-created with a statement such
as <literal>CREATE TABLE</literal>, or altered with
<literal>ALTER TABLE</literal> or <literal>TRUNCATE
- TABLE</literal>. A server restart also affects
- <literal>MEMORY</literal> tables because that is equivalent
- to a <literal>TRUNCATE TABLE</literal> operation. This
- variable was added in MySQL 3.23.0.
+ TABLE</literal>. A server restart also sets the maximum size
+ of existing <literal>MEMORY</literal> tables to the global
+ <literal>max_heap_table_size</literal> value. This variable
+ was added in MySQL 3.23.0.
</para>
<formalpara role="mnmas">
Modified: trunk/refman-4.1/storage-engines.xml
===================================================================
--- trunk/refman-4.1/storage-engines.xml 2008-05-14 17:18:08 UTC (rev 10734)
+++ trunk/refman-4.1/storage-engines.xml 2008-05-14 17:18:21 UTC (rev 10735)
Changed blocks: 2, Lines Added: 6, Lines Deleted: 8; 1458 bytes
@@ -2647,11 +2647,11 @@
you use <literal>ALTER TABLE</literal> or
<literal>TRUNCATE TABLE</literal>, the value in effect at
that time becomes the new maximum size for the table. A
- server restart also affects existing
- <literal>MEMORY</literal> tables because that is
- equivalent to a <literal>TRUNCATE TABLE</literal>
- operation.) You can set the size for individual tables as
- described later in this section.
+ server restart also sets the maximum size of existing
+ <literal>MEMORY</literal> tables to the global
+ <literal>max_heap_table_size</literal> value.) You can set
+ the size for individual tables as described later in this
+ section.
</para>
</listitem>
@@ -2766,9 +2766,7 @@
<para>
Both tables will revert to the server's global
<literal>max_heap_table_size</literal> value if the server
- restarts because that is equivalent to a <literal>TRUNCATE
- TABLE</literal> operation for all <literal>MEMORY</literal>
- tables.
+ restarts.
</para>
<para>
Modified: trunk/refman-5.0/dba-core.xml
===================================================================
--- trunk/refman-5.0/dba-core.xml 2008-05-14 17:18:08 UTC (rev 10734)
+++ trunk/refman-5.0/dba-core.xml 2008-05-14 17:18:21 UTC (rev 10735)
Changed blocks: 1, Lines Added: 3, Lines Deleted: 3; 868 bytes
@@ -5567,9 +5567,9 @@
re-created with a statement such as <literal>CREATE
TABLE</literal> or altered with <literal>ALTER
TABLE</literal> or <literal>TRUNCATE TABLE</literal>. A
- server restart also affects <literal>MEMORY</literal> tables
- because that is equivalent to a <literal>TRUNCATE
- TABLE</literal> operation.
+ server restart also sets the maximum size of existing
+ <literal>MEMORY</literal> tables to the global
+ <literal>max_heap_table_size</literal> value.
</para>
<formalpara role="mnmas">
Modified: trunk/refman-5.0/se-memory.xml
===================================================================
--- trunk/refman-5.0/se-memory.xml 2008-05-14 17:18:08 UTC (rev 10734)
+++ trunk/refman-5.0/se-memory.xml 2008-05-14 17:18:21 UTC (rev 10735)
Changed blocks: 2, Lines Added: 4, Lines Deleted: 6; 1344 bytes
@@ -238,9 +238,9 @@
<literal>ALTER TABLE</literal> or <literal>TRUNCATE
TABLE</literal>, the value in effect at that time becomes
the new maximum size for the table. A server restart also
- affects existing <literal>MEMORY</literal> tables because
- that is equivalent to a <literal>TRUNCATE TABLE</literal>
- operation.) You can set the size for individual tables as
+ sets the maximum size of existing <literal>MEMORY</literal>
+ tables to the global <literal>max_heap_table_size</literal>
+ value.) You can set the size for individual tables as
described later in this section.
</para>
</listitem>
@@ -365,9 +365,7 @@
<para>
Both tables will revert to the server's global
- <literal>max_heap_table_size</literal> value if the server restarts
- because that is equivalent to a <literal>TRUNCATE TABLE</literal>
- operation for all <literal>MEMORY</literal> tables.
+ <literal>max_heap_table_size</literal> value if the server restarts.
</para>
<para>
Modified: trunk/refman-5.1/dba-core.xml
===================================================================
--- trunk/refman-5.1/dba-core.xml 2008-05-14 17:18:08 UTC (rev 10734)
+++ trunk/refman-5.1/dba-core.xml 2008-05-14 17:18:21 UTC (rev 10735)
Changed blocks: 1, Lines Added: 3, Lines Deleted: 3; 868 bytes
@@ -5824,9 +5824,9 @@
re-created with a statement such as <literal>CREATE
TABLE</literal> or altered with <literal>ALTER
TABLE</literal> or <literal>TRUNCATE TABLE</literal>. A
- server restart also affects <literal>MEMORY</literal> tables
- because that is equivalent to a <literal>TRUNCATE
- TABLE</literal> operation.
+ server restart also sets the maximum size of existing
+ <literal>MEMORY</literal> tables to the global
+ <literal>max_heap_table_size</literal> value.
</para>
<formalpara role="mnmas">
Modified: trunk/refman-5.1/se-memory.xml
===================================================================
--- trunk/refman-5.1/se-memory.xml 2008-05-14 17:18:08 UTC (rev 10734)
+++ trunk/refman-5.1/se-memory.xml 2008-05-14 17:18:21 UTC (rev 10735)
Changed blocks: 2, Lines Added: 4, Lines Deleted: 6; 1344 bytes
@@ -231,9 +231,9 @@
<literal>ALTER TABLE</literal> or <literal>TRUNCATE
TABLE</literal>, the value in effect at that time becomes
the new maximum size for the table. A server restart also
- affects existing <literal>MEMORY</literal> tables because
- that is equivalent to a <literal>TRUNCATE TABLE</literal>
- operation.) You can set the size for individual tables as
+ sets the maximum size of existing <literal>MEMORY</literal>
+ tables to the global <literal>max_heap_table_size</literal>
+ value.) You can set the size for individual tables as
described later in this section.
</para>
</listitem>
@@ -358,9 +358,7 @@
<para>
Both tables will revert to the server's global
- <literal>max_heap_table_size</literal> value if the server restarts
- because that is equivalent to a <literal>TRUNCATE TABLE</literal>
- operation for all <literal>MEMORY</literal> tables.
+ <literal>max_heap_table_size</literal> value if the server restarts.
</para>
<para>
Modified: trunk/refman-6.0/dba-core.xml
===================================================================
--- trunk/refman-6.0/dba-core.xml 2008-05-14 17:18:08 UTC (rev 10734)
+++ trunk/refman-6.0/dba-core.xml 2008-05-14 17:18:21 UTC (rev 10735)
Changed blocks: 1, Lines Added: 3, Lines Deleted: 3; 868 bytes
@@ -5712,9 +5712,9 @@
re-created with a statement such as <literal>CREATE
TABLE</literal> or altered with <literal>ALTER
TABLE</literal> or <literal>TRUNCATE TABLE</literal>. A
- server restart also affects <literal>MEMORY</literal> tables
- because that is equivalent to a <literal>TRUNCATE
- TABLE</literal> operation.
+ server restart also sets the maximum size of existing
+ <literal>MEMORY</literal> tables to the global
+ <literal>max_heap_table_size</literal> value.
</para>
<formalpara role="mnmas">
Modified: trunk/refman-6.0/se-memory.xml
===================================================================
--- trunk/refman-6.0/se-memory.xml 2008-05-14 17:18:08 UTC (rev 10734)
+++ trunk/refman-6.0/se-memory.xml 2008-05-14 17:18:21 UTC (rev 10735)
Changed blocks: 2, Lines Added: 4, Lines Deleted: 6; 1344 bytes
@@ -231,9 +231,9 @@
<literal>ALTER TABLE</literal> or <literal>TRUNCATE
TABLE</literal>, the value in effect at that time becomes
the new maximum size for the table. A server restart also
- affects existing <literal>MEMORY</literal> tables because
- that is equivalent to a <literal>TRUNCATE TABLE</literal>
- operation.) You can set the size for individual tables as
+ sets the maximum size of existing <literal>MEMORY</literal>
+ tables to the global <literal>max_heap_table_size</literal>
+ value.) You can set the size for individual tables as
described later in this section.
</para>
</listitem>
@@ -358,9 +358,7 @@
<para>
Both tables will revert to the server's global
- <literal>max_heap_table_size</literal> value if the server restarts
- because that is equivalent to a <literal>TRUNCATE TABLE</literal>
- operation for all <literal>MEMORY</literal> tables.
+ <literal>max_heap_table_size</literal> value if the server restarts.
</para>
<para>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r10735 - in trunk: . it/refman-5.1 pt/refman-5.1 refman-4.1 refman-5.0 refman-5.1 refman-6.0 | paul | 14 May |
