Author: paul
Date: 2008-12-05 03:48:34 +0100 (Fri, 05 Dec 2008)
New Revision: 12795
Log:
r36487@frost: paul | 2008-12-04 19:00:48 -0500
Convert some system variable IDs
Add auto-link markup
Modified:
trunk/dynamic-docs/changelog/mysqld.xml
trunk/dynamic-docs/command-optvars/mysqld.xml
trunk/mysql-monitor/data-items.xml
trunk/refman-4.1/dba-core.xml
trunk/refman-4.1/errors-problems.xml
trunk/refman-4.1/news-4.0.xml
trunk/refman-4.1/optimization.xml
trunk/refman-4.1/sql-syntax-transactions.xml
trunk/refman-4.1/storage-engines.xml
trunk/refman-5.0/dba-core.xml
trunk/refman-5.0/optimization.xml
trunk/refman-5.0/se-memory.xml
trunk/refman-5.0/sql-syntax-server-administration.xml
trunk/refman-5.0/sql-syntax-transactions.xml
trunk/refman-5.1-maria/sql-syntax-server-administration.xml
trunk/refman-5.1/dba-core.xml
trunk/refman-5.1/optimization.xml
trunk/refman-5.1/se-memory.xml
trunk/refman-5.1/sql-syntax-server-administration.xml
trunk/refman-5.1/sql-syntax-transactions.xml
trunk/refman-6.0/dba-core.xml
trunk/refman-6.0/optimization.xml
trunk/refman-6.0/se-memory.xml
trunk/refman-6.0/sql-syntax-server-administration.xml
trunk/refman-6.0/sql-syntax-transactions.xml
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:39854
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:36482
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:35065
+ 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:39854
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:36487
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:35065
Modified: trunk/dynamic-docs/changelog/mysqld.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld.xml 2008-12-05 00:19:35 UTC (rev 12794)
+++ trunk/dynamic-docs/changelog/mysqld.xml 2008-12-05 02:48:34 UTC (rev 12795)
Changed blocks: 2, Lines Added: 2, Lines Deleted: 2; 918 bytes
@@ -57877,7 +57877,7 @@
<message>
<para>
- The default value of the <literal>tmp_table_size</literal>
+ The default value of the <literal role="sysvar">tmp_table_size</literal>
system variable was lowered from 32MB to 16MB because it is
bounded by the value of
<literal role="sysvar">max_heap_table_size</literal>, which has
@@ -58058,7 +58058,7 @@
<para>
Failure to allocate memory associated with
- <literal>transaction_prealloc_size</literal> could cause a
+ <literal role="sysvar">transaction_prealloc_size</literal> could cause a
server crash.
</para>
Modified: trunk/dynamic-docs/command-optvars/mysqld.xml
===================================================================
--- trunk/dynamic-docs/command-optvars/mysqld.xml 2008-12-05 00:19:35 UTC (rev 12794)
+++ trunk/dynamic-docs/command-optvars/mysqld.xml 2008-12-05 02:48:34 UTC (rev 12795)
Changed blocks: 5, Lines Added: 5, Lines Deleted: 5; 1385 bytes
@@ -19055,7 +19055,7 @@
<mysqloption section="innodb" id="timed_mutexes">
- <xrefto id="option_mysqld_timed_mutexes"/>
+ <xrefto id="sysvar_timed_mutexes"/>
<name>timed_mutexes</name>
@@ -19110,7 +19110,7 @@
<mysqloption section="myisam" id="tmp_table_size">
- <xrefto id="option_mysqld_tmp_table_size"/>
+ <xrefto id="sysvar_tmp_table_size"/>
<name>tmp_table_size</name>
@@ -19200,7 +19200,7 @@
<mysqloption section="server" id="transaction_alloc_block_size">
- <xrefto id="option_mysqld_transaction_alloc_block_size"/>
+ <xrefto id="sysvar_transaction_alloc_block_size"/>
<name>transaction_alloc_block_size</name>
@@ -19253,7 +19253,7 @@
<mysqloption section="server" id="transaction_prealloc_size">
- <xrefto id="option_mysqld_transaction_prealloc_size"/>
+ <xrefto id="sysvar_transaction_prealloc_size"/>
<name>transaction_prealloc_size</name>
@@ -19283,7 +19283,7 @@
<mysqloption section="server" id="tx_isolation">
- <xrefto id="option_mysqld_tx_isolation"/>
+ <xrefto id="sysvar_tx_isolation"/>
<name>tx_isolation</name>
Modified: trunk/mysql-monitor/data-items.xml
===================================================================
--- trunk/mysql-monitor/data-items.xml 2008-12-05 00:19:35 UTC (rev 12794)
+++ trunk/mysql-monitor/data-items.xml 2008-12-05 02:48:34 UTC (rev 12795)
Changed blocks: 3, Lines Added: 5, Lines Deleted: 5; 2597 bytes
@@ -4484,7 +4484,7 @@
<entry>0</entry>
</row>
<row>
- <entry><link linkend="option_mysqld_timed_mutexes">mysql:server:timed_mutexes</link></entry>
+ <entry><link linkend="sysvar_timed_mutexes">mysql:server:timed_mutexes</link></entry>
<entry>Specify whether to time mutexes (only InnoDB mutexes are currently
supported)</entry>
<entry>General.Miscellaneous</entry>
@@ -4513,7 +4513,7 @@
<entry>0</entry>
</row>
<row>
- <entry><link linkend="option_mysqld_tmp_table_size">mysql:server:tmp_table_size</link></entry>
+ <entry><link linkend="sysvar_tmp_table_size">mysql:server:tmp_table_size</link></entry>
<entry>If an in-memory temporary table exceeds this size, MySQL will
automatically convert it to an on-disk MyISAM table</entry>
<entry>Memory.Overview</entry>
@@ -4521,21 +4521,21 @@
<entry>0</entry>
</row>
<row>
- <entry><link linkend="option_mysqld_transaction_alloc_block_size">mysql:server:transaction_alloc_block_size</link></entry>
+ <entry><link linkend="sysvar_transaction_alloc_block_size">mysql:server:transaction_alloc_block_size</link></entry>
<entry>Allocation block size for transactions to be stored in binary log</entry>
<entry>SQL.Overview</entry>
<entry>INTEGER</entry>
<entry>0</entry>
</row>
<row>
- <entry><link linkend="option_mysqld_transaction_prealloc_size">mysql:server:transaction_prealloc_size</link></entry>
+ <entry><link linkend="sysvar_transaction_prealloc_size">mysql:server:transaction_prealloc_size</link></entry>
<entry>Persistent buffer for transactions to be stored in binary log</entry>
<entry>SQL.Overview</entry>
<entry>INTEGER</entry>
<entry>0</entry>
</row>
<row>
- <entry><link linkend="option_mysqld_tx_isolation">mysql:server:tx_isolation</link></entry>
+ <entry><link linkend="sysvar_tx_isolation">mysql:server:tx_isolation</link></entry>
<entry>The default transaction isolation level</entry>
<entry>SQL.Overview</entry>
<entry>VARCHAR</entry>
Modified: trunk/refman-4.1/dba-core.xml
===================================================================
--- trunk/refman-4.1/dba-core.xml 2008-12-05 00:19:35 UTC (rev 12794)
+++ trunk/refman-4.1/dba-core.xml 2008-12-05 02:48:34 UTC (rev 12795)
Changed blocks: 9, Lines Added: 17, Lines Deleted: 17; 5838 bytes
@@ -7275,7 +7275,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_tmp_table_size">
+ <para id="sysvar_tmp_table_size">
<indexterm>
<primary>tmp_table_size system variable</primary>
</indexterm>
@@ -7285,17 +7285,17 @@
<secondary>tmp_table_size</secondary>
</indexterm>
- <literal>tmp_table_size</literal>
+ <literal role="sysvar">tmp_table_size</literal>
</para>
<para>
The maximum size of internal in-memory temporary tables.
(The actual limit is determined as the smaller of
<literal role="sysvar">max_heap_table_size</literal> and
- <literal>tmp_table_size</literal>.) If an in-memory
+ <literal role="sysvar">tmp_table_size</literal>.) If an in-memory
temporary table exceeds the limit, MySQL automatically
converts it to an on-disk <literal>MyISAM</literal> table.
- Increase the value of <literal>tmp_table_size</literal> (and
+ Increase the value of <literal role="sysvar">tmp_table_size</literal> (and
<literal role="sysvar">max_heap_table_size</literal> if
necessary) if you do many advanced <literal>GROUP
BY</literal> queries and you have lots of memory. This
@@ -7354,7 +7354,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_transaction_alloc_block_size">
+ <para id="sysvar_transaction_alloc_block_size">
<indexterm>
<primary>transaction_alloc_block_size system variable</primary>
</indexterm>
@@ -7364,19 +7364,19 @@
<secondary>transaction_alloc_block_size</secondary>
</indexterm>
- <literal>transaction_alloc_block_size</literal>
+ <literal role="sysvar">transaction_alloc_block_size</literal>
</para>
<para>
The amount in bytes by which to increase a per-transaction
memory pool which needs memory. See the description of
- <literal>transaction_prealloc_size</literal>. This variable
+ <literal role="sysvar">transaction_prealloc_size</literal>. This variable
was added in MySQL 4.0.16.
</para>
</listitem>
<listitem>
- <para id="option_mysqld_transaction_prealloc_size">
+ <para id="sysvar_transaction_prealloc_size">
<indexterm>
<primary>transaction_prealloc_size system variable</primary>
</indexterm>
@@ -7386,23 +7386,23 @@
<secondary>transaction_prealloc_size</secondary>
</indexterm>
- <literal>transaction_prealloc_size</literal>
+ <literal role="sysvar">transaction_prealloc_size</literal>
</para>
<para>
There is a per-transaction memory pool from which various
transaction-related allocations take memory. The initial
size of the pool in bytes is
- <literal>transaction_prealloc_size</literal>. For every
+ <literal role="sysvar">transaction_prealloc_size</literal>. For every
allocation that cannot be satisfied from the pool because it
has insufficient memory available, the pool is increased by
- <literal>transaction_alloc_block_size</literal> bytes. When
+ <literal role="sysvar">transaction_alloc_block_size</literal> bytes. When
the transaction ends, the pool is truncated to
- <literal>transaction_prealloc_size</literal> bytes.
+ <literal role="sysvar">transaction_prealloc_size</literal> bytes.
</para>
<para>
- By making <literal>transaction_prealloc_size</literal>
+ By making <literal role="sysvar">transaction_prealloc_size</literal>
sufficiently large to contain all statements within a single
transaction, you can avoid many <literal>malloc()</literal>
calls. This variable was added in MySQL 4.0.16.
@@ -7410,7 +7410,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_tx_isolation">
+ <para id="sysvar_tx_isolation">
<indexterm>
<primary>tx_isolation system variable</primary>
</indexterm>
@@ -7420,7 +7420,7 @@
<secondary>tx_isolation</secondary>
</indexterm>
- <literal>tx_isolation</literal>
+ <literal role="sysvar">tx_isolation</literal>
</para>
<para>
@@ -7433,7 +7433,7 @@
<literal role="stmt" condition="set-transaction">SET
TRANSACTION ISOLATION LEVEL</literal> statement. See
<xref linkend="set-transaction"/>. If you set
- <literal>tx_isolation</literal> directly to an isolation
+ <literal role="sysvar">tx_isolation</literal> directly to an isolation
level name that contains a space, the name should be
enclosed within quotes, with the space replaced by a dash.
For example:
@@ -9327,7 +9327,7 @@
The number of in-memory temporary tables created
automatically by the server while executing statements. If
<literal>Created_tmp_disk_tables</literal> is large, you may
- want to increase the <literal>tmp_table_size</literal> value
+ want to increase the <literal role="sysvar">tmp_table_size</literal> value
to cause temporary tables to be memory-based instead of
disk-based.
</para>
Modified: trunk/refman-4.1/errors-problems.xml
===================================================================
--- trunk/refman-4.1/errors-problems.xml 2008-12-05 00:19:35 UTC (rev 12794)
+++ trunk/refman-4.1/errors-problems.xml 2008-12-05 02:48:34 UTC (rev 12795)
Changed blocks: 2, Lines Added: 2, Lines Deleted: 2; 1195 bytes
@@ -1814,7 +1814,7 @@
<para>
You are using a MySQL server older than 3.23 and an
in-memory temporary table becomes larger than
- <literal>tmp_table_size</literal> bytes. To avoid this
+ <literal role="sysvar">tmp_table_size</literal> bytes. To avoid this
problem, you can use the
<option>--tmp_table_size=<replaceable>val</replaceable></option>
option to make <command>mysqld</command> increase the
@@ -1843,7 +1843,7 @@
<para>
As of MySQL 3.23, this problem should not occur. If an
in-memory temporary table becomes larger than
- <literal>tmp_table_size</literal>, the server
+ <literal role="sysvar">tmp_table_size</literal>, the server
automatically converts it to a disk-based
<literal>MyISAM</literal> table.
</para>
Modified: trunk/refman-4.1/news-4.0.xml
===================================================================
--- trunk/refman-4.1/news-4.0.xml 2008-12-05 00:19:35 UTC (rev 12794)
+++ trunk/refman-4.1/news-4.0.xml 2008-12-05 02:48:34 UTC (rev 12795)
Changed blocks: 2, Lines Added: 3, Lines Deleted: 3; 1137 bytes
@@ -3893,8 +3893,8 @@
<literal role="sysvar">range_alloc_block_size</literal>,
<literal role="sysvar">query_alloc_block_size</literal>,
<literal role="sysvar">query_prealloc_size</literal>,
- <literal>transaction_alloc_block_size</literal>, and
- <literal>transaction_prealloc_size</literal>.
+ <literal role="sysvar">transaction_alloc_block_size</literal>, and
+ <literal role="sysvar">transaction_prealloc_size</literal>.
</para>
</listitem>
@@ -5782,7 +5782,7 @@
<para>
Fixed bug if one used a multiple-table
<literal role="stmt">UPDATE</literal> and the query required a
- temporary table bigger than <literal>tmp_table_size</literal>.
+ temporary table bigger than <literal role="sysvar">tmp_table_size</literal>.
(Bug #286)
</para>
</listitem>
Modified: trunk/refman-4.1/optimization.xml
===================================================================
--- trunk/refman-4.1/optimization.xml 2008-12-05 00:19:35 UTC (rev 12794)
+++ trunk/refman-4.1/optimization.xml 2008-12-05 02:48:34 UTC (rev 12795)
Changed blocks: 3, Lines Added: 4, Lines Deleted: 4; 2281 bytes
@@ -9883,7 +9883,7 @@
<para>
The server is copying to a temporary table on disk. The
temporary result set was larger than
- <literal>tmp_table_size</literal> and the thread is
+ <literal role="sysvar">tmp_table_size</literal> and the thread is
changing the temporary table from in-memory to disk-based
format to save memory.
</para>
@@ -12793,14 +12793,14 @@
<para>
One problem before MySQL 3.23.2 is that if an internal
in-memory heap table exceeds the size of
- <literal>tmp_table_size</literal>, the error <literal>The
+ <literal role="sysvar">tmp_table_size</literal>, the error <literal>The
table <replaceable>tbl_name</replaceable> is full</literal>
occurs. From 3.23.2 on, this is handled automatically by
changing the in-memory heap table to a disk-based
<literal>MyISAM</literal> table as necessary. To work around
this problem for older servers, you can increase the
temporary table size by setting the
- <literal>tmp_table_size</literal> option to
+ <literal role="sysvar">tmp_table_size</literal> option to
<command>mysqld</command>, or by setting the SQL option
<literal>sql_big_tables</literal> in the client program. See
<xref linkend="server-session-variables"/>.
@@ -13020,7 +13020,7 @@
TABLE</literal>. However, for internal <literal>MEMORY</literal>
tables, the actual maximum size is determined by
<literal role="sysvar">max_heap_table_size</literal> in
- combination with <literal>tmp_table_size</literal>: Whichever
+ combination with <literal role="sysvar">tmp_table_size</literal>: Whichever
value is smaller is the one that applies. If the size of an
internal <literal>MEMORY</literal> table exceeds the limit,
MySQL automatically converts it to an on-disk
Modified: trunk/refman-4.1/sql-syntax-transactions.xml
===================================================================
--- trunk/refman-4.1/sql-syntax-transactions.xml 2008-12-05 00:19:35 UTC (rev 12794)
+++ trunk/refman-4.1/sql-syntax-transactions.xml 2008-12-05 02:48:34 UTC (rev 12795)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 589 bytes
@@ -1139,7 +1139,7 @@
<para>
To determine the global and session transaction isolation levels
- at runtime, check the value of the <literal>tx_isolation</literal>
+ at runtime, check the value of the <literal role="sysvar">tx_isolation</literal>
system variable:
</para>
Modified: trunk/refman-4.1/storage-engines.xml
===================================================================
--- trunk/refman-4.1/storage-engines.xml 2008-12-05 00:19:35 UTC (rev 12794)
+++ trunk/refman-4.1/storage-engines.xml 2008-12-05 02:48:34 UTC (rev 12795)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 662 bytes
@@ -2667,7 +2667,7 @@
If an internal table becomes too large, the server
automatically converts it to an on-disk table. The size
limit is determined by the value of the
- <literal>tmp_table_size</literal> system variable.
+ <literal role="sysvar">tmp_table_size</literal> system variable.
</para>
</listitem>
Modified: trunk/refman-5.0/dba-core.xml
===================================================================
--- trunk/refman-5.0/dba-core.xml 2008-12-05 00:19:35 UTC (rev 12794)
+++ trunk/refman-5.0/dba-core.xml 2008-12-05 02:48:34 UTC (rev 12795)
Changed blocks: 14, Lines Added: 19, Lines Deleted: 19; 6668 bytes
@@ -8287,7 +8287,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_timed_mutexes">
+ <para id="sysvar_timed_mutexes">
<indexterm>
<primary>timed_mutexes system variable</primary>
</indexterm>
@@ -8297,7 +8297,7 @@
<secondary>timed_mutexes</secondary>
</indexterm>
- <literal>timed_mutexes</literal>
+ <literal role="sysvar">timed_mutexes</literal>
</para>
<para condition="dynamic:optvar:item" role="5.0:mysqld:timed_mutexes"/>
@@ -8318,7 +8318,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_tmp_table_size">
+ <para id="sysvar_tmp_table_size">
<indexterm>
<primary>tmp_table_size system variable</primary>
</indexterm>
@@ -8328,7 +8328,7 @@
<secondary>tmp_table_size</secondary>
</indexterm>
- <literal>tmp_table_size</literal>
+ <literal role="sysvar">tmp_table_size</literal>
</para>
<para condition="dynamic:optvar:item" role="5.0:mysqld:tmp_table_size"/>
@@ -8337,10 +8337,10 @@
The maximum size of internal in-memory temporary tables.
(The actual limit is determined as the smaller of
<literal role="sysvar">max_heap_table_size</literal> and
- <literal>tmp_table_size</literal>.) If an in-memory
+ <literal role="sysvar">tmp_table_size</literal>.) If an in-memory
temporary table exceeds the limit, MySQL automatically
converts it to an on-disk <literal>MyISAM</literal> table.
- Increase the value of <literal>tmp_table_size</literal> (and
+ Increase the value of <literal role="sysvar">tmp_table_size</literal> (and
<literal role="sysvar">max_heap_table_size</literal> if
necessary) if you do many advanced <literal>GROUP
BY</literal> queries and you have lots of memory. This
@@ -8397,7 +8397,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_transaction_alloc_block_size">
+ <para id="sysvar_transaction_alloc_block_size">
<indexterm>
<primary>transaction_alloc_block_size system variable</primary>
</indexterm>
@@ -8407,7 +8407,7 @@
<secondary>transaction_alloc_block_size</secondary>
</indexterm>
- <literal>transaction_alloc_block_size</literal>
+ <literal role="sysvar">transaction_alloc_block_size</literal>
</para>
<para condition="dynamic:optvar:item" role="5.0:mysqld:transaction_alloc_block_size"/>
@@ -8415,12 +8415,12 @@
<para>
The amount in bytes by which to increase a per-transaction
memory pool which needs memory. See the description of
- <literal>transaction_prealloc_size</literal>.
+ <literal role="sysvar">transaction_prealloc_size</literal>.
</para>
</listitem>
<listitem>
- <para id="option_mysqld_transaction_prealloc_size">
+ <para id="sysvar_transaction_prealloc_size">
<indexterm>
<primary>transaction_prealloc_size system variable</primary>
</indexterm>
@@ -8430,7 +8430,7 @@
<secondary>transaction_prealloc_size</secondary>
</indexterm>
- <literal>transaction_prealloc_size</literal>
+ <literal role="sysvar">transaction_prealloc_size</literal>
</para>
<para condition="dynamic:optvar:item" role="5.0:mysqld:transaction_prealloc_size"/>
@@ -8439,16 +8439,16 @@
There is a per-transaction memory pool from which various
transaction-related allocations take memory. The initial
size of the pool in bytes is
- <literal>transaction_prealloc_size</literal>. For every
+ <literal role="sysvar">transaction_prealloc_size</literal>. For every
allocation that cannot be satisfied from the pool because it
has insufficient memory available, the pool is increased by
- <literal>transaction_alloc_block_size</literal> bytes. When
+ <literal role="sysvar">transaction_alloc_block_size</literal> bytes. When
the transaction ends, the pool is truncated to
- <literal>transaction_prealloc_size</literal> bytes.
+ <literal role="sysvar">transaction_prealloc_size</literal> bytes.
</para>
<para>
- By making <literal>transaction_prealloc_size</literal>
+ By making <literal role="sysvar">transaction_prealloc_size</literal>
sufficiently large to contain all statements within a single
transaction, you can avoid many <literal>malloc()</literal>
calls.
@@ -8456,7 +8456,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_tx_isolation">
+ <para id="sysvar_tx_isolation">
<indexterm>
<primary>tx_isolation system variable</primary>
</indexterm>
@@ -8466,7 +8466,7 @@
<secondary>tx_isolation</secondary>
</indexterm>
- <literal>tx_isolation</literal>
+ <literal role="sysvar">tx_isolation</literal>
</para>
<para condition="dynamic:optvar:item" role="5.0:mysqld:tx_isolation"/>
@@ -8481,7 +8481,7 @@
<literal role="stmt" condition="set-transaction">SET
TRANSACTION ISOLATION LEVEL</literal> statement. See
<xref linkend="set-transaction"/>. If you set
- <literal>tx_isolation</literal> directly to an isolation
+ <literal role="sysvar">tx_isolation</literal> directly to an isolation
level name that contains a space, the name should be
enclosed within quotes, with the space replaced by a dash.
For example:
@@ -10514,7 +10514,7 @@
The number of in-memory temporary tables created
automatically by the server while executing statements. If
<literal>Created_tmp_disk_tables</literal> is large, you may
- want to increase the <literal>tmp_table_size</literal> value
+ want to increase the <literal role="sysvar">tmp_table_size</literal> value
to cause temporary tables to be memory-based instead of
disk-based.
</para>
Modified: trunk/refman-5.0/optimization.xml
===================================================================
--- trunk/refman-5.0/optimization.xml 2008-12-05 00:19:35 UTC (rev 12794)
+++ trunk/refman-5.0/optimization.xml 2008-12-05 02:48:34 UTC (rev 12795)
Changed blocks: 4, Lines Added: 6, Lines Deleted: 6; 2707 bytes
@@ -12291,7 +12291,7 @@
<para>
The server is copying to a temporary table on disk. The
temporary result set was larger than
- <literal>tmp_table_size</literal> and the thread is
+ <literal role="sysvar">tmp_table_size</literal> and the thread is
changing the temporary table from in-memory to disk-based
format to save memory.
</para>
@@ -15206,11 +15206,11 @@
<para>
If an internal heap table exceeds the size of
- <literal>tmp_table_size</literal>, MySQL handles this
+ <literal role="sysvar">tmp_table_size</literal>, MySQL handles this
automatically by changing the in-memory heap table to a
disk-based <literal>MyISAM</literal> table as necessary. You
can also increase the temporary table size by setting the
- <literal>tmp_table_size</literal> option to
+ <literal role="sysvar">tmp_table_size</literal> option to
<command>mysqld</command>, or by setting the SQL option
<literal>sql_big_tables</literal> in the client program. See
<xref linkend="server-session-variables"/>.
@@ -15223,9 +15223,9 @@
<para>
Subscribers to the MySQL Enterprise Monitor are alerted
when temporary tables exceed
- <literal>tmp_table_size</literal>. Advisors make
+ <literal role="sysvar">tmp_table_size</literal>. Advisors make
recommendations for the optimum value of
- <literal>tmp_table_size</literal> based on actual table
+ <literal role="sysvar">tmp_table_size</literal> based on actual table
usage. For more information about the MySQL Enterprise
Monitor please see
<ulink url="&base-url-enterprise;advisors.html"/>.
@@ -15436,7 +15436,7 @@
TABLE</literal>. However, for internal <literal>MEMORY</literal>
tables, the actual maximum size is determined by
<literal role="sysvar">max_heap_table_size</literal> in
- combination with <literal>tmp_table_size</literal>: Whichever
+ combination with <literal role="sysvar">tmp_table_size</literal>: Whichever
value is smaller is the one that applies. If the size of an
internal <literal>MEMORY</literal> table exceeds the limit,
MySQL automatically converts it to an on-disk
Modified: trunk/refman-5.0/se-memory.xml
===================================================================
--- trunk/refman-5.0/se-memory.xml 2008-12-05 00:19:35 UTC (rev 12794)
+++ trunk/refman-5.0/se-memory.xml 2008-12-05 02:48:34 UTC (rev 12795)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 628 bytes
@@ -216,7 +216,7 @@
If an internal table becomes too large, the server
automatically converts it to an on-disk table. The size
limit is determined by the value of the
- <literal>tmp_table_size</literal> system variable.
+ <literal role="sysvar">tmp_table_size</literal> system variable.
</para>
</listitem>
Modified: trunk/refman-5.0/sql-syntax-server-administration.xml
===================================================================
--- trunk/refman-5.0/sql-syntax-server-administration.xml 2008-12-05 00:19:35 UTC (rev 12794)
+++ trunk/refman-5.0/sql-syntax-server-administration.xml 2008-12-05 02:48:34 UTC (rev 12795)
Changed blocks: 1, Lines Added: 3, Lines Deleted: 3; 1094 bytes
@@ -5805,11 +5805,11 @@
<para>
<literal>OS_waits_time</literal> indicates the amount of
time (in ms) spent in operating system waits, if the
- <literal>timed_mutexes</literal> system variable is 1
- (<literal>ON</literal>). If <literal>timed_mutexes</literal>
+ <literal role="sysvar">timed_mutexes</literal> system variable is 1
+ (<literal>ON</literal>). If <literal role="sysvar">timed_mutexes</literal>
is 0 (<literal>OFF</literal>), timing is disabled, so
<literal>OS_waits_time</literal> is 0.
- <literal>timed_mutexes</literal> is off by default.
+ <literal role="sysvar">timed_mutexes</literal> is off by default.
</para>
</listitem>
Modified: trunk/refman-5.0/sql-syntax-transactions.xml
===================================================================
--- trunk/refman-5.0/sql-syntax-transactions.xml 2008-12-05 00:19:35 UTC (rev 12794)
+++ trunk/refman-5.0/sql-syntax-transactions.xml 2008-12-05 02:48:34 UTC (rev 12795)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 589 bytes
@@ -1236,7 +1236,7 @@
<para>
To determine the global and session transaction isolation levels
- at runtime, check the value of the <literal>tx_isolation</literal>
+ at runtime, check the value of the <literal role="sysvar">tx_isolation</literal>
system variable:
</para>
Modified: trunk/refman-5.1/dba-core.xml
===================================================================
--- trunk/refman-5.1/dba-core.xml 2008-12-05 00:19:35 UTC (rev 12794)
+++ trunk/refman-5.1/dba-core.xml 2008-12-05 02:48:34 UTC (rev 12795)
Changed blocks: 14, Lines Added: 19, Lines Deleted: 19; 6668 bytes
@@ -8958,7 +8958,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_timed_mutexes">
+ <para id="sysvar_timed_mutexes">
<indexterm>
<primary>timed_mutexes system variable</primary>
</indexterm>
@@ -8968,7 +8968,7 @@
<secondary>timed_mutexes</secondary>
</indexterm>
- <literal>timed_mutexes</literal>
+ <literal role="sysvar">timed_mutexes</literal>
</para>
<para condition="dynamic:optvar:item" role="5.1:mysqld:timed_mutexes"/>
@@ -8988,7 +8988,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_tmp_table_size">
+ <para id="sysvar_tmp_table_size">
<indexterm>
<primary>tmp_table_size system variable</primary>
</indexterm>
@@ -8998,7 +8998,7 @@
<secondary>tmp_table_size</secondary>
</indexterm>
- <literal>tmp_table_size</literal>
+ <literal role="sysvar">tmp_table_size</literal>
</para>
<para condition="dynamic:optvar:item" role="5.1:mysqld:tmp_table_size"/>
@@ -9007,10 +9007,10 @@
The maximum size of internal in-memory temporary tables.
(The actual limit is determined as the smaller of
<literal role="sysvar">max_heap_table_size</literal> and
- <literal>tmp_table_size</literal>.) If an in-memory
+ <literal role="sysvar">tmp_table_size</literal>.) If an in-memory
temporary table exceeds the limit, MySQL automatically
converts it to an on-disk <literal>MyISAM</literal> table.
- Increase the value of <literal>tmp_table_size</literal> (and
+ Increase the value of <literal role="sysvar">tmp_table_size</literal> (and
<literal role="sysvar">max_heap_table_size</literal> if
necessary) if you do many advanced <literal>GROUP
BY</literal> queries and you have lots of memory. This
@@ -9067,7 +9067,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_transaction_alloc_block_size">
+ <para id="sysvar_transaction_alloc_block_size">
<indexterm>
<primary>transaction_alloc_block_size system variable</primary>
</indexterm>
@@ -9077,7 +9077,7 @@
<secondary>transaction_alloc_block_size</secondary>
</indexterm>
- <literal>transaction_alloc_block_size</literal>
+ <literal role="sysvar">transaction_alloc_block_size</literal>
</para>
<para condition="dynamic:optvar:item" role="5.1:mysqld:transaction_alloc_block_size"/>
@@ -9085,12 +9085,12 @@
<para>
The amount in bytes by which to increase a per-transaction
memory pool which needs memory. See the description of
- <literal>transaction_prealloc_size</literal>.
+ <literal role="sysvar">transaction_prealloc_size</literal>.
</para>
</listitem>
<listitem>
- <para id="option_mysqld_transaction_prealloc_size">
+ <para id="sysvar_transaction_prealloc_size">
<indexterm>
<primary>transaction_prealloc_size system variable</primary>
</indexterm>
@@ -9100,7 +9100,7 @@
<secondary>transaction_prealloc_size</secondary>
</indexterm>
- <literal>transaction_prealloc_size</literal>
+ <literal role="sysvar">transaction_prealloc_size</literal>
</para>
<para condition="dynamic:optvar:item" role="5.1:mysqld:transaction_prealloc_size"/>
@@ -9109,16 +9109,16 @@
There is a per-transaction memory pool from which various
transaction-related allocations take memory. The initial
size of the pool in bytes is
- <literal>transaction_prealloc_size</literal>. For every
+ <literal role="sysvar">transaction_prealloc_size</literal>. For every
allocation that cannot be satisfied from the pool because it
has insufficient memory available, the pool is increased by
- <literal>transaction_alloc_block_size</literal> bytes. When
+ <literal role="sysvar">transaction_alloc_block_size</literal> bytes. When
the transaction ends, the pool is truncated to
- <literal>transaction_prealloc_size</literal> bytes.
+ <literal role="sysvar">transaction_prealloc_size</literal> bytes.
</para>
<para>
- By making <literal>transaction_prealloc_size</literal>
+ By making <literal role="sysvar">transaction_prealloc_size</literal>
sufficiently large to contain all statements within a single
transaction, you can avoid many <literal>malloc()</literal>
calls.
@@ -9126,7 +9126,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_tx_isolation">
+ <para id="sysvar_tx_isolation">
<indexterm>
<primary>tx_isolation system variable</primary>
</indexterm>
@@ -9136,7 +9136,7 @@
<secondary>tx_isolation</secondary>
</indexterm>
- <literal>tx_isolation</literal>
+ <literal role="sysvar">tx_isolation</literal>
</para>
<para condition="dynamic:optvar:item" role="5.1:mysqld:tx_isolation"/>
@@ -9151,7 +9151,7 @@
<literal role="stmt" condition="set-transaction">SET
TRANSACTION ISOLATION LEVEL</literal> statement. See
<xref linkend="set-transaction"/>. If you set
- <literal>tx_isolation</literal> directly to an isolation
+ <literal role="sysvar">tx_isolation</literal> directly to an isolation
level name that contains a space, the name should be
enclosed within quotes, with the space replaced by a dash.
For example:
@@ -11125,7 +11125,7 @@
The number of in-memory temporary tables created
automatically by the server while executing statements. If
<literal>Created_tmp_disk_tables</literal> is large, you may
- want to increase the <literal>tmp_table_size</literal> value
+ want to increase the <literal role="sysvar">tmp_table_size</literal> value
to cause temporary tables to be memory-based instead of
disk-based.
</para>
Modified: trunk/refman-5.1/optimization.xml
===================================================================
--- trunk/refman-5.1/optimization.xml 2008-12-05 00:19:35 UTC (rev 12794)
+++ trunk/refman-5.1/optimization.xml 2008-12-05 02:48:34 UTC (rev 12795)
Changed blocks: 4, Lines Added: 6, Lines Deleted: 6; 2707 bytes
@@ -13327,7 +13327,7 @@
<para>
The server is copying to a temporary table on disk. The
temporary result set was larger than
- <literal>tmp_table_size</literal> and the thread is
+ <literal role="sysvar">tmp_table_size</literal> and the thread is
changing the temporary table from in-memory to disk-based
format to save memory.
</para>
@@ -16371,11 +16371,11 @@
<para>
If an internal heap table exceeds the size of
- <literal>tmp_table_size</literal>, MySQL handles this
+ <literal role="sysvar">tmp_table_size</literal>, MySQL handles this
automatically by changing the in-memory heap table to a
disk-based <literal>MyISAM</literal> table as necessary. You
can also increase the temporary table size by setting the
- <literal>tmp_table_size</literal> option to
+ <literal role="sysvar">tmp_table_size</literal> option to
<command>mysqld</command>, or by setting the SQL option
<literal>sql_big_tables</literal> in the client program. See
<xref linkend="server-session-variables"/>.
@@ -16388,9 +16388,9 @@
<para>
Subscribers to the MySQL Enterprise Monitor are alerted
when temporary tables exceed
- <literal>tmp_table_size</literal>. Advisors make
+ <literal role="sysvar">tmp_table_size</literal>. Advisors make
recommendations for the optimum value of
- <literal>tmp_table_size</literal> based on actual table
+ <literal role="sysvar">tmp_table_size</literal> based on actual table
usage. For more information about the MySQL Enterprise
Monitor please see
<ulink url="&base-url-enterprise;advisors.html"/>.
@@ -16605,7 +16605,7 @@
TABLE</literal>. However, for internal <literal>MEMORY</literal>
tables, the actual maximum size is determined by
<literal role="sysvar">max_heap_table_size</literal> in
- combination with <literal>tmp_table_size</literal>: Whichever
+ combination with <literal role="sysvar">tmp_table_size</literal>: Whichever
value is smaller is the one that applies. If the size of an
internal <literal>MEMORY</literal> table exceeds the limit,
MySQL automatically converts it to an on-disk
Modified: trunk/refman-5.1/se-memory.xml
===================================================================
--- trunk/refman-5.1/se-memory.xml 2008-12-05 00:19:35 UTC (rev 12794)
+++ trunk/refman-5.1/se-memory.xml 2008-12-05 02:48:34 UTC (rev 12795)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 628 bytes
@@ -209,7 +209,7 @@
If an internal table becomes too large, the server
automatically converts it to an on-disk table. The size
limit is determined by the value of the
- <literal>tmp_table_size</literal> system variable.
+ <literal role="sysvar">tmp_table_size</literal> system variable.
</para>
</listitem>
Modified: trunk/refman-5.1/sql-syntax-server-administration.xml
===================================================================
--- trunk/refman-5.1/sql-syntax-server-administration.xml 2008-12-05 00:19:35 UTC (rev 12794)
+++ trunk/refman-5.1/sql-syntax-server-administration.xml 2008-12-05 02:48:34 UTC (rev 12795)
Changed blocks: 1, Lines Added: 3, Lines Deleted: 3; 1139 bytes
@@ -5393,12 +5393,12 @@
<para>
<literal>os_wait_times</literal> indicates the amount of
time (in ms) spent in operating system waits, if the
- <literal>timed_mutexes</literal> system variable is 1
+ <literal role="sysvar">timed_mutexes</literal> system variable is 1
(<literal>ON</literal>). If
- <literal>timed_mutexes</literal> is 0
+ <literal role="sysvar">timed_mutexes</literal> is 0
(<literal>OFF</literal>), timing is disabled, so
<literal>os_wait_times</literal> is 0.
- <literal>timed_mutexes</literal> is off by default.
+ <literal role="sysvar">timed_mutexes</literal> is off by default.
</para>
</listitem>
Modified: trunk/refman-5.1/sql-syntax-transactions.xml
===================================================================
--- trunk/refman-5.1/sql-syntax-transactions.xml 2008-12-05 00:19:35 UTC (rev 12794)
+++ trunk/refman-5.1/sql-syntax-transactions.xml 2008-12-05 02:48:34 UTC (rev 12795)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 589 bytes
@@ -1284,7 +1284,7 @@
<para>
To determine the global and session transaction isolation levels
- at runtime, check the value of the <literal>tx_isolation</literal>
+ at runtime, check the value of the <literal role="sysvar">tx_isolation</literal>
system variable:
</para>
Modified: trunk/refman-5.1-maria/sql-syntax-server-administration.xml
===================================================================
--- trunk/refman-5.1-maria/sql-syntax-server-administration.xml 2008-12-05 00:19:35 UTC (rev 12794)
+++ trunk/refman-5.1-maria/sql-syntax-server-administration.xml 2008-12-05 02:48:34 UTC (rev 12795)
Changed blocks: 1, Lines Added: 3, Lines Deleted: 3; 1157 bytes
@@ -5474,12 +5474,12 @@
<para>
<literal>os_wait_times</literal> indicates the amount of
time (in ms) spent in operating system waits, if the
- <literal>timed_mutexes</literal> system variable is 1
+ <literal role="sysvar">timed_mutexes</literal> system variable is 1
(<literal>ON</literal>). If
- <literal>timed_mutexes</literal> is 0
+ <literal role="sysvar">timed_mutexes</literal> is 0
(<literal>OFF</literal>), timing is disabled, so
<literal>os_wait_times</literal> is 0.
- <literal>timed_mutexes</literal> is off by default.
+ <literal role="sysvar">timed_mutexes</literal> is off by default.
</para>
</listitem>
Modified: trunk/refman-6.0/dba-core.xml
===================================================================
--- trunk/refman-6.0/dba-core.xml 2008-12-05 00:19:35 UTC (rev 12794)
+++ trunk/refman-6.0/dba-core.xml 2008-12-05 02:48:34 UTC (rev 12795)
Changed blocks: 14, Lines Added: 19, Lines Deleted: 19; 6668 bytes
@@ -9159,7 +9159,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_timed_mutexes">
+ <para id="sysvar_timed_mutexes">
<indexterm>
<primary>timed_mutexes system variable</primary>
</indexterm>
@@ -9169,7 +9169,7 @@
<secondary>timed_mutexes</secondary>
</indexterm>
- <literal>timed_mutexes</literal>
+ <literal role="sysvar">timed_mutexes</literal>
</para>
<para condition="dynamic:optvar:item" role="6.0:mysqld:timed_mutexes"/>
@@ -9189,7 +9189,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_tmp_table_size">
+ <para id="sysvar_tmp_table_size">
<indexterm>
<primary>tmp_table_size system variable</primary>
</indexterm>
@@ -9199,7 +9199,7 @@
<secondary>tmp_table_size</secondary>
</indexterm>
- <literal>tmp_table_size</literal>
+ <literal role="sysvar">tmp_table_size</literal>
</para>
<para condition="dynamic:optvar:item" role="6.0:mysqld:tmp_table_size"/>
@@ -9208,10 +9208,10 @@
The maximum size of internal in-memory temporary tables.
(The actual limit is determined as the smaller of
<literal role="sysvar">max_heap_table_size</literal> and
- <literal>tmp_table_size</literal>.) If an in-memory
+ <literal role="sysvar">tmp_table_size</literal>.) If an in-memory
temporary table exceeds the limit, MySQL automatically
converts it to an on-disk <literal>MyISAM</literal> table.
- Increase the value of <literal>tmp_table_size</literal> (and
+ Increase the value of <literal role="sysvar">tmp_table_size</literal> (and
<literal role="sysvar">max_heap_table_size</literal> if
necessary) if you do many advanced <literal>GROUP
BY</literal> queries and you have lots of memory. This
@@ -9268,7 +9268,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_transaction_alloc_block_size">
+ <para id="sysvar_transaction_alloc_block_size">
<indexterm>
<primary>transaction_alloc_block_size system variable</primary>
</indexterm>
@@ -9278,7 +9278,7 @@
<secondary>transaction_alloc_block_size</secondary>
</indexterm>
- <literal>transaction_alloc_block_size</literal>
+ <literal role="sysvar">transaction_alloc_block_size</literal>
</para>
<para condition="dynamic:optvar:item" role="6.0:mysqld:transaction_alloc_block_size"/>
@@ -9286,12 +9286,12 @@
<para>
The amount in bytes by which to increase a per-transaction
memory pool which needs memory. See the description of
- <literal>transaction_prealloc_size</literal>.
+ <literal role="sysvar">transaction_prealloc_size</literal>.
</para>
</listitem>
<listitem>
- <para id="option_mysqld_transaction_prealloc_size">
+ <para id="sysvar_transaction_prealloc_size">
<indexterm>
<primary>transaction_prealloc_size system variable</primary>
</indexterm>
@@ -9301,7 +9301,7 @@
<secondary>transaction_prealloc_size</secondary>
</indexterm>
- <literal>transaction_prealloc_size</literal>
+ <literal role="sysvar">transaction_prealloc_size</literal>
</para>
<para condition="dynamic:optvar:item" role="6.0:mysqld:transaction_prealloc_size"/>
@@ -9310,16 +9310,16 @@
There is a per-transaction memory pool from which various
transaction-related allocations take memory. The initial
size of the pool in bytes is
- <literal>transaction_prealloc_size</literal>. For every
+ <literal role="sysvar">transaction_prealloc_size</literal>. For every
allocation that cannot be satisfied from the pool because it
has insufficient memory available, the pool is increased by
- <literal>transaction_alloc_block_size</literal> bytes. When
+ <literal role="sysvar">transaction_alloc_block_size</literal> bytes. When
the transaction ends, the pool is truncated to
- <literal>transaction_prealloc_size</literal> bytes.
+ <literal role="sysvar">transaction_prealloc_size</literal> bytes.
</para>
<para>
- By making <literal>transaction_prealloc_size</literal>
+ By making <literal role="sysvar">transaction_prealloc_size</literal>
sufficiently large to contain all statements within a single
transaction, you can avoid many <literal>malloc()</literal>
calls.
@@ -9327,7 +9327,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_tx_isolation">
+ <para id="sysvar_tx_isolation">
<indexterm>
<primary>tx_isolation system variable</primary>
</indexterm>
@@ -9337,7 +9337,7 @@
<secondary>tx_isolation</secondary>
</indexterm>
- <literal>tx_isolation</literal>
+ <literal role="sysvar">tx_isolation</literal>
</para>
<para condition="dynamic:optvar:item" role="6.0:mysqld:tx_isolation"/>
@@ -9352,7 +9352,7 @@
<literal role="stmt" condition="set-transaction">SET
TRANSACTION ISOLATION LEVEL</literal> statement. See
<xref linkend="set-transaction"/>. If you set
- <literal>tx_isolation</literal> directly to an isolation
+ <literal role="sysvar">tx_isolation</literal> directly to an isolation
level name that contains a space, the name should be
enclosed within quotes, with the space replaced by a dash.
For example:
@@ -11352,7 +11352,7 @@
The number of in-memory temporary tables created
automatically by the server while executing statements. If
<literal>Created_tmp_disk_tables</literal> is large, you may
- want to increase the <literal>tmp_table_size</literal> value
+ want to increase the <literal role="sysvar">tmp_table_size</literal> value
to cause temporary tables to be memory-based instead of
disk-based.
</para>
Modified: trunk/refman-6.0/optimization.xml
===================================================================
--- trunk/refman-6.0/optimization.xml 2008-12-05 00:19:35 UTC (rev 12794)
+++ trunk/refman-6.0/optimization.xml 2008-12-05 02:48:34 UTC (rev 12795)
Changed blocks: 4, Lines Added: 6, Lines Deleted: 6; 2707 bytes
@@ -13679,7 +13679,7 @@
<para>
The server is copying to a temporary table on disk. The
temporary result set was larger than
- <literal>tmp_table_size</literal> and the thread is
+ <literal role="sysvar">tmp_table_size</literal> and the thread is
changing the temporary table from in-memory to disk-based
format to save memory.
</para>
@@ -16564,11 +16564,11 @@
<para>
If an internal heap table exceeds the size of
- <literal>tmp_table_size</literal>, MySQL handles this
+ <literal role="sysvar">tmp_table_size</literal>, MySQL handles this
automatically by changing the in-memory heap table to a
disk-based <literal>MyISAM</literal> table as necessary. You
can also increase the temporary table size by setting the
- <literal>tmp_table_size</literal> option to
+ <literal role="sysvar">tmp_table_size</literal> option to
<command>mysqld</command>, or by setting the SQL option
<literal>sql_big_tables</literal> in the client program. See
<xref linkend="server-session-variables"/>.
@@ -16581,9 +16581,9 @@
<para>
Subscribers to the MySQL Enterprise Monitor are alerted
when temporary tables exceed
- <literal>tmp_table_size</literal>. Advisors make
+ <literal role="sysvar">tmp_table_size</literal>. Advisors make
recommendations for the optimum value of
- <literal>tmp_table_size</literal> based on actual table
+ <literal role="sysvar">tmp_table_size</literal> based on actual table
usage. For more information about the MySQL Enterprise
Monitor please see
<ulink url="&base-url-enterprise;advisors.html"/>.
@@ -16798,7 +16798,7 @@
TABLE</literal>. However, for internal <literal>MEMORY</literal>
tables, the actual maximum size is determined by
<literal role="sysvar">max_heap_table_size</literal> in
- combination with <literal>tmp_table_size</literal>: Whichever
+ combination with <literal role="sysvar">tmp_table_size</literal>: Whichever
value is smaller is the one that applies. If the size of an
internal <literal>MEMORY</literal> table exceeds the limit,
MySQL automatically converts it to an on-disk
Modified: trunk/refman-6.0/se-memory.xml
===================================================================
--- trunk/refman-6.0/se-memory.xml 2008-12-05 00:19:35 UTC (rev 12794)
+++ trunk/refman-6.0/se-memory.xml 2008-12-05 02:48:34 UTC (rev 12795)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 628 bytes
@@ -209,7 +209,7 @@
If an internal table becomes too large, the server
automatically converts it to an on-disk table. The size
limit is determined by the value of the
- <literal>tmp_table_size</literal> system variable.
+ <literal role="sysvar">tmp_table_size</literal> system variable.
</para>
</listitem>
Modified: trunk/refman-6.0/sql-syntax-server-administration.xml
===================================================================
--- trunk/refman-6.0/sql-syntax-server-administration.xml 2008-12-05 00:19:35 UTC (rev 12794)
+++ trunk/refman-6.0/sql-syntax-server-administration.xml 2008-12-05 02:48:34 UTC (rev 12795)
Changed blocks: 1, Lines Added: 3, Lines Deleted: 3; 1139 bytes
@@ -5571,12 +5571,12 @@
<para>
<literal>os_wait_times</literal> indicates the amount of
time (in ms) spent in operating system waits, if the
- <literal>timed_mutexes</literal> system variable is 1
+ <literal role="sysvar">timed_mutexes</literal> system variable is 1
(<literal>ON</literal>). If
- <literal>timed_mutexes</literal> is 0
+ <literal role="sysvar">timed_mutexes</literal> is 0
(<literal>OFF</literal>), timing is disabled, so
<literal>os_wait_times</literal> is 0.
- <literal>timed_mutexes</literal> is off by default.
+ <literal role="sysvar">timed_mutexes</literal> is off by default.
</para>
</listitem>
Modified: trunk/refman-6.0/sql-syntax-transactions.xml
===================================================================
--- trunk/refman-6.0/sql-syntax-transactions.xml 2008-12-05 00:19:35 UTC (rev 12794)
+++ trunk/refman-6.0/sql-syntax-transactions.xml 2008-12-05 02:48:34 UTC (rev 12795)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 589 bytes
@@ -1954,7 +1954,7 @@
<para>
To determine the global and session transaction isolation levels
- at runtime, check the value of the <literal>tx_isolation</literal>
+ at runtime, check the value of the <literal role="sysvar">tx_isolation</literal>
system variable:
</para>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r12795 - in trunk: . dynamic-docs/changelog dynamic-docs/command-optvars mysql-monitor refman-4.1 refman-5.0 refman-5.1... | paul.dubois | 5 Dec |
