Author: paul
Date: 2008-05-14 17:32:19 +0200 (Wed, 14 May 2008)
New Revision: 10733
Log:
r31366@frost: paul | 2008-05-14 10:23:08 -0500
MEMORY tables: Server restart also resets max size; effect of MAX_ROWS
limited by max_heap_table_size. (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:31364
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:31366
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 02:40:04 UTC (rev 10732)
+++ trunk/it/refman-5.1/dba-core.xml 2008-05-14 15:32:19 UTC (rev 10733)
Changed blocks: 1, Lines Added: 4, Lines Deleted: 1; 826 bytes
@@ -5823,7 +5823,10 @@
<literal>MEMORY</literal> 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>.
+ 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.
</para>
<formalpara role="mnmas">
Modified: trunk/it/refman-5.1/se-memory.xml
===================================================================
--- trunk/it/refman-5.1/se-memory.xml 2008-05-14 02:40:04 UTC (rev 10732)
+++ trunk/it/refman-5.1/se-memory.xml 2008-05-14 15:32:19 UTC (rev 10733)
Changed blocks: 2, Lines Added: 19, Lines Deleted: 4; 2001 bytes
@@ -230,9 +230,11 @@
value used for the life of the table. (If 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.) You can also set the
- size for individual tables, as described later in this
- section.
+ 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.
</para>
</listitem>
@@ -355,10 +357,23 @@
</programlisting>
<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.
+ </para>
+
+ <para>
You can also specify a <literal>MAX_ROWS</literal> table option in
<literal>CREATE TABLE</literal> statements for
<literal>MEMORY</literal> tables to provide a hint about the number
- of rows you plan to store in them.
+ of rows you plan to store in them. This does not allow the table to
+ grow beyond the <literal>max_heap_table_size</literal> value, which
+ still acts as a constraint on maximum table size. For maximum
+ flexibility in being able to use <literal>MAX_ROWS</literal>, set
+ <literal>max_heap_table_size</literal> at least as high as the value
+ to which you want each <literal>MEMORY</literal> table to be able to
+ grow.
</para>
<para>
Modified: trunk/pt/refman-5.1/dba-core.xml
===================================================================
--- trunk/pt/refman-5.1/dba-core.xml 2008-05-14 02:40:04 UTC (rev 10732)
+++ trunk/pt/refman-5.1/dba-core.xml 2008-05-14 15:32:19 UTC (rev 10733)
Changed blocks: 1, Lines Added: 4, Lines Deleted: 1; 826 bytes
@@ -5823,7 +5823,10 @@
<literal>MEMORY</literal> 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>.
+ 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.
</para>
<formalpara role="mnmas">
Modified: trunk/pt/refman-5.1/se-memory.xml
===================================================================
--- trunk/pt/refman-5.1/se-memory.xml 2008-05-14 02:40:04 UTC (rev 10732)
+++ trunk/pt/refman-5.1/se-memory.xml 2008-05-14 15:32:19 UTC (rev 10733)
Changed blocks: 2, Lines Added: 19, Lines Deleted: 4; 2001 bytes
@@ -230,9 +230,11 @@
value used for the life of the table. (If 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.) You can also set the
- size for individual tables, as described later in this
- section.
+ 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.
</para>
</listitem>
@@ -355,10 +357,23 @@
</programlisting>
<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.
+ </para>
+
+ <para>
You can also specify a <literal>MAX_ROWS</literal> table option in
<literal>CREATE TABLE</literal> statements for
<literal>MEMORY</literal> tables to provide a hint about the number
- of rows you plan to store in them.
+ of rows you plan to store in them. This does not allow the table to
+ grow beyond the <literal>max_heap_table_size</literal> value, which
+ still acts as a constraint on maximum table size. For maximum
+ flexibility in being able to use <literal>MAX_ROWS</literal>, set
+ <literal>max_heap_table_size</literal> at least as high as the value
+ to which you want each <literal>MEMORY</literal> table to be able to
+ grow.
</para>
<para>
Modified: trunk/refman-4.1/dba-core.xml
===================================================================
--- trunk/refman-4.1/dba-core.xml 2008-05-14 02:40:04 UTC (rev 10732)
+++ trunk/refman-4.1/dba-core.xml 2008-05-14 15:32:19 UTC (rev 10733)
Changed blocks: 1, Lines Added: 4, Lines Deleted: 1; 837 bytes
@@ -4693,7 +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>. This variable was added in MySQL 3.23.0.
+ 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.
</para>
<formalpara role="mnmas">
Modified: trunk/refman-4.1/storage-engines.xml
===================================================================
--- trunk/refman-4.1/storage-engines.xml 2008-05-14 02:40:04 UTC (rev 10732)
+++ trunk/refman-4.1/storage-engines.xml 2008-05-14 15:32:19 UTC (rev 10733)
Changed blocks: 2, Lines Added: 22, Lines Deleted: 4; 2146 bytes
@@ -2646,9 +2646,12 @@
created is the value used for the life of the table. (If
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.) You
- can also set the size for individual tables, as described
- later in this section.
+ 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.
</para>
</listitem>
@@ -2761,10 +2764,25 @@
</programlisting>
<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.
+ </para>
+
+ <para>
You can also specify a <literal>MAX_ROWS</literal> table option in
<literal>CREATE TABLE</literal> statements for
<literal>MEMORY</literal> tables to provide a hint about the
- number of rows you plan to store in them.
+ number of rows you plan to store in them. This does not allow the
+ table to grow beyond the <literal>max_heap_table_size</literal>
+ value, which still acts as a constraint on maximum table size. For
+ maximum flexibility in being able to use
+ <literal>MAX_ROWS</literal>, set
+ <literal>max_heap_table_size</literal> at least as high as the
+ value to which you want each <literal>MEMORY</literal> table to be
+ able to grow.
</para>
<para>
Modified: trunk/refman-5.0/dba-core.xml
===================================================================
--- trunk/refman-5.0/dba-core.xml 2008-05-14 02:40:04 UTC (rev 10732)
+++ trunk/refman-5.0/dba-core.xml 2008-05-14 15:32:19 UTC (rev 10733)
Changed blocks: 1, Lines Added: 4, Lines Deleted: 1; 817 bytes
@@ -5566,7 +5566,10 @@
<literal>MEMORY</literal> 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>.
+ 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.
</para>
<formalpara role="mnmas">
Modified: trunk/refman-5.0/se-memory.xml
===================================================================
--- trunk/refman-5.0/se-memory.xml 2008-05-14 02:40:04 UTC (rev 10732)
+++ trunk/refman-5.0/se-memory.xml 2008-05-14 15:32:19 UTC (rev 10733)
Changed blocks: 2, Lines Added: 19, Lines Deleted: 4; 1992 bytes
@@ -237,9 +237,11 @@
value used for the life of the table. (If 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.) You can also set the
- size for individual tables, as described later in this
- section.
+ 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.
</para>
</listitem>
@@ -362,10 +364,23 @@
</programlisting>
<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.
+ </para>
+
+ <para>
You can also specify a <literal>MAX_ROWS</literal> table option in
<literal>CREATE TABLE</literal> statements for
<literal>MEMORY</literal> tables to provide a hint about the number
- of rows you plan to store in them.
+ of rows you plan to store in them. This does not allow the table to
+ grow beyond the <literal>max_heap_table_size</literal> value, which
+ still acts as a constraint on maximum table size. For maximum
+ flexibility in being able to use <literal>MAX_ROWS</literal>, set
+ <literal>max_heap_table_size</literal> at least as high as the value
+ to which you want each <literal>MEMORY</literal> table to be able to
+ grow.
</para>
<para>
Modified: trunk/refman-5.1/dba-core.xml
===================================================================
--- trunk/refman-5.1/dba-core.xml 2008-05-14 02:40:04 UTC (rev 10732)
+++ trunk/refman-5.1/dba-core.xml 2008-05-14 15:32:19 UTC (rev 10733)
Changed blocks: 1, Lines Added: 4, Lines Deleted: 1; 817 bytes
@@ -5823,7 +5823,10 @@
<literal>MEMORY</literal> 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>.
+ 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.
</para>
<formalpara role="mnmas">
Modified: trunk/refman-5.1/se-memory.xml
===================================================================
--- trunk/refman-5.1/se-memory.xml 2008-05-14 02:40:04 UTC (rev 10732)
+++ trunk/refman-5.1/se-memory.xml 2008-05-14 15:32:19 UTC (rev 10733)
Changed blocks: 2, Lines Added: 19, Lines Deleted: 4; 1992 bytes
@@ -230,9 +230,11 @@
value used for the life of the table. (If 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.) You can also set the
- size for individual tables, as described later in this
- section.
+ 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.
</para>
</listitem>
@@ -355,10 +357,23 @@
</programlisting>
<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.
+ </para>
+
+ <para>
You can also specify a <literal>MAX_ROWS</literal> table option in
<literal>CREATE TABLE</literal> statements for
<literal>MEMORY</literal> tables to provide a hint about the number
- of rows you plan to store in them.
+ of rows you plan to store in them. This does not allow the table to
+ grow beyond the <literal>max_heap_table_size</literal> value, which
+ still acts as a constraint on maximum table size. For maximum
+ flexibility in being able to use <literal>MAX_ROWS</literal>, set
+ <literal>max_heap_table_size</literal> at least as high as the value
+ to which you want each <literal>MEMORY</literal> table to be able to
+ grow.
</para>
<para>
Modified: trunk/refman-6.0/dba-core.xml
===================================================================
--- trunk/refman-6.0/dba-core.xml 2008-05-14 02:40:04 UTC (rev 10732)
+++ trunk/refman-6.0/dba-core.xml 2008-05-14 15:32:19 UTC (rev 10733)
Changed blocks: 1, Lines Added: 4, Lines Deleted: 1; 817 bytes
@@ -5711,7 +5711,10 @@
<literal>MEMORY</literal> 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>.
+ 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.
</para>
<formalpara role="mnmas">
Modified: trunk/refman-6.0/se-memory.xml
===================================================================
--- trunk/refman-6.0/se-memory.xml 2008-05-14 02:40:04 UTC (rev 10732)
+++ trunk/refman-6.0/se-memory.xml 2008-05-14 15:32:19 UTC (rev 10733)
Changed blocks: 2, Lines Added: 19, Lines Deleted: 4; 1992 bytes
@@ -230,9 +230,11 @@
value used for the life of the table. (If 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.) You can also set the
- size for individual tables, as described later in this
- section.
+ 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.
</para>
</listitem>
@@ -355,10 +357,23 @@
</programlisting>
<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.
+ </para>
+
+ <para>
You can also specify a <literal>MAX_ROWS</literal> table option in
<literal>CREATE TABLE</literal> statements for
<literal>MEMORY</literal> tables to provide a hint about the number
- of rows you plan to store in them.
+ of rows you plan to store in them. This does not allow the table to
+ grow beyond the <literal>max_heap_table_size</literal> value, which
+ still acts as a constraint on maximum table size. For maximum
+ flexibility in being able to use <literal>MAX_ROWS</literal>, set
+ <literal>max_heap_table_size</literal> at least as high as the value
+ to which you want each <literal>MEMORY</literal> table to be able to
+ grow.
</para>
<para>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r10733 - 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 |
