| List: | Internals | « Previous MessageNext Message » | |
| From: | jon | Date: | October 1 2005 3:20pm |
| Subject: | bk commit - mysqldoc@docsrva tree (jon:1.3659) | ||
| View as plain text | |||
Below is the list of changes that have just been committed into a local mysqldoc repository of jon. When jon does a push these changes will be propagated to the main repository and, within 24 hours after the push, to the public repository. For information on how to access the public repository see http://www.mysql.com/doc/I/n/Installing_source_tree.html ChangeSet 1.3659 05/10/01 23:20:34 jon@stripped +5 -0 RefMan-5.1 edits for DB Admin chapter. Minimise nonessential diffs between 5.0 and 5.1 versions. Cut some historical stuff from the 5.0 version. Updated current release entities for 5.0 and 5.1. Updated RefMan-5.1 Status file. refman-5.1/versions.ent 1.7 05/10/01 23:20:26 jon@stripped +1 -1 Updated current version entity. refman-5.1/mysql-database-administration.xml 1.48 05/10/01 23:20:26 jon@stripped +453 -593 RefMan-5.1-specific edits. refman-5.1/Status 1.9 05/10/01 23:20:25 jon@stripped +1 -1 Updating... refman-5.0/versions.ent 1.7 05/10/01 23:20:25 jon@stripped +1 -1 Updated current version entity. refman-5.0/mysql-database-administration.xml 1.49 05/10/01 23:20:25 jon@stripped +293 -318 Minimise non-essential diffs. Cut a few archaeological references that had crept in. # This is a BitKeeper patch. What follows are the unified diffs for the # set of deltas contained in the patch. The rest of the patch, the part # that BitKeeper cares about, is below these diffs. # User: jon # Host: gigan. # Root: /home/jon/bk/mysqldoc2 --- 1.8/refman-5.1/Status 2005-09-05 14:04:28 +10:00 +++ 1.9/refman-5.1/Status 2005-10-01 23:20:25 +10:00 @@ -3,11 +3,11 @@ introduction using-mysql-programs error-handling + mysql-database-administration - 5.1 chapters awaiting major edits: preface tutorial - mysql-database-administration language-structure column-types functions --- 1.47/refman-5.1/mysql-database-administration.xml 2005-09-30 04:51:06 +10:00 +++ 1.48/refman-5.1/mysql-database-administration.xml 2005-10-01 23:20:26 +10:00 @@ -262,11 +262,8 @@ <title id="title-mysqld-max">&title-mysqld-max;</title> <remark role="todo"> - -max is dynamically linked to support dynamic loading? - </remark> - - <remark> - (that is stated in UDF section, but not here) + -max is dynamically linked to support dynamic loading? (that is + stated in UDF section, but not here) </remark> <indexterm> @@ -513,7 +510,7 @@ <remark> Output for both SHOW commands following is from - 5.0.7-alpha-nt-max + 5.1.2-alpha-log </remark> <para> @@ -553,36 +550,36 @@ </para> <para> - Before MySQL 4.1.2, <literal>SHOW ENGINES</literal> is - unavailable. Use the following statement instead and check the - value of the variable for the storage engine in which you are - interested: + You can also use the following statement instead of + <literal>SHOW ENGINES</literal>, and check the value of the + variable for the storage engine in which you are interested: </para> <programlisting> mysql> <userinput>SHOW VARIABLES LIKE 'have%';</userinput> -+-----------------------+-------+ -| Variable_name | Value | -+-----------------------+-------+ -| have_archive | YES | -| have_bdb | YES | -| have_blackhole_engine | YES | -| have_compress | YES | -| have_crypt | NO | -| have_csv | NO | -| have_example_engine | NO | -| have_federated_engine | YES | -| have_geometry | YES | -| have_innodb | YES | -| have_isam | NO | -| have_ndbcluster | NO | -| have_openssl | YES | -| have_query_cache | YES | -| have_raid | NO | -| have_rtree_keys | YES | -| have_symlink | YES | -+-----------------------+-------+ -17 rows in set (0.06 sec) ++-----------------------+----------+ +| Variable_name | Value | ++-----------------------+----------+ +| have_archive | YES | +| have_bdb | NO | +| have_blackhole_engine | YES | +| have_compress | YES | +| have_crypt | YES | +| have_csv | YES | +| have_example_engine | NO | +| have_federated_engine | NO | +| have_geometry | YES | +| have_innodb | YES | +| have_isam | NO | +| have_ndbcluster | DISABLED | +| have_openssl | NO | +| have_partition_engine | YES | +| have_query_cache | YES | +| have_raid | NO | +| have_rtree_keys | YES | +| have_symlink | YES | ++-----------------------+----------+ +18 rows in set (0.01 sec) </programlisting> <para> @@ -638,7 +635,11 @@ <literal>InnoDB</literal> or <literal>BDB</literal> storage engines if the server was compiled to support them, but was started with the <option>--skip-innodb</option> or - <option>--skip-bdb</option> options at runtime. + <option>--skip-bdb</option> options at runtime. For the + <literal>NDB Cluster</literal> storage engine, + <literal>DISABLED</literal> means the the server was compiled + with support for MySQL Cluster, but was not started with the + <option>--ndb-cluster</option> option. </para> <para> @@ -807,7 +808,7 @@ </para> <para> - Display a help message and exit. (Added in MySQL 5.0.3) + Display a help message and exit. </para> </listitem> @@ -1013,8 +1014,8 @@ <para> Ignore character set information sent by the client and - use the default server character set. This option makes - MySQL 4.1 and higher behave like MySQL 4.0. + use the default server character set. (This option makes + MySQL behave like MySQL 4.0.) </para> </listitem> @@ -1925,13 +1926,11 @@ The MySQL Instance Manager (IM) is a daemon running on a TCP/IP port, which serves for monitoring and management of MySQL Database Server instances. MySQL Instance Manager is - available for Unix-like operating systems, and also on Windows - as of MySQL 5.0.13. + available for Unix-like operating systems, as well as Windows. </para> <para> - MySQL Instance Manager is included in MySQL distributions from - version 5.0.3, and can be used in place of the + MySQL Instance Manager can be used in place of the <literal>mysqld_safe</literal> script to start and stop the MySQL Server, <emphasis role="bold">even from a remote host</emphasis>. MySQL Instance Manager also implements the @@ -1949,18 +1948,12 @@ <para> Normally, the MySQL Database Server is started with the <command>mysql.server</command> script, which usually resides - in the <literal>/etc/init.d/</literal> folder. In MySQL 5.0.3 - this script invokes <command>mysqlmanager</command> (the MySQL - Instance Manager binary) to start MySQL. (In prior versions of - MySQL the <command>mysqld_safe</command> script is used for - this purpose.) Starting from MySQL 5.0.4 the behavior of the - init script was changed again to incorporate both setup - schemes. In version 5.0.4, the init startup script uses the - old scheme (invoking <command>mysqld_safe</command>) by - default, but one can set the - <literal>use_mysqld_safe</literal> variable in the script to - <literal>0</literal> (zero) to use the MySQL Instance Manager - to start a server. + in the <literal>/etc/init.d/</literal> folder. In MySQL + ¤t-series; this script invokes the + <command>mysqld_safe</command> script by default. However, you + can set the <literal>use_mysqld_safe</literal> variable in the + script to <literal>0</literal> (zero) in order to use the + MySQL Instance Manager to start a server. </para> <remark role="todo"> @@ -1995,11 +1988,11 @@ <para> Note that there is a special option <literal>mysqld-path</literal> (<literal>mysqld-path = - <path-to-mysqld-binary></literal>) which is recognized - only by the IM. Use this variable to let the IM know where the - <command>mysqld</command> binary resides. You should also set - <literal>basedir</literal> and <literal>datadir</literal> - options for the server. + <replaceable>path-to-mysqld-binary</replaceable></literal>) + which is recognized only by the IM. Use this variable to let + the IM know where the <command>mysqld</command> binary + resides. You should also set <literal>basedir</literal> and + <literal>datadir</literal> options for the server. </para> <para> @@ -2168,7 +2161,6 @@ <para> On Windows, install Instance Manager as a Windows service. - This option was added in MySQL 5.0.11. </para> </listitem> @@ -2196,7 +2188,7 @@ restart the instance. One can disable this behavior for particular instances with the <literal>nonguarded</literal> option in the appropriate - instance section. If no value was given, the default of 20 + instance section. If no value was given, the default of 20 seconds will be used. </para> </listitem> @@ -2240,7 +2232,7 @@ </para> <para> - The port number to use for connections. (The efault port + The port number to use for connections. (The default port number, assigned by IANA, is 2273). </para> </listitem> @@ -2264,8 +2256,7 @@ <para> On Windows, removes Instance Manager as a Windows service. This assumes that Instance Manager has been run with - <option>--install</option> previously. This option was - added in MySQL 5.0.11. + <option>--install</option> previously. </para> </listitem> @@ -2299,8 +2290,7 @@ </para> <para> - On Windows, run Instance Manager in standalone mode. This - option was added in MySQL 5.0.13. + On Windows, run Instance Manager in standalone mode. </para> </listitem> @@ -2357,8 +2347,8 @@ </programlisting> <para> - The MySQL Instance Manager only reads and manages the - <filename>/etc/my.cnf</filename> file on Unix. On Windows, + The MySQL Instance Manager reads and manages the + <filename>/etc/my.cnf</filename> file only on Unix. On Windows, MySQL Instance Manager reads the <filename>my.ini</filename> file in the directory where Instance Manager is installed. The default option file location can be changed with the @@ -2392,7 +2382,7 @@ </para> <para> - A number of seconds IM should wait for the instance to + The number of seconds IM should wait for the instance to shut down. The default is 35 seconds. After the delay expires, the IM assumes that the instance is hanging and attempts to <literal>kill -9</literal> it. If you use @@ -2907,9 +2897,7 @@ only UDFs that have at least one auxiliary symbol can be loaded. This prevents attempts at loading functions from shared object files other than those containing legitimate - UDFs. In the MySQL ¤t-series; series of releases, - this option was added in version 5.0.3. See - <xref linkend="udf-security"/>. + UDFs. See <xref linkend="udf-security"/>. </para> </listitem> @@ -3346,8 +3334,7 @@ </para> <para> - This option is disabled by default. It was added in MySQL - 5.0.3. + This option is disabled by default. </para> </listitem> @@ -3411,10 +3398,6 @@ how MySQL enforces restrictions on stored routine creation. See <xref linkend="stored-procedure-logging"/>. </para> - - <para> - This option was added in MySQL 5.0.6. - </para> </listitem> <listitem> @@ -4230,7 +4213,7 @@ </para> <remark role="todo"> - Determine if this is still supported at all in MySQL 5.0. + Determine if this is still supported at all in MySQL 5.1. </remark> <para> @@ -4348,7 +4331,7 @@ non-transactional table, abort the statement if the value occurs in a single-row statement or the first row of a multiple-row statement. More detail is given later in this - section. (Implemented in MySQL 5.0.2) + section. </para> </listitem> @@ -4372,7 +4355,7 @@ want if you are using a non-transactional storage engine, because data changes made prior to the error are not be rolled back, resulting in a <quote>partially done</quote> - update. (Added in MySQL 5.0.2) + update. </para> </listitem> @@ -4418,14 +4401,12 @@ </para> <para> - This mode is implemented in MySQL 5.0.2. Before 5.0.2, - this was the default MySQL date-handling mode. As of - 5.0.2, enabling strict mode causes the server to require - that month and day values be legal, and not merely in the - range 1 to 12 and 1 to 31, respectively. For example, - <literal>'2004-04-31'</literal> is legal with strict mode - disabled, but illegal with strict mode enabled. To allow - such dates in strict mode, enable + In MySQL ¤t-series;, enabling strict mode causes the + server to require that month and day values be legal, and + not merely in the range 1 to 12 and 1 to 31, respectively. + For example, <literal>'2004-04-31'</literal> is legal with + strict mode disabled, but illegal with strict mode + enabled. To allow such dates in strict mode, enable <literal>ALLOW_INVALID_DATES</literal> as well. </para> </listitem> @@ -4472,8 +4453,7 @@ zero. If used in <literal>INSERT IGNORE</literal> or <literal>UPDATE IGNORE</literal>, MySQL generates a warning for divisions by zero, but the result of the - operation is <literal>NULL</literal>. (Implmented in MySQL - 5.0.2) + operation is <literal>NULL</literal>. </para> </listitem> @@ -4487,15 +4467,14 @@ </para> <para> - From MySQL 5.0.2 on, the <literal>NOT</literal> operator - precedence is handled so that expressions such as + In MySQL ¤t-series;, the <literal>NOT</literal> + operator precedence is handled so that expressions such as <literal>NOT a BETWEEN b AND c</literal> are parsed as - <literal>NOT (a BETWEEN b AND c)</literal>. Before MySQL - 5.0.2, the expression is parsed as <literal>(NOT a) - BETWEEN b AND c</literal>. The old higher-precedence - behavior can be obtained by enabling the - <literal>HIGH_NOT_PRECEDENCE</literal> SQL mode. (Added in - MySQL 5.0.2) + <literal>NOT (a BETWEEN b AND c)</literal>. In some older + versions of MySQL, the expression was parsed as + <literal>(NOT a) BETWEEN b AND c</literal>. The old + higher-precedence behavior can be obtained by enabling the + <literal>HIGH_NOT_PRECEDENCE</literal> SQL mode. </para> <programlisting> @@ -4547,7 +4526,7 @@ <para> Prevent <literal>GRANT</literal> from automatically creating new users if it would otherwise do so, unless a - password also is specified. (Added in MySQL 5.0.2) + password also is specified. </para> </listitem> @@ -4603,7 +4582,6 @@ (‘<literal>\</literal>’) as an escape character within strings. With this mode enabled, backslash becomes any ordinary character like any other. - (Implemented in MySQL 5.0.1) </para> </listitem> @@ -4716,7 +4694,7 @@ <literal>'0000-00-00'</literal> as a valid date. You can still insert zero dates with the <literal>IGNORE</literal> option. When not in strict mode, the date is accepted but - a warning is generated. (Added in MySQL 5.0.2) + a warning is generated. </para> </listitem> @@ -4734,8 +4712,7 @@ part is 0. If used with the <literal>IGNORE</literal> option, we insert a <literal>'0000-00-00'</literal> date for any such date. When not in strict mode, the date is - accepted but a warning is generated. (Added in MySQL - 5.0.2) + accepted but a warning is generated. </para> </listitem> @@ -4797,8 +4774,7 @@ <para> Enable strict mode for all storage engines. Invalid data - values are rejected. Additional detail follows. (Added in - MySQL 5.0.2) + values are rejected. Additional detail follows. </para> </listitem> @@ -4814,7 +4790,7 @@ <para> Enable strict mode for transactional storage engines, and when possible for non-transactional storage engines. - Additional details follow. (Implemented in MySQL 5.0.2) + Additional details follow. </para> </listitem> @@ -4922,12 +4898,11 @@ </para> <para> - Equivalent to <literal>REAL_AS_FLOAT</literal>, + In MySQL ¤t-series;, this is equivalent to + <literal>REAL_AS_FLOAT</literal>, <literal>PIPES_AS_CONCAT</literal>, <literal>ANSI_QUOTES</literal>, - <literal>IGNORE_SPACE</literal>. Before MySQL 5.0.3, - <literal>ANSI</literal> also includes - <literal>ONLY_FULL_GROUP_BY</literal>. See + <literal>IGNORE_SPACE</literal>. See <xref linkend="ansi-mode"/>. </para> </listitem> @@ -5234,232 +5209,229 @@ <programlisting> mysql> <userinput>SHOW VARIABLES;</userinput> -+---------------------------------+---------------------------------------------------------+ -| Variable_name | Value | -+---------------------------------+---------------------------------------------------------+ -| auto_increment_increment | 1 | -| auto_increment_offset | 1 | -| automatic_sp_privileges | ON | -| back_log | 50 | -| basedir | / | -| bdb_cache_size | 8388600 | -| bdb_home | /var/lib/mysql/ | -| bdb_log_buffer_size | 32768 | -| bdb_logdir | | -| bdb_max_lock | 10000 | -| bdb_shared_data | OFF | -| bdb_tmpdir | /tmp/ | -| binlog_cache_size | 32768 | -| bulk_insert_buffer_size | 8388608 | -| character_set_client | latin1 | -| character_set_connection | latin1 | -| character_set_database | latin1 | -| character_set_results | latin1 | -| character_set_server | latin1 | -| character_set_system | utf8 | -| character_sets_dir | /usr/share/mysql/charsets/ | -| collation_connection | latin1_swedish_ci | -| collation_database | latin1_swedish_ci | -| collation_server | latin1_swedish_ci | -| completion_type | 0 | -| concurrent_insert | 1 | -| connect_timeout | 5 | -| datadir | /var/lib/mysql/ | -| date_format | %Y-%m-%d | -| datetime_format | %Y-%m-%d %H:%i:%s | -| default_week_format | 0 | -| delay_key_write | ON | -| delayed_insert_limit | 100 | -| delayed_insert_timeout | 300 | -| delayed_queue_size | 1000 | -| div_precision_increment | 4 | -| engine_condition_pushdown | OFF | -| expire_logs_days | 0 | -| flush | OFF | -| flush_time | 0 | -| ft_boolean_syntax | + -><()~*:""&| | -| ft_max_word_len | 84 | -| ft_min_word_len | 4 | -| ft_query_expansion_limit | 20 | -| ft_stopword_file | (built-in) | -| group_concat_max_len | 1024 | -| have_archive | NO | -| have_bdb | YES | -| have_blackhole_engine | YES | -| have_compress | YES | -| have_crypt | YES | -| have_csv | YES | -| have_example_engine | YES | -| have_federated_engine | YES | -| have_geometry | YES | -| have_innodb | YES | -| have_isam | NO | -| have_ndbcluster | DISABLED | -| have_openssl | NO | -| have_query_cache | YES | -| have_raid | NO | -| have_rtree_keys | YES | -| have_symlink | YES | -| init_connect | | -| init_file | | -| init_slave | | -| innodb_additional_mem_pool_size | 1048576 | -| innodb_autoextend_increment | 8 | -| innodb_buffer_pool_awe_mem_mb | 0 | -| innodb_buffer_pool_size | 8388608 | -| innodb_checksums | ON | -| innodb_concurrency_tickets | 500 | -| innodb_data_file_path | ibdata1:10M:autoextend | -| innodb_data_home_dir | | -| innodb_doublewrite | ON | -| innodb_fast_shutdown | 1 | -| innodb_file_io_threads | 4 | -| innodb_file_per_table | OFF | -| innodb_flush_log_at_trx_commit | 1 | -| innodb_flush_method | | -| innodb_force_recovery | 0 | -| innodb_lock_wait_timeout | 50 | -| innodb_locks_unsafe_for_binlog | OFF | -| innodb_log_arch_dir | | -| innodb_log_archive | OFF | -| innodb_log_buffer_size | 1048576 | -| innodb_log_file_size | 5242880 | -| innodb_log_files_in_group | 2 | -| innodb_log_group_home_dir | ./ | -| innodb_max_dirty_pages_pct | 90 | -| innodb_max_purge_lag | 0 | -| innodb_mirrored_log_groups | 1 | -| innodb_open_files | 300 | -| innodb_support_xa | ON | -| innodb_sync_spin_loops | 20 | -| innodb_table_locks | ON | -| innodb_thread_concurrency | 8 | -| innodb_thread_sleep_delay | 10000 | -| interactive_timeout | 28800 | -| join_buffer_size | 131072 | -| key_buffer_size | 8388600 | -| key_cache_age_threshold | 300 | -| key_cache_block_size | 1024 | -| key_cache_division_limit | 100 | -| language | /usr/share/mysql/english/ | -| large_files_support | ON | -| large_pages | OFF | -| large_page_size | 0 | -| license | GPL | -| local_infile | ON | -| locked_in_memory | OFF | -| log | OFF | -| log_bin | OFF | -| log_bin_trust_routine_creators | OFF | -| log_error | | -| log_slave_updates | OFF | -| log_slow_queries | OFF | -| log_warnings | 1 | -| long_query_time | 10 | -| low_priority_updates | OFF | -| lower_case_file_system | OFF | -| lower_case_table_names | 0 | -| max_allowed_packet | 1048576 | -| max_binlog_cache_size | 4294967295 | -| max_binlog_size | 1073741824 | -| max_connect_errors | 10 | -| max_connections | 100 | -| max_delayed_threads | 20 | -| max_error_count | 64 | -| max_heap_table_size | 16777216 | -| max_insert_delayed_threads | 20 | -| max_join_size | 4294967295 | -| max_length_for_sort_data | 1024 | -| max_relay_log_size | 0 | -| max_seeks_for_key | 4294967295 | -| max_sort_length | 1024 | -| max_tmp_tables | 32 | -| max_user_connections | 0 | -| max_write_lock_count | 4294967295 | -| multi_range_count | 256 | -| myisam_data_pointer_size | 6 | -| myisam_max_sort_file_size | 2147483647 | -| myisam_recover_options | OFF | -| myisam_repair_threads | 1 | -| myisam_sort_buffer_size | 8388608 | -| engine_condition_pushdown | OFF | -| ndb_autoincrement_prefetch_sz | 32 | -| ndb_force_send | ON | -| ndb_use_exact_count | ON | -| ndb_use_transactions | ON | -| ndb_cache_check_time | 0 | -| net_buffer_length | 16384 | -| net_read_timeout | 30 | -| net_retry_count | 10 | -| net_write_timeout | 60 | -| new | OFF | -| old_passwords | OFF | -| open_files_limit | 1024 | -| optimizer_prune_level | 1 | -| optimizer_search_depth | 62 | -| pid_file | /var/lib/mysql/gigan.pid | -| port | 3306 | -| preload_buffer_size | 32768 | -| protocol_version | 10 | -| query_alloc_block_size | 8192 | -| query_cache_limit | 1048576 | -| query_cache_min_res_unit | 4096 | -| query_cache_size | 0 | -| query_cache_type | ON | -| query_cache_wlock_invalidate | OFF | -| query_prealloc_size | 8192 | -| range_alloc_block_size | 2048 | -| read_buffer_size | 131072 | -| read_only | OFF | -| read_rnd_buffer_size | 262144 | -| relay_log_purge | ON | -| relay_log_space_limit | 0 | -| rpl_recovery_rank | 0 | -| secure_auth | OFF | -| server_id | 0 | -| skip_external_locking | ON | -| skip_networking | OFF | -| skip_show_database | OFF | -| slave_compressed_protocol | OFF | -| slave_load_tmpdir | /tmp/ | -| slave_net_timeout | 3600 | -| slave_skip_errors | OFF | -| slave_transaction_retries | 10 | -| slow_launch_time | 2 | -| socket | /var/lib/mysql/mysql.sock | -| sort_buffer_size | 2097144 | -| sql_mode | | -| storage_engine | MyISAM | -| sql_notes | OFF | -| sql_warnings | OFF | -| sync_binlog | 0 | -| sync_replication | 0 | -| sync_replication_slave_id | 0 | -| sync_replication_timeout | 10 | -| sync_frm | ON | -| system_time_zone | EST | -| table_cache | 64 | -| table_type | MyISAM | -| thread_cache_size | 0 | -| thread_stack | 196608 | -| time_format | %H:%i:%s | -| time_zone | SYSTEM | -| timed_mutexes | OFF | -| tmp_table_size | 33554432 | -| tmpdir | | -| transaction_alloc_block_size | 8192 | -| transaction_prealloc_size | 4096 | -| tx_isolation | REPEATABLE-READ | -| updatable_views_with_limit | YES | -| version | 5.0.7-beta-Max | -| version_bdb | Sleepycat Software: Berkeley DB 4.1.24: (June 11, 2005) | -| version_comment | MySQL Community Edition - Max (GPL) | -| version_compile_machine | i686 | -| version_compile_os | pc-linux-gnu | -| wait_timeout | 28800 | -+---------------------------------+---------------------------------------------------------+ -219 rows in set (0.00 sec) - ++---------------------------------+-------------------------------------------+ +| Variable_name | Value | ++---------------------------------+-------------------------------------------+ +| auto_increment_increment | 1 | +| auto_increment_offset | 1 | +| automatic_sp_privileges | ON | +| back_log | 50 | +| basedir | /home/jon/bin/mysql/ | +| binlog_cache_size | 32768 | +| bulk_insert_buffer_size | 8388608 | +| character_set_client | latin1 | +| character_set_connection | latin1 | +| character_set_database | latin1 | +| character_set_results | latin1 | +| character_set_server | latin1 | +| character_set_system | utf8 | +| character_sets_dir | /home/jon/bin/mysql/share/mysql/charsets/ | +| collation_connection | latin1_swedish_ci | +| collation_database | latin1_swedish_ci | +| collation_server | latin1_swedish_ci | +| completion_type | 0 | +| concurrent_insert | 1 | +| connect_timeout | 5 | +| datadir | /home/jon/bin/mysql/var/ | +| date_format | %Y-%m-%d | +| datetime_format | %Y-%m-%d %H:%i:%s | +| default_week_format | 0 | +| delay_key_write | ON | +| delayed_insert_limit | 100 | +| delayed_insert_timeout | 300 | +| delayed_queue_size | 1000 | +| div_precision_increment | 4 | +| engine_condition_pushdown | OFF | +| expire_logs_days | 0 | +| flush | OFF | +| flush_time | 0 | +| ft_boolean_syntax | + -><()~*:""&| | +| ft_max_word_len | 84 | +| ft_min_word_len | 4 | +| ft_query_expansion_limit | 20 | +| ft_stopword_file | (built-in) | +| group_concat_max_len | 1024 | +| have_archive | YES | +| have_bdb | NO | +| have_blackhole_engine | YES | +| have_compress | YES | +| have_crypt | YES | +| have_csv | YES | +| have_example_engine | NO | +| have_federated_engine | NO | +| have_geometry | YES | +| have_innodb | YES | +| have_isam | NO | +| have_ndbcluster | DISABLED | +| have_openssl | NO | +| have_partition_engine | YES | +| have_query_cache | YES | +| have_raid | NO | +| have_rtree_keys | YES | +| have_symlink | YES | +| init_connect | | +| init_file | | +| init_slave | | +| innodb_additional_mem_pool_size | 1048576 | +| innodb_autoextend_increment | 8 | +| innodb_buffer_pool_awe_mem_mb | 0 | +| innodb_buffer_pool_size | 8388608 | +| innodb_checksums | ON | +| innodb_commit_concurrency | 0 | +| innodb_concurrency_tickets | 500 | +| innodb_data_file_path | ibdata1:10M:autoextend | +| innodb_data_home_dir | | +| innodb_doublewrite | ON | +| innodb_fast_shutdown | 1 | +| innodb_file_io_threads | 4 | +| innodb_file_per_table | OFF | +| innodb_flush_log_at_trx_commit | 1 | +| innodb_flush_method | | +| innodb_force_recovery | 0 | +| innodb_lock_wait_timeout | 50 | +| innodb_locks_unsafe_for_binlog | OFF | +| innodb_log_arch_dir | | +| innodb_log_archive | OFF | +| innodb_log_buffer_size | 1048576 | +| innodb_log_file_size | 5242880 | +| innodb_log_files_in_group | 2 | +| innodb_log_group_home_dir | ./ | +| innodb_max_dirty_pages_pct | 90 | +| innodb_max_purge_lag | 0 | +| innodb_mirrored_log_groups | 1 | +| innodb_open_files | 300 | +| innodb_support_xa | ON | +| innodb_sync_spin_loops | 20 | +| innodb_table_locks | ON | +| innodb_thread_concurrency | 20 | +| innodb_thread_sleep_delay | 10000 | +| interactive_timeout | 28800 | +| join_buffer_size | 131072 | +| key_buffer_size | 8388600 | +| key_cache_age_threshold | 300 | +| key_cache_block_size | 1024 | +| key_cache_division_limit | 100 | +| language | /home/jon/bin/mysql/share/mysql/english/ | +| large_files_support | ON | +| large_page_size | 0 | +| large_pages | OFF | +| license | GPL | +| local_infile | ON | +| locked_in_memory | OFF | +| log | ON | +| log_bin | ON | +| log_bin_trust_routine_creators | OFF | +| log_error | /home/jon/bin/mysql/var/master1.err | +| log_slave_updates | OFF | +| log_slow_queries | OFF | +| log_warnings | 1 | +| long_query_time | 10 | +| low_priority_updates | OFF | +| lower_case_file_system | OFF | +| lower_case_table_names | 0 | +| max_allowed_packet | 1048576 | +| max_binlog_cache_size | 4294967295 | +| max_binlog_size | 1073741824 | +| max_connect_errors | 10 | +| max_connections | 100 | +| max_delayed_threads | 20 | +| max_error_count | 64 | +| max_heap_table_size | 16777216 | +| max_insert_delayed_threads | 20 | +| max_join_size | 4294967295 | +| max_length_for_sort_data | 1024 | +| max_relay_log_size | 0 | +| max_seeks_for_key | 4294967295 | +| max_sort_length | 1024 | +| max_tmp_tables | 32 | +| max_user_connections | 0 | +| max_write_lock_count | 4294967295 | +| multi_range_count | 256 | +| myisam_data_pointer_size | 6 | +| myisam_max_sort_file_size | 2147483647 | +| myisam_recover_options | OFF | +| myisam_repair_threads | 1 | +| myisam_sort_buffer_size | 8388608 | +| ndb_autoincrement_prefetch_sz | 32 | +| ndb_cache_check_time | 0 | +| ndb_force_send | ON | +| ndb_index_stat_cache_entries | 32 | +| ndb_index_stat_enable | ON | +| ndb_index_stat_update_freq | 20 | +| ndb_use_exact_count | ON | +| ndb_use_transactions | ON | +| net_buffer_length | 16384 | +| net_read_timeout | 30 | +| net_retry_count | 10 | +| net_write_timeout | 60 | +| new | OFF | +| old_alter_table | OFF | +| old_passwords | OFF | +| open_files_limit | 1024 | +| optimizer_prune_level | 1 | +| optimizer_search_depth | 62 | +| pid_file | /home/jon/bin/mysql/var/hostname.pid1 | +| port | 3306 | +| preload_buffer_size | 32768 | +| protocol_version | 10 | +| query_alloc_block_size | 8192 | +| query_cache_limit | 1048576 | +| query_cache_min_res_unit | 4096 | +| query_cache_size | 0 | +| query_cache_type | ON | +| query_cache_wlock_invalidate | OFF | +| query_prealloc_size | 8192 | +| range_alloc_block_size | 2048 | +| read_buffer_size | 131072 | +| read_only | OFF | +| read_rnd_buffer_size | 262144 | +| relay_log_purge | ON | +| relay_log_space_limit | 0 | +| rpl_recovery_rank | 0 | +| secure_auth | OFF | +| server_id | 1 | +| skip_external_locking | ON | +| skip_networking | OFF | +| skip_show_database | OFF | +| slave_compressed_protocol | OFF | +| slave_load_tmpdir | /tmp/ | +| slave_net_timeout | 3600 | +| slave_skip_errors | OFF | +| slave_transaction_retries | 10 | +| slow_launch_time | 2 | +| socket | /tmp/mysql.sock | +| sort_buffer_size | 2097144 | +| sql_mode | | +| sql_notes | ON | +| sql_warnings | ON | +| storage_engine | MyISAM | +| sync_binlog | 0 | +| sync_frm | ON | +| sync_replication | 0 | +| sync_replication_slave_id | 0 | +| sync_replication_timeout | 10 | +| system_time_zone | EST | +| table_cache | 64 | +| table_lock_wait_timeout | 50 | +| table_type | MyISAM | +| thread_cache_size | 0 | +| thread_stack | 196608 | +| time_format | %H:%i:%s | +| time_zone | SYSTEM | +| timed_mutexes | OFF | +| tmp_table_size | 33554432 | +| tmpdir | | +| transaction_alloc_block_size | 8192 | +| transaction_prealloc_size | 4096 | +| tx_isolation | REPEATABLE-READ | +| updatable_views_with_limit | YES | +| version | 5.1.2-alpha-log | +| version_comment | Source distribution | +| version_compile_machine | i686 | +| version_compile_os | suse-linux | +| wait_timeout | 28800 | ++---------------------------------+-------------------------------------------+ +218 rows in set (0.03 sec) </programlisting> <indexterm> @@ -5741,9 +5713,9 @@ </para> <para> - The <literal>auto_increment_increment</literal> variable - was added in MySQL 5.0.2. Its default value is 1. See - <xref linkend="replication"/>. + The default value of + <literal>auto_increment_increment</literal> is 1. See + <xref linkend="replication"/>. </para> </listitem> @@ -5753,9 +5725,9 @@ </para> <para> - This variable was introduced in MySQL 5.0.2. Its default - value is 1. For particulars, see the description for - <literal>auto_increment_increment</literal>. + This variable has a default value of 1. For particulars, + see the description for + <literal>auto_increment_increment</literal>. </para> </listitem> @@ -5913,13 +5885,12 @@ The size of the cache to hold the SQL statements for the binary log during a transaction. A binary log cache is allocated for each client if the server supports any - transactional storage engines and, starting from MySQL - 4.1.2, if the server has binary log enabled - (<option>--log-bin</option> option). If you often use big, - multiple-statement transactions, you can increase this to - get more performance. The + transactional storage engines and if the server has binary + log enabled (<option>--log-bin</option> option). If you + often use big, multiple-statement transactions, you can + increase this to get more performance. The <literal>Binlog_cache_use</literal> and - <literal>Binlog_cache_disk_use</literal> status variables + <literal>Binlog_cache_disk_use</literal> status variables can be useful for tuning the size of this variable. See <xref linkend="binary-log"/>. </para> @@ -6100,10 +6071,6 @@ </listitem> </itemizedlist> - - <para> - This variable was added in MySQL 5.0.3 - </para> </listitem> <listitem> @@ -6122,8 +6089,8 @@ </para> <para> - In MySQL 5.0.6 this variable was changed to an integer - that takes 3 values: + In MySQL ¤t-series; this variable is an integer that + takes 3 values: </para> <informaltable> @@ -6141,16 +6108,17 @@ </row> <row> <entry>1</entry> - <entry>(Default) Enables concurrent insert for MyISAM tables that doesn't have - holes</entry> + <entry>(Default) Enables concurrent insert for + MyISAM tables that don't have holes</entry> </row> <row> <entry>2</entry> - <entry>Enables concurrent inserts for all MyISAM tables. If table has a hole - and is in use by another thread the new row will - be inserted at end of table. If table is not in - use then MySQL will do a normal read lock and - insert the new row into the hole.</entry> + <entry>Enables concurrent inserts for all MyISAM + tables. If table has a hole and is in use by + another thread the new row will be inserted at end + of table. If table is not in use then MySQL will + do a normal read lock and insert the new row into + the hole.</entry> </row> </tbody> </tgroup> @@ -6346,10 +6314,6 @@ | 0.142857142857 | +----------------+ </programlisting> - - <para> - This variable was added in MySQL 5.0.6. - </para> </listitem> <listitem> @@ -6653,8 +6617,7 @@ <para> <literal>YES</literal> if <command>mysqld</command> supports <literal>FEDERATED</literal> tables, - <literal>NO</literal> if not. This variable was added in - MySQL 5.0.3. + <literal>NO</literal> if not. </para> </listitem> @@ -6706,6 +6669,17 @@ <option>--skip-ndbcluster</option> is used. </para> </listitem> + + <listitem> + <para> + <literal>have_partition_engine</literal> + </para> + + <para> + <literal>YES</literal> if <command>mysqld</command> + supports partitioning. Added in MySQL 5.1.1. + </para> + </listitem> <listitem> <para> @@ -7050,8 +7024,7 @@ </para> <para> - Indicates whether large page support is enabled. This - variable was added in MySQL 5.0.3. + Indicates whether large page support is enabled. </para> </listitem> @@ -7139,10 +7112,6 @@ <para> See <xref linkend="stored-procedure-logging"/>. </para> - - <para> - This variable was added in MySQL 5.0.6. - </para> </listitem> <listitem> @@ -7554,13 +7523,12 @@ </para> <para> - Before MySQL 5.0.3, this variable has only global scope. - Beginning with MySQL 5.0.3, it also has a read-only - session scope. The session variable has the same value as - the global variable unless the current account has a - non-zero <literal>MAX_USER_CONNECTIONS</literal> resource - limit. In that case, the session value reflects the - account limit. + In MySQL ¤t-series; this variable has both a global + scope and a (read-only) session scope. The session + variable has the same value as the global variable unless + the current account has a non-zero + <literal>MAX_USER_CONNECTIONS</literal> resource limit. In + that case, the session value reflects the account limit. </para> </listitem> @@ -7585,9 +7553,8 @@ <literal>CREATE TABLE</literal> for <literal>MyISAM</literal> tables when no <literal>MAX_ROWS</literal> option is specified. This - variable cannot be less than 2 or larger than 7. The - default value is 6 (4 before MySQL 5.0.6). This variable - was added in MySQL 4.1.2. See + variable cannot be less than 2 or larger than 7. In MySQL + ¤t-series;, the default value is 6. See <xref linkend="full-table"/>. </para> </listitem> @@ -7599,18 +7566,8 @@ </para> <para> - If the temporary file used for fast - <literal>MyISAM</literal> index creation would be larger - than using the key cache by the amount specified here, - prefer the key cache method. This is mainly used to force - long character keys in large tables to use the slower key - cache method to create the index. The value is given in - bytes. - </para> - - <para> - <emphasis role="bold">Note</emphasis>: This variable was - removed in MySQL 5.0.6. + <emphasis role="bold">Note</emphasis>: This variable is no + longer supported in MySQL ¤t-series;. </para> </listitem> @@ -7696,12 +7653,6 @@ execution, as described in <xref linkend="myisam-index-statistics"/>. </para> - - <para> - This variable was added in MySQL 4.1.15/5.0.14. For older - versions, the statistics collection method is equivalent - to <literal>nulls_equal</literal>. - </para> </listitem> <listitem> @@ -7718,7 +7669,7 @@ <literal>NDBCLUSTER</literal>. This engine needs to send the range requests to all nodes, and sending many of those requests at once reduces the communication costs - significantly. This variable was added in MySQL 5.0.3. + significantly. </para> </listitem> @@ -7864,8 +7815,7 @@ search space. A value of 0 disables heuristics so that the optimizer performs an exhaustive search. A value of 1 causes the optimizer to prune plans based on the number of - rows retrieved by intermediate plans. This variable was - added in MySQL 5.0.1. + rows retrieved by intermediate plans. </para> </listitem> @@ -7885,8 +7835,7 @@ picks a reasonable value. If set to the maximum number of tables used in a query plus 2, the optimizer switches to the algorithm used in MySQL 5.0.0 (and previous versions) - for performing searches. This variable was added in MySQL - 5.0.1. + for performing searches. </para> </listitem> @@ -8149,26 +8098,6 @@ </para> </listitem> -<!-- -<remark role="todo">Cut this?</remark> - <listitem><para> - <literal>safe_show_database</literal> - </para> - - <para> - Don't show databases for which the user has no database or table - privileges. This can improve security if you're concerned about - people being able to see what databases other users have. See also - <literal>skip_show_database</literal>. - </para> - - <para> - This variable was removed in MySQL 4.0.5. Instead, use the - <literal>SHOW DATABASES</literal> privilege to control access by - MySQL accounts to database names. - </para></listitem> ---> - <listitem> <para> <literal>secure_auth</literal> @@ -8352,10 +8281,8 @@ <literal>TransactionInactiveTimeout</literal>, it automatically retries <literal>slave_transaction_retries</literal> times before - stopping with an error. The default in MySQL 4.1 is 0. You - must explicitly set the value greater than 0 to enable the - <quote>retry</quote> behavior, which is probably a good - idea. In MySQL 5.0.3 or newer, the default is 10. + stopping with an error. In MySQL ¤t-series;, the + default value is 10. </para> </listitem> @@ -8382,10 +8309,6 @@ <filename>/var/lib/mysql/mysql.sock</filename>. </para> - <remark role="todo"> - Check this. Doesn't seem to be defined in 5.0.7-nt? - </remark> - <para> <emphasis>Windows</emphasis>: The name of the named pipe used for local client connections. Defaults to @@ -8736,10 +8659,6 @@ </listitem> </itemizedlist> - - <para> - This variable was added in MySQL 5.0.2. - </para> </listitem> <listitem> @@ -9732,7 +9651,7 @@ <para> The <literal>Com_stmt_<replaceable>xxx</replaceable></literal> - status variables were added in 5.0.8: + status variables are as follows: </para> <itemizedlist> @@ -10058,7 +9977,6 @@ <para> The number of pages containing data (dirty or clean). - Added in MySQL 5.0.2. </para> </listitem> @@ -10068,7 +9986,7 @@ </para> <para> - The number of pages currently dirty. Added in MySQL 5.0.2. + The number of pages currently dirty. </para> </listitem> @@ -10079,7 +9997,7 @@ <para> The number of buffer pool pages that have been requested - to be flushed. Added in MySQL 5.0.2. + to be flushed. </para> </listitem> @@ -10089,7 +10007,7 @@ </para> <para> - The number of free pages. Added in MySQL 5.0.2. + The number of free pages. </para> </listitem> @@ -10102,7 +10020,7 @@ The number of latched pages in <literal>InnoDB</literal> buffer pool. These are pages currently being read or written or that cannot be flushed or removed for some - other reason. Added in MySQL 5.0.2. + other reason. </para> </listitem> @@ -10117,8 +10035,7 @@ adaptive hash index. This value can also be calculated as <literal>Innodb_buffer_pool_pages_total</literal> - <literal>Innodb_buffer_pool_pages_free</literal> - - <literal>Innodb_buffer_pool_pages_data</literal>. Added in - MySQL 5.0.2. + <literal>Innodb_buffer_pool_pages_data</literal>. </para> </listitem> @@ -10128,7 +10045,7 @@ </para> <para> - Total size of buffer pool, in pages. Added in MySQL 5.0.2. + Total size of buffer pool, in pages. </para> </listitem> @@ -10141,7 +10058,7 @@ The number of <quote>random</quote> read-aheads <literal>InnoDB</literal> initiated. This happens when a query is to scan a large portion of a table but in random - order. Added in MySQL 5.0.2. + order. </para> </listitem> @@ -10154,7 +10071,7 @@ The number of sequential read-aheads <literal>InnoDB</literal> initiated. This happens when <literal>InnoDB</literal> does a sequential full table - scan. Added in MySQL 5.0.2. + scan. </para> </listitem> @@ -10165,7 +10082,7 @@ <para> The number of logical read requests - <literal>InnoDB</literal> has done. Added in MySQL 5.0.2. + <literal>InnoDB</literal> has done. </para> </listitem> @@ -10181,7 +10098,7 @@ <para> The number of logical reads that <literal>InnoDB</literal> could not satisfy from the buffer pool and had to do a - single-page read. Added in MySQL 5.0.2. + single-page read. </para> </listitem> @@ -10201,7 +10118,7 @@ then it is also necessary to wait for pages to be flushed first. This counter counts instances of these waits. If the buffer pool size has been set properly, this value - should be small. Added in MySQL 5.0.2. + should be small. </para> </listitem> @@ -10212,7 +10129,7 @@ <para> The number writes done to the <literal>InnoDB</literal> - buffer pool. Added in MySQL 5.0.2. + buffer pool. </para> </listitem> @@ -10223,7 +10140,7 @@ <para> The number of <literal>fsync()</literal> operations so - far. Added in MySQL 5.0.2. + far. </para> </listitem> @@ -10234,7 +10151,7 @@ <para> The current number of pending <literal>fsync()</literal> - operations. Added in MySQL 5.0.2. + operations. </para> </listitem> @@ -10244,7 +10161,7 @@ </para> <para> - The current number of pending reads. Added in MySQL 5.0.2. + The current number of pending reads. </para> </listitem> @@ -10254,8 +10171,7 @@ </para> <para> - The current number of pending writes. Added in MySQL - 5.0.2. + The current number of pending writes. </para> </listitem> @@ -10269,8 +10185,7 @@ </remark> <para> - The amount of data read so far, in bytes. Added in MySQL - 5.0.2. + The amount of data read so far, in bytes. </para> </listitem> @@ -10280,7 +10195,7 @@ </para> <para> - The total number of data reads. Added in MySQL 5.0.2. + The total number of data reads. </para> </listitem> @@ -10290,7 +10205,7 @@ </para> <para> - The total number of data writes. Added in MySQL 5.0.2. + The total number of data writes. </para> </listitem> @@ -10304,8 +10219,7 @@ </remark> <para> - The amount of data written so far, in bytes. Added in - MySQL 5.0.2. + The amount of data written so far, in bytes. </para> </listitem> @@ -10318,7 +10232,7 @@ <para> The number of doublewrite operations that have been performed and the number of pages that have been written - for this purpose. Added in MySQL 5.0.2. See + for this purpose. See <xref linkend="innodb-disk-io"/>. </para> </listitem> @@ -10331,7 +10245,7 @@ <para> The number of waits we had because log buffer was too small and we had to wait for it to be flushed before - continuing. Added in MySQL 5.0.2. + continuing. </para> </listitem> @@ -10341,7 +10255,7 @@ </para> <para> - The number of log write requests. Added in MySQL 5.0.2. + The number of log write requests. </para> </listitem> @@ -10351,8 +10265,7 @@ </para> <para> - The number of physical writes to the log file. Added in - MySQL 5.0.2. + The number of physical writes to the log file. </para> </listitem> @@ -10363,7 +10276,7 @@ <para> The number of <literal>fsync()</literal> writes done to - the log file. Added in MySQL 5.0.2. + the log file. </para> </listitem> @@ -10374,7 +10287,7 @@ <para> The number of pending log file <literal>fsync()</literal> - operations. Added in MySQL 5.0.2. + operations. </para> </listitem> @@ -10384,7 +10297,7 @@ </para> <para> - Pending log file writes. Added in MySQL 5.0.2. + Pending log file writes. </para> </listitem> @@ -10394,8 +10307,7 @@ </para> <para> - The number of bytes written to the log file. Added in - MySQL 5.0.2. + The number of bytes written to the log file. </para> </listitem> @@ -10407,8 +10319,7 @@ <para> The compiled-in <literal>InnoDB</literal> page size (default 16KB). Many values are counted in pages; the page - size allows them to be easily converted to bytes. Added in - MySQL 5.0.2. + size allows them to be easily converted to bytes. </para> </listitem> @@ -10418,7 +10329,7 @@ </para> <para> - The number of pages created. Added in MySQL 5.0.2. + The number of pages created. </para> </listitem> @@ -10428,7 +10339,7 @@ </para> <para> - The number of pages read. Added in MySQL 5.0.2. + The number of pages read. </para> </listitem> @@ -10438,7 +10349,7 @@ </para> <para> - The number of pages written. Added in MySQL 5.0.2. + The number of pages written. </para> </listitem> @@ -10448,8 +10359,7 @@ </para> <para> - The number of row locks currently being waited for. Added - in MySQL 5.0.3. + The number of row locks currently being waited for. </para> </listitem> @@ -10460,7 +10370,7 @@ <para> The total time spent in acquiring row locks, in - milliseconds. Added in MySQL 5.0.3. + milliseconds. </para> </listitem> @@ -10471,7 +10381,6 @@ <para> The average time to acquire a row lock, in milliseconds. - Added in MySQL 5.0.3. </para> </listitem> @@ -10482,7 +10391,6 @@ <para> The maximum time to acquire a row lock, in milliseconds. - Added in MySQL 5.0.3. </para> </listitem> @@ -10492,8 +10400,7 @@ </para> <para> - The number of times a row lock had to be waited for. Added - in MySQL 5.0.3. + The number of times a row lock had to be waited for. </para> </listitem> @@ -10504,7 +10411,7 @@ <para> The number of rows deleted from <literal>InnoDB</literal> - tables. Added in MySQL 5.0.2. + tables. </para> </listitem> @@ -10515,7 +10422,7 @@ <para> The number of rows inserted into <literal>InnoDB</literal> - tables. Added in MySQL 5.0.2. + tables. </para> </listitem> @@ -10526,7 +10433,7 @@ <para> The number of rows read from <literal>InnoDB</literal> - tables. Added in MySQL 5.0.2. + tables. </para> </listitem> @@ -10537,7 +10444,7 @@ <para> The number of rows updated in <literal>InnoDB</literal> - tables. Added in MySQL 5.0.2. + tables. </para> </listitem> @@ -10631,12 +10538,9 @@ The total cost of the last compiled query as computed by the query optimizer. Useful for comparing the cost of different query plans for the same query. The default - value of 0 means that no query has been compiled yet. This - variable was added in MySQL 5.0.1, with a default value of - -1. In MySQL 5.0.7, the default was changed to 0; also in - version 5.0.7, the scope of - <literal>Last_query_cost</literal> was changed to session - rather than global. + value of 0 means that no query has been compiled yet. In + MySQL ¤t-series;, the default was changed to 0, and + <literal>Last_query_cost</literal> has session scope. </para> </listitem> @@ -10901,9 +10805,7 @@ <para> Total number of times since startup that the replication - slave SQL thread has retried transactions. For the MySQL - 5.0 series of releases, this variable was added in version - 5.0.4. + slave SQL thread has retried transactions. </para> </listitem> @@ -11361,10 +11263,9 @@ Each storage engine performs any actions necessary for tables that it manages. For example, MyISAM flushes any pending index writes for a table. InnoDB flushes its buffer pool to disk - (starting from 5.0.5: unless - <literal>innodb_fast_shutdown</literal> is 2), writes the - current LSN to the tablespace, and terminates its own internal - threads. + unless <literal>innodb_fast_shutdown</literal> is 2), writes + the current LSN to the tablespace, and terminates its own + internal threads. </para> </listitem> @@ -12017,8 +11918,7 @@ only UDFs that have at least one auxiliary symbol can be loaded. This prevents attempts at loading functions from shared object files other than those containing legitimate - UDFs. For MySQL 5.0, this option was added in MySQL 5.0.3. - See <xref linkend="udf-security"/>. + UDFs. See <xref linkend="udf-security"/>. </para> </listitem> @@ -12699,24 +12599,6 @@ </informaltable> <para> - <literal>Execute_priv</literal> was present in MySQL 5.0.0, but - did not become operational until MySQL 5.0.3. - </para> - - <para> - The <literal>Create_view_priv</literal> and - <literal>Show_view_priv</literal> columns were added in MySQL - 5.0.1. - </para> - - <para> - The <literal>Create_routine_priv</literal>, - <literal>Alter_routine_priv</literal>, and - <literal>max_user_connections</literal> columns were added in - MySQL 5.0.3. - </para> - - <para> During the second stage of access control, the server performs request verification to make sure that each client has sufficient privileges for each request that it issues. In @@ -12848,13 +12730,12 @@ </informaltable> <para> - The <literal>procs_priv</literal> table exists as of MySQL - 5.0.3. The <literal>Routine_type</literal> column was added in - MySQL 5.0.6. It is an <literal>ENUM</literal> column with values - of <literal>'FUNCTION'</literal> or - <literal>'PROCEDURE'</literal> to indicate the type of routine - the row refers to. This column allows privileges to be granted - separately for a function and a procedure with the same name. + The <literal>Routine_type</literal> column is an + <literal>ENUM</literal> column with values of + <literal>'FUNCTION'</literal> or <literal>'PROCEDURE'</literal> + to indicate the type of routine the row refers to. This column + allows privileges to be granted separately for a function and a + procedure with the same name. </para> <para> @@ -13342,17 +13223,15 @@ </informaltable> <para> - <literal>CREATE VIEW</literal> and <literal>SHOW VIEW</literal> - were added in MySQL 5.0.1. <literal>CREATE USER</literal>, - <literal>CREATE ROUTINE</literal>, and <literal>ALTER - ROUTINE</literal> were added in MySQL 5.0.3. Although - <literal>EXECUTE</literal> was present in MySQL 5.0.0, it did - not become operational until MySQL 5.0.3. To use these + + To use the <literal>CREATE VIEW</literal>, <literal>SHOW + VIEW</literal>, <literal>CREATE ROUTINE</literal>, + <literal>ALTER ROUTINE</literal>, and <literal>EXECUTE</literal> privileges when upgrading from an earlier version of MySQL that - does not have them, you must upgrade your grant tables using the + does not have them, you must upgrade your grant tables using the <command>mysql_fix_privilege_tables</command> script provided - with the MySQL distribution. See - <xref linkend="upgrading-grant-tables"/>. + with the MySQL distribution. See <xref + linkend="upgrading-grant-tables"/>. </para> <para> @@ -15105,12 +14984,12 @@ <para> The <literal>PASSWORD()</literal> function is unnecessary when you specify a password using the - <literal>GRANT</literal> or (beginning with MySQL 5.0.2) - <literal>CREATE USER</literal> statements, or the - <command>mysqladmin password</command> command, all of which - automatically use <literal>PASSWORD()</literal> to encrypt - the password. See <xref linkend="passwords"/> and - <xref linkend="create-user"/>. + <literal>GRANT</literal> or <literal>CREATE USER</literal> + statements, or the <command>mysqladmin password</command> + command, all of which automatically use + <literal>PASSWORD()</literal> to encrypt the password. See + <xref linkend="passwords"/> and <xref + linkend="create-user"/>. </para> </listitem> @@ -16904,8 +16783,8 @@ </para> <para> - From MySQL 5.0.3 on, it is also possible to limit the number of - simultaneous connections to the server on a per-account basis. + It is also possible to limit the number of simultaneous + connections to the server on a per-account basis. </para> <para> @@ -17005,11 +16884,6 @@ all such cases, an appropriate error message is issued. </para> - <remark role="todo"> - this isn't correct for pre-5.0.3, where counting is per - user+actual host. - </remark> - <para> Resource counting is done per account, not per client. For example, if your account has a query limit of 50, you cannot @@ -17502,11 +17376,10 @@ <para> To use SSL connections between the MySQL server and client - programs, your system must be able to support OpenSSL and your - version of MySQL must be 4.0.0 or newer. If you're using a - MySQL version with built-in yaSSL support (as of version - 5.0.10), don't read this section, but rather - <xref linkend="secure-using-yassl"/>. + programs, your system must be able to support OpenSSL. If + you're using a MySQL version with built-in yaSSL support, + don't read this section, but rather <xref + linkend="secure-using-yassl"/>. </para> <para> @@ -19717,9 +19590,6 @@ <literal>myisam_stats_method</literal> in <xref linkend="server-system-variables"/> and <xref linkend="myisam-index-statistics"/>. - <literal>stats_method</literal> was added in MySQL - 4.1.15/5.0.14. For older versions, the statistics collection - method is equivalent to <literal>nulls_equal</literal>. </para> <para> @@ -20066,7 +19936,7 @@ parallel, using different threads. <remark role="todo"> - Is this still the case in 5.0? + Is this still the case in 5.1? </remark> <emphasis>This is alpha code. Use at your own @@ -20135,13 +20005,13 @@ <listitem> <para> - <option>--set-character-set=<replaceable>name</replaceable></option> + (<emphasis>OBSOLETE</emphasis>) + <option>--set-character-set=<replaceable>name</replaceable></option> </para> <para> - Change the character set used by the table indexes. This - option was replaced by <option>--set-collation</option> - in MySQL 5.0.3. + No longer used in MySQL ¤t-series;. See + <option>--set-collation</option>. </para> </listitem> @@ -20153,7 +20023,7 @@ <para> Change the collation used to sort table indexes. The character set name is implied by the first part of the - collation name. This option was added in MySQL 5.0.3. + collation name. </para> </listitem> @@ -21772,7 +21642,7 @@ </para> <remark role="todo"> - Still true in 5.0? + Still true in 5.1? </remark> <para> @@ -23441,8 +23311,8 @@ <option>--innodb-safe-binlog</option> option, which adds consistency between the content of <literal>InnoDB</literal> tables and the binary log. (Note: - <option>--innodb-safe-binlog</option> is unneeded as of MySQL - 5.0.3; it was made obsolete by the introduction of XA + <option>--innodb-safe-binlog</option> is unneeded as in MySQL + ¤t-series;; it was made obsolete by the introduction of XA transaction support.) </para> @@ -24069,9 +23939,10 @@ the <command>mysqld-nt</command> server from two different versions of MySQL that are installed at <filename>C:\mysql-4.1.8</filename> and - <filename>C:\mysql-5.0.7</filename>, respectively. (This might - be the case if you're running 4.1.8 as your production server, - but also want to conduct tests using 5.0.7.) + <filename>C:\mysql-¤t-version;</filename>, respectively. + (This might be the case if you're running 4.1.8 as your + production server, but also want to conduct tests using + ¤t-version;.) </para> <para> @@ -24153,11 +24024,11 @@ files. To do this, use a different service name for each server. Suppose that you want to run the 4.1.8 <command>mysqld-nt</command> using the service name of - <literal>mysqld1</literal> and the 5.0.7 + <literal>mysqld1</literal> and the ¤t-version; <command>mysqld-nt</command> using the service name <literal>mysqld2</literal>. In this case, you can use the <literal>[mysqld1]</literal> group for 4.1.8 and the - <literal>[mysqld2]</literal> group for 5.0.7. For example, + <literal>[mysqld2]</literal> group for ¤t-version;. For example, you can set up <filename>C:\my.cnf</filename> like this: </para> @@ -24171,7 +24042,7 @@ # options for mysqld2 service [mysqld2] -basedir = C:/mysql-5.0.7 +basedir = C:/mysql-¤t-version; port = 3308 enable-named-pipe socket = mypipe2 @@ -24185,7 +24056,7 @@ <programlisting> C:\> <userinput>C:\mysql-4.1.8\bin\mysqld-nt --install mysqld1</userinput> -C:\> <userinput>C:\mysql-5.0.7\bin\mysqld-nt --install mysqld2</userinput> +C:\> <userinput>C:\mysql-¤t-version;\bin\mysqld-nt --install mysqld2</userinput> </programlisting> <para> @@ -24236,14 +24107,13 @@ </programlisting> <para> - For the 5.0.7 <command>mysqld-nt</command>, create a file + For the ¤t-version; <command>mysqld-nt</command>, create a file <filename>C:\my-opts2.cnf</filename> that looks like this: </para> <programlisting> [mysqld] -basedir = C:/mysql-5.0.7 -port = 3308 +basedir = C:/mysql-¤t-version; port = 3308 enable-named-pipe socket = mypipe2 </programlisting> @@ -24256,7 +24126,7 @@ <programlisting> C:\> <userinput>C:\mysql-4.1.8\bin\mysqld-nt --install mysqld1</userinput> --defaults-file=C:\my-opts1.cnf -C:\> <userinput>C:\mysql-5.0.7\bin\mysqld-nt --install mysqld2</userinput> +C:\> <userinput>C:\mysql-¤t-version;\bin\mysqld-nt --install mysqld2</userinput> --defaults-file=C:\my-opts2.cnf </programlisting> @@ -24303,15 +24173,15 @@ <para> Assume that an existing 4.1.8 server is configured for the default TCP/IP port number (3306) and Unix socket file - (<filename>/tmp/mysql.sock</filename>). To configure a new 5.0.7 - server to have different operating parameters, use a - <command>configure</command> command something like this: + (<filename>/tmp/mysql.sock</filename>). To configure a new + ¤t-version; server to have different operating parameters, + use a <command>configure</command> command something like this: </para> <programlisting> shell> <userinput>./configure --with-tcp-port=<replaceable>port_number</replaceable> \</userinput> <userinput>--with-unix-socket-path=<replaceable>file_name</replaceable> \</userinput> - <userinput>--prefix=/usr/local/mysql-5.0.7</userinput> + <userinput>--prefix=/usr/local/mysql-¤t-version;</userinput> </programlisting> <para> @@ -24740,16 +24610,6 @@ <para> In MySQL ¤t-series;, queries generated by views are cached. - </para> - - <remark role="todo"> - Need xref to news-5-0-x? - </remark> - - <para> - Before MySQL 5.0, a query that began with a leading comment - could be cached, but could not be fetched from the cache. This - problem is fixed in MySQL 5.0. </para> <para> --- 1.6/refman-5.0/versions.ent 2005-09-16 19:59:45 +10:00 +++ 1.7/refman-5.0/versions.ent 2005-10-01 23:20:25 +10:00 @@ -9,4 +9,4 @@ <!ENTITY current-series "5.0"><!-- Current MySQL release series --> <!ENTITY previous-series "4.1"><!-- Previous MySQL release series --> <!ENTITY next-series "5.1"><!-- Next MySQL release series --> -<!ENTITY current-version "5.0.12-beta"><!-- Current MySQL Version - update with new releases --> +<!ENTITY current-version "5.0.13-rc"><!-- Current MySQL Version - update with new releases --> --- 1.6/refman-5.1/versions.ent 2005-09-16 19:59:45 +10:00 +++ 1.7/refman-5.1/versions.ent 2005-10-01 23:20:26 +10:00 @@ -9,5 +9,5 @@ <!ENTITY current-series "5.1"><!-- Current MySQL release series --> <!ENTITY previous-series "5.0"><!-- Previous MySQL release series --> <!ENTITY next-series "5.2"><!-- Next MySQL release series --> -<!ENTITY current-version "5.1.1-alpha"><!-- Current MySQL Version - update with new releases --> +<!ENTITY current-version "5.1.2-alpha"><!-- Current MySQL Version - update with new releases --> --- 1.48/refman-5.0/mysql-database-administration.xml 2005-09-30 04:51:05 +10:00 +++ 1.49/refman-5.0/mysql-database-administration.xml 2005-10-01 23:20:25 +10:00 @@ -262,11 +262,8 @@ <title id="title-mysqld-max">&title-mysqld-max;</title> <remark role="todo"> - -max is dynamically linked to support dynamic loading? - </remark> - - <remark> - (that is stated in UDF section, but not here) + -max is dynamically linked to support dynamic loading? (that is + stated in UDF section, but not here) </remark> <indexterm> @@ -553,10 +550,9 @@ </para> <para> - Before MySQL 4.1.2, <literal>SHOW ENGINES</literal> is - unavailable. Use the following statement instead and check the - value of the variable for the storage engine in which you are - interested: + You can also use the following statement instead of + <literal>SHOW ENGINES</literal>, and check the value of the + variable for the storage engine in which you are interested: </para> <programlisting> @@ -638,7 +634,11 @@ <literal>InnoDB</literal> or <literal>BDB</literal> storage engines if the server was compiled to support them, but was started with the <option>--skip-innodb</option> or - <option>--skip-bdb</option> options at runtime. + <option>--skip-bdb</option> options at runtime. For the + <literal>NDB Cluster</literal> storage engine, + <literal>DISABLED</literal> means the the server was compiled + with support for MySQL Cluster, but was not started with the + <option>--ndb-cluster</option> option. </para> <para> @@ -1013,8 +1013,8 @@ <para> Ignore character set information sent by the client and - use the default server character set. This option makes - MySQL 4.1 and higher behave like MySQL 4.0. + use the default server character set. (This option makes + MySQL behave like MySQL 4.0.) </para> </listitem> @@ -1959,8 +1959,8 @@ old scheme (invoking <command>mysqld_safe</command>) by default, but one can set the <literal>use_mysqld_safe</literal> variable in the script to - <literal>0</literal> (zero) to use the MySQL Instance Manager - to start a server. + <literal>0</literal> (zero) in order to use the + MySQL Instance Manager to start a server. </para> <remark role="todo"> @@ -1995,11 +1995,11 @@ <para> Note that there is a special option <literal>mysqld-path</literal> (<literal>mysqld-path = - <path-to-mysqld-binary></literal>) which is recognized - only by the IM. Use this variable to let the IM know where the - <command>mysqld</command> binary resides. You should also set - <literal>basedir</literal> and <literal>datadir</literal> - options for the server. + <replaceable>path-to-mysqld-binary</replaceable></literal>) + which is recognized only by the IM. Use this variable to let + the IM know where the <command>mysqld</command> binary + resides. You should also set <literal>basedir</literal> and + <literal>datadir</literal> options for the server. </para> <para> @@ -2196,7 +2196,7 @@ restart the instance. One can disable this behavior for particular instances with the <literal>nonguarded</literal> option in the appropriate - instance section. If no value was given, the default of 20 + instance section. If no value was given, the default of 20 seconds will be used. </para> </listitem> @@ -2240,7 +2240,7 @@ </para> <para> - The port number to use for connections. (The efault port + The port number to use for connections. (The default port number, assigned by IANA, is 2273). </para> </listitem> @@ -2361,8 +2361,8 @@ same configuration files as the MySQL Server, including <filename>/etc/my.cnf</filename>, <filename>~/.my.cnf</filename>, etc. As of MySQL 5.0.10, the - MySQL Instance Manager only reads and manages the - <filename>/etc/my.cnf</filename> file on Unix. On Windows, + MySQL Instance Manager reads and manages the + <filename>/etc/my.cnf</filename> file only on Unix. On Windows, MySQL Instance Manager reads the <filename>my.ini</filename> file in the directory where Instance Manager is installed. The default option file location can be changed with the @@ -2396,7 +2396,7 @@ </para> <para> - A number of seconds IM should wait for the instance to + The number of seconds IM should wait for the instance to shut down. The default is 35 seconds. After the delay expires, the IM assumes that the instance is hanging and attempts to <literal>kill -9</literal> it. If you use @@ -5254,232 +5254,232 @@ <programlisting> mysql> <userinput>SHOW VARIABLES;</userinput> -+---------------------------------+---------------------------------------------------------+ -| Variable_name | Value | -+---------------------------------+---------------------------------------------------------+ -| auto_increment_increment | 1 | -| auto_increment_offset | 1 | -| automatic_sp_privileges | ON | -| back_log | 50 | -| basedir | / | -| bdb_cache_size | 8388600 | -| bdb_home | /var/lib/mysql/ | -| bdb_log_buffer_size | 32768 | -| bdb_logdir | | -| bdb_max_lock | 10000 | -| bdb_shared_data | OFF | -| bdb_tmpdir | /tmp/ | -| binlog_cache_size | 32768 | -| bulk_insert_buffer_size | 8388608 | -| character_set_client | latin1 | -| character_set_connection | latin1 | -| character_set_database | latin1 | -| character_set_results | latin1 | -| character_set_server | latin1 | -| character_set_system | utf8 | -| character_sets_dir | /usr/share/mysql/charsets/ | -| collation_connection | latin1_swedish_ci | -| collation_database | latin1_swedish_ci | -| collation_server | latin1_swedish_ci | -| completion_type | 0 | -| concurrent_insert | 1 | -| connect_timeout | 5 | -| datadir | /var/lib/mysql/ | -| date_format | %Y-%m-%d | -| datetime_format | %Y-%m-%d %H:%i:%s | -| default_week_format | 0 | -| delay_key_write | ON | -| delayed_insert_limit | 100 | -| delayed_insert_timeout | 300 | -| delayed_queue_size | 1000 | -| div_precision_increment | 4 | -| engine_condition_pushdown | OFF | -| expire_logs_days | 0 | -| flush | OFF | -| flush_time | 0 | -| ft_boolean_syntax | + -><()~*:""&| | -| ft_max_word_len | 84 | -| ft_min_word_len | 4 | -| ft_query_expansion_limit | 20 | -| ft_stopword_file | (built-in) | -| group_concat_max_len | 1024 | -| have_archive | NO | -| have_bdb | YES | -| have_blackhole_engine | YES | -| have_compress | YES | -| have_crypt | YES | -| have_csv | YES | -| have_example_engine | YES | -| have_federated_engine | YES | -| have_geometry | YES | -| have_innodb | YES | -| have_isam | NO | -| have_ndbcluster | DISABLED | -| have_openssl | NO | -| have_query_cache | YES | -| have_raid | NO | -| have_rtree_keys | YES | -| have_symlink | YES | -| init_connect | | -| init_file | | -| init_slave | | -| innodb_additional_mem_pool_size | 1048576 | -| innodb_autoextend_increment | 8 | -| innodb_buffer_pool_awe_mem_mb | 0 | -| innodb_buffer_pool_size | 8388608 | -| innodb_checksums | ON | -| innodb_concurrency_tickets | 500 | -| innodb_data_file_path | ibdata1:10M:autoextend | -| innodb_data_home_dir | | -| innodb_doublewrite | ON | -| innodb_fast_shutdown | 1 | -| innodb_file_io_threads | 4 | -| innodb_file_per_table | OFF | -| innodb_flush_log_at_trx_commit | 1 | -| innodb_flush_method | | -| innodb_force_recovery | 0 | -| innodb_lock_wait_timeout | 50 | -| innodb_locks_unsafe_for_binlog | OFF | -| innodb_log_arch_dir | | -| innodb_log_archive | OFF | -| innodb_log_buffer_size | 1048576 | -| innodb_log_file_size | 5242880 | -| innodb_log_files_in_group | 2 | -| innodb_log_group_home_dir | ./ | -| innodb_max_dirty_pages_pct | 90 | -| innodb_max_purge_lag | 0 | -| innodb_mirrored_log_groups | 1 | -| innodb_open_files | 300 | -| innodb_support_xa | ON | -| innodb_sync_spin_loops | 20 | -| innodb_table_locks | ON | -| innodb_thread_concurrency | 8 | -| innodb_thread_sleep_delay | 10000 | -| interactive_timeout | 28800 | -| join_buffer_size | 131072 | -| key_buffer_size | 8388600 | -| key_cache_age_threshold | 300 | -| key_cache_block_size | 1024 | -| key_cache_division_limit | 100 | -| language | /usr/share/mysql/english/ | -| large_files_support | ON | -| large_pages | OFF | -| large_page_size | 0 | -| license | GPL | -| local_infile | ON | -| locked_in_memory | OFF | -| log | OFF | -| log_bin | OFF | -| log_bin_trust_routine_creators | OFF | -| log_error | | -| log_slave_updates | OFF | -| log_slow_queries | OFF | -| log_warnings | 1 | -| long_query_time | 10 | -| low_priority_updates | OFF | -| lower_case_file_system | OFF | -| lower_case_table_names | 0 | -| max_allowed_packet | 1048576 | -| max_binlog_cache_size | 4294967295 | -| max_binlog_size | 1073741824 | -| max_connect_errors | 10 | -| max_connections | 100 | -| max_delayed_threads | 20 | -| max_error_count | 64 | -| max_heap_table_size | 16777216 | -| max_insert_delayed_threads | 20 | -| max_join_size | 4294967295 | -| max_length_for_sort_data | 1024 | -| max_relay_log_size | 0 | -| max_seeks_for_key | 4294967295 | -| max_sort_length | 1024 | -| max_tmp_tables | 32 | -| max_user_connections | 0 | -| max_write_lock_count | 4294967295 | -| multi_range_count | 256 | -| myisam_data_pointer_size | 6 | -| myisam_max_sort_file_size | 2147483647 | -| myisam_recover_options | OFF | -| myisam_repair_threads | 1 | -| myisam_sort_buffer_size | 8388608 | -| engine_condition_pushdown | OFF | -| ndb_autoincrement_prefetch_sz | 32 | -| ndb_force_send | ON | -| ndb_use_exact_count | ON | -| ndb_use_transactions | ON | -| ndb_cache_check_time | 0 | -| net_buffer_length | 16384 | -| net_read_timeout | 30 | -| net_retry_count | 10 | -| net_write_timeout | 60 | -| new | OFF | -| old_passwords | OFF | -| open_files_limit | 1024 | -| optimizer_prune_level | 1 | -| optimizer_search_depth | 62 | -| pid_file | /var/lib/mysql/gigan.pid | -| port | 3306 | -| preload_buffer_size | 32768 | -| protocol_version | 10 | -| query_alloc_block_size | 8192 | -| query_cache_limit | 1048576 | -| query_cache_min_res_unit | 4096 | -| query_cache_size | 0 | -| query_cache_type | ON | -| query_cache_wlock_invalidate | OFF | -| query_prealloc_size | 8192 | -| range_alloc_block_size | 2048 | -| read_buffer_size | 131072 | -| read_only | OFF | -| read_rnd_buffer_size | 262144 | -| relay_log_purge | ON | -| relay_log_space_limit | 0 | -| rpl_recovery_rank | 0 | -| secure_auth | OFF | -| server_id | 0 | -| skip_external_locking | ON | -| skip_networking | OFF | -| skip_show_database | OFF | -| slave_compressed_protocol | OFF | -| slave_load_tmpdir | /tmp/ | -| slave_net_timeout | 3600 | -| slave_skip_errors | OFF | -| slave_transaction_retries | 10 | -| slow_launch_time | 2 | -| socket | /var/lib/mysql/mysql.sock | -| sort_buffer_size | 2097144 | -| sql_mode | | -| storage_engine | MyISAM | -| sql_notes | OFF | -| sql_warnings | OFF | -| sync_binlog | 0 | -| sync_replication | 0 | -| sync_replication_slave_id | 0 | -| sync_replication_timeout | 10 | -| sync_frm | ON | -| system_time_zone | EST | -| table_cache | 64 | -| table_type | MyISAM | -| thread_cache_size | 0 | -| thread_stack | 196608 | -| time_format | %H:%i:%s | -| time_zone | SYSTEM | -| timed_mutexes | OFF | -| tmp_table_size | 33554432 | -| tmpdir | | -| transaction_alloc_block_size | 8192 | -| transaction_prealloc_size | 4096 | -| tx_isolation | REPEATABLE-READ | -| updatable_views_with_limit | YES | -| version | 5.0.7-beta-Max | -| version_bdb | Sleepycat Software: Berkeley DB 4.1.24: (June 11, 2005) | -| version_comment | MySQL Community Edition - Max (GPL) | -| version_compile_machine | i686 | -| version_compile_os | pc-linux-gnu | -| wait_timeout | 28800 | -+---------------------------------+---------------------------------------------------------+ -219 rows in set (0.00 sec) - ++---------------------------------+--------------------------------------------------------------+ +| Variable_name | Value | ++---------------------------------+--------------------------------------------------------------+ +| auto_increment_increment | 1 | +| auto_increment_offset | 1 | +| automatic_sp_privileges | ON | +| back_log | 50 | +| basedir | / | +| bdb_cache_size | 8388600 | +| bdb_home | /var/lib/mysql/ | +| bdb_log_buffer_size | 32768 | +| bdb_logdir | | +| bdb_max_lock | 10000 | +| bdb_shared_data | OFF | +| bdb_tmpdir | /tmp/ | +| binlog_cache_size | 32768 | +| bulk_insert_buffer_size | 8388608 | +| character_set_client | latin1 | +| character_set_connection | latin1 | +| character_set_database | latin1 | +| character_set_results | latin1 | +| character_set_server | latin1 | +| character_set_system | utf8 | +| character_sets_dir | /usr/share/mysql/charsets/ | +| collation_connection | latin1_swedish_ci | +| collation_database | latin1_swedish_ci | +| collation_server | latin1_swedish_ci | +| completion_type | 0 | +| concurrent_insert | 1 | +| connect_timeout | 5 | +| datadir | /var/lib/mysql/ | +| date_format | %Y-%m-%d | +| datetime_format | %Y-%m-%d %H:%i:%s | +| default_week_format | 0 | +| delay_key_write | ON | +| delayed_insert_limit | 100 | +| delayed_insert_timeout | 300 | +| delayed_queue_size | 1000 | +| div_precision_increment | 4 | +| engine_condition_pushdown | OFF | +| expire_logs_days | 0 | +| flush | OFF | +| flush_time | 0 | +| ft_boolean_syntax | + -><()~*:""&| | +| ft_max_word_len | 84 | +| ft_min_word_len | 4 | +| ft_query_expansion_limit | 20 | +| ft_stopword_file | (built-in) | +| group_concat_max_len | 1024 | +| have_archive | YES | +| have_bdb | YES | +| have_blackhole_engine | YES | +| have_compress | YES | +| have_crypt | YES | +| have_csv | YES | +| have_example_engine | YES | +| have_federated_engine | YES | +| have_geometry | YES | +| have_innodb | YES | +| have_isam | NO | +| have_ndbcluster | DISABLED | +| have_openssl | NO | +| have_query_cache | YES | +| have_raid | NO | +| have_rtree_keys | YES | +| have_symlink | YES | +| init_connect | | +| init_file | | +| init_slave | | +| innodb_additional_mem_pool_size | 1048576 | +| innodb_autoextend_increment | 8 | +| innodb_buffer_pool_awe_mem_mb | 0 | +| innodb_buffer_pool_size | 8388608 | +| innodb_checksums | ON | +| innodb_commit_concurrency | 0 | +| innodb_concurrency_tickets | 500 | +| innodb_data_file_path | ibdata1:10M:autoextend | +| innodb_data_home_dir | | +| innodb_doublewrite | ON | +| innodb_fast_shutdown | 1 | +| innodb_file_io_threads | 4 | +| innodb_file_per_table | OFF | +| innodb_flush_log_at_trx_commit | 1 | +| innodb_flush_method | | +| innodb_force_recovery | 0 | +| innodb_lock_wait_timeout | 50 | +| innodb_locks_unsafe_for_binlog | OFF | +| innodb_log_arch_dir | | +| innodb_log_archive | OFF | +| innodb_log_buffer_size | 1048576 | +| innodb_log_file_size | 5242880 | +| innodb_log_files_in_group | 2 | +| innodb_log_group_home_dir | ./ | +| innodb_max_dirty_pages_pct | 90 | +| innodb_max_purge_lag | 0 | +| innodb_mirrored_log_groups | 1 | +| innodb_open_files | 300 | +| innodb_support_xa | ON | +| innodb_sync_spin_loops | 20 | +| innodb_table_locks | ON | +| innodb_thread_concurrency | 20 | +| innodb_thread_sleep_delay | 10000 | +| interactive_timeout | 28800 | +| join_buffer_size | 131072 | +| key_buffer_size | 8388600 | +| key_cache_age_threshold | 300 | +| key_cache_block_size | 1024 | +| key_cache_division_limit | 100 | +| language | /usr/share/mysql/english/ | +| large_files_support | ON | +| large_page_size | 0 | +| large_pages | OFF | +| license | GPL | +| local_infile | ON | +| locked_in_memory | OFF | +| log | OFF | +| log_bin | OFF | +| log_bin_trust_routine_creators | OFF | +| log_error | | +| log_slave_updates | OFF | +| log_slow_queries | OFF | +| log_warnings | 1 | +| long_query_time | 10 | +| low_priority_updates | OFF | +| lower_case_file_system | OFF | +| lower_case_table_names | 0 | +| max_allowed_packet | 1048576 | +| max_binlog_cache_size | 4294967295 | +| max_binlog_size | 1073741824 | +| max_connect_errors | 10 | +| max_connections | 100 | +| max_delayed_threads | 20 | +| max_error_count | 64 | +| max_heap_table_size | 16777216 | +| max_insert_delayed_threads | 20 | +| max_join_size | 4294967295 | +| max_length_for_sort_data | 1024 | +| max_relay_log_size | 0 | +| max_seeks_for_key | 4294967295 | +| max_sort_length | 1024 | +| max_tmp_tables | 32 | +| max_user_connections | 0 | +| max_write_lock_count | 4294967295 | +| multi_range_count | 256 | +| myisam_data_pointer_size | 6 | +| myisam_max_sort_file_size | 2147483647 | +| myisam_recover_options | OFF | +| myisam_repair_threads | 1 | +| myisam_sort_buffer_size | 8388608 | +| ndb_autoincrement_prefetch_sz | 32 | +| ndb_force_send | ON | +| ndb_use_exact_count | ON | +| ndb_use_transactions | ON | +| ndb_cache_check_time | 0 | +| net_buffer_length | 16384 | +| net_read_timeout | 30 | +| net_retry_count | 10 | +| net_write_timeout | 60 | +| new | OFF | +| old_passwords | OFF | +| open_files_limit | 1024 | +| optimizer_prune_level | 1 | +| optimizer_search_depth | 62 | +| pid_file | /var/lib/mysql/mothra.pid | +| port | 3306 | +| preload_buffer_size | 32768 | +| protocol_version | 10 | +| query_alloc_block_size | 8192 | +| query_cache_limit | 1048576 | +| query_cache_min_res_unit | 4096 | +| query_cache_size | 0 | +| query_cache_type | ON | +| query_cache_wlock_invalidate | OFF | +| query_prealloc_size | 8192 | +| range_alloc_block_size | 2048 | +| read_buffer_size | 131072 | +| read_only | OFF | +| read_rnd_buffer_size | 262144 | +| relay_log_purge | ON | +| relay_log_space_limit | 0 | +| rpl_recovery_rank | 0 | +| secure_auth | OFF | +| server_id | 0 | +| skip_external_locking | ON | +| skip_networking | OFF | +| skip_show_database | OFF | +| slave_compressed_protocol | OFF | +| slave_load_tmpdir | /tmp/ | +| slave_net_timeout | 3600 | +| slave_skip_errors | OFF | +| slave_transaction_retries | 10 | +| slow_launch_time | 2 | +| socket | /var/lib/mysql/mysql.sock | +| sort_buffer_size | 2097144 | +| sql_mode | | +| sql_notes | ON | +| sql_warnings | ON | +| storage_engine | MyISAM | +| sync_binlog | 0 | +| sync_frm | ON | +| sync_replication | 0 | +| sync_replication_slave_id | 0 | +| sync_replication_timeout | 10 | +| system_time_zone | EST | +| table_cache | 64 | +| table_lock_wait_timeout | 50 | +| table_type | MyISAM | +| thread_cache_size | 0 | +| thread_stack | 196608 | +| time_format | %H:%i:%s | +| time_zone | SYSTEM | +| timed_mutexes | OFF | +| tmp_table_size | 33554432 | +| tmpdir | | +| transaction_alloc_block_size | 8192 | +| transaction_prealloc_size | 4096 | +| tx_isolation | REPEATABLE-READ | +| updatable_views_with_limit | YES | +| version | 5.0.13-rc-Max | +| version_bdb | Sleepycat Software: Berkeley DB 4.1.24: (September 22, 2005) | +| version_comment | MySQL Community Edition - Max (GPL) | +| version_compile_machine | i686 | +| version_compile_os | pc-linux-gnu | +| wait_timeout | 28800 | ++---------------------------------+--------------------------------------------------------------+ +221 rows in set (0.01 sec) </programlisting> <indexterm> @@ -5933,13 +5933,12 @@ The size of the cache to hold the SQL statements for the binary log during a transaction. A binary log cache is allocated for each client if the server supports any - transactional storage engines and, starting from MySQL - 4.1.2, if the server has binary log enabled - (<option>--log-bin</option> option). If you often use big, - multiple-statement transactions, you can increase this to - get more performance. The + transactional storage engines and if the server has binary + log enabled (<option>--log-bin</option> option). If you + often use big, multiple-statement transactions, you can + increase this to get more performance. The <literal>Binlog_cache_use</literal> and - <literal>Binlog_cache_disk_use</literal> status variables + <literal>Binlog_cache_disk_use</literal> status variables can be useful for tuning the size of this variable. See <xref linkend="binary-log"/>. </para> @@ -6161,16 +6160,17 @@ </row> <row> <entry>1</entry> - <entry>(Default) Enables concurrent insert for MyISAM tables that doesn't have - holes</entry> + <entry>(Default) Enables concurrent insert for + MyISAM tables that don't have holes</entry> </row> <row> <entry>2</entry> - <entry>Enables concurrent inserts for all MyISAM tables. If table has a hole - and is in use by another thread the new row will - be inserted at end of table. If table is not in - use then MySQL will do a normal read lock and - insert the new row into the hole.</entry> + <entry>Enables concurrent inserts for all MyISAM + tables. If table has a hole and is in use by + another thread the new row will be inserted at end + of table. If table is not in use then MySQL will + do a normal read lock and insert the new row into + the hole.</entry> </row> </tbody> </tgroup> @@ -7584,9 +7584,8 @@ Beginning with MySQL 5.0.3, it also has a read-only session scope. The session variable has the same value as the global variable unless the current account has a - non-zero <literal>MAX_USER_CONNECTIONS</literal> resource - limit. In that case, the session value reflects the - account limit. + non-zero <literal>MAX_USER_CONNECTIONS</literal> resource limit. In + that case, the session value reflects the account limit. </para> </listitem> @@ -7724,7 +7723,7 @@ </para> <para> - This variable was added in MySQL 4.1.15/5.0.14. For older + This variable was added in MySQL 5.0.14. For older versions, the statistics collection method is equivalent to <literal>nulls_equal</literal>. </para> @@ -8175,26 +8174,6 @@ </para> </listitem> -<!-- -<remark role="todo">Cut this?</remark> - <listitem><para> - <literal>safe_show_database</literal> - </para> - - <para> - Don't show databases for which the user has no database or table - privileges. This can improve security if you're concerned about - people being able to see what databases other users have. See also - <literal>skip_show_database</literal>. - </para> - - <para> - This variable was removed in MySQL 4.0.5. Instead, use the - <literal>SHOW DATABASES</literal> privilege to control access by - MySQL accounts to database names. - </para></listitem> ---> - <listitem> <para> <literal>secure_auth</literal> @@ -8408,10 +8387,6 @@ <filename>/var/lib/mysql/mysql.sock</filename>. </para> - <remark role="todo"> - Check this. Doesn't seem to be defined in 5.0.7-nt? - </remark> - <para> <emphasis>Windows</emphasis>: The name of the named pipe used for local client connections. Defaults to @@ -10927,8 +10902,8 @@ <para> Total number of times since startup that the replication - slave SQL thread has retried transactions. For the MySQL - 5.0 series of releases, this variable was added in version + slave SQL thread has retried transactions. In MySQL + ¤t-series;, this variable was added in version 5.0.4. </para> </listitem> @@ -11388,9 +11363,9 @@ that it manages. For example, MyISAM flushes any pending index writes for a table. InnoDB flushes its buffer pool to disk (starting from 5.0.5: unless - <literal>innodb_fast_shutdown</literal> is 2), writes the - current LSN to the tablespace, and terminates its own internal - threads. + <literal>innodb_fast_shutdown</literal> is 2), writes + the current LSN to the tablespace, and terminates its own + internal threads. </para> </listitem> @@ -12878,9 +12853,10 @@ 5.0.3. The <literal>Routine_type</literal> column was added in MySQL 5.0.6. It is an <literal>ENUM</literal> column with values of <literal>'FUNCTION'</literal> or - <literal>'PROCEDURE'</literal> to indicate the type of routine - the row refers to. This column allows privileges to be granted - separately for a function and a procedure with the same name. + <literal>'PROCEDURE'</literal> + to indicate the type of routine the row refers to. This column + allows privileges to be granted separately for a function and a + procedure with the same name. </para> <para> @@ -17528,8 +17504,7 @@ <para> To use SSL connections between the MySQL server and client - programs, your system must be able to support OpenSSL and your - version of MySQL must be 4.0.0 or newer. If you're using a + programs, your system must be able to support OpenSSL. If you're using a MySQL version with built-in yaSSL support (as of version 5.0.10), don't read this section, but rather <xref linkend="secure-using-yassl"/>. @@ -19742,9 +19717,9 @@ more information, see the description of <literal>myisam_stats_method</literal> in <xref linkend="server-system-variables"/> and - <xref linkend="myisam-index-statistics"/>. + <xref linkend="myisam-index-statistics"/>. For MySQL ¤t-series;, <literal>stats_method</literal> was added in MySQL - 4.1.15/5.0.14. For older versions, the statistics collection + 5.0.14. For older versions, the statistics collection method is equivalent to <literal>nulls_equal</literal>. </para> @@ -24095,9 +24070,10 @@ the <command>mysqld-nt</command> server from two different versions of MySQL that are installed at <filename>C:\mysql-4.1.8</filename> and - <filename>C:\mysql-5.0.7</filename>, respectively. (This might - be the case if you're running 4.1.8 as your production server, - but also want to conduct tests using 5.0.7.) + <filename>C:\mysql-¤t-version;</filename>, respectively. + (This might be the case if you're running 4.1.8 as your + production server, but also want to conduct tests using + ¤t-version;.) </para> <para> @@ -24179,11 +24155,11 @@ files. To do this, use a different service name for each server. Suppose that you want to run the 4.1.8 <command>mysqld-nt</command> using the service name of - <literal>mysqld1</literal> and the 5.0.7 + <literal>mysqld1</literal> and the ¤t-version; <command>mysqld-nt</command> using the service name <literal>mysqld2</literal>. In this case, you can use the <literal>[mysqld1]</literal> group for 4.1.8 and the - <literal>[mysqld2]</literal> group for 5.0.7. For example, + <literal>[mysqld2]</literal> group for ¤t-version;. For example, you can set up <filename>C:\my.cnf</filename> like this: </para> @@ -24197,7 +24173,7 @@ # options for mysqld2 service [mysqld2] -basedir = C:/mysql-5.0.7 +basedir = C:/mysql-¤t-version; port = 3308 enable-named-pipe socket = mypipe2 @@ -24211,7 +24187,7 @@ <programlisting> C:\> <userinput>C:\mysql-4.1.8\bin\mysqld-nt --install mysqld1</userinput> -C:\> <userinput>C:\mysql-5.0.7\bin\mysqld-nt --install mysqld2</userinput> +C:\> <userinput>C:\mysql-¤t-version;\bin\mysqld-nt --install mysqld2</userinput> </programlisting> <para> @@ -24262,14 +24238,13 @@ </programlisting> <para> - For the 5.0.7 <command>mysqld-nt</command>, create a file + For the ¤t-version; <command>mysqld-nt</command>, create a file <filename>C:\my-opts2.cnf</filename> that looks like this: </para> <programlisting> [mysqld] -basedir = C:/mysql-5.0.7 -port = 3308 +basedir = C:/mysql-¤t-version; port = 3308 enable-named-pipe socket = mypipe2 </programlisting> @@ -24282,7 +24257,7 @@ <programlisting> C:\> <userinput>C:\mysql-4.1.8\bin\mysqld-nt --install mysqld1</userinput> --defaults-file=C:\my-opts1.cnf -C:\> <userinput>C:\mysql-5.0.7\bin\mysqld-nt --install mysqld2</userinput> +C:\> <userinput>C:\mysql-¤t-version;\bin\mysqld-nt --install mysqld2</userinput> --defaults-file=C:\my-opts2.cnf </programlisting> @@ -24329,15 +24304,15 @@ <para> Assume that an existing 4.1.8 server is configured for the default TCP/IP port number (3306) and Unix socket file - (<filename>/tmp/mysql.sock</filename>). To configure a new 5.0.7 - server to have different operating parameters, use a - <command>configure</command> command something like this: + (<filename>/tmp/mysql.sock</filename>). To configure a new + ¤t-version; server to have different operating parameters, + use a <command>configure</command> command something like this: </para> <programlisting> shell> <userinput>./configure --with-tcp-port=<replaceable>port_number</replaceable> \</userinput> <userinput>--with-unix-socket-path=<replaceable>file_name</replaceable> \</userinput> - <userinput>--prefix=/usr/local/mysql-5.0.7</userinput> + <userinput>--prefix=/usr/local/mysql-¤t-version;</userinput> </programlisting> <para>
| Thread | ||
|---|---|---|
| • bk commit - mysqldoc@docsrva tree (jon:1.3659) | jon | 1 Oct |
© 1995-2008 MySQL AB, 2008-2009 Sun Microsystems, Inc.
Page generated in 1.337 sec. using MySQL 5.1.14-beta-log