Author: paul
Date: 2008-12-02 03:57:31 +0100 (Tue, 02 Dec 2008)
New Revision: 12727
Log:
r36305@frost: paul | 2008-12-01 20:53:41 -0500
Convert some system variable IDs
Add auto-link markup
Modified:
trunk/dynamic-docs/changelog/mysqld-1.xml
trunk/dynamic-docs/changelog/mysqld.xml
trunk/dynamic-docs/command-optvars/mysqld.xml
trunk/mysql-monitor/data-items.xml
trunk/refman-4.1/data-types.xml
trunk/refman-4.1/dba-core.xml
trunk/refman-4.1/errors-problems.xml
trunk/refman-4.1/installing.xml
trunk/refman-4.1/news-3.23.xml
trunk/refman-4.1/news-4.0.xml
trunk/refman-4.1/optimization.xml
trunk/refman-4.1/programs-admin-util.xml
trunk/refman-4.1/programs-client.xml
trunk/refman-4.1/replication-options-core.xml
trunk/refman-4.1/replication.xml
trunk/refman-4.1/se-innodb-core.xml
trunk/refman-4.1/sql-syntax-data-definition.xml
trunk/refman-4.1/sql-syntax-prepared-statements.xml
trunk/refman-4.1/sql-syntax-server-administration.xml
trunk/refman-4.1/storage-engines.xml
trunk/refman-5.0/data-types.xml
trunk/refman-5.0/dba-core.xml
trunk/refman-5.0/errors-problems.xml
trunk/refman-5.0/optimization.xml
trunk/refman-5.0/programs-admin-util-core.xml
trunk/refman-5.0/programs-client-core.xml
trunk/refman-5.0/replication-implementation.xml
trunk/refman-5.0/replication-options-core.xml
trunk/refman-5.0/se-innodb-core.xml
trunk/refman-5.0/se-myisam-core.xml
trunk/refman-5.0/sql-syntax-data-definition.xml
trunk/refman-5.0/sql-syntax-prepared-statements.xml
trunk/refman-5.0/sql-syntax-server-administration.xml
trunk/refman-5.0/stored-routines.xml
trunk/refman-5.1-maria/sql-syntax-server-administration.xml
trunk/refman-5.1/data-types.xml
trunk/refman-5.1/dba-core.xml
trunk/refman-5.1/errors-problems-core.xml
trunk/refman-5.1/optimization.xml
trunk/refman-5.1/partitioning.xml
trunk/refman-5.1/programs-admin-util-core.xml
trunk/refman-5.1/programs-client-core.xml
trunk/refman-5.1/replication-implementation.xml
trunk/refman-5.1/replication-options-core.xml
trunk/refman-5.1/se-innodb-core.xml
trunk/refman-5.1/se-myisam-core.xml
trunk/refman-5.1/sql-syntax-data-definition.xml
trunk/refman-5.1/sql-syntax-prepared-statements.xml
trunk/refman-5.1/sql-syntax-server-administration.xml
trunk/refman-5.1/stored-routines.xml
trunk/refman-6.0/data-types.xml
trunk/refman-6.0/dba-core.xml
trunk/refman-6.0/errors-problems.xml
trunk/refman-6.0/optimization.xml
trunk/refman-6.0/partitioning.xml
trunk/refman-6.0/programs-admin-util-core.xml
trunk/refman-6.0/programs-client-core.xml
trunk/refman-6.0/replication-implementation.xml
trunk/refman-6.0/replication-options-core.xml
trunk/refman-6.0/se-innodb-core.xml
trunk/refman-6.0/se-myisam-core.xml
trunk/refman-6.0/sql-syntax-data-definition.xml
trunk/refman-6.0/sql-syntax-prepared-statements.xml
trunk/refman-6.0/sql-syntax-server-administration.xml
trunk/refman-6.0/stored-routines.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:36300
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:34596
+ 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:39854
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:36305
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:34596
Modified: trunk/dynamic-docs/changelog/mysqld-1.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld-1.xml 2008-12-02 00:15:15 UTC (rev 12726)
+++ trunk/dynamic-docs/changelog/mysqld-1.xml 2008-12-02 02:57:31 UTC (rev 12727)
Changed blocks: 4, Lines Added: 4, Lines Deleted: 4; 1604 bytes
@@ -10144,7 +10144,7 @@
<para>
<literal>SET GLOBAL myisam_max_sort_file_size=DEFAULT</literal>
- set <literal>myisam_max_sort_file_size</literal> to an incorrect
+ set <literal role="sysvar">myisam_max_sort_file_size</literal> to an incorrect
value.
</para>
@@ -28193,7 +28193,7 @@
<para>
Unindexed <literal>ORDER BY</literal> did not work on short
<literal>utf32</literal> columns, or on <literal>utf16</literal>
- columns with a short <literal>max_sort_length</literal> value.
+ columns with a short <literal role="sysvar">max_sort_length</literal> value.
</para>
</message>
@@ -45065,7 +45065,7 @@
<para>
<literal>SET GLOBAL myisam_max_sort_file_size=DEFAULT</literal>
- set <literal>myisam_max_sort_file_size</literal> to an incorrect
+ set <literal role="sysvar">myisam_max_sort_file_size</literal> to an incorrect
value.
</para>
@@ -63114,7 +63114,7 @@
<para>
Unindexed <literal>ORDER BY</literal> did not work on short
<literal>utf32</literal> columns, or on <literal>utf16</literal>
- columns with a short <literal>max_sort_length</literal> value.
+ columns with a short <literal role="sysvar">max_sort_length</literal> value.
</para>
</message>
Modified: trunk/dynamic-docs/changelog/mysqld.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld.xml 2008-12-02 00:15:15 UTC (rev 12726)
+++ trunk/dynamic-docs/changelog/mysqld.xml 2008-12-02 02:57:31 UTC (rev 12727)
Changed blocks: 21, Lines Added: 21, Lines Deleted: 21; 7766 bytes
@@ -2131,7 +2131,7 @@
<command>mysqld</command>.
<literal>--log-slow-slave-statements</literal> causes slow
statements executed by a replication slave to be written to the
- slow query log; <literal>min_examined_row_limit</literal> can be
+ slow query log; <literal role="sysvar">min_examined_row_limit</literal> can be
used to cause queries which examine fewer than the stated number
of rows not to be logged.
</para>
@@ -19542,7 +19542,7 @@
<para>
The value of <literal>max_connections_per_hour</literal> was
- capped by the unrelated <literal>max_user_connections</literal>
+ capped by the unrelated <literal role="sysvar">max_user_connections</literal>
setting.
</para>
@@ -19562,7 +19562,7 @@
<para>
The value of <literal>max_connections_per_hour</literal> was
- capped by the unrelated <literal>max_user_connections</literal>
+ capped by the unrelated <literal role="sysvar">max_user_connections</literal>
setting.
</para>
@@ -32263,7 +32263,7 @@
<message>
<para>
- Added the <literal>myisam_stats_method</literal>, which controls
+ Added the <literal role="sysvar">myisam_stats_method</literal>, which controls
whether <literal>NULL</literal> values in indexes are considered
the same or different when collecting statistics for
<literal>MyISAM</literal> tables. This influences the query
@@ -35825,7 +35825,7 @@
<para>
Changed default value of
- <literal>myisam_data_pointer_size</literal> from 4 to 6. This
+ <literal role="sysvar">myisam_data_pointer_size</literal> from 4 to 6. This
allows us to avoid <literal>table is full</literal> errors for
most cases.
</para>
@@ -42153,7 +42153,7 @@
<para>
Attempting to repair a table having a fulltext index on a column
containing words whose length exceeded 21 characters and where
- <literal>myisam_repair_threads</literal> was greater than 1
+ <literal role="sysvar">myisam_repair_threads</literal> was greater than 1
would crash the server.
</para>
@@ -57354,7 +57354,7 @@
<para>
<literal role="stmt">OPTIMIZE TABLE</literal> with
- <literal>myisam_repair_threads</literal> > 1 could result in
+ <literal role="sysvar">myisam_repair_threads</literal> > 1 could result in
<literal>MyISAM</literal> table corruption.
</para>
@@ -61393,7 +61393,7 @@
<message>
<para>
- Insufficient memory (<literal>myisam_sort_buffer_size</literal>)
+ Insufficient memory (<literal role="sysvar">myisam_sort_buffer_size</literal>)
could cause a server crash for several operations on
<literal>MyISAM</literal> tables: repair table, create index by
sort, repair by sort, parallel repair, bulk insert.
@@ -64455,7 +64455,7 @@
<message>
<para>
- The <literal>myisam_stats_method</literal> variable was
+ The <literal role="sysvar">myisam_stats_method</literal> variable was
mishandled when set from an option file or on the command line.
</para>
@@ -66862,7 +66862,7 @@
<para>
Index corruption could occur in cases when
<literal role="sysvar">key_cache_block_size</literal> was not a
- multiple of <literal>myisam_block_size</literal> (for example,
+ multiple of <literal role="sysvar">myisam_block_size</literal> (for example,
with <literal>key_cache_block_size = 1536</literal> and
<literal>myisam_block_size = 1024</literal>).
</para>
@@ -87495,7 +87495,7 @@
<para>
Parallel repair (<command>myisamchk -p</command>,
- <literal>myisam_repair_threads</literal>) sometimes failed to
+ <literal role="sysvar">myisam_repair_threads</literal>) sometimes failed to
repair a table.
</para>
@@ -89565,7 +89565,7 @@
<message>
<para>
- Setting the <literal>myisam_repair_threads</literal> system
+ Setting the <literal role="sysvar">myisam_repair_threads</literal> system
variable to a value larger than 1 could cause corruption of
large <literal>MyISAM</literal> tables.
</para>
@@ -101829,7 +101829,7 @@
<message>
<para>
- New <literal>myisam_data_pointer_size</literal> system variable.
+ New <literal role="sysvar">myisam_data_pointer_size</literal> system variable.
See <xref linkend="server-system-variables"/>.
</para>
@@ -111026,7 +111026,7 @@
<message>
<para>
- Setting <literal>myisam_repair_threads</literal> caused any
+ Setting <literal role="sysvar">myisam_repair_threads</literal> caused any
repair operation on a <literal>MyISAM</literal> table to fail to
update the cardinality of indexes, instead making them always
equal to 1.
@@ -116930,7 +116930,7 @@
<message>
<para>
- Added the global <literal>max_prepared_stmt_count</literal>
+ Added the global <literal role="sysvar">max_prepared_stmt_count</literal>
system variable to limit the total number of prepared statements
in the server. This limits the potential for denial-of-service
attacks based on running the server out of memory by preparing
@@ -125634,7 +125634,7 @@
<message>
<para>
- If <literal>max_join_size</literal> was set, a query containing
+ If <literal role="sysvar">max_join_size</literal> was set, a query containing
a subquery that exceeded the examined-rows limit could hang.
</para>
@@ -126340,7 +126340,7 @@
<message>
<para>
- Added the <literal>myisam_use_mmap</literal> system variable.
+ Added the <literal role="sysvar">myisam_use_mmap</literal> system variable.
</para>
</message>
@@ -127195,7 +127195,7 @@
<message>
<para>
- The values of the <literal>max_sort_length</literal>,
+ The values of the <literal role="sysvar">max_sort_length</literal>,
<literal>sql_mode</literal>, and
<literal role="sysvar">group_concat_max_len</literal> system
variables now are stored in the query cache with other query
@@ -135636,7 +135636,7 @@
<message>
<para>
- WIth small values of <literal>myisam_sort_buffer_size</literal>,
+ WIth small values of <literal role="sysvar">myisam_sort_buffer_size</literal>,
<literal role="stmt">REPAIR TABLE</literal> for
<literal>MyISAM</literal> tables could cause a server crash.
</para>
@@ -136995,7 +136995,7 @@
<para>
For <literal role="sysvar">join_buffer_size</literal>,
<literal>sort_buffer_size</literal>, and
- <literal>myisam_sort_buffer_size</literal>, values are
+ <literal role="sysvar">myisam_sort_buffer_size</literal>, values are
limited to 4GB on all platforms. Larger values are truncated
to 4GB with a warning.
</para>
@@ -137043,7 +137043,7 @@
<para>
For <literal role="sysvar">join_buffer_size</literal>,
<literal>sort_buffer_size</literal>, and
- <literal>myisam_sort_buffer_size</literal>, values larger
+ <literal role="sysvar">myisam_sort_buffer_size</literal>, values larger
than 4GB are allowed on 64-bit platforms (except Windows,
for which large values are truncated to 4GB with a warning).
</para>
Modified: trunk/dynamic-docs/command-optvars/mysqld.xml
===================================================================
--- trunk/dynamic-docs/command-optvars/mysqld.xml 2008-12-02 00:15:15 UTC (rev 12726)
+++ trunk/dynamic-docs/command-optvars/mysqld.xml 2008-12-02 02:57:31 UTC (rev 12727)
Changed blocks: 20, Lines Added: 20, Lines Deleted: 20; 4736 bytes
@@ -13416,7 +13416,7 @@
<mysqloption section="server" id="max_insert_delayed_threads">
- <xrefto id="option_mysqld_max_insert_delayed_threads"/>
+ <xrefto id="sysvar_max_insert_delayed_threads"/>
<name>max_insert_delayed_threads</name>
@@ -13443,7 +13443,7 @@
<mysqloption section="server" id="max_join_size">
- <xrefto id="option_mysqld_max_join_size"/>
+ <xrefto id="sysvar_max_join_size"/>
<name>max_join_size</name>
@@ -13473,7 +13473,7 @@
<mysqloption section="server" id="max_length_for_sort_data">
- <xrefto id="option_mysqld_max_length_for_sort_data"/>
+ <xrefto id="sysvar_max_length_for_sort_data"/>
<name>max_length_for_sort_data</name>
@@ -13504,7 +13504,7 @@
<mysqloption section="server" id="max_prepared_stmt_count">
- <xrefto id="option_mysqld_max_prepared_stmt_count"/>
+ <xrefto id="sysvar_max_prepared_stmt_count"/>
<name>max_prepared_stmt_count</name>
@@ -13539,7 +13539,7 @@
<mysqloption section="server" id="max_relay_log_size">
- <xrefto id="option_mysqld_max_relay_log_size"/>
+ <xrefto id="sysvar_max_relay_log_size"/>
<name>max_relay_log_size</name>
@@ -13569,7 +13569,7 @@
<mysqloption section="server" id="max_seeks_for_key">
- <xrefto id="option_mysqld_max_seeks_for_key"/>
+ <xrefto id="sysvar_max_seeks_for_key"/>
<name>max_seeks_for_key</name>
@@ -13599,7 +13599,7 @@
<mysqloption section="server" id="max_sort_length">
- <xrefto id="option_mysqld_max_sort_length"/>
+ <xrefto id="sysvar_max_sort_length"/>
<name>max_sort_length</name>
@@ -13628,7 +13628,7 @@
<mysqloption section="server" id="max_sp_recursion_depth">
- <xrefto id="option_mysqld_max_sp_recursion_depth"/>
+ <xrefto id="sysvar_max_sp_recursion_depth"/>
<name>max_sp_recursion_depth</name>
@@ -13658,7 +13658,7 @@
<mysqloption section="server" id="max_tmp_tables">
- <xrefto id="option_mysqld_max_tmp_tables"/>
+ <xrefto id="sysvar_max_tmp_tables"/>
<name>max_tmp_tables</name>
@@ -13688,7 +13688,7 @@
<mysqloption section="server" id="max_user_connections">
- <xrefto id="option_mysqld_max_user_connections"/>
+ <xrefto id="sysvar_max_user_connections"/>
<name>max_user_connections</name>
@@ -13719,7 +13719,7 @@
<mysqloption section="server" id="max_write_lock_count">
- <xrefto id="option_mysqld_max_write_lock_count"/>
+ <xrefto id="sysvar_max_write_lock_count"/>
<name>max_write_lock_count</name>
@@ -13910,7 +13910,7 @@
<mysqloption section="myisam" id="myisam_recover_options">
- <xrefto id="option_mysqld_myisam_recover_options"/>
+ <xrefto id="sysvar_myisam_recover_options"/>
<name>myisam_recover_options</name>
@@ -13964,7 +13964,7 @@
<mysqloption section="myisam" id="myisam_block_size">
- <xrefto id="option_mysqld_myisam_block_size"/>
+ <xrefto id="sysvar_myisam_block_size"/>
<name>myisam_block_size</name>
@@ -13992,7 +13992,7 @@
<mysqloption section="myisam" id="myisam_data_pointer_size">
- <xrefto id="option_mysqld_myisam_data_pointer_size"/>
+ <xrefto id="sysvar_myisam_data_pointer_size"/>
<name>myisam_data_pointer_size</name>
@@ -14061,7 +14061,7 @@
<mysqloption section="myisam" id="myisam_max_sort_file_size">
- <xrefto id="option_mysqld_myisam_max_sort_file_size"/>
+ <xrefto id="sysvar_myisam_max_sort_file_size"/>
<name>myisam_max_sort_file_size</name>
@@ -14124,7 +14124,7 @@
<mysqloption section="myisam" id="myisam_repair_threads">
- <xrefto id="option_mysqld_myisam_repair_threads"/>
+ <xrefto id="sysvar_myisam_repair_threads"/>
<name>myisam_repair_threads</name>
@@ -14154,7 +14154,7 @@
<mysqloption section="myisam" id="myisam_sort_buffer_size">
- <xrefto id="option_mysqld_myisam_sort_buffer_size"/>
+ <xrefto id="sysvar_myisam_sort_buffer_size"/>
<name>myisam_sort_buffer_size</name>
@@ -14184,7 +14184,7 @@
<mysqloption section="myisam" id="myisam_stats_method">
- <xrefto id="option_mysqld_myisam_stats_method"/>
+ <xrefto id="sysvar_myisam_stats_method"/>
<name>myisam_stats_method</name>
@@ -14223,7 +14223,7 @@
<!-- check 5.1 manual -->
- <xrefto id="option_mysqld_myisam_use_mmap"/>
+ <xrefto id="sysvar_myisam_use_mmap"/>
<name>myisam_use_mmap</name>
@@ -18052,7 +18052,7 @@
<mysqloption section="server" id="sql_max_join_size">
- <xrefto id="option_mysqld_max_join_size"/>
+ <xrefto id="sysvar_max_join_size"/>
<name>sql_max_join_size</name>
Modified: trunk/mysql-monitor/data-items.xml
===================================================================
--- trunk/mysql-monitor/data-items.xml 2008-12-02 00:15:15 UTC (rev 12726)
+++ trunk/mysql-monitor/data-items.xml 2008-12-02 02:57:31 UTC (rev 12727)
Changed blocks: 10, Lines Added: 16, Lines Deleted: 16; 7918 bytes
@@ -3265,14 +3265,14 @@
<entry>0</entry>
</row>
<row>
- <entry><link linkend="option_mysqld_max_insert_delayed_threads">mysql:server:max_insert_delayed_threads</link></entry>
+ <entry><link linkend="sysvar_max_insert_delayed_threads">mysql:server:max_insert_delayed_threads</link></entry>
<entry>This variable is a synonym for max_delayed_threads</entry>
<entry>General.Performance</entry>
<entry>INTEGER</entry>
<entry>0</entry>
</row>
<row>
- <entry><link linkend="option_mysqld_max_join_size">mysql:server:max_join_size</link></entry>
+ <entry><link linkend="sysvar_max_join_size">mysql:server:max_join_size</link></entry>
<entry>Joins that are probably going to read more than max_join_size records
return an error</entry>
<entry>General.Performance</entry>
@@ -3280,21 +3280,21 @@
<entry>0</entry>
</row>
<row>
- <entry><link linkend="option_mysqld_max_length_for_sort_data">mysql:server:max_length_for_sort_data</link></entry>
+ <entry><link linkend="sysvar_max_length_for_sort_data">mysql:server:max_length_for_sort_data</link></entry>
<entry>Max number of bytes in sorted records</entry>
<entry>General.Miscellaneous</entry>
<entry>INTEGER</entry>
<entry>0</entry>
</row>
<row>
- <entry><link linkend="option_mysqld_max_prepared_stmt_count">mysql:server:max_prepared_stmt_count</link></entry>
+ <entry><link linkend="sysvar_max_prepared_stmt_count">mysql:server:max_prepared_stmt_count</link></entry>
<entry>Maximum number of prepared statements in the server</entry>
<entry>General.Features</entry>
<entry>INTEGER</entry>
<entry>0</entry>
</row>
<row>
- <entry><link linkend="option_mysqld_max_relay_log_size">mysql:server:max_relay_log_size</link></entry>
+ <entry><link linkend="sysvar_max_relay_log_size">mysql:server:max_relay_log_size</link></entry>
<entry>If non-zero: relay log will be rotated automatically when the size
exceeds this value</entry>
<entry>General.Logs</entry>
@@ -3302,28 +3302,28 @@
<entry>0</entry>
</row>
<row>
- <entry><link linkend="option_mysqld_max_seeks_for_key">mysql:server:max_seeks_for_key</link></entry>
+ <entry><link linkend="sysvar_max_seeks_for_key">mysql:server:max_seeks_for_key</link></entry>
<entry>Limit assumed max number of seeks when looking up rows based on a key</entry>
<entry>General.Performance</entry>
<entry>INTEGER</entry>
<entry>0</entry>
</row>
<row>
- <entry><link linkend="option_mysqld_max_sort_length">mysql:server:max_sort_length</link></entry>
+ <entry><link linkend="sysvar_max_sort_length">mysql:server:max_sort_length</link></entry>
<entry>The number of bytes to use when sorting BLOB or TEXT values</entry>
<entry>General.Performance</entry>
<entry>INTEGER</entry>
<entry>0</entry>
</row>
<row>
- <entry><link linkend="option_mysqld_max_sp_recursion_depth">mysql:server:max_sp_recursion_depth</link></entry>
+ <entry><link linkend="sysvar_max_sp_recursion_depth">mysql:server:max_sp_recursion_depth</link></entry>
<entry>Maximum stored procedure recursion depth</entry>
<entry>General.Features</entry>
<entry>INTEGER</entry>
<entry>0</entry>
</row>
<row>
- <entry><link linkend="option_mysqld_max_tmp_tables">mysql:server:max_tmp_tables</link></entry>
+ <entry><link linkend="sysvar_max_tmp_tables">mysql:server:max_tmp_tables</link></entry>
<entry>Maximum number of temporary tables a client can keep open at a time</entry>
<entry>Memory.Overview</entry>
<entry>INTEGER</entry>
@@ -3338,7 +3338,7 @@
<entry>0</entry>
</row>
<row>
- <entry><link linkend="option_mysqld_max_user_connections">mysql:server:max_user_connections</link></entry>
+ <entry><link linkend="sysvar_max_user_connections">mysql:server:max_user_connections</link></entry>
<entry>The maximum number of active connections for a single user (0 = no
limit)</entry>
<entry>Connections.Overview</entry>
@@ -3346,7 +3346,7 @@
<entry>0</entry>
</row>
<row>
- <entry><link linkend="option_mysqld_max_write_lock_count">mysql:server:max_write_lock_count</link></entry>
+ <entry><link linkend="sysvar_max_write_lock_count">mysql:server:max_write_lock_count</link></entry>
<entry>After this many write locks, allow some read locks to run in between</entry>
<entry>General.Performance</entry>
<entry>INTEGER</entry>
@@ -3361,7 +3361,7 @@
<entry>0</entry>
</row>
<row>
- <entry><link linkend="option_mysqld_myisam_data_pointer_size">mysql:server:myisam_data_pointer_size</link></entry>
+ <entry><link linkend="sysvar_myisam_data_pointer_size">mysql:server:myisam_data_pointer_size</link></entry>
<entry>Default pointer size to be used for MyISAM tables</entry>
<entry>Table Types.MyISAM</entry>
<entry>INTEGER</entry>
@@ -3375,7 +3375,7 @@
<entry>0</entry>
</row>
<row>
- <entry><link linkend="option_mysqld_myisam_max_sort_file_size">mysql:server:myisam_max_sort_file_size</link></entry>
+ <entry><link linkend="sysvar_myisam_max_sort_file_size">mysql:server:myisam_max_sort_file_size</link></entry>
<entry>Don't use the fast sort index method to created index if the temporary
file would get bigger than this</entry>
<entry>Table Types.MyISAM</entry>
@@ -3390,7 +3390,7 @@
<entry>0</entry>
</row>
<row>
- <entry><link linkend="option_mysqld_myisam_repair_threads">mysql:server:myisam_repair_threads</link></entry>
+ <entry><link linkend="sysvar_myisam_repair_threads">mysql:server:myisam_repair_threads</link></entry>
<entry>Number of threads to use when repairing MyISAM tables. The value of 1
disables parallel repair</entry>
<entry>Table Types.MyISAM</entry>
@@ -3398,7 +3398,7 @@
<entry>0</entry>
</row>
<row>
- <entry><link linkend="option_mysqld_myisam_sort_buffer_size">mysql:server:myisam_sort_buffer_size</link></entry>
+ <entry><link linkend="sysvar_myisam_sort_buffer_size">mysql:server:myisam_sort_buffer_size</link></entry>
<entry>The buffer that is allocated when sorting the index when doing a REPAIR
or when creating indexes with CREATE INDEX or ALTER TABLE</entry>
<entry>Memory.Buffers</entry>
@@ -3406,7 +3406,7 @@
<entry>0</entry>
</row>
<row>
- <entry><link linkend="option_mysqld_myisam_stats_method">mysql:server:myisam_stats_method</link></entry>
+ <entry><link linkend="sysvar_myisam_stats_method">mysql:server:myisam_stats_method</link></entry>
<entry>Specifies how MyISAM index statistics collection code should treat NULLs</entry>
<entry>General.Features</entry>
<entry>VARCHAR</entry>
Modified: trunk/refman-4.1/data-types.xml
===================================================================
--- trunk/refman-4.1/data-types.xml 2008-12-02 00:15:15 UTC (rev 12726)
+++ trunk/refman-4.1/data-types.xml 2008-12-02 02:57:31 UTC (rev 12727)
Changed blocks: 3, Lines Added: 5, Lines Deleted: 5; 1934 bytes
@@ -5127,9 +5127,9 @@
<listitem>
<para>
- Only the first <literal>max_sort_length</literal> bytes of
+ Only the first <literal role="sysvar">max_sort_length</literal> bytes of
the column are used when sorting. The default value of
- <literal>max_sort_length</literal> is 1024. This value can
+ <literal role="sysvar">max_sort_length</literal> is 1024. This value can
be changed using the
<option>--max_sort_length=<replaceable>N</replaceable></option>
option when starting the <command>mysqld</command> server.
@@ -5139,9 +5139,9 @@
<para>
As of MySQL 4.0.3, you can make more bytes significant in
sorting or grouping by increasing the value of
- <literal>max_sort_length</literal> at runtime. Any client
+ <literal role="sysvar">max_sort_length</literal> at runtime. Any client
can change the value of its session
- <literal>max_sort_length</literal> variable:
+ <literal role="sysvar">max_sort_length</literal> variable:
</para>
<programlisting>
@@ -5156,7 +5156,7 @@
<literal role="type">BLOB</literal> or
<literal role="type">TEXT</literal> column containing long
values when you want more than
- <literal>max_sort_length</literal> bytes to be significant
+ <literal role="sysvar">max_sort_length</literal> bytes to be significant
is to convert the column value into a fixed-length object.
The standard way to do this is with the
<literal role="func">SUBSTRING()</literal> function. For
Modified: trunk/refman-4.1/dba-core.xml
===================================================================
--- trunk/refman-4.1/dba-core.xml 2008-12-02 00:15:15 UTC (rev 12726)
+++ trunk/refman-4.1/dba-core.xml 2008-12-02 02:57:31 UTC (rev 12727)
Changed blocks: 43, Lines Added: 50, Lines Deleted: 50; 16262 bytes
@@ -5406,7 +5406,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_max_insert_delayed_threads">
+ <para id="sysvar_max_insert_delayed_threads">
<indexterm>
<primary>max_insert_delayed_threads system variable</primary>
</indexterm>
@@ -5416,7 +5416,7 @@
<secondary>max_insert_delayed_threads</secondary>
</indexterm>
- <literal>max_insert_delayed_threads</literal>
+ <literal role="sysvar">max_insert_delayed_threads</literal>
</para>
<para>
@@ -5427,7 +5427,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_max_join_size">
+ <para id="sysvar_max_join_size">
<indexterm>
<primary>max_join_size system variable</primary>
</indexterm>
@@ -5437,16 +5437,16 @@
<secondary>max_join_size</secondary>
</indexterm>
- <literal>max_join_size</literal>
+ <literal role="sysvar">max_join_size</literal>
</para>
<para>
Do not allow <literal role="stmt">SELECT</literal>
statements that probably need to examine more than
- <literal>max_join_size</literal> rows (for single-table
+ <literal role="sysvar">max_join_size</literal> rows (for single-table
statements) or row combinations (for multiple-table
statements) or that are likely to do more than
- <literal>max_join_size</literal> disk seeks. By setting this
+ <literal role="sysvar">max_join_size</literal> disk seeks. By setting this
value, you can catch <literal role="stmt">SELECT</literal>
statements where keys are not used properly and that would
probably take a long time. Set it if your users tend to
@@ -5460,7 +5460,7 @@
<literal role="sysvar">sql_big_selects</literal> to
<literal>0</literal>. If you set the
<literal role="sysvar">sql_big_selects</literal> value
- again, the <literal>max_join_size</literal> variable is
+ again, the <literal role="sysvar">max_join_size</literal> variable is
ignored.
</para>
@@ -5478,7 +5478,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_max_length_for_sort_data">
+ <para id="sysvar_max_length_for_sort_data">
<indexterm>
<primary>max_length_for_sort_data system variable</primary>
</indexterm>
@@ -5488,7 +5488,7 @@
<secondary>max_length_for_sort_data</secondary>
</indexterm>
- <literal>max_length_for_sort_data</literal>
+ <literal role="sysvar">max_length_for_sort_data</literal>
</para>
<para>
@@ -5500,7 +5500,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_max_prepared_stmt_count">
+ <para id="sysvar_max_prepared_stmt_count">
<indexterm>
<primary>max_prepared_stmt_count system variable</primary>
</indexterm>
@@ -5510,7 +5510,7 @@
<secondary>max_prepared_stmt_count</secondary>
</indexterm>
- <literal>max_prepared_stmt_count</literal>
+ <literal role="sysvar">max_prepared_stmt_count</literal>
</para>
<para>
@@ -5528,7 +5528,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_max_relay_log_size">
+ <para id="sysvar_max_relay_log_size">
<indexterm>
<primary>max_relay_log_size system variable</primary>
</indexterm>
@@ -5538,7 +5538,7 @@
<secondary>max_relay_log_size</secondary>
</indexterm>
- <literal>max_relay_log_size</literal>
+ <literal role="sysvar">max_relay_log_size</literal>
</para>
<para>
@@ -5546,13 +5546,13 @@
the current log file size to exceed the value of this
variable, the slave rotates the relay logs (closes the
current file and opens the next one). If
- <literal>max_relay_log_size</literal> is 0, the server uses
+ <literal role="sysvar">max_relay_log_size</literal> is 0, the server uses
<literal role="sysvar">max_binlog_size</literal> for both
the binary log and the relay log. If
- <literal>max_relay_log_size</literal> is greater than 0, it
+ <literal role="sysvar">max_relay_log_size</literal> is greater than 0, it
constrains the size of the relay log, which enables you to
have different sizes for the two logs. You must set
- <literal>max_relay_log_size</literal> to between 4096 bytes
+ <literal role="sysvar">max_relay_log_size</literal> to between 4096 bytes
and 1GB (inclusive), or to <literal>0</literal>. The default
value is <literal>0</literal>. This variable was added in
MySQL 4.0.14. See
@@ -5561,7 +5561,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_max_seeks_for_key">
+ <para id="sysvar_max_seeks_for_key">
<indexterm>
<primary>max_seeks_for_key system variable</primary>
</indexterm>
@@ -5571,7 +5571,7 @@
<secondary>max_seeks_for_key</secondary>
</indexterm>
- <literal>max_seeks_for_key</literal>
+ <literal role="sysvar">max_seeks_for_key</literal>
</para>
<para>
@@ -5591,7 +5591,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_max_sort_length">
+ <para id="sysvar_max_sort_length">
<indexterm>
<primary>max_sort_length system variable</primary>
</indexterm>
@@ -5601,20 +5601,20 @@
<secondary>max_sort_length</secondary>
</indexterm>
- <literal>max_sort_length</literal>
+ <literal role="sysvar">max_sort_length</literal>
</para>
<para>
The number of bytes to use when sorting
<literal role="type">BLOB</literal> or
<literal role="type">TEXT</literal> values. Only the first
- <literal>max_sort_length</literal> bytes of each value are
+ <literal role="sysvar">max_sort_length</literal> bytes of each value are
used; the rest are ignored.
</para>
</listitem>
<listitem>
- <para id="option_mysqld_max_tmp_tables">
+ <para id="sysvar_max_tmp_tables">
<indexterm>
<primary>max_tmp_tables system variable</primary>
</indexterm>
@@ -5624,7 +5624,7 @@
<secondary>max_tmp_tables</secondary>
</indexterm>
- <literal>max_tmp_tables</literal>
+ <literal role="sysvar">max_tmp_tables</literal>
</para>
<para>
@@ -5635,7 +5635,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_max_user_connections">
+ <para id="sysvar_max_user_connections">
<indexterm>
<primary>max_user_connections system variable</primary>
</indexterm>
@@ -5645,7 +5645,7 @@
<secondary>max_user_connections</secondary>
</indexterm>
- <literal>max_user_connections</literal>
+ <literal role="sysvar">max_user_connections</literal>
</para>
<para>
@@ -5661,7 +5661,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_max_write_lock_count">
+ <para id="sysvar_max_write_lock_count">
<indexterm>
<primary>max_write_lock_count system variable</primary>
</indexterm>
@@ -5671,7 +5671,7 @@
<secondary>max_write_lock_count</secondary>
</indexterm>
- <literal>max_write_lock_count</literal>
+ <literal role="sysvar">max_write_lock_count</literal>
</para>
<para>
@@ -5682,7 +5682,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_myisam_block_size">
+ <para id="sysvar_myisam_block_size">
<indexterm>
<primary>myisam_block_size system variable</primary>
</indexterm>
@@ -5692,7 +5692,7 @@
<secondary>myisam_block_size</secondary>
</indexterm>
- <literal>myisam_block_size</literal>
+ <literal role="sysvar">myisam_block_size</literal>
</para>
<para condition="dynamic:optvar:item" role="4.1:mysqld:myisam_block_size"/>
@@ -5704,7 +5704,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_myisam_data_pointer_size">
+ <para id="sysvar_myisam_data_pointer_size">
<indexterm>
<primary>myisam_data_pointer_size system variable</primary>
</indexterm>
@@ -5714,7 +5714,7 @@
<secondary>myisam_data_pointer_size</secondary>
</indexterm>
- <literal>myisam_data_pointer_size</literal>
+ <literal role="sysvar">myisam_data_pointer_size</literal>
</para>
<para>
@@ -5761,7 +5761,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_myisam_max_sort_file_size">
+ <para id="sysvar_myisam_max_sort_file_size">
<indexterm>
<primary>myisam_max_sort_file_size system variable</primary>
</indexterm>
@@ -5771,7 +5771,7 @@
<secondary>myisam_max_sort_file_size</secondary>
</indexterm>
- <literal>myisam_max_sort_file_size</literal>
+ <literal role="sysvar">myisam_max_sort_file_size</literal>
</para>
<para>
@@ -5801,7 +5801,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_myisam_recover_options">
+ <para id="sysvar_myisam_recover_options">
<indexterm>
<primary>myisam_recover_options system variable</primary>
</indexterm>
@@ -5811,7 +5811,7 @@
<secondary>myisam_recover_options</secondary>
</indexterm>
- <literal>myisam_recover_options</literal>
+ <literal role="sysvar">myisam_recover_options</literal>
</para>
<para>
@@ -5822,7 +5822,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_myisam_repair_threads">
+ <para id="sysvar_myisam_repair_threads">
<indexterm>
<primary>myisam_repair_threads system variable</primary>
</indexterm>
@@ -5832,7 +5832,7 @@
<secondary>myisam_repair_threads</secondary>
</indexterm>
- <literal>myisam_repair_threads</literal>
+ <literal role="sysvar">myisam_repair_threads</literal>
</para>
<para>
@@ -5852,7 +5852,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_myisam_sort_buffer_size">
+ <para id="sysvar_myisam_sort_buffer_size">
<indexterm>
<primary>myisam_sort_buffer_size system variable</primary>
</indexterm>
@@ -5862,7 +5862,7 @@
<secondary>myisam_sort_buffer_size</secondary>
</indexterm>
- <literal>myisam_sort_buffer_size</literal>
+ <literal role="sysvar">myisam_sort_buffer_size</literal>
</para>
<para>
@@ -5876,7 +5876,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_myisam_stats_method">
+ <para id="sysvar_myisam_stats_method">
<indexterm>
<primary>myisam_stats_method system variable</primary>
</indexterm>
@@ -5886,7 +5886,7 @@
<secondary>myisam_stats_method</secondary>
</indexterm>
- <literal>myisam_stats_method</literal>
+ <literal role="sysvar">myisam_stats_method</literal>
</para>
<para>
@@ -6220,7 +6220,7 @@
<para>
The current number of prepared statements. (The maximum
number of statements is given by the
- <literal>max_prepared_stmt_count</literal> system variable.)
+ <literal role="sysvar">max_prepared_stmt_count</literal> system variable.)
This variable was added in MySQL 4.1.19. In MySQL 4.1.23, it
was converted to the global
<literal>Prepared_stmt_count</literal> status variable.
@@ -7972,14 +7972,14 @@
likely to take a very long time to execute (that is,
statements for which the optimizer estimates that the number
of examined rows exceeds the value of
- <literal>max_join_size</literal>). This is useful when an
+ <literal role="sysvar">max_join_size</literal>). This is useful when an
inadvisable <literal>WHERE</literal> statement has been
issued. The default value for a new connection is 1, which
allows all <literal role="stmt">SELECT</literal> statements.
</para>
<para>
- If you set the <literal>max_join_size</literal> system
+ If you set the <literal role="sysvar">max_join_size</literal> system
variable to a value other than <literal>DEFAULT</literal>,
<literal role="sysvar">sql_big_selects</literal> is set to
0.
@@ -8523,7 +8523,7 @@
value to the compiled-in MySQL default value, use the
<literal>DEFAULT</literal> keyword. For example, the following
two statements are identical in setting the session value of
- <literal>max_join_size</literal> to the global value:
+ <literal role="sysvar">max_join_size</literal> to the global value:
</para>
<programlisting>
@@ -9664,7 +9664,7 @@
<para>
The current number of prepared statements. (The maximum
number of statements is given by the
- <literal>max_prepared_stmt_count</literal> system variable.)
+ <literal role="sysvar">max_prepared_stmt_count</literal> system variable.)
This variable was added in MySQL 4.1.23.
</para>
</listitem>
@@ -13351,7 +13351,7 @@
<para>
If you want to restrict the number of connections allowed to
a single account, you can do so by setting the
- <literal>max_user_connections</literal> variable in
+ <literal role="sysvar">max_user_connections</literal> variable in
<command>mysqld</command>. The
<literal role="stmt">GRANT</literal> statement also supports
resource control options for limiting the extent of server
@@ -14259,7 +14259,7 @@
</row>
<row>
<entry/>
- <entry><literal>max_user_connections</literal></entry>
+ <entry><literal role="sysvar">max_user_connections</literal></entry>
<entry/>
</row>
</tbody>
@@ -18321,7 +18321,7 @@
<para>
Before MySQL 4.0.2, the only available method for limiting use
of MySQL server resources is to set the
- <literal>max_user_connections</literal> system variable to a
+ <literal role="sysvar">max_user_connections</literal> system variable to a
non-zero value. But that method is strictly global. It does not
allow for management of individual accounts. Also, it limits
only the number of simultaneous connections made using a single
@@ -18389,7 +18389,7 @@
limits are stored in the <literal>max_questions</literal>,
<literal>max_updates</literal>,
<literal role="sysvar">max_connections</literal>, and
- <literal>max_user_connections</literal> columns. If your
+ <literal role="sysvar">max_user_connections</literal> columns. If your
<literal>user</literal> table does not have these columns, it
must be upgraded; see
<xref linkend="mysql-fix-privilege-tables"/>.
Modified: trunk/refman-4.1/errors-problems.xml
===================================================================
--- trunk/refman-4.1/errors-problems.xml 2008-12-02 00:15:15 UTC (rev 12726)
+++ trunk/refman-4.1/errors-problems.xml 2008-12-02 02:57:31 UTC (rev 12727)
Changed blocks: 2, Lines Added: 4, Lines Deleted: 4; 1952 bytes
@@ -1921,12 +1921,12 @@
<para>
To change the default size limit for
<literal>MyISAM</literal> data and index table files, set
- the <literal>myisam_data_pointer_size</literal>, which
+ the <literal role="sysvar">myisam_data_pointer_size</literal>, which
sets the number of bytes used for internal row pointers.
The value is used to set the pointer size for new tables
if you do not specify the <literal>MAX_ROWS</literal>
option. The value of
- <literal>myisam_data_pointer_size</literal> can be from 2
+ <literal role="sysvar">myisam_data_pointer_size</literal> can be from 2
to 7. A value of 4 allows table files up to 4GB; a value
of 6 allows table files up to 256TB.
</para>
@@ -5839,10 +5839,10 @@
<quote>reliably</quote> be used in <literal>GROUP
BY</literal>, <literal>ORDER BY</literal> or
<literal>DISTINCT</literal>. Only the first
- <literal>max_sort_length</literal> bytes are used when
+ <literal role="sysvar">max_sort_length</literal> bytes are used when
comparing <literal role="type">BLOB</literal> values in
these cases. The default value of
- <literal>max_sort_length</literal> value is 1024 and can
+ <literal role="sysvar">max_sort_length</literal> value is 1024 and can
be changed at server startup time. As of MySQL 4.0.3, it
can be changed at runtime. For older versions, a
workaround is to use a substring. For example:
Modified: trunk/refman-4.1/installing.xml
===================================================================
--- trunk/refman-4.1/installing.xml 2008-12-02 00:15:15 UTC (rev 12726)
+++ trunk/refman-4.1/installing.xml 2008-12-02 02:57:31 UTC (rev 12727)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 652 bytes
@@ -13986,7 +13986,7 @@
</row>
<row>
<entry><literal>sql_max_join_size</literal></entry>
- <entry><literal>max_join_size</literal></entry>
+ <entry><literal role="sysvar">max_join_size</literal></entry>
</row>
<row>
<entry><literal>sql_query_cache_type</literal></entry>
Modified: trunk/refman-4.1/news-3.23.xml
===================================================================
--- trunk/refman-4.1/news-3.23.xml 2008-12-02 00:15:15 UTC (rev 12726)
+++ trunk/refman-4.1/news-3.23.xml 2008-12-02 02:57:31 UTC (rev 12727)
Changed blocks: 4, Lines Added: 4, Lines Deleted: 4; 1520 bytes
@@ -3237,7 +3237,7 @@
<listitem>
<para>
Added <command>mysqld</command> variables
- <literal>myisam_max_sort_file_size</literal> and
+ <literal role="sysvar">myisam_max_sort_file_size</literal> and
<literal>myisam_max_extra_sort_file_size</literal>.
</para>
</listitem>
@@ -3525,7 +3525,7 @@
<listitem>
<para>
- Added <literal>max_user_connections</literal> variable to
+ Added <literal role="sysvar">max_user_connections</literal> variable to
<command>mysqld</command>.
</para>
</listitem>
@@ -7192,7 +7192,7 @@
<listitem>
<para>
Added <literal>select_limit</literal> and
- <literal>max_join_size</literal> variables to
+ <literal role="sysvar">max_join_size</literal> variables to
<command>mysql</command>.
</para>
</listitem>
@@ -7594,7 +7594,7 @@
<listitem>
<para>
- Added <literal>max_write_lock_count</literal> variable to
+ Added <literal role="sysvar">max_write_lock_count</literal> variable to
<command>mysqld</command> to force a <literal>READ</literal>
lock after a certain number of <literal>WRITE</literal> locks.
</para>
Modified: trunk/refman-4.1/news-4.0.xml
===================================================================
--- trunk/refman-4.1/news-4.0.xml 2008-12-02 00:15:15 UTC (rev 12726)
+++ trunk/refman-4.1/news-4.0.xml 2008-12-02 02:57:31 UTC (rev 12727)
Changed blocks: 9, Lines Added: 11, Lines Deleted: 11; 3815 bytes
@@ -703,7 +703,7 @@
<para>
Attempting to repair a table having a fulltext index on a
column containing words whose length exceeded 21 characters
- and where <literal>myisam_repair_threads</literal> was greater
+ and where <literal role="sysvar">myisam_repair_threads</literal> was greater
than 1 would crash the server. (Bug #11684)
</para>
</listitem>
@@ -2409,7 +2409,7 @@
<listitem>
<para>
- Added <literal>max_insert_delayed_threads</literal> system
+ Added <literal role="sysvar">max_insert_delayed_threads</literal> system
variable as a synonym for
<literal role="sysvar">max_delayed_threads</literal>.
</para>
@@ -2622,7 +2622,7 @@
<para>
Fixed core dump crash in replication during relay-log switch
when the relay log went over
- <literal>max_relay_log_size</literal> and the slave thread did
+ <literal role="sysvar">max_relay_log_size</literal> and the slave thread did
a <literal>flush_io_cache()</literal> at the same time.
</para>
</listitem>
@@ -2684,7 +2684,7 @@
<listitem>
<para>
Fixed a bug in parallel repair (<command>myisamchk
- -p</command>, <literal>myisam_repair_threads</literal>) -
+ -p</command>, <literal role="sysvar">myisam_repair_threads</literal>) -
sometimes repair process failed to repair a table. (Bug #1334)
</para>
</listitem>
@@ -4945,7 +4945,7 @@
<listitem>
<para>
- Added thread-specific <literal>max_seeks_for_key</literal>
+ Added thread-specific <literal role="sysvar">max_seeks_for_key</literal>
variable that can be used to force the optimizer to use keys
instead of table scans even if the cardinality of the index is
low.
@@ -5035,10 +5035,10 @@
<listitem>
<para>
- Added <literal>max_relay_log_size</literal> variable; the
+ Added <literal role="sysvar">max_relay_log_size</literal> variable; the
relay log is rotated automatically when its size exceeds
- <literal>max_relay_log_size</literal>. But if
- <literal>max_relay_log_size</literal> is 0 (the default),
+ <literal role="sysvar">max_relay_log_size</literal>. But if
+ <literal role="sysvar">max_relay_log_size</literal> is 0 (the default),
<literal role="sysvar">max_binlog_size</literal> is used (as
in older versions).
<literal role="sysvar">max_binlog_size</literal> still applies
@@ -5186,7 +5186,7 @@
<listitem>
<para>
- Fixed a problem with <literal>max_user_connections</literal>.
+ Fixed a problem with <literal role="sysvar">max_user_connections</literal>.
</para>
</listitem>
@@ -5506,7 +5506,7 @@
<listitem>
<para>
Added multi-threaded <literal>MyISAM</literal> repair
- optimization and <literal>myisam_repair_threads</literal>
+ optimization and <literal role="sysvar">myisam_repair_threads</literal>
variable to enable it. See
<xref linkend="server-system-variables"/>.
</para>
@@ -8359,7 +8359,7 @@
<listitem>
<para>
The startup parameters
- <literal>myisam_max_sort_file_size</literal> and
+ <literal role="sysvar">myisam_max_sort_file_size</literal> and
<literal>myisam_max_extra_sort_file_size</literal> are now
given in bytes, not megabytes.
</para>
Modified: trunk/refman-4.1/optimization.xml
===================================================================
--- trunk/refman-4.1/optimization.xml 2008-12-02 00:15:15 UTC (rev 12726)
+++ trunk/refman-4.1/optimization.xml 2008-12-02 02:57:31 UTC (rev 12727)
Changed blocks: 15, Lines Added: 16, Lines Deleted: 16; 6793 bytes
@@ -1594,7 +1594,7 @@
of the <literal role="stmt">EXPLAIN</literal> output. This
should tell you roughly how many rows MySQL must examine to
execute the query. If you restrict queries with the
- <literal>max_join_size</literal> system variable, this row
+ <literal role="sysvar">max_join_size</literal> system variable, this row
product also is used to determine which multiple-table
<literal role="stmt">SELECT</literal> statements to execute and
which to abort. See <xref linkend="server-parameters"/>.
@@ -3461,7 +3461,7 @@
slower, not faster. To avoid a slowdown, the optimization is
used only if the total size of the extra columns in the sort
tuple does not exceed the value of the
- <literal>max_length_for_sort_data</literal> system variable. (A
+ <literal role="sysvar">max_length_for_sort_data</literal> system variable. (A
symptom of setting the value of this variable too high is that
you should see high disk activity and low CPU activity.)
</para>
@@ -3469,7 +3469,7 @@
<para>
For slow queries for which <literal>filesort</literal> is not
used, you might try lowering
- <literal>max_length_for_sort_data</literal> to a value that is
+ <literal role="sysvar">max_length_for_sort_data</literal> to a value that is
appropriate to trigger a <literal>filesort</literal>.
</para>
@@ -5359,7 +5359,7 @@
<para>
Starting from MySQL 3.23.7, you can start
<command>mysqld</command> with a low value for the
- <literal>max_write_lock_count</literal> system variable to
+ <literal role="sysvar">max_write_lock_count</literal> system variable to
force MySQL to temporarily elevate the priority of all
<literal role="stmt">SELECT</literal> statements that are
waiting for a table after a specific number of inserts to
@@ -7284,7 +7284,7 @@
<para>
For <literal>MyISAM</literal> tables, you have some control over
collection of table statistics by means of the
- <literal>myisam_stats_method</literal> system variable. This
+ <literal role="sysvar">myisam_stats_method</literal> system variable. This
variable has two possible values, which differ as follows:
</para>
@@ -7292,7 +7292,7 @@
<listitem>
<para>
- When <literal>myisam_stats_method</literal> is
+ When <literal role="sysvar">myisam_stats_method</literal> is
<literal>nulls_equal</literal>, all <literal>NULL</literal>
values are treated as identical (that is, they all form a
single value group).
@@ -7313,7 +7313,7 @@
<listitem>
<para>
- When <literal>myisam_stats_method</literal> is
+ When <literal role="sysvar">myisam_stats_method</literal> is
<literal>nulls_unequal</literal>, <literal>NULL</literal>
values are not considered the same. Instead, each
<literal>NULL</literal> value forms a separate value group
@@ -7346,7 +7346,7 @@
</para>
<para>
- The <literal>myisam_stats_method</literal> system variable has
+ The <literal role="sysvar">myisam_stats_method</literal> system variable has
global and session values. Setting the global value affects
<literal>MyISAM</literal> statistics collection for all
<literal>MyISAM</literal> tables. Setting the session value
@@ -7354,7 +7354,7 @@
connection. This means that you can force a table's statistics
to be regenerated with a given method without affecting other
clients by setting the session value of
- <literal>myisam_stats_method</literal>.
+ <literal role="sysvar">myisam_stats_method</literal>.
</para>
<para>
@@ -7366,7 +7366,7 @@
<listitem>
<para>
- Set <literal>myisam_stats_method</literal>, and then issue a
+ Set <literal role="sysvar">myisam_stats_method</literal>, and then issue a
<literal role="stmt">CHECK TABLE</literal> statement
</para>
</listitem>
@@ -7383,7 +7383,7 @@
<para>
Change the table to cause its statistics to go out of date
(for example, insert a row and then delete it), and then set
- <literal>myisam_stats_method</literal> and issue an
+ <literal role="sysvar">myisam_stats_method</literal> and issue an
<literal role="stmt">ANALYZE TABLE</literal> statement
</para>
</listitem>
@@ -7392,7 +7392,7 @@
<para>
Some caveats regarding the use of
- <literal>myisam_stats_method</literal>:
+ <literal role="sysvar">myisam_stats_method</literal>:
</para>
<itemizedlist>
@@ -7407,9 +7407,9 @@
(This may occur for bulk inserts or deletes, or some
<literal role="stmt">ALTER TABLE</literal> statements, for
example.) If this happens, the statistics are collected
- using whatever value <literal>myisam_stats_method</literal>
+ using whatever value <literal role="sysvar">myisam_stats_method</literal>
has at the time. Thus, if you collect statistics using one
- method, but <literal>myisam_stats_method</literal> is set to
+ method, but <literal role="sysvar">myisam_stats_method</literal> is set to
the other method when a table's statistics are collected
automatically later, the other method will be used.
</para>
@@ -7424,7 +7424,7 @@
<listitem>
<para>
- <literal>myisam_stats_method</literal> applies only to
+ <literal role="sysvar">myisam_stats_method</literal> applies only to
<literal>MyISAM</literal> tables. Other storage engines have
only one method for collecting table statistics. Usually it
is closer to the <literal>nulls_equal</literal> method.
@@ -7506,7 +7506,7 @@
<para>
The <literal>table_cache</literal>,
<literal role="sysvar">max_connections</literal>, and
- <literal>max_tmp_tables</literal> system variables affect the
+ <literal role="sysvar">max_tmp_tables</literal> system variables affect the
maximum number of files the server keeps open. If you increase
one or more of these values, you may run up against a limit
imposed by your operating system on the per-process number of
Modified: trunk/refman-4.1/programs-admin-util.xml
===================================================================
--- trunk/refman-4.1/programs-admin-util.xml 2008-12-02 00:15:15 UTC (rev 12726)
+++ trunk/refman-4.1/programs-admin-util.xml 2008-12-02 02:57:31 UTC (rev 12727)
Changed blocks: 3, Lines Added: 4, Lines Deleted: 4; 1573 bytes
@@ -705,7 +705,7 @@
<entry>523264</entry>
</row>
<row>
- <entry><literal>myisam_block_size</literal></entry>
+ <entry><literal role="sysvar">myisam_block_size</literal></entry>
<entry>1024</entry>
</row>
<row>
@@ -799,7 +799,7 @@
</para>
<para>
- <literal>myisam_block_size</literal> is the size used for index
+ <literal role="sysvar">myisam_block_size</literal> is the size used for index
blocks. It is available as of MySQL 4.0.0.
</para>
@@ -807,9 +807,9 @@
<literal>stats_method</literal> influences how
<literal>NULL</literal> values are treated for index statistics
collection when the <option>--analyze</option> option is given.
- It acts like the <literal>myisam_stats_method</literal> system
+ It acts like the <literal role="sysvar">myisam_stats_method</literal> system
variable. For more information, see the description of
- <literal>myisam_stats_method</literal> in
+ <literal role="sysvar">myisam_stats_method</literal> in
<xref linkend="server-system-variables"/>, and
<xref linkend="myisam-index-statistics"/>.
<literal>stats_method</literal> was added in MySQL
Modified: trunk/refman-4.1/programs-client.xml
===================================================================
--- trunk/refman-4.1/programs-client.xml 2008-12-02 00:15:15 UTC (rev 12726)
+++ trunk/refman-4.1/programs-client.xml 2008-12-02 02:57:31 UTC (rev 12727)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 508 bytes
@@ -1438,7 +1438,7 @@
<primary>max_join_size variable</primary>
</indexterm>
- <literal>max_join_size</literal>
+ <literal role="sysvar">max_join_size</literal>
</para>
<para>
Modified: trunk/refman-4.1/replication-options-core.xml
===================================================================
--- trunk/refman-4.1/replication-options-core.xml 2008-12-02 00:15:15 UTC (rev 12726)
+++ trunk/refman-4.1/replication-options-core.xml 2008-12-02 02:57:31 UTC (rev 12727)
Changed blocks: 2, Lines Added: 3, Lines Deleted: 3; 1326 bytes
@@ -988,7 +988,7 @@
numeric suffix to the basename. You can specify the option to
create hostname-independent relay log names, or if your relay
logs tend to be big (and you don't want to decrease
- <literal>max_relay_log_size</literal>) and you need to put
+ <literal role="sysvar">max_relay_log_size</literal>) and you need to put
them in some area different from the data directory, or if you
want to increase speed by balancing load between disks.
</para>
@@ -1929,9 +1929,9 @@
</para>
<para>
- If <literal>max_relay_log_size</literal> is 0, the value of
+ If <literal role="sysvar">max_relay_log_size</literal> is 0, the value of
<literal role="sysvar">max_binlog_size</literal> applies to
- relay logs as well. <literal>max_relay_log_size</literal> was
+ relay logs as well. <literal role="sysvar">max_relay_log_size</literal> was
added in MySQL 4.0.14.
</para>
</listitem>
Modified: trunk/refman-4.1/replication.xml
===================================================================
--- trunk/refman-4.1/replication.xml 2008-12-02 00:15:15 UTC (rev 12726)
+++ trunk/refman-4.1/replication.xml 2008-12-02 02:57:31 UTC (rev 12727)
Changed blocks: 1, Lines Added: 3, Lines Deleted: 3; 1300 bytes
@@ -493,20 +493,20 @@
<listitem>
<para>
- If the value of <literal>max_relay_log_size</literal> is
+ If the value of <literal role="sysvar">max_relay_log_size</literal> is
greater than 0, that is the maximum relay log file size.
</para>
</listitem>
<listitem>
<para>
- If the value of <literal>max_relay_log_size</literal> is
+ If the value of <literal role="sysvar">max_relay_log_size</literal> is
0, <literal role="sysvar">max_binlog_size</literal>
determines the maximum relay log file size.
<literal role="sysvar">max_binlog_size</literal> always
determines the relay log size before MySQL 4.0.14, the
first version in which
- <literal>max_relay_log_size</literal> appears.
+ <literal role="sysvar">max_relay_log_size</literal> appears.
</para>
</listitem>
Modified: trunk/refman-4.1/se-innodb-core.xml
===================================================================
--- trunk/refman-4.1/se-innodb-core.xml 2008-12-02 00:15:15 UTC (rev 12726)
+++ trunk/refman-4.1/se-innodb-core.xml 2008-12-02 02:57:31 UTC (rev 12727)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 800 bytes
@@ -7733,7 +7733,7 @@
values good enough for your particular tables, you can use
<literal>FORCE INDEX</literal> with your queries to force the
use of a particular index, or set the
- <literal>max_seeks_for_key</literal> system variable to ensure
+ <literal role="sysvar">max_seeks_for_key</literal> system variable to ensure
that MySQL prefers index lookups over table scans. See
<xref linkend="server-system-variables"/>, and
<xref linkend="optimizer-issues"/>.
Modified: trunk/refman-4.1/sql-syntax-data-definition.xml
===================================================================
--- trunk/refman-4.1/sql-syntax-data-definition.xml 2008-12-02 00:15:15 UTC (rev 12726)
+++ trunk/refman-4.1/sql-syntax-data-definition.xml 2008-12-02 02:57:31 UTC (rev 12727)
Changed blocks: 3, Lines Added: 3, Lines Deleted: 3; 1761 bytes
@@ -250,7 +250,7 @@
to be copied (such as when you change the name of a column). For
<literal>MyISAM</literal> tables, you can speed up the index
re-creation operation (which is the slowest part of the alteration
- process) by setting the <literal>myisam_sort_buffer_size</literal>
+ process) by setting the <literal role="sysvar">myisam_sort_buffer_size</literal>
system variable to a high value.
</para>
@@ -2268,7 +2268,7 @@
<literal role="type">BLOB</literal> column in a
<literal role="stmt">SELECT</literal>, the server sorts values
using only the initial number of bytes indicated by the
- <literal>max_sort_length</literal> system variable. See
+ <literal role="sysvar">max_sort_length</literal> system variable. See
<xref linkend="blob"/>.
</para>
</listitem>
@@ -2561,7 +2561,7 @@
system limit.) If you want to keep down the pointer sizes to
make the index smaller and faster and you do not really need
big files, you can decrease the default pointer size by
- setting the <literal>myisam_data_pointer_size</literal> system
+ setting the <literal role="sysvar">myisam_data_pointer_size</literal> system
variable, which was added in MySQL 4.1.2. (See
<xref linkend="server-system-variables"/>.) If you want all
your tables to be able to grow above the default limit and are
Modified: trunk/refman-4.1/sql-syntax-prepared-statements.xml
===================================================================
--- trunk/refman-4.1/sql-syntax-prepared-statements.xml 2008-12-02 00:15:15 UTC (rev 12726)
+++ trunk/refman-4.1/sql-syntax-prepared-statements.xml 2008-12-02 02:57:31 UTC (rev 12727)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 594 bytes
@@ -270,7 +270,7 @@
<para>
To guard against too many prepared statements being created
- simultaneously, the <literal>max_prepared_stmt_count</literal>
+ simultaneously, the <literal role="sysvar">max_prepared_stmt_count</literal>
system variable can be set.
</para>
Modified: trunk/refman-4.1/sql-syntax-server-administration.xml
===================================================================
--- trunk/refman-4.1/sql-syntax-server-administration.xml 2008-12-02 00:15:15 UTC (rev 12726)
+++ trunk/refman-4.1/sql-syntax-server-administration.xml 2008-12-02 02:57:31 UTC (rev 12727)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 697 bytes
@@ -3018,7 +3018,7 @@
value to the compiled-in MySQL default value, use the
<literal>DEFAULT</literal> keyword. For example, the following two
statements are identical in setting the session value of
- <literal>max_join_size</literal> to the global value:
+ <literal role="sysvar">max_join_size</literal> to the global value:
</para>
<programlisting>
Modified: trunk/refman-4.1/storage-engines.xml
===================================================================
--- trunk/refman-4.1/storage-engines.xml 2008-12-02 00:15:15 UTC (rev 12726)
+++ trunk/refman-4.1/storage-engines.xml 2008-12-02 02:57:31 UTC (rev 12727)
Changed blocks: 2, Lines Added: 2, Lines Deleted: 2; 701 bytes
@@ -815,7 +815,7 @@
<listitem>
<para>
- <literal>myisam_max_sort_file_size</literal>
+ <literal role="sysvar">myisam_max_sort_file_size</literal>
</para>
<para>
@@ -840,7 +840,7 @@
<listitem>
<para>
- <literal>myisam_sort_buffer_size</literal>
+ <literal role="sysvar">myisam_sort_buffer_size</literal>
</para>
<para>
Modified: trunk/refman-5.0/data-types.xml
===================================================================
--- trunk/refman-5.0/data-types.xml 2008-12-02 00:15:15 UTC (rev 12726)
+++ trunk/refman-5.0/data-types.xml 2008-12-02 02:57:31 UTC (rev 12727)
Changed blocks: 3, Lines Added: 5, Lines Deleted: 5; 1915 bytes
@@ -4930,9 +4930,9 @@
<listitem>
<para>
- Only the first <literal>max_sort_length</literal> bytes of
+ Only the first <literal role="sysvar">max_sort_length</literal> bytes of
the column are used when sorting. The default value of
- <literal>max_sort_length</literal> is 1024. This value can
+ <literal role="sysvar">max_sort_length</literal> is 1024. This value can
be changed using the
<option>--max_sort_length=<replaceable>N</replaceable></option>
option when starting the <command>mysqld</command> server.
@@ -4942,9 +4942,9 @@
<para>
You can make more bytes significant in sorting or grouping
by increasing the value of
- <literal>max_sort_length</literal> at runtime. Any client
+ <literal role="sysvar">max_sort_length</literal> at runtime. Any client
can change the value of its session
- <literal>max_sort_length</literal> variable:
+ <literal role="sysvar">max_sort_length</literal> variable:
</para>
<programlisting>
@@ -4959,7 +4959,7 @@
<literal role="type">BLOB</literal> or
<literal role="type">TEXT</literal> column containing long
values when you want more than
- <literal>max_sort_length</literal> bytes to be significant
+ <literal role="sysvar">max_sort_length</literal> bytes to be significant
is to convert the column value into a fixed-length object.
The standard way to do this is with the
<literal role="func">SUBSTRING()</literal> function. For
Modified: trunk/refman-5.0/dba-core.xml
===================================================================
--- trunk/refman-5.0/dba-core.xml 2008-12-02 00:15:15 UTC (rev 12726)
+++ trunk/refman-5.0/dba-core.xml 2008-12-02 02:57:31 UTC (rev 12727)
Changed blocks: 49, Lines Added: 56, Lines Deleted: 56; 19471 bytes
@@ -6113,7 +6113,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_max_insert_delayed_threads">
+ <para id="sysvar_max_insert_delayed_threads">
<indexterm>
<primary>max_insert_delayed_threads system variable</primary>
</indexterm>
@@ -6123,7 +6123,7 @@
<secondary>max_insert_delayed_threads</secondary>
</indexterm>
- <literal>max_insert_delayed_threads</literal>
+ <literal role="sysvar">max_insert_delayed_threads</literal>
</para>
<para condition="dynamic:optvar:item" role="5.0:mysqld:max_insert_delayed_threads"/>
@@ -6135,7 +6135,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_max_join_size">
+ <para id="sysvar_max_join_size">
<indexterm>
<primary>max_join_size system variable</primary>
</indexterm>
@@ -6145,7 +6145,7 @@
<secondary>max_join_size</secondary>
</indexterm>
- <literal>max_join_size</literal>
+ <literal role="sysvar">max_join_size</literal>
</para>
<para condition="dynamic:optvar:item" role="5.0:mysqld:max_join_size"/>
@@ -6153,10 +6153,10 @@
<para>
Do not allow <literal role="stmt">SELECT</literal>
statements that probably need to examine more than
- <literal>max_join_size</literal> rows (for single-table
+ <literal role="sysvar">max_join_size</literal> rows (for single-table
statements) or row combinations (for multiple-table
statements) or that are likely to do more than
- <literal>max_join_size</literal> disk seeks. By setting this
+ <literal role="sysvar">max_join_size</literal> disk seeks. By setting this
value, you can catch <literal role="stmt">SELECT</literal>
statements where keys are not used properly and that would
probably take a long time. Set it if your users tend to
@@ -6170,7 +6170,7 @@
<literal role="sysvar">sql_big_selects</literal> to
<literal>0</literal>. If you set the
<literal role="sysvar">sql_big_selects</literal> value
- again, the <literal>max_join_size</literal> variable is
+ again, the <literal role="sysvar">max_join_size</literal> variable is
ignored.
</para>
@@ -6188,7 +6188,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_max_length_for_sort_data">
+ <para id="sysvar_max_length_for_sort_data">
<indexterm>
<primary>max_length_for_sort_data system variable</primary>
</indexterm>
@@ -6198,7 +6198,7 @@
<secondary>max_length_for_sort_data</secondary>
</indexterm>
- <literal>max_length_for_sort_data</literal>
+ <literal role="sysvar">max_length_for_sort_data</literal>
</para>
<para condition="dynamic:optvar:item" role="5.0:mysqld:max_length_for_sort_data"/>
@@ -6211,7 +6211,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_max_prepared_stmt_count">
+ <para id="sysvar_max_prepared_stmt_count">
<indexterm>
<primary>max_prepared_stmt_count system variable</primary>
</indexterm>
@@ -6221,7 +6221,7 @@
<secondary>max_prepared_stmt_count</secondary>
</indexterm>
- <literal>max_prepared_stmt_count</literal>
+ <literal role="sysvar">max_prepared_stmt_count</literal>
</para>
<para condition="dynamic:optvar:item" role="5.0:mysqld:max_prepared_stmt_count"/>
@@ -6241,7 +6241,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_max_relay_log_size">
+ <para id="sysvar_max_relay_log_size">
<indexterm>
<primary>max_relay_log_size system variable</primary>
</indexterm>
@@ -6251,7 +6251,7 @@
<secondary>max_relay_log_size</secondary>
</indexterm>
- <literal>max_relay_log_size</literal>
+ <literal role="sysvar">max_relay_log_size</literal>
</para>
<para condition="dynamic:optvar:item" role="5.0:mysqld:max_relay_log_size"/>
@@ -6261,20 +6261,20 @@
the current log file size to exceed the value of this
variable, the slave rotates the relay logs (closes the
current file and opens the next one). If
- <literal>max_relay_log_size</literal> is 0, the server uses
+ <literal role="sysvar">max_relay_log_size</literal> is 0, the server uses
<literal role="sysvar">max_binlog_size</literal> for both
the binary log and the relay log. If
- <literal>max_relay_log_size</literal> is greater than 0, it
+ <literal role="sysvar">max_relay_log_size</literal> is greater than 0, it
constrains the size of the relay log, which enables you to
have different sizes for the two logs. You must set
- <literal>max_relay_log_size</literal> to between 4096 bytes
+ <literal role="sysvar">max_relay_log_size</literal> to between 4096 bytes
and 1GB (inclusive), or to 0. The default value is 0. See
<xref linkend="replication-implementation-details"/>.
</para>
</listitem>
<listitem>
- <para id="option_mysqld_max_seeks_for_key">
+ <para id="sysvar_max_seeks_for_key">
<indexterm>
<primary>max_seeks_for_key system variable</primary>
</indexterm>
@@ -6284,7 +6284,7 @@
<secondary>max_seeks_for_key</secondary>
</indexterm>
- <literal>max_seeks_for_key</literal>
+ <literal role="sysvar">max_seeks_for_key</literal>
</para>
<para condition="dynamic:optvar:item" role="5.0:mysqld:max_seeks_for_key"/>
@@ -6302,7 +6302,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_max_sort_length">
+ <para id="sysvar_max_sort_length">
<indexterm>
<primary>max_sort_length system variable</primary>
</indexterm>
@@ -6312,7 +6312,7 @@
<secondary>max_sort_length</secondary>
</indexterm>
- <literal>max_sort_length</literal>
+ <literal role="sysvar">max_sort_length</literal>
</para>
<para condition="dynamic:optvar:item" role="5.0:mysqld:max_sort_length"/>
@@ -6321,13 +6321,13 @@
The number of bytes to use when sorting
<literal role="type">BLOB</literal> or
<literal role="type">TEXT</literal> values. Only the first
- <literal>max_sort_length</literal> bytes of each value are
+ <literal role="sysvar">max_sort_length</literal> bytes of each value are
used; the rest are ignored.
</para>
</listitem>
<listitem>
- <para id="option_mysqld_max_sp_recursion_depth">
+ <para id="sysvar_max_sp_recursion_depth">
<indexterm>
<primary>max_sp_recursion_depth system variable</primary>
</indexterm>
@@ -6337,7 +6337,7 @@
<secondary>max_sp_recursion_depth</secondary>
</indexterm>
- <literal>max_sp_recursion_depth</literal>
+ <literal role="sysvar">max_sp_recursion_depth</literal>
</para>
<para condition="dynamic:optvar:item" role="5.0:mysqld:max_sp_recursion_depth"/>
@@ -6352,7 +6352,7 @@
<para>
Stored procedure recursion increases the demand on thread
stack space. If you increase the value of
- <literal>max_sp_recursion_depth</literal>, it may be
+ <literal role="sysvar">max_sp_recursion_depth</literal>, it may be
necessary to increase thread stack size by increasing the
value of <literal>thread_stack</literal> at server startup.
</para>
@@ -6363,7 +6363,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_max_tmp_tables">
+ <para id="sysvar_max_tmp_tables">
<indexterm>
<primary>max_tmp_tables system variable</primary>
</indexterm>
@@ -6373,7 +6373,7 @@
<secondary>max_tmp_tables</secondary>
</indexterm>
- <literal>max_tmp_tables</literal>
+ <literal role="sysvar">max_tmp_tables</literal>
</para>
<para condition="dynamic:optvar:item" role="5.0:mysqld:max_tmp_tables"/>
@@ -6386,7 +6386,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_max_user_connections">
+ <para id="sysvar_max_user_connections">
<indexterm>
<primary>max_user_connections system variable</primary>
</indexterm>
@@ -6396,7 +6396,7 @@
<secondary>max_user_connections</secondary>
</indexterm>
- <literal>max_user_connections</literal>
+ <literal role="sysvar">max_user_connections</literal>
</para>
<para condition="dynamic:optvar:item" role="5.0:mysqld:max_user_connections"/>
@@ -6418,7 +6418,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_max_write_lock_count">
+ <para id="sysvar_max_write_lock_count">
<indexterm>
<primary>max_write_lock_count system variable</primary>
</indexterm>
@@ -6428,7 +6428,7 @@
<secondary>max_write_lock_count</secondary>
</indexterm>
- <literal>max_write_lock_count</literal>
+ <literal role="sysvar">max_write_lock_count</literal>
</para>
<para condition="dynamic:optvar:item" role="5.0:mysqld:max_write_lock_count"/>
@@ -6440,7 +6440,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_myisam_block_size">
+ <para id="sysvar_myisam_block_size">
<indexterm>
<primary>myisam_block_size system variable</primary>
</indexterm>
@@ -6450,7 +6450,7 @@
<secondary>myisam_block_size</secondary>
</indexterm>
- <literal>myisam_block_size</literal>
+ <literal role="sysvar">myisam_block_size</literal>
</para>
<para condition="dynamic:optvar:item" role="5.0:mysqld:myisam_block_size"/>
@@ -6462,7 +6462,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_myisam_data_pointer_size">
+ <para id="sysvar_myisam_data_pointer_size">
<indexterm>
<primary>myisam_data_pointer_size system variable</primary>
</indexterm>
@@ -6472,7 +6472,7 @@
<secondary>myisam_data_pointer_size</secondary>
</indexterm>
- <literal>myisam_data_pointer_size</literal>
+ <literal role="sysvar">myisam_data_pointer_size</literal>
</para>
<para condition="dynamic:optvar:item" role="5.0:mysqld:myisam_data_pointer_size"/>
@@ -6509,7 +6509,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_myisam_max_sort_file_size">
+ <para id="sysvar_myisam_max_sort_file_size">
<indexterm>
<primary>myisam_max_sort_file_size system variable</primary>
</indexterm>
@@ -6519,7 +6519,7 @@
<secondary>myisam_max_sort_file_size</secondary>
</indexterm>
- <literal>myisam_max_sort_file_size</literal>
+ <literal role="sysvar">myisam_max_sort_file_size</literal>
</para>
<para condition="dynamic:optvar:item" role="5.0:mysqld:myisam_max_sort_file_size"/>
@@ -6543,7 +6543,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_myisam_recover_options">
+ <para id="sysvar_myisam_recover_options">
<indexterm>
<primary>myisam_recover_options system variable</primary>
</indexterm>
@@ -6553,7 +6553,7 @@
<secondary>myisam_recover_options</secondary>
</indexterm>
- <literal>myisam_recover_options</literal>
+ <literal role="sysvar">myisam_recover_options</literal>
</para>
<para condition="dynamic:optvar:item" role="5.0:mysqld:myisam_recover_options"/>
@@ -6565,7 +6565,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_myisam_repair_threads">
+ <para id="sysvar_myisam_repair_threads">
<indexterm>
<primary>myisam_repair_threads system variable</primary>
</indexterm>
@@ -6575,7 +6575,7 @@
<secondary>myisam_repair_threads</secondary>
</indexterm>
- <literal>myisam_repair_threads</literal>
+ <literal role="sysvar">myisam_repair_threads</literal>
</para>
<para condition="dynamic:optvar:item" role="5.0:mysqld:myisam_repair_threads"/>
@@ -6596,7 +6596,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_myisam_sort_buffer_size">
+ <para id="sysvar_myisam_sort_buffer_size">
<indexterm>
<primary>myisam_sort_buffer_size system variable</primary>
</indexterm>
@@ -6606,7 +6606,7 @@
<secondary>myisam_sort_buffer_size</secondary>
</indexterm>
- <literal>myisam_sort_buffer_size</literal>
+ <literal role="sysvar">myisam_sort_buffer_size</literal>
</para>
<para condition="dynamic:optvar:item" role="5.0:mysqld:myisam_sort_buffer_size"/>
@@ -6621,12 +6621,12 @@
<para>
The maximum allowable setting for
- <literal>myisam_sort_buffer_size</literal> is 4GB.
+ <literal role="sysvar">myisam_sort_buffer_size</literal> is 4GB.
</para>
</listitem>
<listitem>
- <para id="option_mysqld_myisam_stats_method">
+ <para id="sysvar_myisam_stats_method">
<indexterm>
<primary>myisam_stats_method system variable</primary>
</indexterm>
@@ -6636,7 +6636,7 @@
<secondary>myisam_stats_method</secondary>
</indexterm>
- <literal>myisam_stats_method</literal>
+ <literal role="sysvar">myisam_stats_method</literal>
</para>
<para condition="dynamic:optvar:item" role="5.0:mysqld:myisam_stats_method"/>
@@ -7078,7 +7078,7 @@
<para>
The current number of prepared statements. (The maximum
number of statements is given by the
- <literal>max_prepared_stmt_count</literal> system variable.)
+ <literal role="sysvar">max_prepared_stmt_count</literal> system variable.)
This variable was added in MySQL 5.0.21. In MySQL 5.0.32, it
was converted to the global
<literal>Prepared_stmt_count</literal> status variable.
@@ -9135,14 +9135,14 @@
likely to take a very long time to execute (that is,
statements for which the optimizer estimates that the number
of examined rows exceeds the value of
- <literal>max_join_size</literal>). This is useful when an
+ <literal role="sysvar">max_join_size</literal>). This is useful when an
inadvisable <literal>WHERE</literal> statement has been
issued. The default value for a new connection is 1, which
allows all <literal role="stmt">SELECT</literal> statements.
</para>
<para>
- If you set the <literal>max_join_size</literal> system
+ If you set the <literal role="sysvar">max_join_size</literal> system
variable to a value other than <literal>DEFAULT</literal>,
<literal role="sysvar">sql_big_selects</literal> is set to
0.
@@ -9666,7 +9666,7 @@
value to the compiled-in MySQL default value, use the
<literal>DEFAULT</literal> keyword. For example, the following
two statements are identical in setting the session value of
- <literal>max_join_size</literal> to the global value:
+ <literal role="sysvar">max_join_size</literal> to the global value:
</para>
<programlisting>
@@ -11396,7 +11396,7 @@
<para>
The current number of prepared statements. (The maximum
number of statements is given by the
- <literal>max_prepared_stmt_count</literal> system variable.)
+ <literal role="sysvar">max_prepared_stmt_count</literal> system variable.)
This variable was added in MySQL 5.0.32.
</para>
</listitem>
@@ -15201,7 +15201,7 @@
<para>
If you want to restrict the number of connections allowed to
a single account, you can do so by setting the
- <literal>max_user_connections</literal> variable in
+ <literal role="sysvar">max_user_connections</literal> variable in
<command>mysqld</command>. The
<literal role="stmt">GRANT</literal> statement also supports
resource control options for limiting the extent of server
@@ -16190,7 +16190,7 @@
</row>
<row>
<entry/>
- <entry><literal>max_user_connections</literal></entry>
+ <entry><literal role="sysvar">max_user_connections</literal></entry>
<entry/>
</row>
</tbody>
@@ -16211,7 +16211,7 @@
<para>
The <literal>Create_routine_priv</literal>,
<literal>Alter_routine_priv</literal>, and
- <literal>max_user_connections</literal> columns were added in
+ <literal role="sysvar">max_user_connections</literal> columns were added in
MySQL 5.0.3.
</para>
@@ -20390,7 +20390,7 @@
<para>
One means of limiting use of MySQL server resources is to set
- the <literal>max_user_connections</literal> system variable to a
+ the <literal role="sysvar">max_user_connections</literal> system variable to a
non-zero value. However, this method is strictly global, and
does not allow for management of individual accounts. In
addition, it limits only the number of simultaneous connections
@@ -20479,7 +20479,7 @@
limits are stored in the <literal>max_questions</literal>,
<literal>max_updates</literal>,
<literal role="sysvar">max_connections</literal>, and
- <literal>max_user_connections</literal> columns. If your
+ <literal role="sysvar">max_user_connections</literal> columns. If your
<literal>user</literal> table doesn't have these columns, it
must be upgraded; see <xref linkend="mysql-upgrade"/>.
</para>
@@ -20515,7 +20515,7 @@
indicating the maximum number of simultaneous connections the
account can make at any one time. If the limit is set to the
default value of zero, the
- <literal>max_user_connections</literal> system variable
+ <literal role="sysvar">max_user_connections</literal> system variable
determines the number of simultaneous connections for the
account.
</para>
Modified: trunk/refman-5.0/errors-problems.xml
===================================================================
--- trunk/refman-5.0/errors-problems.xml 2008-12-02 00:15:15 UTC (rev 12726)
+++ trunk/refman-5.0/errors-problems.xml 2008-12-02 02:57:31 UTC (rev 12727)
Changed blocks: 2, Lines Added: 4, Lines Deleted: 4; 1844 bytes
@@ -1849,11 +1849,11 @@
<para>
To change the default size limit for
<literal>MyISAM</literal> tables, set the
- <literal>myisam_data_pointer_size</literal>, which sets
+ <literal role="sysvar">myisam_data_pointer_size</literal>, which sets
the number of bytes used for internal row pointers. The
value is used to set the pointer size for new tables if
you do not specify the <literal>MAX_ROWS</literal> option.
- The value of <literal>myisam_data_pointer_size</literal>
+ The value of <literal role="sysvar">myisam_data_pointer_size</literal>
can be from 2 to 7. A value of 4 allows tables up to 4GB;
a value of 6 allows tables up to 256TB.
</para>
@@ -5564,10 +5564,10 @@
<literal role="type">TEXT</literal> values can't reliably
be used in <literal>GROUP BY</literal>, <literal>ORDER
BY</literal> or <literal>DISTINCT</literal>. Only the
- first <literal>max_sort_length</literal> bytes are used
+ first <literal role="sysvar">max_sort_length</literal> bytes are used
when comparing <literal role="type">BLOB</literal> values
in these cases. The default value of
- <literal>max_sort_length</literal> is 1024 and can be
+ <literal role="sysvar">max_sort_length</literal> is 1024 and can be
changed at server startup time or at runtime.
</para>
</listitem>
Modified: trunk/refman-5.0/optimization.xml
===================================================================
--- trunk/refman-5.0/optimization.xml 2008-12-02 00:15:15 UTC (rev 12726)
+++ trunk/refman-5.0/optimization.xml 2008-12-02 02:57:31 UTC (rev 12727)
Changed blocks: 14, Lines Added: 15, Lines Deleted: 15; 6452 bytes
@@ -1655,7 +1655,7 @@
of the <literal role="stmt">EXPLAIN</literal> output. This
should tell you roughly how many rows MySQL must examine to
execute the query. If you restrict queries with the
- <literal>max_join_size</literal> system variable, this row
+ <literal role="sysvar">max_join_size</literal> system variable, this row
product also is used to determine which multiple-table
<literal role="stmt">SELECT</literal> statements to execute and
which to abort. See <xref linkend="server-parameters"/>.
@@ -5004,7 +5004,7 @@
slower, not faster. To avoid a slowdown, the optimization is
used only if the total size of the extra columns in the sort
tuple does not exceed the value of the
- <literal>max_length_for_sort_data</literal> system variable. (A
+ <literal role="sysvar">max_length_for_sort_data</literal> system variable. (A
symptom of setting the value of this variable too high is that
you should see high disk activity and low CPU activity.)
</para>
@@ -5012,7 +5012,7 @@
<para>
For slow queries for which <literal>filesort</literal> is not
used, you might try lowering
- <literal>max_length_for_sort_data</literal> to a value that is
+ <literal role="sysvar">max_length_for_sort_data</literal> to a value that is
appropriate to trigger a <literal>filesort</literal>.
</para>
@@ -7609,7 +7609,7 @@
<listitem>
<para>
You can start <command>mysqld</command> with a low value for
- the <literal>max_write_lock_count</literal> system variable
+ the <literal role="sysvar">max_write_lock_count</literal> system variable
to force MySQL to temporarily elevate the priority of all
<literal role="stmt">SELECT</literal> statements that are
waiting for a table after a specific number of inserts to
@@ -9556,7 +9556,7 @@
<para>
For <literal>MyISAM</literal> tables, you have some control over
collection of table statistics by means of the
- <literal>myisam_stats_method</literal> system variable. This
+ <literal role="sysvar">myisam_stats_method</literal> system variable. This
variable has two possible values, which differ as follows:
</para>
@@ -9564,7 +9564,7 @@
<listitem>
<para>
- When <literal>myisam_stats_method</literal> is
+ When <literal role="sysvar">myisam_stats_method</literal> is
<literal>nulls_equal</literal>, all <literal>NULL</literal>
values are treated as identical (that is, they all form a
single value group).
@@ -9585,7 +9585,7 @@
<listitem>
<para>
- When <literal>myisam_stats_method</literal> is
+ When <literal role="sysvar">myisam_stats_method</literal> is
<literal>nulls_unequal</literal>, <literal>NULL</literal>
values are not considered the same. Instead, each
<literal>NULL</literal> value forms a separate value group
@@ -9618,7 +9618,7 @@
</para>
<para>
- The <literal>myisam_stats_method</literal> system variable has
+ The <literal role="sysvar">myisam_stats_method</literal> system variable has
global and session values. Setting the global value affects
<literal>MyISAM</literal> statistics collection for all
<literal>MyISAM</literal> tables. Setting the session value
@@ -9626,7 +9626,7 @@
connection. This means that you can force a table's statistics
to be regenerated with a given method without affecting other
clients by setting the session value of
- <literal>myisam_stats_method</literal>.
+ <literal role="sysvar">myisam_stats_method</literal>.
</para>
<para>
@@ -9648,7 +9648,7 @@
<para>
Change the table to cause its statistics to go out of date
(for example, insert a row and then delete it), and then set
- <literal>myisam_stats_method</literal> and issue an
+ <literal role="sysvar">myisam_stats_method</literal> and issue an
<literal role="stmt">ANALYZE TABLE</literal> statement
</para>
</listitem>
@@ -9657,7 +9657,7 @@
<para>
Some caveats regarding the use of
- <literal>myisam_stats_method</literal>:
+ <literal role="sysvar">myisam_stats_method</literal>:
</para>
<itemizedlist>
@@ -9672,9 +9672,9 @@
(This may occur for bulk inserts or deletes, or some
<literal role="stmt">ALTER TABLE</literal> statements, for
example.) If this happens, the statistics are collected
- using whatever value <literal>myisam_stats_method</literal>
+ using whatever value <literal role="sysvar">myisam_stats_method</literal>
has at the time. Thus, if you collect statistics using one
- method, but <literal>myisam_stats_method</literal> is set to
+ method, but <literal role="sysvar">myisam_stats_method</literal> is set to
the other method when a table's statistics are collected
automatically later, the other method will be used.
</para>
@@ -9689,7 +9689,7 @@
<listitem>
<para>
- <literal>myisam_stats_method</literal> applies only to
+ <literal role="sysvar">myisam_stats_method</literal> applies only to
<literal>MyISAM</literal> tables. Other storage engines have
only one method for collecting table statistics. Usually it
is closer to the <literal>nulls_equal</literal> method.
@@ -9771,7 +9771,7 @@
<para>
The <literal>table_cache</literal>,
<literal role="sysvar">max_connections</literal>, and
- <literal>max_tmp_tables</literal> system variables affect the
+ <literal role="sysvar">max_tmp_tables</literal> system variables affect the
maximum number of files the server keeps open. If you increase
one or more of these values, you may run up against a limit
imposed by your operating system on the per-process number of
Modified: trunk/refman-5.0/programs-admin-util-core.xml
===================================================================
--- trunk/refman-5.0/programs-admin-util-core.xml 2008-12-02 00:15:15 UTC (rev 12726)
+++ trunk/refman-5.0/programs-admin-util-core.xml 2008-12-02 02:57:31 UTC (rev 12727)
Changed blocks: 3, Lines Added: 4, Lines Deleted: 4; 1575 bytes
@@ -812,7 +812,7 @@
<entry>523264</entry>
</row>
<row>
- <entry><literal>myisam_block_size</literal></entry>
+ <entry><literal role="sysvar">myisam_block_size</literal></entry>
<entry>1024</entry>
</row>
<row>
@@ -906,7 +906,7 @@
</para>
<para>
- <literal>myisam_block_size</literal> is the size used for index
+ <literal role="sysvar">myisam_block_size</literal> is the size used for index
blocks.
</para>
@@ -914,9 +914,9 @@
<literal>stats_method</literal> influences how
<literal>NULL</literal> values are treated for index statistics
collection when the <option>--analyze</option> option is given.
- It acts like the <literal>myisam_stats_method</literal> system
+ It acts like the <literal role="sysvar">myisam_stats_method</literal> system
variable. For more information, see the description of
- <literal>myisam_stats_method</literal> in
+ <literal role="sysvar">myisam_stats_method</literal> in
<xref linkend="server-system-variables"/>, and
<xref linkend="myisam-index-statistics"/>. For MySQL
¤t-series;, <literal>stats_method</literal> was added in
Modified: trunk/refman-5.0/programs-client-core.xml
===================================================================
--- trunk/refman-5.0/programs-client-core.xml 2008-12-02 00:15:15 UTC (rev 12726)
+++ trunk/refman-5.0/programs-client-core.xml 2008-12-02 02:57:31 UTC (rev 12727)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 523 bytes
@@ -1577,7 +1577,7 @@
<primary>max_join_size variable</primary>
</indexterm>
- <literal>max_join_size</literal>
+ <literal role="sysvar">max_join_size</literal>
</para>
<para>
Modified: trunk/refman-5.0/replication-implementation.xml
===================================================================
--- trunk/refman-5.0/replication-implementation.xml 2008-12-02 00:15:15 UTC (rev 12726)
+++ trunk/refman-5.0/replication-implementation.xml 2008-12-02 02:57:31 UTC (rev 12727)
Changed blocks: 1, Lines Added: 2, Lines Deleted: 2; 970 bytes
@@ -342,14 +342,14 @@
<listitem>
<para>
- If the value of <literal>max_relay_log_size</literal> is
+ If the value of <literal role="sysvar">max_relay_log_size</literal> is
greater than 0, that is the maximum relay log file size.
</para>
</listitem>
<listitem>
<para>
- If the value of <literal>max_relay_log_size</literal> is
+ If the value of <literal role="sysvar">max_relay_log_size</literal> is
0, <literal role="sysvar">max_binlog_size</literal>
determines the maximum relay log file size.
</para>
Modified: trunk/refman-5.0/replication-options-core.xml
===================================================================
--- trunk/refman-5.0/replication-options-core.xml 2008-12-02 00:15:15 UTC (rev 12726)
+++ trunk/refman-5.0/replication-options-core.xml 2008-12-02 02:57:31 UTC (rev 12727)
Changed blocks: 2, Lines Added: 2, Lines Deleted: 2; 1149 bytes
@@ -1292,7 +1292,7 @@
numeric suffix to the basename. You can specify the option to
create hostname-independent relay log names, or if your relay
logs tend to be big (and you don't want to decrease
- <literal>max_relay_log_size</literal>) and you need to put
+ <literal role="sysvar">max_relay_log_size</literal>) and you need to put
them in some area different from the data directory, or if you
want to increase speed by balancing load between disks.
</para>
@@ -2231,7 +2231,7 @@
</para>
<para>
- If <literal>max_relay_log_size</literal> is 0, the value of
+ If <literal role="sysvar">max_relay_log_size</literal> is 0, the value of
<literal role="sysvar">max_binlog_size</literal> applies to
relay logs as well.
</para>
Modified: trunk/refman-5.0/se-innodb-core.xml
===================================================================
--- trunk/refman-5.0/se-innodb-core.xml 2008-12-02 00:15:15 UTC (rev 12726)
+++ trunk/refman-5.0/se-innodb-core.xml 2008-12-02 02:57:31 UTC (rev 12727)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 800 bytes
@@ -7919,7 +7919,7 @@
values good enough for your particular tables, you can use
<literal>FORCE INDEX</literal> with your queries to force the
use of a particular index, or set the
- <literal>max_seeks_for_key</literal> system variable to ensure
+ <literal role="sysvar">max_seeks_for_key</literal> system variable to ensure
that MySQL prefers index lookups over table scans. See
<xref linkend="server-system-variables"/>, and
<xref linkend="optimizer-issues"/>.
Modified: trunk/refman-5.0/se-myisam-core.xml
===================================================================
--- trunk/refman-5.0/se-myisam-core.xml 2008-12-02 00:15:15 UTC (rev 12726)
+++ trunk/refman-5.0/se-myisam-core.xml 2008-12-02 02:57:31 UTC (rev 12727)
Changed blocks: 2, Lines Added: 2, Lines Deleted: 2; 674 bytes
@@ -416,7 +416,7 @@
<listitem>
<para>
- <literal>myisam_max_sort_file_size</literal>
+ <literal role="sysvar">myisam_max_sort_file_size</literal>
</para>
<para>
@@ -433,7 +433,7 @@
<listitem>
<para>
- <literal>myisam_sort_buffer_size</literal>
+ <literal role="sysvar">myisam_sort_buffer_size</literal>
</para>
<para>
Modified: trunk/refman-5.0/sql-syntax-data-definition.xml
===================================================================
--- trunk/refman-5.0/sql-syntax-data-definition.xml 2008-12-02 00:15:15 UTC (rev 12726)
+++ trunk/refman-5.0/sql-syntax-data-definition.xml 2008-12-02 02:57:31 UTC (rev 12727)
Changed blocks: 3, Lines Added: 3, Lines Deleted: 3; 1740 bytes
@@ -362,7 +362,7 @@
to be copied (such as when you change the name of a column). For
<literal>MyISAM</literal> tables, you can speed up the index
re-creation operation (which is the slowest part of the alteration
- process) by setting the <literal>myisam_sort_buffer_size</literal>
+ process) by setting the <literal role="sysvar">myisam_sort_buffer_size</literal>
system variable to a high value.
</para>
@@ -3171,7 +3171,7 @@
<literal role="type">BLOB</literal> column in a
<literal role="stmt">SELECT</literal>, the server sorts values
using only the initial number of bytes indicated by the
- <literal>max_sort_length</literal> system variable. See
+ <literal role="sysvar">max_sort_length</literal> system variable. See
<xref linkend="blob"/>.
</para>
</listitem>
@@ -3465,7 +3465,7 @@
you want to keep down the pointer sizes to make the index
smaller and faster and you don't really need big files, you
can decrease the default pointer size by setting the
- <literal>myisam_data_pointer_size</literal> system variable,
+ <literal role="sysvar">myisam_data_pointer_size</literal> system variable,
which was added in MySQL 4.1.2. (See
<xref linkend="server-system-variables"/>.) If you want all
your tables to be able to grow above the default limit and are
Modified: trunk/refman-5.0/sql-syntax-prepared-statements.xml
===================================================================
--- trunk/refman-5.0/sql-syntax-prepared-statements.xml 2008-12-02 00:15:15 UTC (rev 12726)
+++ trunk/refman-5.0/sql-syntax-prepared-statements.xml 2008-12-02 02:57:31 UTC (rev 12727)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 594 bytes
@@ -277,7 +277,7 @@
<para>
To guard against too many prepared statements being created
- simultaneously, the <literal>max_prepared_stmt_count</literal>
+ simultaneously, the <literal role="sysvar">max_prepared_stmt_count</literal>
system variable can be set.
</para>
Modified: trunk/refman-5.0/sql-syntax-server-administration.xml
===================================================================
--- trunk/refman-5.0/sql-syntax-server-administration.xml 2008-12-02 00:15:15 UTC (rev 12726)
+++ trunk/refman-5.0/sql-syntax-server-administration.xml 2008-12-02 02:57:31 UTC (rev 12727)
Changed blocks: 2, Lines Added: 2, Lines Deleted: 2; 1162 bytes
@@ -1177,7 +1177,7 @@
in MySQL 5.0.3, limits the maximum number of simultaneous
connections that the account can make. If
<replaceable>count</replaceable> is <literal>0</literal> (the
- default), the <literal>max_user_connections</literal> system
+ default), the <literal role="sysvar">max_user_connections</literal> system
variable determines the number of simultaneous connections for
the account.
</para>
@@ -3401,7 +3401,7 @@
value to the compiled-in MySQL default value, use the
<literal>DEFAULT</literal> keyword. For example, the following two
statements are identical in setting the session value of
- <literal>max_join_size</literal> to the global value:
+ <literal role="sysvar">max_join_size</literal> to the global value:
</para>
<programlisting>
Modified: trunk/refman-5.0/stored-routines.xml
===================================================================
--- trunk/refman-5.0/stored-routines.xml 2008-12-02 00:15:15 UTC (rev 12726)
+++ trunk/refman-5.0/stored-routines.xml 2008-12-02 02:57:31 UTC (rev 12727)
Changed blocks: 1, Lines Added: 2, Lines Deleted: 2; 1053 bytes
@@ -231,10 +231,10 @@
<para>
Recursion in stored procedures is allowed but disabled by default.
To enable recursion, set the
- <literal>max_sp_recursion_depth</literal> server system variable
+ <literal role="sysvar">max_sp_recursion_depth</literal> server system variable
to a value greater than zero. Stored procedure recursion increases
the demand on thread stack space. If you increase the value of
- <literal>max_sp_recursion_depth</literal>, it may be necessary to
+ <literal role="sysvar">max_sp_recursion_depth</literal>, it may be necessary to
increase thread stack size by increasing the value of
<literal>thread_stack</literal> at server startup. See
<xref linkend="server-system-variables"/>, for more information.
Modified: trunk/refman-5.1/data-types.xml
===================================================================
--- trunk/refman-5.1/data-types.xml 2008-12-02 00:15:15 UTC (rev 12726)
+++ trunk/refman-5.1/data-types.xml 2008-12-02 02:57:31 UTC (rev 12727)
Changed blocks: 3, Lines Added: 5, Lines Deleted: 5; 1915 bytes
@@ -4657,9 +4657,9 @@
<listitem>
<para>
- Only the first <literal>max_sort_length</literal> bytes of
+ Only the first <literal role="sysvar">max_sort_length</literal> bytes of
the column are used when sorting. The default value of
- <literal>max_sort_length</literal> is 1024. This value can
+ <literal role="sysvar">max_sort_length</literal> is 1024. This value can
be changed using the
<option>--max_sort_length=<replaceable>N</replaceable></option>
option when starting the <command>mysqld</command> server.
@@ -4669,9 +4669,9 @@
<para>
You can make more bytes significant in sorting or grouping
by increasing the value of
- <literal>max_sort_length</literal> at runtime. Any client
+ <literal role="sysvar">max_sort_length</literal> at runtime. Any client
can change the value of its session
- <literal>max_sort_length</literal> variable:
+ <literal role="sysvar">max_sort_length</literal> variable:
</para>
<programlisting>
@@ -4686,7 +4686,7 @@
<literal role="type">BLOB</literal> or
<literal role="type">TEXT</literal> column containing long
values when you want more than
- <literal>max_sort_length</literal> bytes to be significant
+ <literal role="sysvar">max_sort_length</literal> bytes to be significant
is to convert the column value into a fixed-length object.
The standard way to do this is with the
<literal role="func">SUBSTRING()</literal> function. For
Modified: trunk/refman-5.1/dba-core.xml
===================================================================
--- trunk/refman-5.1/dba-core.xml 2008-12-02 00:15:15 UTC (rev 12726)
+++ trunk/refman-5.1/dba-core.xml 2008-12-02 02:57:31 UTC (rev 12727)
Changed blocks: 53, Lines Added: 60, Lines Deleted: 60; 21138 bytes
@@ -6403,7 +6403,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_max_insert_delayed_threads">
+ <para id="sysvar_max_insert_delayed_threads">
<indexterm>
<primary>max_insert_delayed_threads system variable</primary>
</indexterm>
@@ -6413,7 +6413,7 @@
<secondary>max_insert_delayed_threads</secondary>
</indexterm>
- <literal>max_insert_delayed_threads</literal>
+ <literal role="sysvar">max_insert_delayed_threads</literal>
</para>
<para condition="dynamic:optvar:item" role="5.1:mysqld:max_insert_delayed_threads"/>
@@ -6425,7 +6425,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_max_join_size">
+ <para id="sysvar_max_join_size">
<indexterm>
<primary>max_join_size system variable</primary>
</indexterm>
@@ -6435,7 +6435,7 @@
<secondary>max_join_size</secondary>
</indexterm>
- <literal>max_join_size</literal>
+ <literal role="sysvar">max_join_size</literal>
</para>
<para condition="dynamic:optvar:item" role="5.1:mysqld:max_join_size"/>
@@ -6443,10 +6443,10 @@
<para>
Do not allow <literal role="stmt">SELECT</literal>
statements that probably need to examine more than
- <literal>max_join_size</literal> rows (for single-table
+ <literal role="sysvar">max_join_size</literal> rows (for single-table
statements) or row combinations (for multiple-table
statements) or that are likely to do more than
- <literal>max_join_size</literal> disk seeks. By setting this
+ <literal role="sysvar">max_join_size</literal> disk seeks. By setting this
value, you can catch <literal role="stmt">SELECT</literal>
statements where keys are not used properly and that would
probably take a long time. Set it if your users tend to
@@ -6460,7 +6460,7 @@
<literal role="sysvar">sql_big_selects</literal> to
<literal>0</literal>. If you set the
<literal role="sysvar">sql_big_selects</literal> value
- again, the <literal>max_join_size</literal> variable is
+ again, the <literal role="sysvar">max_join_size</literal> variable is
ignored.
</para>
@@ -6478,7 +6478,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_max_length_for_sort_data">
+ <para id="sysvar_max_length_for_sort_data">
<indexterm>
<primary>max_length_for_sort_data system variable</primary>
</indexterm>
@@ -6488,7 +6488,7 @@
<secondary>max_length_for_sort_data</secondary>
</indexterm>
- <literal>max_length_for_sort_data</literal>
+ <literal role="sysvar">max_length_for_sort_data</literal>
</para>
<para condition="dynamic:optvar:item" role="5.1:mysqld:max_length_for_sort_data"/>
@@ -6501,7 +6501,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_max_prepared_stmt_count">
+ <para id="sysvar_max_prepared_stmt_count">
<indexterm>
<primary>max_prepared_stmt_count system variable</primary>
</indexterm>
@@ -6511,7 +6511,7 @@
<secondary>max_prepared_stmt_count</secondary>
</indexterm>
- <literal>max_prepared_stmt_count</literal>
+ <literal role="sysvar">max_prepared_stmt_count</literal>
</para>
<para condition="dynamic:optvar:item" role="5.1:mysqld:max_prepared_stmt_count"/>
@@ -6531,7 +6531,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_max_relay_log_size">
+ <para id="sysvar_max_relay_log_size">
<indexterm>
<primary>max_relay_log_size system variable</primary>
</indexterm>
@@ -6541,7 +6541,7 @@
<secondary>max_relay_log_size</secondary>
</indexterm>
- <literal>max_relay_log_size</literal>
+ <literal role="sysvar">max_relay_log_size</literal>
</para>
<para condition="dynamic:optvar:item" role="5.1:mysqld:max_relay_log_size"/>
@@ -6551,20 +6551,20 @@
the current log file size to exceed the value of this
variable, the slave rotates the relay logs (closes the
current file and opens the next one). If
- <literal>max_relay_log_size</literal> is 0, the server uses
+ <literal role="sysvar">max_relay_log_size</literal> is 0, the server uses
<literal role="sysvar">max_binlog_size</literal> for both
the binary log and the relay log. If
- <literal>max_relay_log_size</literal> is greater than 0, it
+ <literal role="sysvar">max_relay_log_size</literal> is greater than 0, it
constrains the size of the relay log, which enables you to
have different sizes for the two logs. You must set
- <literal>max_relay_log_size</literal> to between 4096 bytes
+ <literal role="sysvar">max_relay_log_size</literal> to between 4096 bytes
and 1GB (inclusive), or to 0. The default value is 0. See
<xref linkend="replication-implementation-details"/>.
</para>
</listitem>
<listitem>
- <para id="option_mysqld_max_seeks_for_key">
+ <para id="sysvar_max_seeks_for_key">
<indexterm>
<primary>max_seeks_for_key system variable</primary>
</indexterm>
@@ -6574,7 +6574,7 @@
<secondary>max_seeks_for_key</secondary>
</indexterm>
- <literal>max_seeks_for_key</literal>
+ <literal role="sysvar">max_seeks_for_key</literal>
</para>
<para condition="dynamic:optvar:item" role="5.1:mysqld:max_seeks_for_key"/>
@@ -6592,7 +6592,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_max_sort_length">
+ <para id="sysvar_max_sort_length">
<indexterm>
<primary>max_sort_length system variable</primary>
</indexterm>
@@ -6602,7 +6602,7 @@
<secondary>max_sort_length</secondary>
</indexterm>
- <literal>max_sort_length</literal>
+ <literal role="sysvar">max_sort_length</literal>
</para>
<para condition="dynamic:optvar:item" role="5.1:mysqld:max_sort_length"/>
@@ -6611,13 +6611,13 @@
The number of bytes to use when sorting
<literal role="type">BLOB</literal> or
<literal role="type">TEXT</literal> values. Only the first
- <literal>max_sort_length</literal> bytes of each value are
+ <literal role="sysvar">max_sort_length</literal> bytes of each value are
used; the rest are ignored.
</para>
</listitem>
<listitem>
- <para id="option_mysqld_max_sp_recursion_depth">
+ <para id="sysvar_max_sp_recursion_depth">
<indexterm>
<primary>max_sp_recursion_depth system variable</primary>
</indexterm>
@@ -6627,7 +6627,7 @@
<secondary>max_sp_recursion_depth</secondary>
</indexterm>
- <literal>max_sp_recursion_depth</literal>
+ <literal role="sysvar">max_sp_recursion_depth</literal>
</para>
<para condition="dynamic:optvar:item" role="5.1:mysqld:max_sp_recursion_depth"/>
@@ -6642,14 +6642,14 @@
<para>
Stored procedure recursion increases the demand on thread
stack space. If you increase the value of
- <literal>max_sp_recursion_depth</literal>, it may be
+ <literal role="sysvar">max_sp_recursion_depth</literal>, it may be
necessary to increase thread stack size by increasing the
value of <literal>thread_stack</literal> at server startup.
</para>
</listitem>
<listitem>
- <para id="option_mysqld_max_tmp_tables">
+ <para id="sysvar_max_tmp_tables">
<indexterm>
<primary>max_tmp_tables system variable</primary>
</indexterm>
@@ -6659,7 +6659,7 @@
<secondary>max_tmp_tables</secondary>
</indexterm>
- <literal>max_tmp_tables</literal>
+ <literal role="sysvar">max_tmp_tables</literal>
</para>
<para condition="dynamic:optvar:item" role="5.1:mysqld:max_tmp_tables"/>
@@ -6672,7 +6672,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_max_user_connections">
+ <para id="sysvar_max_user_connections">
<indexterm>
<primary>max_user_connections system variable</primary>
</indexterm>
@@ -6682,7 +6682,7 @@
<secondary>max_user_connections</secondary>
</indexterm>
- <literal>max_user_connections</literal>
+ <literal role="sysvar">max_user_connections</literal>
</para>
<para condition="dynamic:optvar:item" role="5.1:mysqld:max_user_connections"/>
@@ -6704,7 +6704,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_max_write_lock_count">
+ <para id="sysvar_max_write_lock_count">
<indexterm>
<primary>max_write_lock_count system variable</primary>
</indexterm>
@@ -6714,7 +6714,7 @@
<secondary>max_write_lock_count</secondary>
</indexterm>
- <literal>max_write_lock_count</literal>
+ <literal role="sysvar">max_write_lock_count</literal>
</para>
<para condition="dynamic:optvar:item" role="5.1:mysqld:max_write_lock_count"/>
@@ -6726,7 +6726,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_min_examined_row_limit">
+ <para id="sysvar_min_examined_row_limit">
<indexterm>
<primary>min_examined_row_limit system variable</primary>
</indexterm>
@@ -6736,7 +6736,7 @@
<secondary>min_examined_row_limit</secondary>
</indexterm>
- <literal>min_examined_row_limit</literal>
+ <literal role="sysvar">min_examined_row_limit</literal>
</para>
<para condition="dynamic:optvar:item" role="5.1:mysqld:min-examined-row-limit"/>
@@ -6749,7 +6749,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_myisam_block_size">
+ <para id="sysvar_myisam_block_size">
<indexterm>
<primary>myisam_block_size system variable</primary>
</indexterm>
@@ -6759,7 +6759,7 @@
<secondary>myisam_block_size</secondary>
</indexterm>
- <literal>myisam_block_size</literal>
+ <literal role="sysvar">myisam_block_size</literal>
</para>
<para condition="dynamic:optvar:item" role="5.1:mysqld:myisam_block_size"/>
@@ -6771,7 +6771,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_myisam_data_pointer_size">
+ <para id="sysvar_myisam_data_pointer_size">
<indexterm>
<primary>myisam_data_pointer_size system variable</primary>
</indexterm>
@@ -6781,7 +6781,7 @@
<secondary>myisam_data_pointer_size</secondary>
</indexterm>
- <literal>myisam_data_pointer_size</literal>
+ <literal role="sysvar">myisam_data_pointer_size</literal>
</para>
<para condition="dynamic:optvar:item" role="5.1:mysqld:myisam_data_pointer_size"/>
@@ -6797,7 +6797,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_myisam_max_sort_file_size">
+ <para id="sysvar_myisam_max_sort_file_size">
<indexterm>
<primary>myisam_max_sort_file_size system variable</primary>
</indexterm>
@@ -6807,7 +6807,7 @@
<secondary>myisam_max_sort_file_size</secondary>
</indexterm>
- <literal>myisam_max_sort_file_size</literal>
+ <literal role="sysvar">myisam_max_sort_file_size</literal>
</para>
<para condition="dynamic:optvar:item" role="5.1:mysqld:myisam_max_sort_file_size"/>
@@ -6831,7 +6831,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_myisam_recover_options">
+ <para id="sysvar_myisam_recover_options">
<indexterm>
<primary>myisam_recover_options system variable</primary>
</indexterm>
@@ -6841,7 +6841,7 @@
<secondary>myisam_recover_options</secondary>
</indexterm>
- <literal>myisam_recover_options</literal>
+ <literal role="sysvar">myisam_recover_options</literal>
</para>
<para condition="dynamic:optvar:item" role="5.1:mysqld:myisam_recover_options"/>
@@ -6853,7 +6853,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_myisam_repair_threads">
+ <para id="sysvar_myisam_repair_threads">
<indexterm>
<primary>myisam_repair_threads system variable</primary>
</indexterm>
@@ -6863,7 +6863,7 @@
<secondary>myisam_repair_threads</secondary>
</indexterm>
- <literal>myisam_repair_threads</literal>
+ <literal role="sysvar">myisam_repair_threads</literal>
</para>
<para condition="dynamic:optvar:item" role="5.1:mysqld:myisam_repair_threads"/>
@@ -6884,7 +6884,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_myisam_sort_buffer_size">
+ <para id="sysvar_myisam_sort_buffer_size">
<indexterm>
<primary>myisam_sort_buffer_size system variable</primary>
</indexterm>
@@ -6894,7 +6894,7 @@
<secondary>myisam_sort_buffer_size</secondary>
</indexterm>
- <literal>myisam_sort_buffer_size</literal>
+ <literal role="sysvar">myisam_sort_buffer_size</literal>
</para>
<para condition="dynamic:optvar:item" role="5.1:mysqld:myisam_sort_buffer_size"/>
@@ -6909,7 +6909,7 @@
<para>
The maximum allowable setting for
- <literal>myisam_sort_buffer_size</literal> is 4GB. As of
+ <literal role="sysvar">myisam_sort_buffer_size</literal> is 4GB. As of
MySQL 5.1.23, values larger than 4GB are allowed for 64-bit
platforms (except 64-bit Windows, for which large values are
truncated to 4GB with a warning).
@@ -6917,7 +6917,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_myisam_stats_method">
+ <para id="sysvar_myisam_stats_method">
<indexterm>
<primary>myisam_stats_method system variable</primary>
</indexterm>
@@ -6927,7 +6927,7 @@
<secondary>myisam_stats_method</secondary>
</indexterm>
- <literal>myisam_stats_method</literal>
+ <literal role="sysvar">myisam_stats_method</literal>
</para>
<para condition="dynamic:optvar:item" role="5.1:mysqld:myisam_stats_method"/>
@@ -6962,7 +6962,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_myisam_use_mmap">
+ <para id="sysvar_myisam_use_mmap">
<indexterm>
<primary>myisam_use_mmap system variable</primary>
</indexterm>
@@ -6972,7 +6972,7 @@
<secondary>myisam_use_mmap</secondary>
</indexterm>
- <literal>myisam_use_mmap</literal>
+ <literal role="sysvar">myisam_use_mmap</literal>
</para>
<para condition="dynamic:optvar:item" role="5.1:mysqld:myisam_use_mmap"/>
@@ -7422,7 +7422,7 @@
<para>
The current number of prepared statements. (The maximum
number of statements is given by the
- <literal>max_prepared_stmt_count</literal> system variable.)
+ <literal role="sysvar">max_prepared_stmt_count</literal> system variable.)
This variable was added in MySQL 5.1.10. In MySQL 5.1.14, it
was converted to the global
<literal>Prepared_stmt_count</literal> status variable.
@@ -9762,14 +9762,14 @@
likely to take a very long time to execute (that is,
statements for which the optimizer estimates that the number
of examined rows exceeds the value of
- <literal>max_join_size</literal>). This is useful when an
+ <literal role="sysvar">max_join_size</literal>). This is useful when an
inadvisable <literal>WHERE</literal> statement has been
issued. The default value for a new connection is 1, which
allows all <literal role="stmt">SELECT</literal> statements.
</para>
<para>
- If you set the <literal>max_join_size</literal> system
+ If you set the <literal role="sysvar">max_join_size</literal> system
variable to a value other than <literal>DEFAULT</literal>,
<literal role="sysvar">sql_big_selects</literal> is set to
0.
@@ -10291,7 +10291,7 @@
value to the compiled-in MySQL default value, use the
<literal>DEFAULT</literal> keyword. For example, the following
two statements are identical in setting the session value of
- <literal>max_join_size</literal> to the global value:
+ <literal role="sysvar">max_join_size</literal> to the global value:
</para>
<programlisting>
@@ -12000,7 +12000,7 @@
<para>
The current number of prepared statements. (The maximum
number of statements is given by the
- <literal>max_prepared_stmt_count</literal> system variable.)
+ <literal role="sysvar">max_prepared_stmt_count</literal> system variable.)
This variable was added in MySQL 5.1.14.
</para>
</listitem>
@@ -16411,7 +16411,7 @@
The slow query log consists of all SQL statements that took more
than <literal role="sysvar">long_query_time</literal> seconds to
execute and (as of MySQL 5.1.21) required at least
- <literal>min_examined_row_limit</literal> rows to be examined.
+ <literal role="sysvar">min_examined_row_limit</literal> rows to be examined.
The time to acquire the initial table locks is not counted as
execution time. <command>mysqld</command> writes a statement to
the slow query log after it has been executed and after all
@@ -17335,7 +17335,7 @@
<para>
If you want to restrict the number of connections allowed to
a single account, you can do so by setting the
- <literal>max_user_connections</literal> variable in
+ <literal role="sysvar">max_user_connections</literal> variable in
<command>mysqld</command>. The
<literal role="stmt">GRANT</literal> statement also supports
resource control options for limiting the extent of server
@@ -18363,7 +18363,7 @@
</row>
<row>
<entry/>
- <entry><literal>max_user_connections</literal></entry>
+ <entry><literal role="sysvar">max_user_connections</literal></entry>
<entry/>
</row>
</tbody>
@@ -22561,7 +22561,7 @@
<para>
One means of limiting use of MySQL server resources is to set
- the <literal>max_user_connections</literal> system variable to a
+ the <literal role="sysvar">max_user_connections</literal> system variable to a
non-zero value. However, this method is strictly global, and
does not allow for management of individual accounts. In
addition, it limits only the number of simultaneous connections
@@ -22650,7 +22650,7 @@
limits are stored in the <literal>max_questions</literal>,
<literal>max_updates</literal>,
<literal role="sysvar">max_connections</literal>, and
- <literal>max_user_connections</literal> columns. If your
+ <literal role="sysvar">max_user_connections</literal> columns. If your
<literal>user</literal> table doesn't have these columns, it
must be upgraded; see <xref linkend="mysql-upgrade"/>.
</para>
@@ -22686,7 +22686,7 @@
indicating the maximum number of simultaneous connections the
account can make at any one time. If the limit is set to the
default value of zero, the
- <literal>max_user_connections</literal> system variable
+ <literal role="sysvar">max_user_connections</literal> system variable
determines the number of simultaneous connections for the
account.
</para>
Modified: trunk/refman-5.1/errors-problems-core.xml
===================================================================
--- trunk/refman-5.1/errors-problems-core.xml 2008-12-02 00:15:15 UTC (rev 12726)
+++ trunk/refman-5.1/errors-problems-core.xml 2008-12-02 02:57:31 UTC (rev 12727)
Changed blocks: 2, Lines Added: 4, Lines Deleted: 4; 1859 bytes
@@ -1853,11 +1853,11 @@
<para>
To change the default size limit for
<literal>MyISAM</literal> tables, set the
- <literal>myisam_data_pointer_size</literal>, which sets
+ <literal role="sysvar">myisam_data_pointer_size</literal>, which sets
the number of bytes used for internal row pointers. The
value is used to set the pointer size for new tables if
you do not specify the <literal>MAX_ROWS</literal> option.
- The value of <literal>myisam_data_pointer_size</literal>
+ The value of <literal role="sysvar">myisam_data_pointer_size</literal>
can be from 2 to 7. A value of 4 allows tables up to 4GB;
a value of 6 allows tables up to 256TB.
</para>
@@ -5445,10 +5445,10 @@
<literal role="type">TEXT</literal> values can't reliably
be used in <literal>GROUP BY</literal>, <literal>ORDER
BY</literal> or <literal>DISTINCT</literal>. Only the
- first <literal>max_sort_length</literal> bytes are used
+ first <literal role="sysvar">max_sort_length</literal> bytes are used
when comparing <literal role="type">BLOB</literal> values
in these cases. The default value of
- <literal>max_sort_length</literal> is 1024 and can be
+ <literal role="sysvar">max_sort_length</literal> is 1024 and can be
changed at server startup time or at runtime.
</para>
</listitem>
Modified: trunk/refman-5.1/optimization.xml
===================================================================
--- trunk/refman-5.1/optimization.xml 2008-12-02 00:15:15 UTC (rev 12726)
+++ trunk/refman-5.1/optimization.xml 2008-12-02 02:57:31 UTC (rev 12727)
Changed blocks: 15, Lines Added: 16, Lines Deleted: 16; 6925 bytes
@@ -1812,7 +1812,7 @@
of the <literal role="stmt">EXPLAIN</literal> output. This
should tell you roughly how many rows MySQL must examine to
execute the query. If you restrict queries with the
- <literal>max_join_size</literal> system variable, this row
+ <literal role="sysvar">max_join_size</literal> system variable, this row
product also is used to determine which multiple-table
<literal role="stmt">SELECT</literal> statements to execute and
which to abort. See <xref linkend="server-parameters"/>.
@@ -5140,7 +5140,7 @@
slower, not faster. To avoid a slowdown, the optimization is
used only if the total size of the extra columns in the sort
tuple does not exceed the value of the
- <literal>max_length_for_sort_data</literal> system variable. (A
+ <literal role="sysvar">max_length_for_sort_data</literal> system variable. (A
symptom of setting the value of this variable too high is that
you should see high disk activity and low CPU activity.)
</para>
@@ -5148,7 +5148,7 @@
<para>
For slow queries for which <literal>filesort</literal> is not
used, you might try lowering
- <literal>max_length_for_sort_data</literal> to a value that is
+ <literal role="sysvar">max_length_for_sort_data</literal> to a value that is
appropriate to trigger a <literal>filesort</literal>.
</para>
@@ -8449,7 +8449,7 @@
<listitem>
<para>
You can start <command>mysqld</command> with a low value for
- the <literal>max_write_lock_count</literal> system variable
+ the <literal role="sysvar">max_write_lock_count</literal> system variable
to force MySQL to temporarily elevate the priority of all
<literal role="stmt">SELECT</literal> statements that are
waiting for a table after a specific number of inserts to
@@ -10394,7 +10394,7 @@
<para>
For <literal>MyISAM</literal> tables, you have some control over
collection of table statistics by means of the
- <literal>myisam_stats_method</literal> system variable. This
+ <literal role="sysvar">myisam_stats_method</literal> system variable. This
variable has two possible values, which differ as follows:
</para>
@@ -10402,7 +10402,7 @@
<listitem>
<para>
- When <literal>myisam_stats_method</literal> is
+ When <literal role="sysvar">myisam_stats_method</literal> is
<literal>nulls_equal</literal>, all <literal>NULL</literal>
values are treated as identical (that is, they all form a
single value group).
@@ -10423,7 +10423,7 @@
<listitem>
<para>
- When <literal>myisam_stats_method</literal> is
+ When <literal role="sysvar">myisam_stats_method</literal> is
<literal>nulls_unequal</literal>, <literal>NULL</literal>
values are not considered the same. Instead, each
<literal>NULL</literal> value forms a separate value group
@@ -10456,7 +10456,7 @@
</para>
<para>
- The <literal>myisam_stats_method</literal> system variable has
+ The <literal role="sysvar">myisam_stats_method</literal> system variable has
global and session values. Setting the global value affects
<literal>MyISAM</literal> statistics collection for all
<literal>MyISAM</literal> tables. Setting the session value
@@ -10464,7 +10464,7 @@
connection. This means that you can force a table's statistics
to be regenerated with a given method without affecting other
clients by setting the session value of
- <literal>myisam_stats_method</literal>.
+ <literal role="sysvar">myisam_stats_method</literal>.
</para>
<para>
@@ -10486,7 +10486,7 @@
<para>
Change the table to cause its statistics to go out of date
(for example, insert a row and then delete it), and then set
- <literal>myisam_stats_method</literal> and issue an
+ <literal role="sysvar">myisam_stats_method</literal> and issue an
<literal role="stmt">ANALYZE TABLE</literal> statement
</para>
</listitem>
@@ -10495,7 +10495,7 @@
<para>
Some caveats regarding the use of
- <literal>myisam_stats_method</literal>:
+ <literal role="sysvar">myisam_stats_method</literal>:
</para>
<itemizedlist>
@@ -10510,9 +10510,9 @@
(This may occur for bulk inserts or deletes, or some
<literal role="stmt">ALTER TABLE</literal> statements, for
example.) If this happens, the statistics are collected
- using whatever value <literal>myisam_stats_method</literal>
+ using whatever value <literal role="sysvar">myisam_stats_method</literal>
has at the time. Thus, if you collect statistics using one
- method, but <literal>myisam_stats_method</literal> is set to
+ method, but <literal role="sysvar">myisam_stats_method</literal> is set to
the other method when a table's statistics are collected
automatically later, the other method will be used.
</para>
@@ -10527,7 +10527,7 @@
<listitem>
<para>
- <literal>myisam_stats_method</literal> applies only to
+ <literal role="sysvar">myisam_stats_method</literal> applies only to
<literal>MyISAM</literal> tables. Other storage engines have
only one method for collecting table statistics. Usually it
is closer to the <literal>nulls_equal</literal> method.
@@ -10616,7 +10616,7 @@
<para>
The <literal>table_open_cache</literal>,
<literal role="sysvar">max_connections</literal>, and
- <literal>max_tmp_tables</literal> system variables affect the
+ <literal role="sysvar">max_tmp_tables</literal> system variables affect the
maximum number of files the server keeps open. If you increase
one or more of these values, you may run up against a limit
imposed by your operating system on the per-process number of
@@ -16311,7 +16311,7 @@
<para>
Before MySQL 5.1.4, only compressed
<literal>MyISAM</literal> tables are memory mapped. As of
- MySQL 5.1.4, the <literal>myisam_use_mmap</literal> system
+ MySQL 5.1.4, the <literal role="sysvar">myisam_use_mmap</literal> system
variable can be set to 1 to enable memory-mapping for all
<literal>MyISAM</literal> tables.
</para>
Modified: trunk/refman-5.1/partitioning.xml
===================================================================
--- trunk/refman-5.1/partitioning.xml 2008-12-02 00:15:15 UTC (rev 12726)
+++ trunk/refman-5.1/partitioning.xml 2008-12-02 02:57:31 UTC (rev 12727)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 834 bytes
@@ -4524,7 +4524,7 @@
<literal>open_files_limit</literal> is set properly.
For partitioned tables using the
<literal>MyISAM</literal> storage engine, increasing
- <literal>myisam_max_sort_file_size</literal> may
+ <literal role="sysvar">myisam_max_sort_file_size</literal> may
improve performance; partitioning and repartitioning
operations involving <literal>InnoDB</literal>
tables may be made more efficient by enabling
Modified: trunk/refman-5.1/programs-admin-util-core.xml
===================================================================
--- trunk/refman-5.1/programs-admin-util-core.xml 2008-12-02 00:15:15 UTC (rev 12726)
+++ trunk/refman-5.1/programs-admin-util-core.xml 2008-12-02 02:57:31 UTC (rev 12727)
Changed blocks: 3, Lines Added: 4, Lines Deleted: 4; 1575 bytes
@@ -817,7 +817,7 @@
<entry>523264</entry>
</row>
<row>
- <entry><literal>myisam_block_size</literal></entry>
+ <entry><literal role="sysvar">myisam_block_size</literal></entry>
<entry>1024</entry>
</row>
<row>
@@ -903,7 +903,7 @@
</para>
<para>
- <literal>myisam_block_size</literal> is the size used for index
+ <literal role="sysvar">myisam_block_size</literal> is the size used for index
blocks.
</para>
@@ -911,9 +911,9 @@
<literal>stats_method</literal> influences how
<literal>NULL</literal> values are treated for index statistics
collection when the <option>--analyze</option> option is given.
- It acts like the <literal>myisam_stats_method</literal> system
+ It acts like the <literal role="sysvar">myisam_stats_method</literal> system
variable. For more information, see the description of
- <literal>myisam_stats_method</literal> in
+ <literal role="sysvar">myisam_stats_method</literal> in
<xref linkend="server-system-variables"/>, and
<xref linkend="myisam-index-statistics"/>. For MySQL
¤t-series;, <literal>stats_method</literal> was added in
Modified: trunk/refman-5.1/programs-client-core.xml
===================================================================
--- trunk/refman-5.1/programs-client-core.xml 2008-12-02 00:15:15 UTC (rev 12726)
+++ trunk/refman-5.1/programs-client-core.xml 2008-12-02 02:57:31 UTC (rev 12727)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 523 bytes
@@ -1625,7 +1625,7 @@
<primary>max_join_size variable</primary>
</indexterm>
- <literal>max_join_size</literal>
+ <literal role="sysvar">max_join_size</literal>
</para>
<para>
Modified: trunk/refman-5.1/replication-implementation.xml
===================================================================
--- trunk/refman-5.1/replication-implementation.xml 2008-12-02 00:15:15 UTC (rev 12726)
+++ trunk/refman-5.1/replication-implementation.xml 2008-12-02 02:57:31 UTC (rev 12727)
Changed blocks: 1, Lines Added: 2, Lines Deleted: 2; 998 bytes
@@ -417,14 +417,14 @@
<listitem>
<para>
- If the value of <literal>max_relay_log_size</literal> is
+ If the value of <literal role="sysvar">max_relay_log_size</literal> is
greater than 0, that is the maximum relay log file size.
</para>
</listitem>
<listitem>
<para>
- If the value of <literal>max_relay_log_size</literal> is
+ If the value of <literal role="sysvar">max_relay_log_size</literal> is
0, <literal role="sysvar">max_binlog_size</literal>
determines the maximum relay log file size.
</para>
Modified: trunk/refman-5.1/replication-options-core.xml
===================================================================
--- trunk/refman-5.1/replication-options-core.xml 2008-12-02 00:15:15 UTC (rev 12726)
+++ trunk/refman-5.1/replication-options-core.xml 2008-12-02 02:57:31 UTC (rev 12727)
Changed blocks: 2, Lines Added: 2, Lines Deleted: 2; 1149 bytes
@@ -1353,7 +1353,7 @@
numeric suffix to the basename. You can specify the option to
create hostname-independent relay log names, or if your relay
logs tend to be big (and you don't want to decrease
- <literal>max_relay_log_size</literal>) and you need to put
+ <literal role="sysvar">max_relay_log_size</literal>) and you need to put
them in some area different from the data directory, or if you
want to increase speed by balancing load between disks.
</para>
@@ -2615,7 +2615,7 @@
</para>
<para>
- If <literal>max_relay_log_size</literal> is 0, the value of
+ If <literal role="sysvar">max_relay_log_size</literal> is 0, the value of
<literal role="sysvar">max_binlog_size</literal> applies to
relay logs as well.
</para>
Modified: trunk/refman-5.1/se-innodb-core.xml
===================================================================
--- trunk/refman-5.1/se-innodb-core.xml 2008-12-02 00:15:15 UTC (rev 12726)
+++ trunk/refman-5.1/se-innodb-core.xml 2008-12-02 02:57:31 UTC (rev 12727)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 800 bytes
@@ -8664,7 +8664,7 @@
values good enough for your particular tables, you can use
<literal>FORCE INDEX</literal> with your queries to force the
use of a particular index, or set the
- <literal>max_seeks_for_key</literal> system variable to ensure
+ <literal role="sysvar">max_seeks_for_key</literal> system variable to ensure
that MySQL prefers index lookups over table scans. See
<xref linkend="server-system-variables"/>, and
<xref linkend="optimizer-issues"/>.
Modified: trunk/refman-5.1/se-myisam-core.xml
===================================================================
--- trunk/refman-5.1/se-myisam-core.xml 2008-12-02 00:15:15 UTC (rev 12726)
+++ trunk/refman-5.1/se-myisam-core.xml 2008-12-02 02:57:31 UTC (rev 12727)
Changed blocks: 2, Lines Added: 2, Lines Deleted: 2; 674 bytes
@@ -409,7 +409,7 @@
<listitem>
<para>
- <literal>myisam_max_sort_file_size</literal>
+ <literal role="sysvar">myisam_max_sort_file_size</literal>
</para>
<para>
@@ -426,7 +426,7 @@
<listitem>
<para>
- <literal>myisam_sort_buffer_size</literal>
+ <literal role="sysvar">myisam_sort_buffer_size</literal>
</para>
<para>
Modified: trunk/refman-5.1/sql-syntax-data-definition.xml
===================================================================
--- trunk/refman-5.1/sql-syntax-data-definition.xml 2008-12-02 00:15:15 UTC (rev 12726)
+++ trunk/refman-5.1/sql-syntax-data-definition.xml 2008-12-02 02:57:31 UTC (rev 12727)
Changed blocks: 3, Lines Added: 3, Lines Deleted: 3; 1752 bytes
@@ -908,7 +908,7 @@
wouldn't strictly need to be copied. For <literal>MyISAM</literal>
tables, you can speed up the index re-creation operation (which is
the slowest part of the alteration process) by setting the
- <literal>myisam_sort_buffer_size</literal> system variable to a
+ <literal role="sysvar">myisam_sort_buffer_size</literal> system variable to a
high value.
</para>
@@ -5568,7 +5568,7 @@
<literal role="type">BLOB</literal> column in a
<literal role="stmt">SELECT</literal>, the server sorts values
using only the initial number of bytes indicated by the
- <literal>max_sort_length</literal> system variable. See
+ <literal role="sysvar">max_sort_length</literal> system variable. See
<xref linkend="blob"/>.
</para>
</listitem>
@@ -5908,7 +5908,7 @@
file size limit.) If you want to keep down the pointer sizes
to make the index smaller and faster and you don't really need
big files, you can decrease the default pointer size by
- setting the <literal>myisam_data_pointer_size</literal> system
+ setting the <literal role="sysvar">myisam_data_pointer_size</literal> system
variable. (See <xref linkend="server-system-variables"/>.) If
you want all your tables to be able to grow above the default
limit and are willing to have your tables slightly slower and
Modified: trunk/refman-5.1/sql-syntax-prepared-statements.xml
===================================================================
--- trunk/refman-5.1/sql-syntax-prepared-statements.xml 2008-12-02 00:15:15 UTC (rev 12726)
+++ trunk/refman-5.1/sql-syntax-prepared-statements.xml 2008-12-02 02:57:31 UTC (rev 12727)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 594 bytes
@@ -281,7 +281,7 @@
<para>
To guard against too many prepared statements being created
- simultaneously, the <literal>max_prepared_stmt_count</literal>
+ simultaneously, the <literal role="sysvar">max_prepared_stmt_count</literal>
system variable can be set.
</para>
Modified: trunk/refman-5.1/sql-syntax-server-administration.xml
===================================================================
--- trunk/refman-5.1/sql-syntax-server-administration.xml 2008-12-02 00:15:15 UTC (rev 12726)
+++ trunk/refman-5.1/sql-syntax-server-administration.xml 2008-12-02 02:57:31 UTC (rev 12727)
Changed blocks: 2, Lines Added: 2, Lines Deleted: 2; 1130 bytes
@@ -1135,7 +1135,7 @@
maximum number of simultaneous connections that the account can
make. If <replaceable>count</replaceable> is
<literal>0</literal> (the default), the
- <literal>max_user_connections</literal> system variable
+ <literal role="sysvar">max_user_connections</literal> system variable
determines the number of simultaneous connections for the
account.
</para>
@@ -3645,7 +3645,7 @@
value to the compiled-in MySQL default value, use the
<literal>DEFAULT</literal> keyword. For example, the following two
statements are identical in setting the session value of
- <literal>max_join_size</literal> to the global value:
+ <literal role="sysvar">max_join_size</literal> to the global value:
</para>
<programlisting>
Modified: trunk/refman-5.1/stored-routines.xml
===================================================================
--- trunk/refman-5.1/stored-routines.xml 2008-12-02 00:15:15 UTC (rev 12726)
+++ trunk/refman-5.1/stored-routines.xml 2008-12-02 02:57:31 UTC (rev 12727)
Changed blocks: 1, Lines Added: 2, Lines Deleted: 2; 1053 bytes
@@ -222,10 +222,10 @@
<para>
Recursion in stored procedures is allowed but disabled by default.
To enable recursion, set the
- <literal>max_sp_recursion_depth</literal> server system variable
+ <literal role="sysvar">max_sp_recursion_depth</literal> server system variable
to a value greater than zero. Stored procedure recursion increases
the demand on thread stack space. If you increase the value of
- <literal>max_sp_recursion_depth</literal>, it may be necessary to
+ <literal role="sysvar">max_sp_recursion_depth</literal>, it may be necessary to
increase thread stack size by increasing the value of
<literal>thread_stack</literal> at server startup. See
<xref linkend="server-system-variables"/>, for more information.
Modified: trunk/refman-5.1-maria/sql-syntax-server-administration.xml
===================================================================
--- trunk/refman-5.1-maria/sql-syntax-server-administration.xml 2008-12-02 00:15:15 UTC (rev 12726)
+++ trunk/refman-5.1-maria/sql-syntax-server-administration.xml 2008-12-02 02:57:31 UTC (rev 12727)
Changed blocks: 2, Lines Added: 2, Lines Deleted: 2; 1148 bytes
@@ -1135,7 +1135,7 @@
maximum number of simultaneous connections that the account can
make. If <replaceable>count</replaceable> is
<literal>0</literal> (the default), the
- <literal>max_user_connections</literal> system variable
+ <literal role="sysvar">max_user_connections</literal> system variable
determines the number of simultaneous connections for the
account.
</para>
@@ -3726,7 +3726,7 @@
value to the compiled-in MySQL default value, use the
<literal>DEFAULT</literal> keyword. For example, the following two
statements are identical in setting the session value of
- <literal>max_join_size</literal> to the global value:
+ <literal role="sysvar">max_join_size</literal> to the global value:
</para>
<programlisting>
Modified: trunk/refman-6.0/data-types.xml
===================================================================
--- trunk/refman-6.0/data-types.xml 2008-12-02 00:15:15 UTC (rev 12726)
+++ trunk/refman-6.0/data-types.xml 2008-12-02 02:57:31 UTC (rev 12727)
Changed blocks: 3, Lines Added: 5, Lines Deleted: 5; 1915 bytes
@@ -4649,9 +4649,9 @@
<listitem>
<para>
- Only the first <literal>max_sort_length</literal> bytes of
+ Only the first <literal role="sysvar">max_sort_length</literal> bytes of
the column are used when sorting. The default value of
- <literal>max_sort_length</literal> is 1024. This value can
+ <literal role="sysvar">max_sort_length</literal> is 1024. This value can
be changed using the
<option>--max_sort_length=<replaceable>N</replaceable></option>
option when starting the <command>mysqld</command> server.
@@ -4661,9 +4661,9 @@
<para>
You can make more bytes significant in sorting or grouping
by increasing the value of
- <literal>max_sort_length</literal> at runtime. Any client
+ <literal role="sysvar">max_sort_length</literal> at runtime. Any client
can change the value of its session
- <literal>max_sort_length</literal> variable:
+ <literal role="sysvar">max_sort_length</literal> variable:
</para>
<programlisting>
@@ -4678,7 +4678,7 @@
<literal role="type">BLOB</literal> or
<literal role="type">TEXT</literal> column containing long
values when you want more than
- <literal>max_sort_length</literal> bytes to be significant
+ <literal role="sysvar">max_sort_length</literal> bytes to be significant
is to convert the column value into a fixed-length object.
The standard way to do this is with the
<literal role="func">SUBSTRING()</literal> function. For
Modified: trunk/refman-6.0/dba-core.xml
===================================================================
--- trunk/refman-6.0/dba-core.xml 2008-12-02 00:15:15 UTC (rev 12726)
+++ trunk/refman-6.0/dba-core.xml 2008-12-02 02:57:31 UTC (rev 12727)
Changed blocks: 53, Lines Added: 60, Lines Deleted: 60; 20834 bytes
@@ -6922,7 +6922,7 @@
</para>
<para>
- If <literal>max_relay_log_size</literal> is 0, the value of
+ If <literal role="sysvar">max_relay_log_size</literal> is 0, the value of
<literal role="sysvar">max_binlog_size</literal> applies to
relay logs as well.
</para>
@@ -7105,7 +7105,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_max_insert_delayed_threads">
+ <para id="sysvar_max_insert_delayed_threads">
<indexterm>
<primary>max_insert_delayed_threads system variable</primary>
</indexterm>
@@ -7115,7 +7115,7 @@
<secondary>max_insert_delayed_threads</secondary>
</indexterm>
- <literal>max_insert_delayed_threads</literal>
+ <literal role="sysvar">max_insert_delayed_threads</literal>
</para>
<para condition="dynamic:optvar:item" role="6.0:mysqld:max_insert_delayed_threads"/>
@@ -7127,7 +7127,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_max_join_size">
+ <para id="sysvar_max_join_size">
<indexterm>
<primary>max_join_size system variable</primary>
</indexterm>
@@ -7137,7 +7137,7 @@
<secondary>max_join_size</secondary>
</indexterm>
- <literal>max_join_size</literal>
+ <literal role="sysvar">max_join_size</literal>
</para>
<para condition="dynamic:optvar:item" role="6.0:mysqld:max_join_size"/>
@@ -7145,10 +7145,10 @@
<para>
Do not allow <literal role="stmt">SELECT</literal>
statements that probably need to examine more than
- <literal>max_join_size</literal> rows (for single-table
+ <literal role="sysvar">max_join_size</literal> rows (for single-table
statements) or row combinations (for multiple-table
statements) or that are likely to do more than
- <literal>max_join_size</literal> disk seeks. By setting this
+ <literal role="sysvar">max_join_size</literal> disk seeks. By setting this
value, you can catch <literal role="stmt">SELECT</literal>
statements where keys are not used properly and that would
probably take a long time. Set it if your users tend to
@@ -7162,7 +7162,7 @@
<literal role="sysvar">sql_big_selects</literal> to
<literal>0</literal>. If you set the
<literal role="sysvar">sql_big_selects</literal> value
- again, the <literal>max_join_size</literal> variable is
+ again, the <literal role="sysvar">max_join_size</literal> variable is
ignored.
</para>
@@ -7180,7 +7180,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_max_length_for_sort_data">
+ <para id="sysvar_max_length_for_sort_data">
<indexterm>
<primary>max_length_for_sort_data system variable</primary>
</indexterm>
@@ -7190,7 +7190,7 @@
<secondary>max_length_for_sort_data</secondary>
</indexterm>
- <literal>max_length_for_sort_data</literal>
+ <literal role="sysvar">max_length_for_sort_data</literal>
</para>
<para condition="dynamic:optvar:item" role="6.0:mysqld:max_length_for_sort_data"/>
@@ -7203,7 +7203,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_max_prepared_stmt_count">
+ <para id="sysvar_max_prepared_stmt_count">
<indexterm>
<primary>max_prepared_stmt_count system variable</primary>
</indexterm>
@@ -7213,7 +7213,7 @@
<secondary>max_prepared_stmt_count</secondary>
</indexterm>
- <literal>max_prepared_stmt_count</literal>
+ <literal role="sysvar">max_prepared_stmt_count</literal>
</para>
<para>
@@ -7231,7 +7231,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_max_relay_log_size">
+ <para id="sysvar_max_relay_log_size">
<indexterm>
<primary>max_relay_log_size system variable</primary>
</indexterm>
@@ -7241,7 +7241,7 @@
<secondary>max_relay_log_size</secondary>
</indexterm>
- <literal>max_relay_log_size</literal>
+ <literal role="sysvar">max_relay_log_size</literal>
</para>
<para condition="dynamic:optvar:item" role="6.0:mysqld:max_relay_log_size"/>
@@ -7251,20 +7251,20 @@
the current log file size to exceed the value of this
variable, the slave rotates the relay logs (closes the
current file and opens the next one). If
- <literal>max_relay_log_size</literal> is 0, the server uses
+ <literal role="sysvar">max_relay_log_size</literal> is 0, the server uses
<literal role="sysvar">max_binlog_size</literal> for both
the binary log and the relay log. If
- <literal>max_relay_log_size</literal> is greater than 0, it
+ <literal role="sysvar">max_relay_log_size</literal> is greater than 0, it
constrains the size of the relay log, which enables you to
have different sizes for the two logs. You must set
- <literal>max_relay_log_size</literal> to between 4096 bytes
+ <literal role="sysvar">max_relay_log_size</literal> to between 4096 bytes
and 1GB (inclusive), or to 0. The default value is 0. See
<xref linkend="replication-implementation-details"/>.
</para>
</listitem>
<listitem>
- <para id="option_mysqld_max_seeks_for_key">
+ <para id="sysvar_max_seeks_for_key">
<indexterm>
<primary>max_seeks_for_key system variable</primary>
</indexterm>
@@ -7274,7 +7274,7 @@
<secondary>max_seeks_for_key</secondary>
</indexterm>
- <literal>max_seeks_for_key</literal>
+ <literal role="sysvar">max_seeks_for_key</literal>
</para>
<para condition="dynamic:optvar:item" role="6.0:mysqld:max_seeks_for_key"/>
@@ -7292,7 +7292,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_max_sort_length">
+ <para id="sysvar_max_sort_length">
<indexterm>
<primary>max_sort_length system variable</primary>
</indexterm>
@@ -7302,7 +7302,7 @@
<secondary>max_sort_length</secondary>
</indexterm>
- <literal>max_sort_length</literal>
+ <literal role="sysvar">max_sort_length</literal>
</para>
<para condition="dynamic:optvar:item" role="6.0:mysqld:max_sort_length"/>
@@ -7311,13 +7311,13 @@
The number of bytes to use when sorting
<literal role="type">BLOB</literal> or
<literal role="type">TEXT</literal> values. Only the first
- <literal>max_sort_length</literal> bytes of each value are
+ <literal role="sysvar">max_sort_length</literal> bytes of each value are
used; the rest are ignored.
</para>
</listitem>
<listitem>
- <para id="option_mysqld_max_sp_recursion_depth">
+ <para id="sysvar_max_sp_recursion_depth">
<indexterm>
<primary>max_sp_recursion_depth system variable</primary>
</indexterm>
@@ -7327,7 +7327,7 @@
<secondary>max_sp_recursion_depth</secondary>
</indexterm>
- <literal>max_sp_recursion_depth</literal>
+ <literal role="sysvar">max_sp_recursion_depth</literal>
</para>
<para condition="dynamic:optvar:item" role="6.0:mysqld:max_sp_recursion_depth"/>
@@ -7342,14 +7342,14 @@
<para>
Stored procedure recursion increases the demand on thread
stack space. If you increase the value of
- <literal>max_sp_recursion_depth</literal>, it may be
+ <literal role="sysvar">max_sp_recursion_depth</literal>, it may be
necessary to increase thread stack size by increasing the
value of <literal>thread_stack</literal> at server startup.
</para>
</listitem>
<listitem>
- <para id="option_mysqld_max_tmp_tables">
+ <para id="sysvar_max_tmp_tables">
<indexterm>
<primary>max_tmp_tables system variable</primary>
</indexterm>
@@ -7359,7 +7359,7 @@
<secondary>max_tmp_tables</secondary>
</indexterm>
- <literal>max_tmp_tables</literal>
+ <literal role="sysvar">max_tmp_tables</literal>
</para>
<para condition="dynamic:optvar:item" role="6.0:mysqld:max_tmp_tables"/>
@@ -7372,7 +7372,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_max_user_connections">
+ <para id="sysvar_max_user_connections">
<indexterm>
<primary>max_user_connections system variable</primary>
</indexterm>
@@ -7382,7 +7382,7 @@
<secondary>max_user_connections</secondary>
</indexterm>
- <literal>max_user_connections</literal>
+ <literal role="sysvar">max_user_connections</literal>
</para>
<para condition="dynamic:optvar:item" role="6.0:mysqld:max_user_connections"/>
@@ -7404,7 +7404,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_max_write_lock_count">
+ <para id="sysvar_max_write_lock_count">
<indexterm>
<primary>max_write_lock_count system variable</primary>
</indexterm>
@@ -7414,7 +7414,7 @@
<secondary>max_write_lock_count</secondary>
</indexterm>
- <literal>max_write_lock_count</literal>
+ <literal role="sysvar">max_write_lock_count</literal>
</para>
<para condition="dynamic:optvar:item" role="6.0:mysqld:max_write_lock_count"/>
@@ -7426,7 +7426,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_min_examined_row_limit">
+ <para id="sysvar_min_examined_row_limit">
<indexterm>
<primary>min_examined_row_limit system variable</primary>
</indexterm>
@@ -7436,7 +7436,7 @@
<secondary>min_examined_row_limit</secondary>
</indexterm>
- <literal>min_examined_row_limit</literal>
+ <literal role="sysvar">min_examined_row_limit</literal>
</para>
<para condition="dynamic:optvar:item" role="6.0:mysqld:min-examined-row-limit"/>
@@ -7449,7 +7449,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_myisam_block_size">
+ <para id="sysvar_myisam_block_size">
<indexterm>
<primary>myisam_block_size system variable</primary>
</indexterm>
@@ -7459,7 +7459,7 @@
<secondary>myisam_block_size</secondary>
</indexterm>
- <literal>myisam_block_size</literal>
+ <literal role="sysvar">myisam_block_size</literal>
</para>
<para condition="dynamic:optvar:item" role="6.0:mysqld:myisam_block_size"/>
@@ -7471,7 +7471,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_myisam_data_pointer_size">
+ <para id="sysvar_myisam_data_pointer_size">
<indexterm>
<primary>myisam_data_pointer_size system variable</primary>
</indexterm>
@@ -7481,7 +7481,7 @@
<secondary>myisam_data_pointer_size</secondary>
</indexterm>
- <literal>myisam_data_pointer_size</literal>
+ <literal role="sysvar">myisam_data_pointer_size</literal>
</para>
<para condition="dynamic:optvar:item" role="6.0:mysqld:myisam_data_pointer_size"/>
@@ -7497,7 +7497,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_myisam_max_sort_file_size">
+ <para id="sysvar_myisam_max_sort_file_size">
<indexterm>
<primary>myisam_max_sort_file_size system variable</primary>
</indexterm>
@@ -7507,7 +7507,7 @@
<secondary>myisam_max_sort_file_size</secondary>
</indexterm>
- <literal>myisam_max_sort_file_size</literal>
+ <literal role="sysvar">myisam_max_sort_file_size</literal>
</para>
<para condition="dynamic:optvar:item" role="6.0:mysqld:myisam_max_sort_file_size"/>
@@ -7531,7 +7531,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_myisam_recover_options">
+ <para id="sysvar_myisam_recover_options">
<indexterm>
<primary>myisam_recover_options system variable</primary>
</indexterm>
@@ -7541,7 +7541,7 @@
<secondary>myisam_recover_options</secondary>
</indexterm>
- <literal>myisam_recover_options</literal>
+ <literal role="sysvar">myisam_recover_options</literal>
</para>
<para condition="dynamic:optvar:item" role="6.0:mysqld:myisam_recover_options"/>
@@ -7553,7 +7553,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_myisam_repair_threads">
+ <para id="sysvar_myisam_repair_threads">
<indexterm>
<primary>myisam_repair_threads system variable</primary>
</indexterm>
@@ -7563,7 +7563,7 @@
<secondary>myisam_repair_threads</secondary>
</indexterm>
- <literal>myisam_repair_threads</literal>
+ <literal role="sysvar">myisam_repair_threads</literal>
</para>
<para condition="dynamic:optvar:item" role="6.0:mysqld:myisam_repair_threads"/>
@@ -7584,7 +7584,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_myisam_sort_buffer_size">
+ <para id="sysvar_myisam_sort_buffer_size">
<indexterm>
<primary>myisam_sort_buffer_size system variable</primary>
</indexterm>
@@ -7594,7 +7594,7 @@
<secondary>myisam_sort_buffer_size</secondary>
</indexterm>
- <literal>myisam_sort_buffer_size</literal>
+ <literal role="sysvar">myisam_sort_buffer_size</literal>
</para>
<para condition="dynamic:optvar:item" role="6.0:mysqld:myisam_sort_buffer_size"/>
@@ -7609,7 +7609,7 @@
<para>
The maximum allowable setting for
- <literal>myisam_sort_buffer_size</literal> is 4GB. Values
+ <literal role="sysvar">myisam_sort_buffer_size</literal> is 4GB. Values
larger than 4GB are allowed for 64-bit platforms (except
64-bit Windows, for which large values are truncated to 4GB
with a warning).
@@ -7617,7 +7617,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_myisam_stats_method">
+ <para id="sysvar_myisam_stats_method">
<indexterm>
<primary>myisam_stats_method system variable</primary>
</indexterm>
@@ -7627,7 +7627,7 @@
<secondary>myisam_stats_method</secondary>
</indexterm>
- <literal>myisam_stats_method</literal>
+ <literal role="sysvar">myisam_stats_method</literal>
</para>
<para condition="dynamic:optvar:item" role="6.0:mysqld:myisam_stats_method"/>
@@ -7662,7 +7662,7 @@
</listitem>
<listitem>
- <para id="option_mysqld_myisam_use_mmap">
+ <para id="sysvar_myisam_use_mmap">
<indexterm>
<primary>myisam_use_mmap system variable</primary>
</indexterm>
@@ -7672,7 +7672,7 @@
<secondary>myisam_use_mmap</secondary>
</indexterm>
- <literal>myisam_use_mmap</literal>
+ <literal role="sysvar">myisam_use_mmap</literal>
</para>
<para condition="dynamic:optvar:item" role="6.0:mysqld:myisam_use_mmap"/>
@@ -10924,14 +10924,14 @@
likely to take a very long time to execute (that is,
statements for which the optimizer estimates that the number
of examined rows exceeds the value of
- <literal>max_join_size</literal>). This is useful when an
+ <literal role="sysvar">max_join_size</literal>). This is useful when an
inadvisable <literal>WHERE</literal> statement has been
issued. The default value for a new connection is 1, which
allows all <literal role="stmt">SELECT</literal> statements.
</para>
<para>
- If you set the <literal>max_join_size</literal> system
+ If you set the <literal role="sysvar">max_join_size</literal> system
variable to a value other than <literal>DEFAULT</literal>,
<literal role="sysvar">sql_big_selects</literal> is set to
0.
@@ -11453,7 +11453,7 @@
value to the compiled-in MySQL default value, use the
<literal>DEFAULT</literal> keyword. For example, the following
two statements are identical in setting the session value of
- <literal>max_join_size</literal> to the global value:
+ <literal role="sysvar">max_join_size</literal> to the global value:
</para>
<programlisting>
@@ -13160,7 +13160,7 @@
<para>
The current number of prepared statements. (The maximum
number of statements is given by the
- <literal>max_prepared_stmt_count</literal> system variable.)
+ <literal role="sysvar">max_prepared_stmt_count</literal> system variable.)
</para>
</listitem>
@@ -18003,7 +18003,7 @@
The slow query log consists of all SQL statements that took more
than <literal role="sysvar">long_query_time</literal> seconds to
execute and (as of MySQL 6.0.4) required at least
- <literal>min_examined_row_limit</literal> rows to be examined.
+ <literal role="sysvar">min_examined_row_limit</literal> rows to be examined.
The time to acquire the initial table locks is not counted as
execution time. <command>mysqld</command> writes a statement to
the slow query log after it has been executed and after all
@@ -18933,7 +18933,7 @@
<para>
If you want to restrict the number of connections allowed to
a single account, you can do so by setting the
- <literal>max_user_connections</literal> variable in
+ <literal role="sysvar">max_user_connections</literal> variable in
<command>mysqld</command>. The
<literal role="stmt">GRANT</literal> statement also supports
resource control options for limiting the extent of server
@@ -19962,7 +19962,7 @@
</row>
<row>
<entry/>
- <entry><literal>max_user_connections</literal></entry>
+ <entry><literal role="sysvar">max_user_connections</literal></entry>
<entry/>
</row>
</tbody>
@@ -24164,7 +24164,7 @@
<para>
One means of limiting use of MySQL server resources is to set
- the <literal>max_user_connections</literal> system variable to a
+ the <literal role="sysvar">max_user_connections</literal> system variable to a
non-zero value. However, this method is strictly global, and
does not allow for management of individual accounts. In
addition, it limits only the number of simultaneous connections
@@ -24253,7 +24253,7 @@
limits are stored in the <literal>max_questions</literal>,
<literal>max_updates</literal>,
<literal role="sysvar">max_connections</literal>, and
- <literal>max_user_connections</literal> columns. If your
+ <literal role="sysvar">max_user_connections</literal> columns. If your
<literal>user</literal> table doesn't have these columns, it
must be upgraded; see <xref linkend="mysql-upgrade"/>.
</para>
@@ -24289,7 +24289,7 @@
indicating the maximum number of simultaneous connections the
account can make at any one time. If the limit is set to the
default value of zero, the
- <literal>max_user_connections</literal> system variable
+ <literal role="sysvar">max_user_connections</literal> system variable
determines the number of simultaneous connections for the
account.
</para>
Modified: trunk/refman-6.0/errors-problems.xml
===================================================================
--- trunk/refman-6.0/errors-problems.xml 2008-12-02 00:15:15 UTC (rev 12726)
+++ trunk/refman-6.0/errors-problems.xml 2008-12-02 02:57:31 UTC (rev 12727)
Changed blocks: 2, Lines Added: 4, Lines Deleted: 4; 1844 bytes
@@ -1841,11 +1841,11 @@
<para>
To change the default size limit for
<literal>MyISAM</literal> tables, set the
- <literal>myisam_data_pointer_size</literal>, which sets
+ <literal role="sysvar">myisam_data_pointer_size</literal>, which sets
the number of bytes used for internal row pointers. The
value is used to set the pointer size for new tables if
you do not specify the <literal>MAX_ROWS</literal> option.
- The value of <literal>myisam_data_pointer_size</literal>
+ The value of <literal role="sysvar">myisam_data_pointer_size</literal>
can be from 2 to 7. A value of 4 allows tables up to 4GB;
a value of 6 allows tables up to 256TB.
</para>
@@ -5417,10 +5417,10 @@
<literal role="type">TEXT</literal> values can't reliably
be used in <literal>GROUP BY</literal>, <literal>ORDER
BY</literal> or <literal>DISTINCT</literal>. Only the
- first <literal>max_sort_length</literal> bytes are used
+ first <literal role="sysvar">max_sort_length</literal> bytes are used
when comparing <literal role="type">BLOB</literal> values
in these cases. The default value of
- <literal>max_sort_length</literal> is 1024 and can be
+ <literal role="sysvar">max_sort_length</literal> is 1024 and can be
changed at server startup time or at runtime.
</para>
</listitem>
Modified: trunk/refman-6.0/optimization.xml
===================================================================
--- trunk/refman-6.0/optimization.xml 2008-12-02 00:15:15 UTC (rev 12726)
+++ trunk/refman-6.0/optimization.xml 2008-12-02 02:57:31 UTC (rev 12727)
Changed blocks: 15, Lines Added: 16, Lines Deleted: 16; 6814 bytes
@@ -1814,7 +1814,7 @@
of the <literal role="stmt">EXPLAIN</literal> output. This
should tell you roughly how many rows MySQL must examine to
execute the query. If you restrict queries with the
- <literal>max_join_size</literal> system variable, this row
+ <literal role="sysvar">max_join_size</literal> system variable, this row
product also is used to determine which multiple-table
<literal role="stmt">SELECT</literal> statements to execute and
which to abort. See <xref linkend="server-parameters"/>.
@@ -5488,7 +5488,7 @@
slower, not faster. To avoid a slowdown, the optimization is
used only if the total size of the extra columns in the sort
tuple does not exceed the value of the
- <literal>max_length_for_sort_data</literal> system variable. (A
+ <literal role="sysvar">max_length_for_sort_data</literal> system variable. (A
symptom of setting the value of this variable too high is that
you should see high disk activity and low CPU activity.)
</para>
@@ -5496,7 +5496,7 @@
<para>
For slow queries for which <literal>filesort</literal> is not
used, you might try lowering
- <literal>max_length_for_sort_data</literal> to a value that is
+ <literal role="sysvar">max_length_for_sort_data</literal> to a value that is
appropriate to trigger a <literal>filesort</literal>.
</para>
@@ -8797,7 +8797,7 @@
<listitem>
<para>
You can start <command>mysqld</command> with a low value for
- the <literal>max_write_lock_count</literal> system variable
+ the <literal role="sysvar">max_write_lock_count</literal> system variable
to force MySQL to temporarily elevate the priority of all
<literal role="stmt">SELECT</literal> statements that are
waiting for a table after a specific number of inserts to
@@ -10741,7 +10741,7 @@
<para>
For <literal>MyISAM</literal> tables, you have some control over
collection of table statistics by means of the
- <literal>myisam_stats_method</literal> system variable. This
+ <literal role="sysvar">myisam_stats_method</literal> system variable. This
variable has two possible values, which differ as follows:
</para>
@@ -10749,7 +10749,7 @@
<listitem>
<para>
- When <literal>myisam_stats_method</literal> is
+ When <literal role="sysvar">myisam_stats_method</literal> is
<literal>nulls_equal</literal>, all <literal>NULL</literal>
values are treated as identical (that is, they all form a
single value group).
@@ -10770,7 +10770,7 @@
<listitem>
<para>
- When <literal>myisam_stats_method</literal> is
+ When <literal role="sysvar">myisam_stats_method</literal> is
<literal>nulls_unequal</literal>, <literal>NULL</literal>
values are not considered the same. Instead, each
<literal>NULL</literal> value forms a separate value group
@@ -10803,7 +10803,7 @@
</para>
<para>
- The <literal>myisam_stats_method</literal> system variable has
+ The <literal role="sysvar">myisam_stats_method</literal> system variable has
global and session values. Setting the global value affects
<literal>MyISAM</literal> statistics collection for all
<literal>MyISAM</literal> tables. Setting the session value
@@ -10811,7 +10811,7 @@
connection. This means that you can force a table's statistics
to be regenerated with a given method without affecting other
clients by setting the session value of
- <literal>myisam_stats_method</literal>.
+ <literal role="sysvar">myisam_stats_method</literal>.
</para>
<para>
@@ -10833,7 +10833,7 @@
<para>
Change the table to cause its statistics to go out of date
(for example, insert a row and then delete it), and then set
- <literal>myisam_stats_method</literal> and issue an
+ <literal role="sysvar">myisam_stats_method</literal> and issue an
<literal role="stmt">ANALYZE TABLE</literal> statement
</para>
</listitem>
@@ -10842,7 +10842,7 @@
<para>
Some caveats regarding the use of
- <literal>myisam_stats_method</literal>:
+ <literal role="sysvar">myisam_stats_method</literal>:
</para>
<itemizedlist>
@@ -10857,9 +10857,9 @@
(This may occur for bulk inserts or deletes, or some
<literal role="stmt">ALTER TABLE</literal> statements, for
example.) If this happens, the statistics are collected
- using whatever value <literal>myisam_stats_method</literal>
+ using whatever value <literal role="sysvar">myisam_stats_method</literal>
has at the time. Thus, if you collect statistics using one
- method, but <literal>myisam_stats_method</literal> is set to
+ method, but <literal role="sysvar">myisam_stats_method</literal> is set to
the other method when a table's statistics are collected
automatically later, the other method will be used.
</para>
@@ -10874,7 +10874,7 @@
<listitem>
<para>
- <literal>myisam_stats_method</literal> applies only to
+ <literal role="sysvar">myisam_stats_method</literal> applies only to
<literal>MyISAM</literal> tables. Other storage engines have
only one method for collecting table statistics. Usually it
is closer to the <literal>nulls_equal</literal> method.
@@ -10956,7 +10956,7 @@
<para>
The <literal>table_open_cache</literal>,
<literal role="sysvar">max_connections</literal>, and
- <literal>max_tmp_tables</literal> system variables affect the
+ <literal role="sysvar">max_tmp_tables</literal> system variables affect the
maximum number of files the server keeps open. If you increase
one or more of these values, you may run up against a limit
imposed by your operating system on the per-process number of
@@ -16505,7 +16505,7 @@
<listitem>
<para>
- The <literal>myisam_use_mmap</literal> system variable can
+ The <literal role="sysvar">myisam_use_mmap</literal> system variable can
be set to 1 to enable memory-mapping for all
<literal>MyISAM</literal> tables.
</para>
Modified: trunk/refman-6.0/partitioning.xml
===================================================================
--- trunk/refman-6.0/partitioning.xml 2008-12-02 00:15:15 UTC (rev 12726)
+++ trunk/refman-6.0/partitioning.xml 2008-12-02 02:57:31 UTC (rev 12727)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 834 bytes
@@ -4396,7 +4396,7 @@
<literal>open_files_limit</literal> is set properly.
For partitioned tables using the
<literal>MyISAM</literal> storage engine, increasing
- <literal>myisam_max_sort_file_size</literal> may
+ <literal role="sysvar">myisam_max_sort_file_size</literal> may
improve performance; partitioning and repartitioning
operations involving <literal>InnoDB</literal>
tables may be made more efficient by enabling
Modified: trunk/refman-6.0/programs-admin-util-core.xml
===================================================================
--- trunk/refman-6.0/programs-admin-util-core.xml 2008-12-02 00:15:15 UTC (rev 12726)
+++ trunk/refman-6.0/programs-admin-util-core.xml 2008-12-02 02:57:31 UTC (rev 12727)
Changed blocks: 3, Lines Added: 4, Lines Deleted: 4; 1575 bytes
@@ -817,7 +817,7 @@
<entry>523264</entry>
</row>
<row>
- <entry><literal>myisam_block_size</literal></entry>
+ <entry><literal role="sysvar">myisam_block_size</literal></entry>
<entry>1024</entry>
</row>
<row>
@@ -903,7 +903,7 @@
</para>
<para>
- <literal>myisam_block_size</literal> is the size used for index
+ <literal role="sysvar">myisam_block_size</literal> is the size used for index
blocks.
</para>
@@ -911,9 +911,9 @@
<literal>stats_method</literal> influences how
<literal>NULL</literal> values are treated for index statistics
collection when the <option>--analyze</option> option is given.
- It acts like the <literal>myisam_stats_method</literal> system
+ It acts like the <literal role="sysvar">myisam_stats_method</literal> system
variable. For more information, see the description of
- <literal>myisam_stats_method</literal> in
+ <literal role="sysvar">myisam_stats_method</literal> in
<xref linkend="server-system-variables"/>, and
<xref linkend="myisam-index-statistics"/>. For MySQL
¤t-series;, <literal>stats_method</literal> was added in
Modified: trunk/refman-6.0/programs-client-core.xml
===================================================================
--- trunk/refman-6.0/programs-client-core.xml 2008-12-02 00:15:15 UTC (rev 12726)
+++ trunk/refman-6.0/programs-client-core.xml 2008-12-02 02:57:31 UTC (rev 12727)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 523 bytes
@@ -1628,7 +1628,7 @@
<primary>max_join_size variable</primary>
</indexterm>
- <literal>max_join_size</literal>
+ <literal role="sysvar">max_join_size</literal>
</para>
<para>
Modified: trunk/refman-6.0/replication-implementation.xml
===================================================================
--- trunk/refman-6.0/replication-implementation.xml 2008-12-02 00:15:15 UTC (rev 12726)
+++ trunk/refman-6.0/replication-implementation.xml 2008-12-02 02:57:31 UTC (rev 12727)
Changed blocks: 1, Lines Added: 2, Lines Deleted: 2; 998 bytes
@@ -417,14 +417,14 @@
<listitem>
<para>
- If the value of <literal>max_relay_log_size</literal> is
+ If the value of <literal role="sysvar">max_relay_log_size</literal> is
greater than 0, that is the maximum relay log file size.
</para>
</listitem>
<listitem>
<para>
- If the value of <literal>max_relay_log_size</literal> is
+ If the value of <literal role="sysvar">max_relay_log_size</literal> is
0, <literal role="sysvar">max_binlog_size</literal>
determines the maximum relay log file size.
</para>
Modified: trunk/refman-6.0/replication-options-core.xml
===================================================================
--- trunk/refman-6.0/replication-options-core.xml 2008-12-02 00:15:15 UTC (rev 12726)
+++ trunk/refman-6.0/replication-options-core.xml 2008-12-02 02:57:31 UTC (rev 12727)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 813 bytes
@@ -408,7 +408,7 @@
numeric suffix to the basename. You can specify the option to
create hostname-independent relay log names, or if your relay
logs tend to be big (and you don't want to decrease
- <literal>max_relay_log_size</literal>) and you need to put them
+ <literal role="sysvar">max_relay_log_size</literal>) and you need to put them
in some area different from the data directory, or if you want
to increase speed by balancing load between disks.
</para>
Modified: trunk/refman-6.0/se-innodb-core.xml
===================================================================
--- trunk/refman-6.0/se-innodb-core.xml 2008-12-02 00:15:15 UTC (rev 12726)
+++ trunk/refman-6.0/se-innodb-core.xml 2008-12-02 02:57:31 UTC (rev 12727)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 800 bytes
@@ -8530,7 +8530,7 @@
values good enough for your particular tables, you can use
<literal>FORCE INDEX</literal> with your queries to force the
use of a particular index, or set the
- <literal>max_seeks_for_key</literal> system variable to ensure
+ <literal role="sysvar">max_seeks_for_key</literal> system variable to ensure
that MySQL prefers index lookups over table scans. See
<xref linkend="server-system-variables"/>, and
<xref linkend="optimizer-issues"/>.
Modified: trunk/refman-6.0/se-myisam-core.xml
===================================================================
--- trunk/refman-6.0/se-myisam-core.xml 2008-12-02 00:15:15 UTC (rev 12726)
+++ trunk/refman-6.0/se-myisam-core.xml 2008-12-02 02:57:31 UTC (rev 12727)
Changed blocks: 2, Lines Added: 2, Lines Deleted: 2; 674 bytes
@@ -408,7 +408,7 @@
<listitem>
<para>
- <literal>myisam_max_sort_file_size</literal>
+ <literal role="sysvar">myisam_max_sort_file_size</literal>
</para>
<para>
@@ -425,7 +425,7 @@
<listitem>
<para>
- <literal>myisam_sort_buffer_size</literal>
+ <literal role="sysvar">myisam_sort_buffer_size</literal>
</para>
<para>
Modified: trunk/refman-6.0/sql-syntax-data-definition.xml
===================================================================
--- trunk/refman-6.0/sql-syntax-data-definition.xml 2008-12-02 00:15:15 UTC (rev 12726)
+++ trunk/refman-6.0/sql-syntax-data-definition.xml 2008-12-02 02:57:31 UTC (rev 12727)
Changed blocks: 3, Lines Added: 3, Lines Deleted: 3; 1752 bytes
@@ -780,7 +780,7 @@
wouldn't strictly need to be copied. For <literal>MyISAM</literal>
tables, you can speed up the index re-creation operation (which is
the slowest part of the alteration process) by setting the
- <literal>myisam_sort_buffer_size</literal> system variable to a
+ <literal role="sysvar">myisam_sort_buffer_size</literal> system variable to a
high value.
</para>
@@ -4678,7 +4678,7 @@
<literal role="type">BLOB</literal> column in a
<literal role="stmt">SELECT</literal>, the server sorts values
using only the initial number of bytes indicated by the
- <literal>max_sort_length</literal> system variable. See
+ <literal role="sysvar">max_sort_length</literal> system variable. See
<xref linkend="blob"/>.
</para>
</listitem>
@@ -4990,7 +4990,7 @@
file size limit.) If you want to keep down the pointer sizes
to make the index smaller and faster and you don't really need
big files, you can decrease the default pointer size by
- setting the <literal>myisam_data_pointer_size</literal> system
+ setting the <literal role="sysvar">myisam_data_pointer_size</literal> system
variable. (See <xref linkend="server-system-variables"/>.) If
you want all your tables to be able to grow above the default
limit and are willing to have your tables slightly slower and
Modified: trunk/refman-6.0/sql-syntax-prepared-statements.xml
===================================================================
--- trunk/refman-6.0/sql-syntax-prepared-statements.xml 2008-12-02 00:15:15 UTC (rev 12726)
+++ trunk/refman-6.0/sql-syntax-prepared-statements.xml 2008-12-02 02:57:31 UTC (rev 12727)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 594 bytes
@@ -281,7 +281,7 @@
<para>
To guard against too many prepared statements being created
- simultaneously, the <literal>max_prepared_stmt_count</literal>
+ simultaneously, the <literal role="sysvar">max_prepared_stmt_count</literal>
system variable can be set.
</para>
Modified: trunk/refman-6.0/sql-syntax-server-administration.xml
===================================================================
--- trunk/refman-6.0/sql-syntax-server-administration.xml 2008-12-02 00:15:15 UTC (rev 12726)
+++ trunk/refman-6.0/sql-syntax-server-administration.xml 2008-12-02 02:57:31 UTC (rev 12727)
Changed blocks: 2, Lines Added: 2, Lines Deleted: 2; 1130 bytes
@@ -1145,7 +1145,7 @@
maximum number of simultaneous connections that the account can
make. If <replaceable>count</replaceable> is
<literal>0</literal> (the default), the
- <literal>max_user_connections</literal> system variable
+ <literal role="sysvar">max_user_connections</literal> system variable
determines the number of simultaneous connections for the
account.
</para>
@@ -3882,7 +3882,7 @@
value to the compiled-in MySQL default value, use the
<literal>DEFAULT</literal> keyword. For example, the following two
statements are identical in setting the session value of
- <literal>max_join_size</literal> to the global value:
+ <literal role="sysvar">max_join_size</literal> to the global value:
</para>
<programlisting>
Modified: trunk/refman-6.0/stored-routines.xml
===================================================================
--- trunk/refman-6.0/stored-routines.xml 2008-12-02 00:15:15 UTC (rev 12726)
+++ trunk/refman-6.0/stored-routines.xml 2008-12-02 02:57:31 UTC (rev 12727)
Changed blocks: 1, Lines Added: 2, Lines Deleted: 2; 1053 bytes
@@ -222,10 +222,10 @@
<para>
Recursion in stored procedures is allowed but disabled by default.
To enable recursion, set the
- <literal>max_sp_recursion_depth</literal> server system variable
+ <literal role="sysvar">max_sp_recursion_depth</literal> server system variable
to a value greater than zero. Stored procedure recursion increases
the demand on thread stack space. If you increase the value of
- <literal>max_sp_recursion_depth</literal>, it may be necessary to
+ <literal role="sysvar">max_sp_recursion_depth</literal>, it may be necessary to
increase thread stack size by increasing the value of
<literal>thread_stack</literal> at server startup. See
<xref linkend="server-system-variables"/>, for more information.
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r12727 - in trunk: . dynamic-docs/changelog dynamic-docs/command-optvars mysql-monitor refman-4.1 refman-5.0 refman-5.1... | paul.dubois | 2 Dec |
