[Pkg-mysql-commits] r1020 - branches/sid-5.0/debian/manpages
Norbert Tretkowski
nobse at alioth.debian.org
Mon Nov 26 12:34:29 UTC 2007
Author: nobse
Date: 2007-11-26 12:34:29 +0000 (Mon, 26 Nov 2007)
New Revision: 1020
Added:
branches/sid-5.0/debian/manpages/comp_err.1
branches/sid-5.0/debian/manpages/innochecksum.1
branches/sid-5.0/debian/manpages/make_win_bin_dist.1
branches/sid-5.0/debian/manpages/make_win_src_distribution.1
branches/sid-5.0/debian/manpages/msql2mysql.1
branches/sid-5.0/debian/manpages/my_print_defaults.1
branches/sid-5.0/debian/manpages/myisam_ftdump.1
branches/sid-5.0/debian/manpages/myisamchk.1
branches/sid-5.0/debian/manpages/myisamlog.1
branches/sid-5.0/debian/manpages/myisampack.1
branches/sid-5.0/debian/manpages/mysql-stress-test.pl.1
branches/sid-5.0/debian/manpages/mysql-test-run.pl.1
branches/sid-5.0/debian/manpages/mysql.1
branches/sid-5.0/debian/manpages/mysql.server.1
branches/sid-5.0/debian/manpages/mysql_client_test.1
branches/sid-5.0/debian/manpages/mysql_client_test_embedded.1
branches/sid-5.0/debian/manpages/mysql_config.1
branches/sid-5.0/debian/manpages/mysql_convert_table_format.1
branches/sid-5.0/debian/manpages/mysql_explain_log.1
branches/sid-5.0/debian/manpages/mysql_find_rows.1
branches/sid-5.0/debian/manpages/mysql_fix_extensions.1
branches/sid-5.0/debian/manpages/mysql_fix_privilege_tables.1
branches/sid-5.0/debian/manpages/mysql_install_db.1
branches/sid-5.0/debian/manpages/mysql_secure_installation.1
branches/sid-5.0/debian/manpages/mysql_setpermission.1
branches/sid-5.0/debian/manpages/mysql_tableinfo.1
branches/sid-5.0/debian/manpages/mysql_tzinfo_to_sql.1
branches/sid-5.0/debian/manpages/mysql_upgrade.1
branches/sid-5.0/debian/manpages/mysql_waitpid.1
branches/sid-5.0/debian/manpages/mysql_zap.1
branches/sid-5.0/debian/manpages/mysqlaccess.1
branches/sid-5.0/debian/manpages/mysqladmin.1
branches/sid-5.0/debian/manpages/mysqlbinlog.1
branches/sid-5.0/debian/manpages/mysqlcheck.1
branches/sid-5.0/debian/manpages/mysqld.8
branches/sid-5.0/debian/manpages/mysqld_multi.1
branches/sid-5.0/debian/manpages/mysqld_safe.1
branches/sid-5.0/debian/manpages/mysqldump.1
branches/sid-5.0/debian/manpages/mysqlhotcopy.1
branches/sid-5.0/debian/manpages/mysqlimport.1
branches/sid-5.0/debian/manpages/mysqlmanager-pwgen.1
branches/sid-5.0/debian/manpages/mysqlmanager.8
branches/sid-5.0/debian/manpages/mysqlmanagerc.1
branches/sid-5.0/debian/manpages/mysqlshow.1
branches/sid-5.0/debian/manpages/mysqltest.1
branches/sid-5.0/debian/manpages/mysqltest_embedded.1
branches/sid-5.0/debian/manpages/ndb_config.1
branches/sid-5.0/debian/manpages/ndb_cpcd.1
branches/sid-5.0/debian/manpages/ndb_delete_all.1
branches/sid-5.0/debian/manpages/ndb_desc.1
branches/sid-5.0/debian/manpages/ndb_drop_index.1
branches/sid-5.0/debian/manpages/ndb_drop_table.1
branches/sid-5.0/debian/manpages/ndb_error_reporter.1
branches/sid-5.0/debian/manpages/ndb_mgm.1
branches/sid-5.0/debian/manpages/ndb_mgmd.1
branches/sid-5.0/debian/manpages/ndb_print_backup_file.1
branches/sid-5.0/debian/manpages/ndb_print_schema_file.1
branches/sid-5.0/debian/manpages/ndb_print_sys_file.1
branches/sid-5.0/debian/manpages/ndb_restore.1
branches/sid-5.0/debian/manpages/ndb_select_all.1
branches/sid-5.0/debian/manpages/ndb_select_count.1
branches/sid-5.0/debian/manpages/ndb_show_tables.1
branches/sid-5.0/debian/manpages/ndb_size.pl.1
branches/sid-5.0/debian/manpages/ndb_waiter.1
branches/sid-5.0/debian/manpages/ndbd.1
branches/sid-5.0/debian/manpages/perror.1
branches/sid-5.0/debian/manpages/replace.1
branches/sid-5.0/debian/manpages/resolve_stack_dump.1
branches/sid-5.0/debian/manpages/resolveip.1
branches/sid-5.0/debian/manpages/safe_mysqld.1
Log:
Added upstream manpages.
Added: branches/sid-5.0/debian/manpages/comp_err.1
===================================================================
--- branches/sid-5.0/debian/manpages/comp_err.1 (rev 0)
+++ branches/sid-5.0/debian/manpages/comp_err.1 2007-11-26 12:34:29 UTC (rev 1020)
@@ -0,0 +1,141 @@
+.\" Title: \fBcomp_err\fR
+.\" Author:
+.\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
+.\" Date: 11/25/2007
+.\" Manual: MySQL Database System
+.\" Source: MySQL 5.0
+.\"
+.TH "\fBCOMP_ERR\fR" "1" "11/25/2007" "MySQL 5.0" "MySQL Database System"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
+.SH "NAME"
+comp_err \- compile MySQL error message file
+.SH "SYNOPSIS"
+.HP 19
+\fBcomp_err [\fR\fB\fIoptions\fR\fR\fB]\fR
+.SH "DESCRIPTION"
+.PP
+\fBcomp_err\fR
+creates the
+\fIerrmsg.sys\fR
+file that is used by
+\fBmysqld\fR
+to determine the error messages to display for different error codes.
+\fBcomp_err\fR
+normally is run automatically when MySQL is built. It compiles the
+\fIerrmsg.sys\fR
+file from the plaintext file located at
+\fIsql/share/errmsg.txt\fR
+in MySQL source distributions.
+.PP
+\fBcomp_err\fR
+also generates
+\fImysqld_error.h\fR,
+\fImysqld_ername.h\fR, and
+\fIsql_state.h\fR
+header files.
+.PP
+For more information about how error messages are defined, see the MySQL Internals Manual.
+.PP
+Invoke
+\fBcomp_err\fR
+like this:
+.sp
+.RS 3n
+.nf
+shell> \fBcomp_err [\fR\fB\fIoptions\fR\fR\fB]\fR
+.fi
+.RE
+.PP
+\fBcomp_err\fR
+understands the options described in the following list.
+.TP 3n
+\(bu
+\fB\-\-help\fR,
+\fB\-?\fR
+.sp
+Display a help message and exit.
+.TP 3n
+\(bu
+\fB\-\-charset=\fR\fB\fIpath\fR\fR\fB, \-C \fR\fB\fIpath\fR\fR
+.sp
+The character set directory. The default is
+\fI../sql/share/charsets\fR.
+.TP 3n
+\(bu
+\fB\-\-debug=\fR\fB\fIdebug_options\fR\fR\fB, \-# \fR\fB\fIdebug_options\fR\fR
+.sp
+Write a debugging log. The
+\fIdebug_options\fR
+string often is
+\'d:t:O,\fIfile_name\fR'. The default is
+\'d:t:O,/tmp/comp_err.trace'.
+.TP 3n
+\(bu
+\fB\-\-debug\-info\fR,
+\fB\-T\fR
+.sp
+Print some debugging information when the program exits.
+.TP 3n
+\(bu
+\fB\-\-header_file=\fR\fB\fIfile_name\fR\fR\fB, \-H \fR\fB\fIfile_name\fR\fR
+.sp
+The name of the error header file. The default is
+\fImysqld_error.h\fR.
+.TP 3n
+\(bu
+\fB\-\-in_file=\fR\fB\fIfile_name\fR\fR\fB, \-F \fR\fB\fIfile_name\fR\fR
+.sp
+The name of the input file. The default is
+\fI../sql/share/errmsg.txt\fR.
+.TP 3n
+\(bu
+\fB\-\-name_file=\fR\fB\fIfile_name\fR\fR\fB, \-N \fR\fB\fIfile_name\fR\fR
+.sp
+The name of the error name file. The default is
+\fImysqld_ername.h\fR.
+.TP 3n
+\(bu
+\fB\-\-out_dir=\fR\fB\fIpath\fR\fR\fB, \-D \fR\fB\fIpath\fR\fR
+.sp
+The name of the output base directory. The default is
+\fI../sql/share/\fR.
+.TP 3n
+\(bu
+\fB\-\-out_file=\fR\fB\fIfile_name\fR\fR\fB, \-O \fR\fB\fIfile_name\fR\fR
+.sp
+The name of the output file. The default is
+\fIerrmsg.sys\fR.
+.TP 3n
+\(bu
+\fB\-\-statefile=\fR\fB\fIfile_name\fR\fR\fB, \-S \fR\fB\fIfile_name\fR\fR
+.sp
+The name for the SQLSTATE header file. The default is
+\fIsql_state.h\fR.
+.TP 3n
+\(bu
+\fB\-\-version\fR,
+\fB\-V\fR
+.sp
+Display version information and exit.
+.SH "COPYRIGHT"
+.PP
+Copyright 2007 MySQL AB
+.PP
+This documentation is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License.
+.PP
+This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
+.PP
+You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110\-1301 USA or see http://www.gnu.org/licenses/.
+.PP
+Please email
+<docs at mysql.com>
+for more information or if you are interested in doing a translation.
+.SH "SEE ALSO"
+For more information, please refer to the MySQL Reference Manual,
+which may already be installed locally and which is also available
+online at http://dev.mysql.com/doc/.
+.SH AUTHOR
+MySQL AB (http://www.mysql.com/).
Added: branches/sid-5.0/debian/manpages/innochecksum.1
===================================================================
--- branches/sid-5.0/debian/manpages/innochecksum.1 (rev 0)
+++ branches/sid-5.0/debian/manpages/innochecksum.1 2007-11-26 12:34:29 UTC (rev 1020)
@@ -0,0 +1,85 @@
+.\" Title: \fBinnochecksum\fR
+.\" Author:
+.\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
+.\" Date: 11/25/2007
+.\" Manual: MySQL Database System
+.\" Source: MySQL 5.0
+.\"
+.TH "\fBINNOCHECKSUM\fR" "1" "11/25/2007" "MySQL 5.0" "MySQL Database System"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
+.SH "NAME"
+innochecksum \- offline InnoDB file checksum utility
+.SH "SYNOPSIS"
+.HP 33
+\fBinnochecksum [\fR\fB\fIoptions\fR\fR\fB] \fR\fB\fIfile_name\fR\fR
+.SH "DESCRIPTION"
+.PP
+\fBinnochecksum\fR
+prints checksums for
+InnoDB
+files.
+.PP
+Invoke
+\fBinnochecksum\fR
+like this:
+.sp
+.RS 3n
+.nf
+shell> \fBinnochecksum [\fR\fB\fIoptions\fR\fR\fB] \fR\fB\fIfile_name\fR\fR
+.fi
+.RE
+.PP
+\fBinnodchecksum\fR
+understands the options described in the following list. For options that refer to page numbers, the numbers are zero\-based.
+.TP 3n
+\(bu
+\fB\-c\fR
+.sp
+Print a count of the number of pages in the file.
+.TP 3n
+\(bu
+\fB\-d\fR
+.sp
+Debug mode; prints checksums for each page.
+.TP 3n
+\(bu
+\fB\-e \fR\fB\fInum\fR\fR
+.sp
+End at this page number.
+.TP 3n
+\(bu
+\fB\-p \fR\fB\fInum\fR\fR
+.sp
+Check only this page number.
+.TP 3n
+\(bu
+\fB\-s \fR\fB\fInum\fR\fR
+.sp
+Start at this page number.
+.TP 3n
+\(bu
+\fB\-v\fR
+.sp
+Verbose mode; print a progress indicator every five seconds.
+.SH "COPYRIGHT"
+.PP
+Copyright 2007 MySQL AB
+.PP
+This documentation is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License.
+.PP
+This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
+.PP
+You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110\-1301 USA or see http://www.gnu.org/licenses/.
+.PP
+Please email
+<docs at mysql.com>
+for more information or if you are interested in doing a translation.
+.SH "SEE ALSO"
+For more information, please refer to the MySQL Reference Manual,
+which may already be installed locally and which is also available
+online at http://dev.mysql.com/doc/.
+.SH AUTHOR
+MySQL AB (http://www.mysql.com/).
Added: branches/sid-5.0/debian/manpages/make_win_bin_dist.1
===================================================================
--- branches/sid-5.0/debian/manpages/make_win_bin_dist.1 (rev 0)
+++ branches/sid-5.0/debian/manpages/make_win_bin_dist.1 2007-11-26 12:34:29 UTC (rev 1020)
@@ -0,0 +1,110 @@
+.\" Title: \fBmake_win_bin_dist\fR
+.\" Author:
+.\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
+.\" Date: 11/25/2007
+.\" Manual: MySQL Database System
+.\" Source: MySQL 5.0
+.\"
+.TH "\fBMAKE_WIN_BIN_DIST" "1" "11/25/2007" "MySQL 5.0" "MySQL Database System"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
+.SH "NAME"
+make_win_bin_dist \- package MySQL distribution as ZIP archive
+.SH "SYNOPSIS"
+.HP 60
+\fBmake_win_bin_dist [\fR\fB\fIoptions\fR\fR\fB] \fR\fB\fIpackage_basename\fR\fR\fB [\fR\fB\fIcopy_def\fR\fR\fB ...]\fR
+.SH "DESCRIPTION"
+.PP
+This script is used on Windows after building a MySQL distribution from source to create executable programs. It packages the binaries and support files into a ZIP archive that can be unpacked at the location where you want to install MySQL.
+.PP
+\fBmake_win_bin_dist\fR
+is a shell script, so you must have Cygwin installed to use it.
+.PP
+This program's use is subject to change. Currently, you invoke it as follows from the root directory of your source distribution:
+.sp
+.RS 3n
+.nf
+shell> \fBmake_win_bin_dist [\fR\fB\fIoptions\fR\fR\fB] \fR\fB\fIpackage_basename\fR\fR\fB [\fR\fB\fIcopy_def\fR\fR\fB ...]\fR
+.fi
+.RE
+.PP
+The
+\fIpackage_basename\fR
+argument provides the basename for the resulting ZIP archive. This name will be the name of the directory that results from unpacking the archive.
+.PP
+Because you might want to include files of directories from other builds, you can instruct this script do copy them in for you, via
+\fIcopy_def\fR
+arguments, which of which is of the form
+\fIrelative_dest_name\fR=\fIsource_name\fR.
+.PP
+Example:
+.sp
+.RS 3n
+.nf
+bin/mysqld\-max.exe=../my\-max\-build/sql/release/mysqld.exe
+.fi
+.RE
+.PP
+If you specify a directory, the entire directory will be copied.
+.PP
+\fBmake_win_bin_dist\fR
+understands the following options:
+.TP 3n
+\(bu
+\fB\-\-debug\fR
+.sp
+Pack the debug binaries and produce an error if they were not built.
+.TP 3n
+\(bu
+\fB\-\-embedded\fR
+.sp
+Pack the embedded server and produce an error if it was not built. The default is to pack it if it was built.
+.TP 3n
+\(bu
+\fB\-\-exe\-suffix=\fR\fB\fIsuffix\fR\fR
+.sp
+Add a suffix to the basename of the
+\fBmysql\fR
+binary. For example, a suffix of
+\-abc
+produces a binary named
+\fBmysqld\-abc.exe\fR.
+.TP 3n
+\(bu
+\fB\-\-no\-debug\fR
+.sp
+Don't pack the debug binaries even if they were built.
+.TP 3n
+\(bu
+\fB\-\-no\-embedded\fR
+.sp
+Don't pack the embedded server even if it was built.
+.TP 3n
+\(bu
+\fB\-\-only\-debug\fR
+.sp
+Use this option when the target for this build was
+Debug, and you just want to replace the normal binaries with debug versions (that is, do not use separate
+\fIdebug\fR
+directories).
+.SH "COPYRIGHT"
+.PP
+Copyright 2007 MySQL AB
+.PP
+This documentation is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License.
+.PP
+This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
+.PP
+You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110\-1301 USA or see http://www.gnu.org/licenses/.
+.PP
+Please email
+<docs at mysql.com>
+for more information or if you are interested in doing a translation.
+.SH "SEE ALSO"
+For more information, please refer to the MySQL Reference Manual,
+which may already be installed locally and which is also available
+online at http://dev.mysql.com/doc/.
+.SH AUTHOR
+MySQL AB (http://www.mysql.com/).
Added: branches/sid-5.0/debian/manpages/make_win_src_distribution.1
===================================================================
--- branches/sid-5.0/debian/manpages/make_win_src_distribution.1 (rev 0)
+++ branches/sid-5.0/debian/manpages/make_win_src_distribution.1 2007-11-26 12:34:29 UTC (rev 1020)
@@ -0,0 +1,100 @@
+.\" Title: \fBmake_win_src_distribution\fR
+.\" Author:
+.\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
+.\" Date: 11/25/2007
+.\" Manual: MySQL Database System
+.\" Source: MySQL 5.0
+.\"
+.TH "\fBMAKE_WIN_SRC_DIST" "1" "11/25/2007" "MySQL 5.0" "MySQL Database System"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
+.SH "NAME"
+make_win_src_distribution \- create source distribution for Windows
+.SH "SYNOPSIS"
+.HP 36
+\fBmake_win_src_distribution [\fR\fB\fIoptions\fR\fR\fB]\fR
+.SH "DESCRIPTION"
+.PP
+\fBmake_win_src_distribution\fR
+creates a Windows source package to be used on Windows systems. It is used after you configure and build the source distribution on a Unix or Unix\-like system so that you have a server binary to work with. (See the instructions at
+Section\ 4.15.6.5, \(lqCreating a Windows Source Package from the BitKeeper Repository\(rq.)
+.PP
+Invoke
+\fBmake_win_src_distribution\fR
+like this from the top\-level directory of a MySQL source distribution:
+.sp
+.RS 3n
+.nf
+shell> \fBmake_win_src_distribution [\fR\fB\fIoptions\fR\fR\fB]\fR
+.fi
+.RE
+.PP
+\fBmake_win_src_distribution\fR
+understands the following options:
+.TP 3n
+\(bu
+\fB\-\-help\fR
+.sp
+Display a help message and exit.
+.TP 3n
+\(bu
+\fB\-\-debug\fR
+.sp
+Print information about script operations; do not create a package.
+.TP 3n
+\(bu
+\fB\-\-tmp\fR
+.sp
+Specify the temporary location.
+.TP 3n
+\(bu
+\fB\-\-suffix\fR
+.sp
+The suffix name for the package.
+.TP 3n
+\(bu
+\fB\-\-dirname\fR
+.sp
+Directory name to copy files (intermediate).
+.TP 3n
+\(bu
+\fB\-\-silent\fR
+.sp
+Do not print verbose list of files processed.
+.TP 3n
+\(bu
+\fB\-\-tar\fR
+.sp
+Create a
+\fItar.gz\fR
+package instead of a
+\fI.zip\fR
+package.
+.sp
+By default,
+\fBmake_win_src_distribution\fR
+creates a Zip\-format archive with the name
+\fImysql\-\fR\fI\fIVERSION\fR\fR\fI\-win\-src.zip\fR, where
+\fIVERSION\fR
+represents the version of your MySQL source tree.
+.SH "COPYRIGHT"
+.PP
+Copyright 2007 MySQL AB
+.PP
+This documentation is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License.
+.PP
+This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
+.PP
+You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110\-1301 USA or see http://www.gnu.org/licenses/.
+.PP
+Please email
+<docs at mysql.com>
+for more information or if you are interested in doing a translation.
+.SH "SEE ALSO"
+For more information, please refer to the MySQL Reference Manual,
+which may already be installed locally and which is also available
+online at http://dev.mysql.com/doc/.
+.SH AUTHOR
+MySQL AB (http://www.mysql.com/).
Added: branches/sid-5.0/debian/manpages/msql2mysql.1
===================================================================
--- branches/sid-5.0/debian/manpages/msql2mysql.1 (rev 0)
+++ branches/sid-5.0/debian/manpages/msql2mysql.1 2007-11-26 12:34:29 UTC (rev 1020)
@@ -0,0 +1,65 @@
+.\" Title: \fBmsql2mysql\fR
+.\" Author:
+.\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
+.\" Date: 11/25/2007
+.\" Manual: MySQL Database System
+.\" Source: MySQL 5.0
+.\"
+.TH "\fBMSQL2MYSQL\fR" "1" "11/25/2007" "MySQL 5.0" "MySQL Database System"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
+.SH "NAME"
+msql2mysql \- convert mSQL programs for use with MySQL
+.SH "SYNOPSIS"
+.HP 28
+\fBmsql2mysql\fR\fB\fIC\-source\-file\fR\fR\fB ...\fR
+.SH "DESCRIPTION"
+.PP
+Initially, the MySQL C API was developed to be very similar to that for the mSQL database system. Because of this, mSQL programs often can be converted relatively easily for use with MySQL by changing the names of the C API functions.
+.PP
+The
+\fBmsql2mysql\fR
+utility performs the conversion of mSQL C API function calls to their MySQL equivalents.
+\fBmsql2mysql\fR
+converts the input file in place, so make a copy of the original before converting it. For example, use
+\fBmsql2mysql\fR
+like this:
+.sp
+.RS 3n
+.nf
+shell> \fBcp client\-prog.c client\-prog.c.orig\fR
+shell> \fBmsql2mysql client\-prog.c\fR
+client\-prog.c converted
+.fi
+.RE
+.PP
+Then examine
+\fIclient\-prog.c\fR
+and make any post\-conversion revisions that may be necessary.
+.PP
+\fBmsql2mysql\fR
+uses the
+\fBreplace\fR
+utility to make the function name substitutions. See
+\fBreplace\fR(1).
+.SH "COPYRIGHT"
+.PP
+Copyright 2007 MySQL AB
+.PP
+This documentation is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License.
+.PP
+This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
+.PP
+You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110\-1301 USA or see http://www.gnu.org/licenses/.
+.PP
+Please email
+<docs at mysql.com>
+for more information or if you are interested in doing a translation.
+.SH "SEE ALSO"
+For more information, please refer to the MySQL Reference Manual,
+which may already be installed locally and which is also available
+online at http://dev.mysql.com/doc/.
+.SH AUTHOR
+MySQL AB (http://www.mysql.com/).
Added: branches/sid-5.0/debian/manpages/my_print_defaults.1
===================================================================
--- branches/sid-5.0/debian/manpages/my_print_defaults.1 (rev 0)
+++ branches/sid-5.0/debian/manpages/my_print_defaults.1 2007-11-26 12:34:29 UTC (rev 1020)
@@ -0,0 +1,115 @@
+.\" Title: \fBmy_print_defaults\fR
+.\" Author:
+.\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
+.\" Date: 11/25/2007
+.\" Manual: MySQL Database System
+.\" Source: MySQL 5.0
+.\"
+.TH "\fBMY_PRINT_DEFAULTS" "1" "11/25/2007" "MySQL 5.0" "MySQL Database System"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
+.SH "NAME"
+my_print_defaults \- display options from option files
+.SH "SYNOPSIS"
+.HP 45
+\fBmy_print_defaults [\fR\fB\fIoptions\fR\fR\fB] \fR\fB\fIoption_group\fR\fR\fB ...\fR
+.SH "DESCRIPTION"
+.PP
+\fBmy_print_defaults\fR
+displays the options that are present in option groups of option files. The output indicates what options will be used by programs that read the specified option groups. For example, the
+\fBmysqlcheck\fR
+program reads the
+[mysqlcheck]
+and
+[client]
+option groups. To see what options are present in those groups in the standard option files, invoke
+\fBmy_print_defaults\fR
+like this:
+.sp
+.RS 3n
+.nf
+shell> \fBmy_print_defaults mysqlcheck client\fR
+\-\-user=myusername
+\-\-password=secret
+\-\-host=localhost
+.fi
+.RE
+.PP
+The output consists of options, one per line, in the form that they would be specified on the command line.
+.PP
+my_print_defaults
+understands the following options:
+.TP 3n
+\(bu
+\fB\-\-help\fR,
+\fB\-?\fR
+.sp
+Display a help message and exit.
+.TP 3n
+\(bu
+\fB\-\-config\-file=\fR\fB\fIfile_name\fR\fR,
+\fB\-\-defaults\-file=\fR\fB\fIfile_name\fR\fR,
+\fB\-c \fR\fB\fIfile_name\fR\fR
+.sp
+Read only the given option file.
+.TP 3n
+\(bu
+\fB\-\-debug=\fR\fB\fIdebug_options\fR\fR\fB, \-# \fR\fB\fIdebug_options\fR\fR
+.sp
+Write a debugging log. The
+\fIdebug_options\fR
+string often is
+\'d:t:o,\fIfile_name\fR'. The default is
+\'d:t:o,/tmp/my_print_defaults.trace'.
+.TP 3n
+\(bu
+\fB\-\-defaults\-extra\-file=\fR\fB\fIfile_name\fR\fR,
+\fB\-\-extra\-file=\fR\fB\fIfile_name\fR\fR,
+\fB\-e \fR\fB\fIfile_name\fR\fR
+.sp
+Read this option file after the global option file but (on Unix) before the user option file.
+.TP 3n
+\(bu
+\fB\-\-defaults\-group\-suffix=\fR\fB\fIsuffix\fR\fR,
+\fB\-g \fR\fB\fIsuffix\fR\fR
+.sp
+In addition to the groups named on the command line, read groups that have the given suffix.
+.TP 3n
+\(bu
+\fB\-\-no\-defaults\fR,
+\fB\-n\fR
+.sp
+Return an empty string.
+.TP 3n
+\(bu
+\fB\-\-verbose\fR,
+\fB\-v\fR
+.sp
+Verbose mode. Print more information about what the program does.
+.TP 3n
+\(bu
+\fB\-\-version\fR,
+\fB\-V\fR
+.sp
+Display version information and exit.
+.SH "COPYRIGHT"
+.PP
+Copyright 2007 MySQL AB
+.PP
+This documentation is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License.
+.PP
+This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
+.PP
+You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110\-1301 USA or see http://www.gnu.org/licenses/.
+.PP
+Please email
+<docs at mysql.com>
+for more information or if you are interested in doing a translation.
+.SH "SEE ALSO"
+For more information, please refer to the MySQL Reference Manual,
+which may already be installed locally and which is also available
+online at http://dev.mysql.com/doc/.
+.SH AUTHOR
+MySQL AB (http://www.mysql.com/).
Added: branches/sid-5.0/debian/manpages/myisam_ftdump.1
===================================================================
--- branches/sid-5.0/debian/manpages/myisam_ftdump.1 (rev 0)
+++ branches/sid-5.0/debian/manpages/myisam_ftdump.1 2007-11-26 12:34:29 UTC (rev 1020)
@@ -0,0 +1,155 @@
+.\" Title: \fBmyisam_ftdump\fR
+.\" Author:
+.\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
+.\" Date: 11/25/2007
+.\" Manual: MySQL Database System
+.\" Source: MySQL 5.0
+.\"
+.TH "\fBMYISAM_FTDUMP\fR" "1" "11/25/2007" "MySQL 5.0" "MySQL Database System"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
+.SH "NAME"
+myisam_ftdump \- display full\-text index information
+.SH "SYNOPSIS"
+.HP 43
+\fBmyisam_ftdump [\fR\fB\fIoptions\fR\fR\fB] \fR\fB\fItbl_name\fR\fR\fB \fR\fB\fIindex_num\fR\fR
+.SH "DESCRIPTION"
+.PP
+\fBmyisam_ftdump\fR
+displays information about
+FULLTEXT
+indexes in
+MyISAM
+tables. It reads the
+MyISAM
+index file directly, so it must be run on the server host where the table is located
+.PP
+Invoke
+\fBmyisam_ftdump\fR
+like this:
+.sp
+.RS 3n
+.nf
+shell> \fBmyisam_ftdump [\fR\fB\fIoptions\fR\fR\fB] \fR\fB\fItbl_name\fR\fR\fB \fR\fB\fIindex_num\fR\fR
+.fi
+.RE
+.PP
+The
+\fItbl_name\fR
+argument should be the name of a
+MyISAM
+table. You can also specify a table by naming its index file (the file with the
+\fI.MYI\fR
+suffix). If you do not invoke
+\fBmyisam_ftdump\fR
+in the directory where the table files are located, the table or index file name must be preceded by the pathname to the table's database directory. Index numbers begin with 0.
+.PP
+Example: Suppose that the
+test
+database contains a table named
+mytexttablel
+that has the following definition:
+.sp
+.RS 3n
+.nf
+CREATE TABLE mytexttable
+(
+ id INT NOT NULL,
+ txt TEXT NOT NULL,
+ PRIMARY KEY (id),
+ FULLTEXT (txt)
+);
+.fi
+.RE
+.PP
+The index on
+id
+is index 0 and the
+FULLTEXT
+index on
+txt
+is index 1. If your working directory is the
+test
+database directory, invoke
+\fBmyisam_ftdump\fR
+as follows:
+.sp
+.RS 3n
+.nf
+shell> \fBmyisam_ftdump mytexttable 1\fR
+.fi
+.RE
+.PP
+If the pathname to the
+test
+database directory is
+\fI/usr/local/mysql/data/test\fR, you can also specify the table name argument using that pathname. This is useful if you do not invoke
+\fBmyisam_ftdump\fR
+in the database directory:
+.sp
+.RS 3n
+.nf
+shell> \fBmyisam_ftdump /usr/local/mysql/data/test/mytexttable 1\fR
+.fi
+.RE
+.PP
+\fBmyisam_ftdump\fR
+understands the following options:
+.TP 3n
+\(bu
+\fB\-\-help\fR,
+\fB\-h\fR
+\fB\-?\fR
+.sp
+Display a help message and exit.
+.TP 3n
+\(bu
+\fB\-\-count\fR,
+\fB\-c\fR
+.sp
+Calculate per\-word statistics (counts and global weights).
+.TP 3n
+\(bu
+\fB\-\-dump\fR,
+\fB\-d\fR
+.sp
+Dump the index, including data offsets and word weights.
+.TP 3n
+\(bu
+\fB\-\-length\fR,
+\fB\-l\fR
+.sp
+Report the length distribution.
+.TP 3n
+\(bu
+\fB\-\-stats\fR,
+\fB\-s\fR
+.sp
+Report global index statistics. This is the default operation if no other operation is specified.
+.TP 3n
+\(bu
+\fB\-\-verbose\fR,
+\fB\-v\fR
+.sp
+Verbose mode. Print more output about what the program does.
+.SH "COPYRIGHT"
+.PP
+Copyright 2007 MySQL AB
+.PP
+This documentation is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License.
+.PP
+This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
+.PP
+You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110\-1301 USA or see http://www.gnu.org/licenses/.
+.PP
+Please email
+<docs at mysql.com>
+for more information or if you are interested in doing a translation.
+.SH "SEE ALSO"
+For more information, please refer to the MySQL Reference Manual,
+which may already be installed locally and which is also available
+online at http://dev.mysql.com/doc/.
+.SH AUTHOR
+MySQL AB (http://www.mysql.com/).
Added: branches/sid-5.0/debian/manpages/myisamchk.1
===================================================================
--- branches/sid-5.0/debian/manpages/myisamchk.1 (rev 0)
+++ branches/sid-5.0/debian/manpages/myisamchk.1 2007-11-26 12:34:29 UTC (rev 1020)
@@ -0,0 +1,836 @@
+.\" Title: \fBmyisamchk\fR
+.\" Author:
+.\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
+.\" Date: 11/25/2007
+.\" Manual: MySQL Database System
+.\" Source: MySQL 5.0
+.\"
+.TH "\fBMYISAMCHK\fR" "1" "11/25/2007" "MySQL 5.0" "MySQL Database System"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
+.SH "NAME"
+myisamchk \- MyISAM table\-maintenance utility
+.SH "SYNOPSIS"
+.HP 33
+\fBmyisamchk [\fR\fB\fIoptions\fR\fR\fB] \fR\fB\fItbl_name\fR\fR\fB ...\fR
+.SH "DESCRIPTION"
+.PP
+The
+\fBmyisamchk\fR
+utility gets information about your database tables or checks, repairs, or optimizes them.
+\fBmyisamchk\fR
+works with
+MyISAM
+tables (tables that have
+\fI.MYD\fR
+and
+\fI.MYI\fR
+files for storing data and indexes).
+.sp
+.it 1 an-trap
+.nr an-no-space-flag 1
+.nr an-break-flag 1
+.br
+\fBCaution\fR
+.PP
+It is best to make a backup of a table before performing a table repair operation; under some circumstances the operation might cause data loss. Possible causes include but are not limited to filesystem errors.
+.PP
+Invoke
+\fBmyisamchk\fR
+like this:
+.sp
+.RS 3n
+.nf
+shell> \fBmyisamchk [\fR\fB\fIoptions\fR\fR\fB] \fR\fB\fItbl_name\fR\fR\fB ...\fR
+.fi
+.RE
+.PP
+The
+\fIoptions\fR
+specify what you want
+\fBmyisamchk\fR
+to do. They are described in the following sections. You can also get a list of options by invoking
+\fBmyisamchk \-\-help\fR.
+.PP
+With no options,
+\fBmyisamchk\fR
+simply checks your table as the default operation. To get more information or to tell
+\fBmyisamchk\fR
+to take corrective action, specify options as described in the following discussion.
+.PP
+\fItbl_name\fR
+is the database table you want to check or repair. If you run
+\fBmyisamchk\fR
+somewhere other than in the database directory, you must specify the path to the database directory, because
+\fBmyisamchk\fR
+has no idea where the database is located. In fact,
+\fBmyisamchk\fR
+doesn't actually care whether the files you are working on are located in a database directory. You can copy the files that correspond to a database table into some other location and perform recovery operations on them there.
+.PP
+You can name several tables on the
+\fBmyisamchk\fR
+command line if you wish. You can also specify a table by naming its index file (the file with the
+\fI.MYI\fR
+suffix). This allows you to specify all tables in a directory by using the pattern
+\fI*.MYI\fR. For example, if you are in a database directory, you can check all the
+MyISAM
+tables in that directory like this:
+.sp
+.RS 3n
+.nf
+shell> \fBmyisamchk *.MYI\fR
+.fi
+.RE
+.PP
+If you are not in the database directory, you can check all the tables there by specifying the path to the directory:
+.sp
+.RS 3n
+.nf
+shell> \fBmyisamchk \fR\fB\fI/path/to/database_dir/\fR\fR\fB*.MYI\fR
+.fi
+.RE
+.PP
+You can even check all tables in all databases by specifying a wildcard with the path to the MySQL data directory:
+.sp
+.RS 3n
+.nf
+shell> \fBmyisamchk \fR\fB\fI/path/to/datadir/*/*\fR\fR\fB.MYI\fR
+.fi
+.RE
+.PP
+The recommended way to quickly check all
+MyISAM
+tables is:
+.sp
+.RS 3n
+.nf
+shell> \fBmyisamchk \-\-silent \-\-fast \fR\fB\fI/path/to/datadir/*/*\fR\fR\fB.MYI\fR
+.fi
+.RE
+.PP
+If you want to check all
+MyISAM
+tables and repair any that are corrupted, you can use the following command:
+.sp
+.RS 3n
+.nf
+shell> \fBmyisamchk \-\-silent \-\-force \-\-fast \-\-update\-state \\\fR
+ \fB\-\-key_buffer_size=64M \-\-sort_buffer_size=64M \\\fR
+ \fB\-\-read_buffer_size=1M \-\-write_buffer_size=1M \\\fR
+ \fB\fI/path/to/datadir/*/*\fR\fR\fB.MYI\fR
+.fi
+.RE
+.PP
+This command assumes that you have more than 64MB free. For more information about memory allocation with
+\fBmyisamchk\fR, see
+the section called \(lq\fBMYISAMCHK\fR MEMORY USAGE\(rq.
+.sp
+.it 1 an-trap
+.nr an-no-space-flag 1
+.nr an-break-flag 1
+.br
+\fBImportant\fR
+.PP
+\fIYou must ensure that no other program is using the tables while you are running \fR\fI\fBmyisamchk\fR\fR. The most effective means of doing so is to shut down the MySQL server while running
+\fBmyisamchk\fR, or to lock all tables that
+\fBmyisamchk\fR
+is being used on.
+.PP
+Otherwise, when you run
+\fBmyisamchk\fR, it may display the following error message:
+.sp
+.RS 3n
+.nf
+warning: clients are using or haven't closed the table properly
+.fi
+.RE
+.PP
+This means that you are trying to check a table that has been updated by another program (such as the
+\fBmysqld\fR
+server) that hasn't yet closed the file or that has died without closing the file properly, which can sometimes lead to the corruption of one or more
+MyISAM
+tables.
+.PP
+If
+\fBmysqld\fR
+is running, you must force it to flush any table modifications that are still buffered in memory by using
+FLUSH TABLES. You should then ensure that no one is using the tables while you are running
+\fBmyisamchk\fR
+.PP
+However, the easiest way to avoid this problem is to use
+CHECK TABLE
+instead of
+\fBmyisamchk\fR
+to check tables. See
+Section\ 5.2.3, \(lqCHECK TABLE Syntax\(rq.
+.SH "\fBMYISAMCHK\fR GENERAL OPTIONS"
+.PP
+The options described in this section can be used for any type of table maintenance operation performed by
+\fBmyisamchk\fR. The sections following this one describe options that pertain only to specific operations, such as table checking or repairing.
+.TP 3n
+\(bu
+\fB\-\-help\fR,
+\fB\-?\fR
+.sp
+Display a help message and exit.
+.TP 3n
+\(bu
+\fB\-\-debug=\fR\fB\fIdebug_options\fR\fR\fB, \-# \fR\fB\fIdebug_options\fR\fR
+.sp
+Write a debugging log. The
+\fIdebug_options\fR
+string often is
+\'d:t:o,\fIfile_name\fR'.
+.TP 3n
+\(bu
+\fB\-\-silent\fR,
+\fB\-s\fR
+.sp
+Silent mode. Write output only when errors occur. You can use
+\fB\-s\fR
+twice (\fB\-ss\fR) to make
+\fBmyisamchk\fR
+very silent.
+.TP 3n
+\(bu
+\fB\-\-verbose\fR,
+\fB\-v\fR
+.sp
+Verbose mode. Print more information about what the program does. This can be used with
+\fB\-d\fR
+and
+\fB\-e\fR. Use
+\fB\-v\fR
+multiple times (\fB\-vv\fR,
+\fB\-vvv\fR) for even more output.
+.TP 3n
+\(bu
+\fB\-\-version\fR,
+\fB\-V\fR
+.sp
+Display version information and exit.
+.TP 3n
+\(bu
+\fB\-\-wait\fR,
+\fB\-w\fR
+.sp
+Instead of terminating with an error if the table is locked, wait until the table is unlocked before continuing. If you are running
+\fBmysqld\fR
+with external locking disabled, the table can be locked only by another
+\fBmyisamchk\fR
+command.
+.sp
+.RE
+.PP
+You can also set the following variables by using
+\fB\-\-\fR\fB\fIvar_name\fR\fR\fB=\fR\fB\fIvalue\fR\fR
+syntax:
+.TS
+allbox tab(:);
+l l
+l l
+l l
+l l
+l l
+l l
+l l
+l l
+l l
+l l
+l l
+l l.
+T{
+\fBVariable\fR
+T}:T{
+\fBDefault Value\fR
+T}
+T{
+sort_key_blocks
+T}:T{
+16
+T}
+T{
+stats_method
+T}:T{
+nulls_unequal
+T}
+T{
+write_buffer_size
+T}:T{
+262136
+T}
+T{
+decode_bits
+T}:T{
+9
+T}
+T{
+ft_max_word_len
+T}:T{
+version\-dependent
+T}
+T{
+ft_min_word_len
+T}:T{
+4
+T}
+T{
+ft_stopword_file
+T}:T{
+built\-in list
+T}
+T{
+key_buffer_size
+T}:T{
+523264
+T}
+T{
+myisam_block_size
+T}:T{
+1024
+T}
+T{
+read_buffer_size
+T}:T{
+262136
+T}
+T{
+sort_buffer_size
+T}:T{
+2097144
+T}
+.TE
+.sp
+.PP
+It is also possible to set variables by using
+\fB\-\-set\-variable=\fR\fB\fIvar_name\fR\fR\fB=\fR\fB\fIvalue\fR\fR
+or
+\fB\-O \fR\fB\fIvar_name\fR\fR\fB=\fR\fB\fIvalue\fR\fR
+syntax. However, this syntax is deprecated as of MySQL 4.0.
+.PP
+The possible
+\fBmyisamchk\fR
+variables and their default values can be examined with
+\fBmyisamchk \-\-help\fR:
+.PP
+sort_buffer_size
+is used when the keys are repaired by sorting keys, which is the normal case when you use
+\fB\-\-recover\fR.
+.PP
+key_buffer_size
+is used when you are checking the table with
+\fB\-\-extend\-check\fR
+or when the keys are repaired by inserting keys row by row into the table (like when doing normal inserts). Repairing through the key buffer is used in the following cases:
+.TP 3n
+\(bu
+You use
+\fB\-\-safe\-recover\fR.
+.TP 3n
+\(bu
+The temporary files needed to sort the keys would be more than twice as big as when creating the key file directly. This is often the case when you have large key values for
+CHAR,
+VARCHAR, or
+TEXT
+columns, because the sort operation needs to store the complete key values as it proceeds. If you have lots of temporary space and you can force
+\fBmyisamchk\fR
+to repair by sorting, you can use the
+\fB\-\-sort\-recover\fR
+option.
+.sp
+.RE
+.PP
+Repairing through the key buffer takes much less disk space than using sorting, but is also much slower.
+.PP
+If you want a faster repair, set the
+key_buffer_size
+and
+sort_buffer_size
+variables to about 25% of your available memory. You can set both variables to large values, because only one of them is used at a time.
+.PP
+myisam_block_size
+is the size used for index blocks.
+.PP
+stats_method
+influences how
+NULL
+values are treated for index statistics collection when the
+\fB\-\-analyze\fR
+option is given. It acts like the
+myisam_stats_method
+system variable. For more information, see the description of
+myisam_stats_method
+in
+the section called \(lqSYSTEM VARIABLES\(rq, and
+Section\ 4.7, \(lqMyISAM Index Statistics Collection\(rq. For MySQL 5.0,
+stats_method
+was added in MySQL 5.0.14. For older versions, the statistics collection method is equivalent to
+nulls_equal.
+.PP
+The
+ft_min_word_len
+and
+ft_max_word_len
+variables are available as of MySQL 4.0.0.
+ft_stopword_file
+is available as of MySQL 4.0.19.
+.PP
+ft_min_word_len
+and
+ft_max_word_len
+indicate the minimum and maximum word length for
+FULLTEXT
+indexes.
+ft_stopword_file
+names the stopword file. These need to be set under the following circumstances.
+.PP
+If you use
+\fBmyisamchk\fR
+to perform an operation that modifies table indexes (such as repair or analyze), the
+FULLTEXT
+indexes are rebuilt using the default full\-text parameter values for minimum and maximum word length and the stopword file unless you specify otherwise. This can result in queries failing.
+.PP
+The problem occurs because these parameters are known only by the server. They are not stored in
+MyISAM
+index files. To avoid the problem if you have modified the minimum or maximum word length or the stopword file in the server, specify the same
+ft_min_word_len,
+ft_max_word_len, and
+ft_stopword_file
+values to
+\fBmyisamchk\fR
+that you use for
+\fBmysqld\fR. For example, if you have set the minimum word length to 3, you can repair a table with
+\fBmyisamchk\fR
+like this:
+.sp
+.RS 3n
+.nf
+shell> \fBmyisamchk \-\-recover \-\-ft_min_word_len=3 \fR\fB\fItbl_name\fR\fR\fB.MYI\fR
+.fi
+.RE
+.PP
+To ensure that
+\fBmyisamchk\fR
+and the server use the same values for full\-text parameters, you can place each one in both the
+[mysqld]
+and
+[myisamchk]
+sections of an option file:
+.sp
+.RS 3n
+.nf
+[mysqld]
+ft_min_word_len=3
+[myisamchk]
+ft_min_word_len=3
+.fi
+.RE
+.PP
+An alternative to using
+\fBmyisamchk\fR
+is to use the
+REPAIR TABLE,
+ANALYZE TABLE,
+OPTIMIZE TABLE, or
+ALTER TABLE. These statements are performed by the server, which knows the proper full\-text parameter values to use.
+.SH "\fBMYISAMCHK\fR CHECK OPTIONS"
+.PP
+\fBmyisamchk\fR
+supports the following options for table checking operations:
+.TP 3n
+\(bu
+\fB\-\-check\fR,
+\fB\-c\fR
+.sp
+Check the table for errors. This is the default operation if you specify no option that selects an operation type explicitly.
+.TP 3n
+\(bu
+\fB\-\-check\-only\-changed\fR,
+\fB\-C\fR
+.sp
+Check only tables that have changed since the last check.
+.TP 3n
+\(bu
+\fB\-\-extend\-check\fR,
+\fB\-e\fR
+.sp
+Check the table very thoroughly. This is quite slow if the table has many indexes. This option should only be used in extreme cases. Normally,
+\fBmyisamchk\fR
+or
+\fBmyisamchk \-\-medium\-check\fR
+should be able to determine whether there are any errors in the table.
+.sp
+If you are using
+\fB\-\-extend\-check\fR
+and have plenty of memory, setting the
+key_buffer_size
+variable to a large value helps the repair operation run faster.
+.TP 3n
+\(bu
+\fB\-\-fast\fR,
+\fB\-F\fR
+.sp
+Check only tables that haven't been closed properly.
+.TP 3n
+\(bu
+\fB\-\-force\fR,
+\fB\-f\fR
+.sp
+Do a repair operation automatically if
+\fBmyisamchk\fR
+finds any errors in the table. The repair type is the same as that specified with the
+\fB\-\-recover\fR
+or
+\fB\-r\fR
+option.
+.TP 3n
+\(bu
+\fB\-\-information\fR,
+\fB\-i\fR
+.sp
+Print informational statistics about the table that is checked.
+.TP 3n
+\(bu
+\fB\-\-medium\-check\fR,
+\fB\-m\fR
+.sp
+Do a check that is faster than an
+\fB\-\-extend\-check\fR
+operation. This finds only 99.99% of all errors, which should be good enough in most cases.
+.TP 3n
+\(bu
+\fB\-\-read\-only\fR,
+\fB\-T\fR
+.sp
+Don't mark the table as checked. This is useful if you use
+\fBmyisamchk\fR
+to check a table that is in use by some other application that doesn't use locking, such as
+\fBmysqld\fR
+when run with external locking disabled.
+.TP 3n
+\(bu
+\fB\-\-update\-state\fR,
+\fB\-U\fR
+.sp
+Store information in the
+\fI.MYI\fR
+file to indicate when the table was checked and whether the table crashed. This should be used to get full benefit of the
+\fB\-\-check\-only\-changed\fR
+option, but you shouldn't use this option if the
+\fBmysqld\fR
+server is using the table and you are running it with external locking disabled.
+.SH "\fBMYISAMCHK\fR REPAIR OPTIONS"
+.PP
+\fBmyisamchk\fR
+supports the following options for table repair operations:
+.TP 3n
+\(bu
+\fB\-\-backup\fR,
+\fB\-B\fR
+.sp
+Make a backup of the
+\fI.MYD\fR
+file as
+\fI\fIfile_name\fR\fR\fI\-\fR\fI\fItime\fR\fR\fI.BAK\fR
+.TP 3n
+\(bu
+\fB\-\-character\-sets\-dir=\fR\fB\fIpath\fR\fR
+.sp
+The directory where character sets are installed. See
+Section\ 2, \(lqThe Character Set Used for Data and Sorting\(rq.
+.TP 3n
+\(bu
+\fB\-\-correct\-checksum\fR
+.sp
+Correct the checksum information for the table.
+.TP 3n
+\(bu
+\fB\-\-data\-file\-length=\fR\fB\fIlen\fR\fR\fB, \-D \fR\fB\fIlen\fR\fR
+.sp
+Maximum length of the data file (when re\-creating data file when it is
+\(lqfull\(rq).
+.TP 3n
+\(bu
+\fB\-\-extend\-check\fR,
+\fB\-e\fR
+.sp
+Do a repair that tries to recover every possible row from the data file. Normally, this also finds a lot of garbage rows. Don't use this option unless you are desperate.
+.TP 3n
+\(bu
+\fB\-\-force\fR,
+\fB\-f\fR
+.sp
+Overwrite old intermediate files (files with names like
+\fI\fItbl_name\fR\fR\fI.TMD\fR) instead of aborting.
+.TP 3n
+\(bu
+\fB\-\-keys\-used=\fR\fB\fIval\fR\fR,
+\fB\-k \fR\fB\fIval\fR\fR
+.sp
+For
+\fBmyisamchk\fR, the option value is a bit\-value that indicates which indexes to update. Each binary bit of the option value corresponds to a table index, where the first index is bit 0. An option value of 0 disables updates to all indexes, which can be used to get faster inserts. Deactivated indexes can be reactivated by using
+\fBmyisamchk \-r\fR.
+.TP 3n
+\(bu
+\fB\-\-no\-symlinks\fR,
+\fB\-l\fR
+.sp
+Do not follow symbolic links. Normally
+\fBmyisamchk\fR
+repairs the table that a symlink points to. This option does not exist as of MySQL 4.0 because versions from 4.0 on do not remove symlinks during repair operations.
+.TP 3n
+\(bu
+\fB\-\-max\-record\-length=\fR\fB\fIlen\fR\fR
+.sp
+Skip rows larger than the given length if
+\fBmyisamchk\fR
+cannot allocate memory to hold them.
+.TP 3n
+\(bu
+\fB\-\-parallel\-recover\fR,
+\fB\-p\fR
+.sp
+Uses the same technique as
+\fB\-r\fR
+and
+\fB\-n\fR, but creates all the keys in parallel, using different threads.
+\fIThis is beta\-quality code. Use at your own risk!\fR
+.TP 3n
+\(bu
+\fB\-\-quick\fR,
+\fB\-q\fR
+.sp
+Achieve a faster repair by not modifying the data file. You can specify this option twice to force
+\fBmyisamchk\fR
+to modify the original data file in case of duplicate keys.
+.TP 3n
+\(bu
+\fB\-\-recover\fR,
+\fB\-r\fR
+.sp
+Do a repair that can fix almost any problem except unique keys that aren't unique (which is an extremely unlikely error with
+MyISAM
+tables). If you want to recover a table, this is the option to try first. You should try
+\fB\-\-safe\-recover\fR
+only if
+\fBmyisamchk\fR
+reports that the table can't be recovered using
+\fB\-\-recover\fR. (In the unlikely case that
+\fB\-\-recover\fR
+fails, the data file remains intact.)
+.sp
+If you have lots of memory, you should increase the value of
+sort_buffer_size.
+.TP 3n
+\(bu
+\fB\-\-safe\-recover\fR,
+\fB\-o\fR
+.sp
+Do a repair using an old recovery method that reads through all rows in order and updates all index trees based on the rows found. This is an order of magnitude slower than
+\fB\-\-recover\fR, but can handle a couple of very unlikely cases that
+\fB\-\-recover\fR
+cannot. This recovery method also uses much less disk space than
+\fB\-\-recover\fR. Normally, you should repair first with
+\fB\-\-recover\fR, and then with
+\fB\-\-safe\-recover\fR
+only if
+\fB\-\-recover\fR
+fails.
+.sp
+If you have lots of memory, you should increase the value of
+key_buffer_size.
+.TP 3n
+\(bu
+\fB\-\-set\-character\-set=\fR\fB\fIname\fR\fR
+.sp
+Change the character set used by the table indexes. This option was replaced by
+\fB\-\-set\-collation\fR
+in MySQL 5.0.3.
+.TP 3n
+\(bu
+\fB\-\-set\-collation=\fR\fB\fIname\fR\fR
+.sp
+Specify the collation to use for sorting 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.
+.TP 3n
+\(bu
+\fB\-\-sort\-recover\fR,
+\fB\-n\fR
+.sp
+Force
+\fBmyisamchk\fR
+to use sorting to resolve the keys even if the temporary files would be very large.
+.TP 3n
+\(bu
+\fB\-\-tmpdir=\fR\fB\fIpath\fR\fR,
+\fB\-t \fR\fB\fIpath\fR\fR
+.sp
+Path of the directory to be used for storing temporary files. If this is not set,
+\fBmyisamchk\fR
+uses the value of the
+TMPDIR
+environment variable.
+tmpdir
+can be set to a list of directory paths that are used successively in round\-robin fashion for creating temporary files. The separator character between directory names is the colon (\(lq:\(rq) on Unix and the semicolon (\(lq;\(rq) on Windows, NetWare, and OS/2.
+.TP 3n
+\(bu
+\fB\-\-unpack\fR,
+\fB\-u\fR
+.sp
+Unpack a table that was packed with
+\fBmyisampack\fR.
+.SH "OTHER MYISAMCHK OPTIONS"
+.PP
+\fBmyisamchk\fR
+supports the following options for actions other than table checks and repairs:
+.TP 3n
+\(bu
+\fB\-\-analyze\fR,
+\fB\-a\fR
+.sp
+Analyze the distribution of key values. This improves join performance by enabling the join optimizer to better choose the order in which to join the tables and which indexes it should use. To obtain information about the key distribution, use a
+\fBmyisamchk \-\-description \-\-verbose \fR\fB\fItbl_name\fR\fR
+command or the
+SHOW INDEX FROM \fItbl_name\fR
+statement.
+.TP 3n
+\(bu
+\fB\-\-block\-search=\fR\fB\fIoffset\fR\fR,
+\fB\-b \fR\fB\fIoffset\fR\fR
+.sp
+Find the record that a block at the given offset belongs to.
+.TP 3n
+\(bu
+\fB\-\-description\fR,
+\fB\-d\fR
+.sp
+Print some descriptive information about the table.
+.TP 3n
+\(bu
+\fB\-\-set\-auto\-increment[=\fR\fB\fIvalue\fR\fR\fB]\fR,
+\fB\-A[\fR\fB\fIvalue\fR\fR\fB]\fR
+.sp
+Force
+AUTO_INCREMENT
+numbering for new records to start at the given value (or higher, if there are existing records with
+AUTO_INCREMENT
+values this large). If
+\fIvalue\fR
+is not specified,
+AUTO_INCREMENT
+numbers for new records begin with the largest value currently in the table, plus one.
+.TP 3n
+\(bu
+\fB\-\-sort\-index\fR,
+\fB\-S\fR
+.sp
+Sort the index tree blocks in high\-low order. This optimizes seeks and makes table scans that use indexes faster.
+.TP 3n
+\(bu
+\fB\-\-sort\-records=\fR\fB\fIN\fR\fR,
+\fB\-R \fR\fB\fIN\fR\fR
+.sp
+Sort records according to a particular index. This makes your data much more localized and may speed up range\-based
+SELECT
+and
+ORDER BY
+operations that use this index. (The first time you use this option to sort a table, it may be very slow.) To determine a table's index numbers, use
+SHOW INDEX, which displays a table's indexes in the same order that
+\fBmyisamchk\fR
+sees them. Indexes are numbered beginning with 1.
+.sp
+If keys are not packed (PACK_KEYS=0), they have the same length, so when
+\fBmyisamchk\fR
+sorts and moves records, it just overwrites record offsets in the index. If keys are packed (PACK_KEYS=1),
+\fBmyisamchk\fR
+must unpack key blocks first, then re\-create indexes and pack the key blocks again. (In this case, re\-creating indexes is faster than updating offsets for each index.)
+.SH "\fBMYISAMCHK\fR MEMORY USAGE"
+.PP
+Memory allocation is important when you run
+\fBmyisamchk\fR.
+\fBmyisamchk\fR
+uses no more memory than its memory\-related variables are set to. If you are going to use
+\fBmyisamchk\fR
+on very large tables, you should first decide how much memory you want it to use. The default is to use only about 3MB to perform repairs. By using larger values, you can get
+\fBmyisamchk\fR
+to operate faster. For example, if you have more than 32MB RAM, you could use options such as these (in addition to any other options you might specify):
+.sp
+.RS 3n
+.nf
+shell> \fBmyisamchk \-\-sort_buffer_size=16M \-\-key_buffer_size=16M \\\fR
+ \fB\-\-read_buffer_size=1M \-\-write_buffer_size=1M ...\fR
+.fi
+.RE
+.PP
+Using
+\fB\-\-sort_buffer_size=16M\fR
+should probably be enough for most cases.
+.PP
+Be aware that
+\fBmyisamchk\fR
+uses temporary files in
+TMPDIR. If
+TMPDIR
+points to a memory filesystem, you may easily get out of memory errors. If this happens, run
+\fBmyisamchk\fR
+with the
+\fB\-\-tmpdir=\fR\fB\fIpath\fR\fR
+option to specify some directory located on a filesystem that has more space.
+.PP
+When repairing,
+\fBmyisamchk\fR
+also needs a lot of disk space:
+.TP 3n
+\(bu
+Double the size of the data file (the original file and a copy). This space is not needed if you do a repair with
+\fB\-\-quick\fR; in this case, only the index file is re\-created. This space is needed on the same filesystem as the original data file! (The copy is created in the same directory as the original.)
+.TP 3n
+\(bu
+Space for the new index file that replaces the old one. The old index file is truncated at the start of the repair operation, so you usually ignore this space. This space is needed on the same filesystem as the original index file!
+.TP 3n
+\(bu
+When using
+\fB\-\-recover\fR
+or
+\fB\-\-sort\-recover\fR
+(but not when using
+\fB\-\-safe\-recover\fR), you need space for a sort buffer. The following formula yields the amount of space required:
+.sp
+.RS 3n
+.nf
+(\fIlargest_key\fR + \fIrow_pointer_length\fR) \(mu \fInumber_of_rows\fR \(mu 2
+.fi
+.RE
+You can check the length of the keys and the
+row_pointer_length
+with
+\fBmyisamchk \-dv \fR\fB\fItbl_name\fR\fR. This space is allocated in the temporary directory (specified by
+TMPDIR
+or
+\fB\-\-tmpdir=\fR\fB\fIpath\fR\fR).
+.sp
+.RE
+.PP
+If you have a problem with disk space during repair, you can try
+\fB\-\-safe\-recover\fR
+instead of
+\fB\-\-recover\fR.
+.SH "COPYRIGHT"
+.PP
+Copyright 2007 MySQL AB
+.PP
+This documentation is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License.
+.PP
+This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
+.PP
+You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110\-1301 USA or see http://www.gnu.org/licenses/.
+.PP
+Please email
+<docs at mysql.com>
+for more information or if you are interested in doing a translation.
+.SH "SEE ALSO"
+For more information, please refer to the MySQL Reference Manual,
+which may already be installed locally and which is also available
+online at http://dev.mysql.com/doc/.
+.SH AUTHOR
+MySQL AB (http://www.mysql.com/).
Added: branches/sid-5.0/debian/manpages/myisamlog.1
===================================================================
--- branches/sid-5.0/debian/manpages/myisamlog.1 (rev 0)
+++ branches/sid-5.0/debian/manpages/myisamlog.1 2007-11-26 12:34:29 UTC (rev 1020)
@@ -0,0 +1,133 @@
+.\" Title: \fBmyisamlog\fR
+.\" Author:
+.\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
+.\" Date: 11/25/2007
+.\" Manual: MySQL Database System
+.\" Source: MySQL 5.0
+.\"
+.TH "\fBMYISAMLOG\fR" "1" "11/25/2007" "MySQL 5.0" "MySQL Database System"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
+.SH "NAME"
+myisamlog \- display MyISAM log file contents
+.SH "SYNOPSIS"
+.HP 46
+\fBmyisamlog [\fR\fB\fIoptions\fR\fR\fB] [\fR\fB\fIlog_file\fR\fR\fB [\fR\fB\fItbl_name\fR\fR\fB] ...]\fR
+.SH "DESCRIPTION"
+.PP
+\fBmyisamlog\fR
+processes the contents of a
+MyISAM
+log file.
+.PP
+Invoke
+\fBmyisamlog\fR
+like this:
+.sp
+.RS 3n
+.nf
+shell> \fBmyisamlog [\fR\fB\fIoptions\fR\fR\fB] [\fR\fB\fIlog_file\fR\fR\fB [\fR\fB\fItbl_name\fR\fR\fB] ...]\fR
+shell> \fBisamlog [\fR\fB\fIoptions\fR\fR\fB] [\fR\fB\fIlog_file\fR\fR\fB [\fR\fB\fItbl_name\fR\fR\fB] ...]\fR
+.fi
+.RE
+.PP
+The default operation is update (\fB\-u\fR). If a recovery is done (\fB\-r\fR), all writes and possibly updates and deletes are done and errors are only counted. The default log file name is
+\fImyisam.log\fR
+for
+\fBmyisamlog\fR
+and
+\fIisam.log\fR
+for
+\fBisamlog\fR
+if no
+\fIlog_file\fR
+argument is given, If tables are named on the command line, only those tables are updated.
+.PP
+\fBmyisamlog\fR
+understands the following options:
+.TP 3n
+\(bu
+\fB\-?\fR,
+\fB\-I\fR
+.sp
+Display a help message and exit.
+.TP 3n
+\(bu
+\fB\-c \fR\fB\fIN\fR\fR
+.sp
+Execute only
+\fIN\fR
+commands.
+.TP 3n
+\(bu
+\fB\-f \fR\fB\fIN\fR\fR
+.sp
+Specify the maximum number of open files.
+.TP 3n
+\(bu
+\fB\-i\fR
+.sp
+Display extra information before exiting.
+.TP 3n
+\(bu
+\fB\-o \fR\fB\fIoffset\fR\fR
+.sp
+Specify the starting offset.
+.TP 3n
+\(bu
+\fB\-p \fR\fB\fIN\fR\fR
+.sp
+Remove
+\fIN\fR
+components from path.
+.TP 3n
+\(bu
+\fB\-r\fR
+.sp
+Perform a recovery operation.
+.TP 3n
+\(bu
+\fB\-R \fR\fB\fIrecord_pos_file record_pos\fR\fR
+.sp
+Specify record position file and record position.
+.TP 3n
+\(bu
+\fB\-u\fR
+.sp
+Perform an update operation.
+.TP 3n
+\(bu
+\fB\-v\fR
+.sp
+Verbose mode. Print more output about what the program does. This option can be given multiple times to produce more and more output.
+.TP 3n
+\(bu
+\fB\-w \fR\fB\fIwrite_file\fR\fR
+.sp
+Specify the write file.
+.TP 3n
+\(bu
+\fB\-V\fR
+.sp
+Display version information.
+.SH "COPYRIGHT"
+.PP
+Copyright 2007 MySQL AB
+.PP
+This documentation is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License.
+.PP
+This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
+.PP
+You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110\-1301 USA or see http://www.gnu.org/licenses/.
+.PP
+Please email
+<docs at mysql.com>
+for more information or if you are interested in doing a translation.
+.SH "SEE ALSO"
+For more information, please refer to the MySQL Reference Manual,
+which may already be installed locally and which is also available
+online at http://dev.mysql.com/doc/.
+.SH AUTHOR
+MySQL AB (http://www.mysql.com/).
Added: branches/sid-5.0/debian/manpages/myisampack.1
===================================================================
--- branches/sid-5.0/debian/manpages/myisampack.1 (rev 0)
+++ branches/sid-5.0/debian/manpages/myisampack.1 2007-11-26 12:34:29 UTC (rev 1020)
@@ -0,0 +1,516 @@
+.\" Title: \fBmyisampack\fR
+.\" Author:
+.\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
+.\" Date: 11/25/2007
+.\" Manual: MySQL Database System
+.\" Source: MySQL 5.0
+.\"
+.TH "\fBMYISAMPACK\fR" "1" "11/25/2007" "MySQL 5.0" "MySQL Database System"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
+.SH "NAME"
+myisampack \- generate compressed, read\-only MyISAM tables
+.SH "SYNOPSIS"
+.HP 35
+\fBmyisampack [\fR\fB\fIoptions\fR\fR\fB] \fR\fB\fIfile_name\fR\fR\fB ...\fR
+.SH "DESCRIPTION"
+.PP
+The
+\fBmyisampack\fR
+utility compresses
+MyISAM
+tables.
+\fBmyisampack\fR
+works by compressing each column in the table separately. Usually,
+\fBmyisampack\fR
+packs the data file 40%\-70%.
+.PP
+When the table is used later, the server reads into memory the information needed to decompress columns. This results in much better performance when accessing individual rows, because you only have to uncompress exactly one row.
+.PP
+MySQL uses
+mmap()
+when possible to perform memory mapping on compressed tables. If
+mmap()
+does not work, MySQL falls back to normal read/write file operations.
+.PP
+Please note the following:
+.TP 3n
+\(bu
+If the
+\fBmysqld\fR
+server was invoked with external locking disabled, it is not a good idea to invoke
+\fBmyisampack\fR
+if the table might be updated by the server during the packing process. It is safest to compress tables with the server stopped.
+.TP 3n
+\(bu
+After packing a table, it becomes read only. This is generally intended (such as when accessing packed tables on a CD). Allowing writes to a packed table is on our TODO list, but with low priority.
+.sp
+.RE
+.PP
+Invoke
+\fBmyisampack\fR
+like this:
+.sp
+.RS 3n
+.nf
+shell> \fBmyisampack [\fR\fB\fIoptions\fR\fR\fB] \fR\fB\fIfile_name\fR\fR\fB ...\fR
+.fi
+.RE
+.PP
+Each filename argument should be the name of an index (\fI.MYI\fR) file. If you are not in the database directory, you should specify the pathname to the file. It is permissible to omit the
+\fI.MYI\fR
+extension.
+.PP
+After you compress a table with
+\fBmyisampack\fR, you should use
+\fBmyisamchk \-rq\fR
+to rebuild its indexes.
+\fBmyisamchk\fR(1).
+.PP
+\fBmyisampack\fR
+supports the following options:
+.TP 3n
+\(bu
+\fB\-\-help\fR,
+\fB\-?\fR
+.sp
+Display a help message and exit.
+.TP 3n
+\(bu
+\fB\-\-backup\fR,
+\fB\-b\fR
+.sp
+Make a backup of each table's data file using the name
+\fI\fItbl_name\fR\fR\fI.OLD\fR.
+.TP 3n
+\(bu
+\fB\-\-character\-sets\-dir=\fR\fB\fIpath\fR\fR
+.sp
+The directory where character sets are installed. See
+Section\ 2, \(lqThe Character Set Used for Data and Sorting\(rq.
+.TP 3n
+\(bu
+\fB\-\-debug[=\fR\fB\fIdebug_options\fR\fR\fB]\fR,
+\fB\-# [\fR\fB\fIdebug_options\fR\fR\fB]\fR
+.sp
+Write a debugging log. The
+\fIdebug_options\fR
+string often is
+\'d:t:o,\fIfile_name\fR'.
+.TP 3n
+\(bu
+\fB\-\-force\fR,
+\fB\-f\fR
+.sp
+Produce a packed table even if it becomes larger than the original or if the intermediate file from an earlier invocation of
+\fBmyisampack\fR
+exists. (\fBmyisampack\fR
+creates an intermediate file named
+\fI\fItbl_name\fR\fR\fI.TMD\fR
+in the database directory while it compresses the table. If you kill
+\fBmyisampack\fR, the
+\fI.TMD\fR
+file might not be deleted.) Normally,
+\fBmyisampack\fR
+exits with an error if it finds that
+\fI\fItbl_name\fR\fR\fI.TMD\fR
+exists. With
+\fB\-\-force\fR,
+\fBmyisampack\fR
+packs the table anyway.
+.TP 3n
+\(bu
+\fB\-\-join=\fR\fB\fIbig_tbl_name\fR\fR,
+\fB\-j \fR\fB\fIbig_tbl_name\fR\fR
+.sp
+Join all tables named on the command line into a single table
+\fIbig_tbl_name\fR. All tables that are to be combined
+\fImust\fR
+have identical structure (same column names and types, same indexes, and so forth).
+.TP 3n
+\(bu
+\fB\-\-silent\fR,
+\fB\-s\fR
+.sp
+Silent mode. Write output only when errors occur.
+.TP 3n
+\(bu
+\fB\-\-test\fR,
+\fB\-t\fR
+.sp
+Do not actually pack the table, just test packing it.
+.TP 3n
+\(bu
+\fB\-\-tmpdir=\fR\fB\fIpath\fR\fR,
+\fB\-T \fR\fB\fIpath\fR\fR
+.sp
+Use the named directory as the location where
+\fBmyisampack\fR
+creates temporary files.
+.TP 3n
+\(bu
+\fB\-\-verbose\fR,
+\fB\-v\fR
+.sp
+Verbose mode. Write information about the progress of the packing operation and its result.
+.TP 3n
+\(bu
+\fB\-\-version\fR,
+\fB\-V\fR
+.sp
+Display version information and exit.
+.TP 3n
+\(bu
+\fB\-\-wait\fR,
+\fB\-w\fR
+.sp
+Wait and retry if the table is in use. If the
+\fBmysqld\fR
+server was invoked with external locking disabled, it is not a good idea to invoke
+\fBmyisampack\fR
+if the table might be updated by the server during the packing process.
+.sp
+.RE
+.PP
+The following sequence of commands illustrates a typical table compression session:
+.sp
+.RS 3n
+.nf
+shell> \fBls \-l station.*\fR
+\-rw\-rw\-r\-\- 1 monty my 994128 Apr 17 19:00 station.MYD
+\-rw\-rw\-r\-\- 1 monty my 53248 Apr 17 19:00 station.MYI
+\-rw\-rw\-r\-\- 1 monty my 5767 Apr 17 19:00 station.frm
+shell> \fBmyisamchk \-dvv station\fR
+MyISAM file: station
+Isam\-version: 2
+Creation time: 1996\-03\-13 10:08:58
+Recover time: 1997\-02\-02 3:06:43
+Data records: 1192 Deleted blocks: 0
+Datafile parts: 1192 Deleted data: 0
+Datafile pointer (bytes): 2 Keyfile pointer (bytes): 2
+Max datafile length: 54657023 Max keyfile length: 33554431
+Recordlength: 834
+Record format: Fixed length
+table description:
+Key Start Len Index Type Root Blocksize Rec/key
+1 2 4 unique unsigned long 1024 1024 1
+2 32 30 multip. text 10240 1024 1
+Field Start Length Type
+1 1 1
+2 2 4
+3 6 4
+4 10 1
+5 11 20
+6 31 1
+7 32 30
+8 62 35
+9 97 35
+10 132 35
+11 167 4
+12 171 16
+13 187 35
+14 222 4
+15 226 16
+16 242 20
+17 262 20
+18 282 20
+19 302 30
+20 332 4
+21 336 4
+22 340 1
+23 341 8
+24 349 8
+25 357 8
+26 365 2
+27 367 2
+28 369 4
+29 373 4
+30 377 1
+31 378 2
+32 380 8
+33 388 4
+34 392 4
+35 396 4
+36 400 4
+37 404 1
+38 405 4
+39 409 4
+40 413 4
+41 417 4
+42 421 4
+43 425 4
+44 429 20
+45 449 30
+46 479 1
+47 480 1
+48 481 79
+49 560 79
+50 639 79
+51 718 79
+52 797 8
+53 805 1
+54 806 1
+55 807 20
+56 827 4
+57 831 4
+shell> \fBmyisampack station.MYI\fR
+Compressing station.MYI: (1192 records)
+\- Calculating statistics
+normal: 20 empty\-space: 16 empty\-zero: 12 empty\-fill: 11
+pre\-space: 0 end\-space: 12 table\-lookups: 5 zero: 7
+Original trees: 57 After join: 17
+\- Compressing file
+87.14%
+Remember to run myisamchk \-rq on compressed tables
+shell> \fBls \-l station.*\fR
+\-rw\-rw\-r\-\- 1 monty my 127874 Apr 17 19:00 station.MYD
+\-rw\-rw\-r\-\- 1 monty my 55296 Apr 17 19:04 station.MYI
+\-rw\-rw\-r\-\- 1 monty my 5767 Apr 17 19:00 station.frm
+shell> \fBmyisamchk \-dvv station\fR
+MyISAM file: station
+Isam\-version: 2
+Creation time: 1996\-03\-13 10:08:58
+Recover time: 1997\-04\-17 19:04:26
+Data records: 1192 Deleted blocks: 0
+Datafile parts: 1192 Deleted data: 0
+Datafile pointer (bytes): 3 Keyfile pointer (bytes): 1
+Max datafile length: 16777215 Max keyfile length: 131071
+Recordlength: 834
+Record format: Compressed
+table description:
+Key Start Len Index Type Root Blocksize Rec/key
+1 2 4 unique unsigned long 10240 1024 1
+2 32 30 multip. text 54272 1024 1
+Field Start Length Type Huff tree Bits
+1 1 1 constant 1 0
+2 2 4 zerofill(1) 2 9
+3 6 4 no zeros, zerofill(1) 2 9
+4 10 1 3 9
+5 11 20 table\-lookup 4 0
+6 31 1 3 9
+7 32 30 no endspace, not_always 5 9
+8 62 35 no endspace, not_always, no empty 6 9
+9 97 35 no empty 7 9
+10 132 35 no endspace, not_always, no empty 6 9
+11 167 4 zerofill(1) 2 9
+12 171 16 no endspace, not_always, no empty 5 9
+13 187 35 no endspace, not_always, no empty 6 9
+14 222 4 zerofill(1) 2 9
+15 226 16 no endspace, not_always, no empty 5 9
+16 242 20 no endspace, not_always 8 9
+17 262 20 no endspace, no empty 8 9
+18 282 20 no endspace, no empty 5 9
+19 302 30 no endspace, no empty 6 9
+20 332 4 always zero 2 9
+21 336 4 always zero 2 9
+22 340 1 3 9
+23 341 8 table\-lookup 9 0
+24 349 8 table\-lookup 10 0
+25 357 8 always zero 2 9
+26 365 2 2 9
+27 367 2 no zeros, zerofill(1) 2 9
+28 369 4 no zeros, zerofill(1) 2 9
+29 373 4 table\-lookup 11 0
+30 377 1 3 9
+31 378 2 no zeros, zerofill(1) 2 9
+32 380 8 no zeros 2 9
+33 388 4 always zero 2 9
+34 392 4 table\-lookup 12 0
+35 396 4 no zeros, zerofill(1) 13 9
+36 400 4 no zeros, zerofill(1) 2 9
+37 404 1 2 9
+38 405 4 no zeros 2 9
+39 409 4 always zero 2 9
+40 413 4 no zeros 2 9
+41 417 4 always zero 2 9
+42 421 4 no zeros 2 9
+43 425 4 always zero 2 9
+44 429 20 no empty 3 9
+45 449 30 no empty 3 9
+46 479 1 14 4
+47 480 1 14 4
+48 481 79 no endspace, no empty 15 9
+49 560 79 no empty 2 9
+50 639 79 no empty 2 9
+51 718 79 no endspace 16 9
+52 797 8 no empty 2 9
+53 805 1 17 1
+54 806 1 3 9
+55 807 20 no empty 3 9
+56 827 4 no zeros, zerofill(2) 2 9
+57 831 4 no zeros, zerofill(1) 2 9
+.fi
+.RE
+.PP
+\fBmyisampack\fR
+displays the following kinds of information:
+.TP 3n
+\(bu
+normal
+.sp
+The number of columns for which no extra packing is used.
+.TP 3n
+\(bu
+empty\-space
+.sp
+The number of columns containing values that are only spaces. These occupy one bit.
+.TP 3n
+\(bu
+empty\-zero
+.sp
+The number of columns containing values that are only binary zeros. These occupy one bit.
+.TP 3n
+\(bu
+empty\-fill
+.sp
+The number of integer columns that do not occupy the full byte range of their type. These are changed to a smaller type. For example, a
+BIGINT
+column (eight bytes) can be stored as a
+TINYINT
+column (one byte) if all its values are in the range from
+\-128
+to
+127.
+.TP 3n
+\(bu
+pre\-space
+.sp
+The number of decimal columns that are stored with leading spaces. In this case, each value contains a count for the number of leading spaces.
+.TP 3n
+\(bu
+end\-space
+.sp
+The number of columns that have a lot of trailing spaces. In this case, each value contains a count for the number of trailing spaces.
+.TP 3n
+\(bu
+table\-lookup
+.sp
+The column had only a small number of different values, which were converted to an
+ENUM
+before Huffman compression.
+.TP 3n
+\(bu
+zero
+.sp
+The number of columns for which all values are zero.
+.TP 3n
+\(bu
+Original trees
+.sp
+The initial number of Huffman trees.
+.TP 3n
+\(bu
+After join
+.sp
+The number of distinct Huffman trees left after joining trees to save some header space.
+.sp
+.RE
+.PP
+After a table has been compressed,
+\fBmyisamchk \-dvv\fR
+prints additional information about each column:
+.TP 3n
+\(bu
+Type
+.sp
+The data type. The value may contain any of the following descriptors:
+.RS 3n
+.TP 3n
+\(bu
+constant
+.sp
+All rows have the same value.
+.TP 3n
+\(bu
+no endspace
+.sp
+Do not store endspace.
+.TP 3n
+\(bu
+no endspace, not_always
+.sp
+Do not store endspace and do not do endspace compression for all values.
+.TP 3n
+\(bu
+no endspace, no empty
+.sp
+Do not store endspace. Do not store empty values.
+.TP 3n
+\(bu
+table\-lookup
+.sp
+The column was converted to an
+ENUM.
+.TP 3n
+\(bu
+zerofill(\fIN\fR)
+.sp
+The most significant
+\fIN\fR
+bytes in the value are always 0 and are not stored.
+.TP 3n
+\(bu
+no zeros
+.sp
+Do not store zeros.
+.TP 3n
+\(bu
+always zero
+.sp
+Zero values are stored using one bit.
+.RE
+.TP 3n
+\(bu
+Huff tree
+.sp
+The number of the Huffman tree associated with the column.
+.TP 3n
+\(bu
+Bits
+.sp
+The number of bits used in the Huffman tree.
+.sp
+.RE
+.PP
+After you run
+\fBmyisampack\fR, you must run
+\fBmyisamchk\fR
+to re\-create any indexes. At this time, you can also sort the index blocks and create statistics needed for the MySQL optimizer to work more efficiently:
+.sp
+.RS 3n
+.nf
+shell> \fBmyisamchk \-rq \-\-sort\-index \-\-analyze \fR\fB\fItbl_name\fR\fR\fB.MYI\fR
+.fi
+.RE
+.PP
+After you have installed the packed table into the MySQL database directory, you should execute
+\fBmysqladmin flush\-tables\fR
+to force
+\fBmysqld\fR
+to start using the new table.
+.PP
+To unpack a packed table, use the
+\fB\-\-unpack\fR
+option to
+\fBmyisamchk\fR.
+.SH "COPYRIGHT"
+.PP
+Copyright 2007 MySQL AB
+.PP
+This documentation is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License.
+.PP
+This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
+.PP
+You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110\-1301 USA or see http://www.gnu.org/licenses/.
+.PP
+Please email
+<docs at mysql.com>
+for more information or if you are interested in doing a translation.
+.SH "SEE ALSO"
+For more information, please refer to the MySQL Reference Manual,
+which may already be installed locally and which is also available
+online at http://dev.mysql.com/doc/.
+.SH AUTHOR
+MySQL AB (http://www.mysql.com/).
Added: branches/sid-5.0/debian/manpages/mysql-stress-test.pl.1
===================================================================
--- branches/sid-5.0/debian/manpages/mysql-stress-test.pl.1 (rev 0)
+++ branches/sid-5.0/debian/manpages/mysql-stress-test.pl.1 2007-11-26 12:34:29 UTC (rev 1020)
@@ -0,0 +1,238 @@
+.\" Title: \fBmysql\-stress\-test.pl\fR
+.\" Author:
+.\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
+.\" Date: 11/21/2007
+.\" Manual: MySQL Database System
+.\" Source: MySQL
+.\"
+.TH "\fBMYSQL\-STRESS\-TEST" "1" "11/21/2007" "MySQL" "MySQL Database System"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
+.SH "NAME"
+mysql\-stress\-test.pl \- server stress test program
+.SH "SYNOPSIS"
+.HP 31
+\fBmysql\-stress\-test.pl [\fR\fB\fIoptions\fR\fR\fB]\fR
+.SH "DESCRIPTION"
+.PP
+The
+\fBmysql\-stress\-test.pl\fR
+Perl script performs stress\-testing of the MySQL server. (MySQL 5.0 and up only)
+.PP
+\fBmysql\-stress\-test.pl\fR
+requires a version of Perl that has been built with threads support.
+.PP
+Invoke
+\fBmysql\-stress\-test.pl\fR
+like this:
+.sp
+.RS 3n
+.nf
+shell> \fBmysql\-stress\-test.pl [\fR\fB\fIoptions\fR\fR\fB]\fR
+.fi
+.RE
+.PP
+\fBmysql\-stress\-test.pl\fR
+supports the following options:
+.TP 3n
+\(bu
+\fB\-\-help\fR
+.sp
+Display a help message and exit.
+.TP 3n
+\(bu
+\fB\-\-abort\-on\-error\fR
+.sp
+Unknown.
+.TP 3n
+\(bu
+\fB\-\-check\-tests\-file\fR
+.sp
+Periodically check the file that lists the tests to be run. If it has been modified, reread the file. This can be useful if you update the list of tests to be run during a stress test.
+.TP 3n
+\(bu
+\fB\-\-cleanup\fR
+.sp
+Force cleanup of the working directory.
+.TP 3n
+\(bu
+\fB\-\-log\-error\-details\fR
+.sp
+Log error details in the global error log file.
+.TP 3n
+\(bu
+\fB\-\-loop\-count=\fR\fB\fIN\fR\fR
+.sp
+In sequential test mode, the number of loops to execute before exiting.
+.TP 3n
+\(bu
+\fB\-\-mysqltest=\fR\fB\fIpath\fR\fR
+.sp
+The pathname to the
+\fBmysqltest\fR
+program.
+.TP 3n
+\(bu
+\fB\-\-server\-database=\fR\fB\fIdb_name\fR\fR
+.sp
+The database to use for the tests.
+.TP 3n
+\(bu
+\fB\-\-server\-host=\fR\fB\fIhost_name\fR\fR
+.sp
+The hostname of the local host to use for making a TCP/IP connection to the local server. By default, the connection is made to
+localhost
+using a Unix socket file.
+.TP 3n
+\(bu
+\fB\-\-server\-logs\-dir=\fR\fB\fIpath\fR\fR
+.sp
+This option is required.
+\fIpath\fR
+is the directory where all client session logs will be stored. Usually this is the shared directory that is associated with the server used for testing.
+.TP 3n
+\(bu
+\fB\-\-server\-password=\fR\fB\fIpassword\fR\fR
+.sp
+The password to use when connecting to the server.
+.TP 3n
+\(bu
+\fB\-\-server\-port=\fR\fB\fIport_num\fR\fR
+.sp
+The TCP/IP port number to use for connecting to the server. The default is 3306.
+.TP 3n
+\(bu
+\fB\-\-server\-socket=\fR\fB\fIfile_name\fR\fR
+.sp
+For connections to
+localhost, the Unix socket file to use, or, on Windows, the name of the named pipe to use. The default if
+\fI/tmp/mysql.sock\fR.
+.TP 3n
+\(bu
+\fB\-\-server\-user=\fR\fB\fIuser_name\fR\fR
+.sp
+The MySQL username to use when connecting to the server. The default is
+root.
+.TP 3n
+\(bu
+\fB\-\-sleep\-time=\fR\fB\fIN\fR\fR
+.sp
+The delay in seconds between test executions.
+.TP 3n
+\(bu
+\fB\-\-stress\-basedir=\fR\fB\fIpath\fR\fR
+.sp
+This option is required.
+\fIpath\fR
+is the working directory for the test run. It is used as the temporary location for result tracking during testing.
+.TP 3n
+\(bu
+\fB\-\-stress\-datadir=\fR\fB\fIpath\fR\fR
+.sp
+The directory of data files to be used during testing. The default location is the
+\fIdata\fR
+directory under the location given by the
+\fB\-\-stress\-suite\-basedir\fR
+option.
+.TP 3n
+\(bu
+\fB\-\-stress\-init\-file[=\fR\fB\fIpath\fR\fR\fB]\fR
+.sp
+\fIfile_name\fR
+is the location of the file that contains the list of tests. If missing, the default file is
+\fIstress_init.txt\fR
+in the test suite directory.
+.TP 3n
+\(bu
+\fB\-\-stress\-mode=\fR\fB\fImode\fR\fR
+.sp
+This option indicates the test order in stress\-test mode. The
+\fImode\fR
+value is either
+random
+to select tests in random order or
+seq
+to run tests in each thread in the order specified in the test list file. The default mode is
+random.
+.TP 3n
+\(bu
+\fB\-\-stress\-suite\-basedir=\fR\fB\fIpath\fR\fR
+.sp
+This option is required.
+\fIpath\fR
+is the directory that has the
+\fIt\fR
+and
+\fIr\fR
+subdirectories containing the test case and result files. This directory is also the default location of the
+\fIstress\-test.txt\fR
+file that contains the list of tests. (A different location can be specified with the
+\fB\-\-stress\-tests\-file\fR
+option.)
+.TP 3n
+\(bu
+\fB\-\-stress\-tests\-file[=\fR\fB\fIfile_name\fR\fR\fB]\fR
+.sp
+Use this option to run the stress tests.
+\fIfile_name\fR
+is the location of the file that contains the list of tests. If
+\fIfile_name\fR
+is omitted, the default file is
+\fIstress\-test.txt\fR
+in the stress suite directory. (See
+\fB\-\-stress\-suite\-basedir\fR.)
+.TP 3n
+\(bu
+\fB\-\-suite=\fR\fB\fIsuite_name\fR\fR
+.sp
+Run the named test suite. The default name is
+main
+(the regular test suite located in the
+\fImysql\-test\fR
+directory).
+.TP 3n
+\(bu
+\fB\-\-test\-count=\fR\fB\fIN\fR\fR
+.sp
+The number of tests to execute before exiting.
+.TP 3n
+\(bu
+\fB\-\-test\-duration=\fR\fB\fIN\fR\fR
+.sp
+The duration of stress testing in seconds.
+.TP 3n
+\(bu
+\fB\-\-test\-suffix=\fR\fB\fIstr\fR\fR
+.sp
+Unknown.
+.TP 3n
+\(bu
+\fB\-\-threads=\fR\fB\fIN\fR\fR
+.sp
+The number of threads. The default is 1.
+.TP 3n
+\(bu
+\fB\-\-verbose\fR
+.sp
+Verbose mode. Print more information about what the program does.
+.SH "COPYRIGHT"
+.PP
+Copyright 2007 MySQL AB
+.PP
+This documentation is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License.
+.PP
+This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
+.PP
+You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110\-1301 USA or see http://www.gnu.org/licenses/.
+.PP
+Please email
+<docs at mysql.com>
+for more information or if you are interested in doing a translation.
+.SH "SEE ALSO"
+For more information, please refer to the MySQL Reference Manual,
+which may already be installed locally and which is also available
+online at http://dev.mysql.com/doc/.
+.SH AUTHOR
+MySQL AB (http://www.mysql.com/).
Added: branches/sid-5.0/debian/manpages/mysql-test-run.pl.1
===================================================================
--- branches/sid-5.0/debian/manpages/mysql-test-run.pl.1 (rev 0)
+++ branches/sid-5.0/debian/manpages/mysql-test-run.pl.1 2007-11-26 12:34:29 UTC (rev 1020)
@@ -0,0 +1,1004 @@
+.\" Title: \fBmysql\-test\-run.pl\fR
+.\" Author:
+.\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
+.\" Date: 11/21/2007
+.\" Manual: MySQL Database System
+.\" Source: MySQL
+.\"
+.TH "\fBMYSQL\-TEST\-RUN.PL" "1" "11/21/2007" "MySQL" "MySQL Database System"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
+.SH "NAME"
+mysql\-test\-run.pl \- run MySQL test suite
+.SH "SYNOPSIS"
+.HP 28
+\fBmysql\-test\-run.pl [\fR\fB\fIoptions\fR\fR\fB]\fR
+.SH "DESCRIPTION"
+.PP
+The
+\fBmysql\-test\-run.pl\fR
+Perl script is the main application used to run the MySQL test suite. It invokes
+\fBmysqltest\fR
+to run individual test cases. (Prior to MySQL 4.1, a similar shell script,
+\fBmysql\-test\-run\fR, can be used instead.)
+.PP
+Invoke
+\fBmysql\-test\-run.pl\fR
+in the
+\fImysql\-test\fR
+directory like this:
+.sp
+.RS 3n
+.nf
+shell> \fBmysql\-test\-run.pl [\fR\fB\fIoptions\fR\fR\fB] [\fR\fB\fItest_name\fR\fR\fB] ...\fR
+.fi
+.RE
+.PP
+Each
+\fItest_name\fR
+argument names a test case. The test case file that corresponds to the test name is
+\fIt/\fR\fI\fItest_name\fR\fR\fI.test\fR.
+.PP
+For each
+\fItest_name\fR
+argument,
+\fBmysql\-test\-run.pl\fR
+runs the named test case. With no
+\fItest_name\fR
+arguments,
+\fBmysql\-test\-run.pl\fR
+runs all
+\fI.test\fR
+files in the
+\fIt\fR
+subdirectory.
+.PP
+If no suffix is given for the test name, a suffix of
+\fI.test\fR
+is assumed. Any leading pathname is ignored. These commands are equivalent:
+.sp
+.RS 3n
+.nf
+shell> \fBmysql\-test\-run.pl mytest\fR
+shell> \fBmysql\-test\-run.pl mytest.test\fR
+shell> \fBmysql\-test\-run.pl t/mytest.test\fR
+.fi
+.RE
+.PP
+As of MySQL 5.1.23, a suite name can be given as part of the test name. That is, the syntax for naming a test is:
+.sp
+.RS 3n
+.nf
+[\fIsuite_name\fR.]\fItest_name\fR[.\fIsuffix\fR]
+.fi
+.RE
+.PP
+If a suite name is given,
+\fBmysql\-test\-run.pl\fR
+looks in that suite for the test. With no suite name,
+\fBmysql\-test\-run.pl\fR
+looks in the default list of suites for a match and runs the test in any suites where it finds the test. Suppose that the default suite list is
+main,
+binlog,
+rpl, and that a test
+\fImytest.test\fR
+exists in the
+main
+and
+rpl
+suites. With an argument of
+mytest
+or
+mytest.test,
+\fBmysql\-test\-run.pl\fR
+will run
+\fImytest.test\fR
+from the
+main
+and
+rpl
+suites.
+.PP
+To run a family of test cases for which the names share a common prefix, use the
+\fB\-\-do\-test=\fR\fB\fIprefix\fR\fR
+option. For example,
+\fB\-\-do\-test=rpl\fR
+runs the replication tests (test cases that have names beginning with
+rpl).
+.PP
+To perform setup prior to running tests,
+\fBmysql\-test\-run.pl\fR
+needs to invoke
+\fBmysqld\fR
+with the
+\fB\-\-bootstrap\fR
+and
+\fB\-\-skip\-grant\-tables\fR
+options (see
+[1]\&\fITypical \fBconfigure\fR Options\fR). If MySQL was configured with the
+\fB\-\-disable\-grant\-options\fR
+option,
+\fB\-\-bootstrap\fR,
+\fB\-\-skip\-grant\-tables\fR, and
+\fB\-\-init\-file\fR
+will be disabled. To handle this, set the
+MYSQLD_BOOTSTRAP
+environment variable to the full pathname of a server that has all options enabled.
+\fBmysql\-test\-run.pl\fR
+will use that server to perform setup; it is not used to run the tests.
+.PP
+The
+init_file
+test will fail if
+\fB\-\-init\-file\fR
+is disabled. This is an expected failure that can be handled as follows:
+.sp
+.RS 3n
+.nf
+shell> \fBexport MYSQLD_BOOTSTRAP\fR
+shell> \fBMYSQLD_BOOTSTRAP=/full/path/to/mysqld\fR
+shell> \fBmake test force="\-\-skip\-test=init_file"\fR
+.fi
+.RE
+.PP
+To run
+\fBmysql\-test\-run.pl\fR
+on Windows, you'll need either Cygwin or ActiveState Perl to run it. You may also need to install the modules required by the script. To run the test script, change location into the
+\fImysql\-test\fR
+directory, set the
+MTR_VS_CONFIG
+environment variable to the configuration you selected earlier (or use the
+\fB\-\-vs\-config\fR
+option), and invoke
+\fBmysql\-test\-run.pl\fR. For example (using Cygwin and the
+\fBbash\fR
+shell):
+.sp
+.RS 3n
+.nf
+shell> \fBcd mysql\-test\fR
+shell> \fBexport MTS_VS_CONFIG=debug\fR
+shell> \fB./mysqltest\-run.pl \-\-force \-\-timer\fR
+shell> \fB./mysqltest\-run.pl \-\-force \-\-timer \-\-ps\-protocol\fR
+.fi
+.RE
+.PP
+If you have a copy of
+\fBmysqld\fR
+running on the machine where you want to run the test suite, you do not have to stop it, as long as it is not using ports
+9306
+or
+9307. If either of those ports is taken, you should set the
+MTR_BUILD_THREAD
+environment variable to an appropriate value, and the test suite will use a different set of ports for master, slave, NDB, and Instance Manager). For example:
+.sp
+.RS 3n
+.nf
+shell> \fBexport MTR_BUILD_THREAD=31\fR
+shell> \fB./mysql\-test\-run.pl [\fR\fB\fIoptions\fR\fR\fB] [\fR\fB\fItest_name\fR\fR\fB]\fR
+.fi
+.RE
+.PP
+\fBmysql\-test\-run.pl\fR
+defines several environment variables. Some of them are listed in the following table.
+.TS
+allbox tab(:);
+l l
+l l
+l l
+l l
+l l
+l l.
+T{
+\fBVariable\fR
+T}:T{
+\fBMeaning\fR
+T}
+T{
+MYSQL_TEST
+T}:T{
+Pathname to \fBmysqltest\fR binary
+T}
+T{
+MYSQLTEST_VARDIR
+T}:T{
+Pathname to the \fIvar\fR directory that is used for
+ logs, temporary files, and so forth
+T}
+T{
+MYSQLD_BOOTSTRAP
+T}:T{
+Full pathname to \fBmysqld\fR that has all options enabled
+T}
+T{
+MASTER_MYPORT
+T}:T{
+???
+T}
+T{
+MASTER_MYSOCK
+T}:T{
+???
+T}
+.TE
+.sp
+.PP
+Tests sometimes rely on certain environment variables being defined. For example, certain tests assume that
+MYSQL_TEST
+is defined so that
+\fBmysqltest\fR
+can invoke itself with
+exec $MYSQL_TEST.
+.PP
+\fBmysql\-test\-run.pl\fR
+supports the options in the following list. An argument of
+\fB\-\-\fR
+tells
+\fBmysql\-test\-run.pl\fR
+not to process any following arguments as options. (A description of differences between the options supported by
+\fBmysql\-test\-run.pl\fR
+and
+\fBmysql\-test\-run\fR
+appears following the list.)
+.TP 3n
+\(bu
+\fB\-\-help\fR,
+\fB\-h\fR
+.sp
+Display a help message and exit.
+.TP 3n
+\(bu
+\fB\-\-bench\fR
+.sp
+Run the benchmark suite.
+.TP 3n
+\(bu
+\fB\-\-benchdir=\fR\fB\fIpath\fR\fR
+.sp
+The directory where the benchmark suite is located. The default path is
+\fI../../mysql\-bench\fR.
+.TP 3n
+\(bu
+\fB\-\-big\-test\fR
+.sp
+Pass the
+\fB\-\-big\-test\fR
+option to
+\fBmysqltest\fR.
+.TP 3n
+\(bu
+\fB\-\-check\-testcases\fR
+.sp
+Check test cases for side effects.
+.TP 3n
+\(bu
+\fB\-\-client\-ddd\fR
+.sp
+Start
+\fBmysqltest\fR
+in the
+\fBddd\fR
+debugger.
+.TP 3n
+\(bu
+\fB\-\-client\-debugger\fR
+.sp
+Start
+\fBmysqltest\fR
+in the named debugger.
+.TP 3n
+\(bu
+\fB\-\-client\-gdb\fR
+.sp
+Start
+\fBmysqltest\fR
+in the
+\fBgdb\fR
+debugger.
+.TP 3n
+\(bu
+\fB\-\-comment=\fR\fB\fIstr\fR\fR
+.sp
+Write
+\fIstr\fR
+to the output.
+.TP 3n
+\(bu
+\fB\-\-compress\fR
+.sp
+Compress all information sent between the client and the server if both support compression.
+.TP 3n
+\(bu
+\fB\-\-cursor\-protocol\fR
+.sp
+Pass the
+\fB\-\-cursor\-protocol\fR
+option to
+\fBmysqltest\fR
+(implies
+\fB\-\-ps\-protocol\fR).
+.TP 3n
+\(bu
+\fB\-\-ddd\fR
+.sp
+Start
+\fBmysqld\fR
+in the
+\fBddd\fR
+debugger.
+.TP 3n
+\(bu
+\fB\-\-debug\fR
+.sp
+Dump trace output for all clients and servers.
+.TP 3n
+\(bu
+\fB\-\-debugger\fR
+.sp
+Start
+\fBmysqld\fR
+using the named debugger.
+.TP 3n
+\(bu
+\fB\-\-do\-test=\fR\fB\fIprefix\fR\fR
+.sp
+Run all test cases having a name that begins with the given
+\fIprefix\fR
+value. This option provides a convenient way to run a family of similarly named tests.
+.TP 3n
+\(bu
+\fB\-\-embedded\-server\fR
+.sp
+Use a version of
+\fBmysqltest\fR
+built with the embedded server.
+.TP 3n
+\(bu
+\fB\-\-extern\fR
+.sp
+Use an already running server.
+.sp
+Note: If a test case has an
+\fI.opt\fR
+file that requires the server to be restarted with specific options, the file will not be used. The test case likely will fail as a result.
+.TP 3n
+\(bu
+\fB\-\-fast\fR
+.sp
+Do not clean up from earlier test runs.
+.TP 3n
+\(bu
+\fB\-\-force\fR
+.sp
+Normally,
+\fBmysql\-test\-run.pl\fR
+exits if a test case fails.
+\fB\-\-force\fR
+causes execution to continue regardless of test case failure.
+.TP 3n
+\(bu
+\fB\-\-gcov\fR
+.sp
+Run tests with the
+\fBgcov\fR
+test coverage tool.
+.TP 3n
+\(bu
+\fB\-\-gdb\fR
+.sp
+Start
+\fBmysqld\fR
+in the
+\fBgdb\fR
+debugger.
+.TP 3n
+\(bu
+\fB\-\-gprof\fR
+.sp
+Run tests with the
+\fBgprof\fR
+profiling tool.
+.TP 3n
+\(bu
+\fB\-\-im\-mysqld1\-port\fR
+.sp
+TCP/IP port number to use for the first
+\fBmysqld\fR, controlled by Instance Manager.
+.TP 3n
+\(bu
+\fB\-\-im\-mysqld2\-port\fR
+.sp
+TCP/IP port number to use for the second
+\fBmysqld\fR, controlled by Instance Manager.
+.TP 3n
+\(bu
+\fB\-\-im\-port\fR
+.sp
+TCP/IP port number to use for
+\fBmysqld\fR, controlled by Instance Manager.
+.TP 3n
+\(bu
+\fB\-\-log\-warnings\fR
+.sp
+Pass the
+\fB\-\-log\-warnings\fR
+option to
+\fBmysqld\fR.
+.TP 3n
+\(bu
+\fB\-\-manual\-debug\fR
+.sp
+Use a server that has already been started by the user in a debugger.
+.TP 3n
+\(bu
+\fB\-\-manual\-gdb\fR
+.sp
+Use a server that has already been started by the user in the
+\fBgdb\fR
+debugger.
+.TP 3n
+\(bu
+\fB\-\-master\-binary=\fR\fB\fIpath\fR\fR
+.sp
+Specify the path of the
+\fBmysqld\fR
+binary to use for master servers.
+.TP 3n
+\(bu
+\fB\-\-master_port=\fR\fB\fIport_num\fR\fR
+.sp
+Specify the TCP/IP port number for the first master server to use. Observe that the option name has an underscore and not a dash.
+.TP 3n
+\(bu
+\fB\-\-mem\fR
+.sp
+Run the test suite in memory, using tmpfs or ramdisk. This can decrease test times significantly.
+\fBmysql\-test\-run.pl\fR
+attempts to find a suitable location using a built\-in list of standard locations for tmpfs and puts the
+\fIvar\fR
+directory there. This option also affects placement of temporary files, which are created in
+\fIvar/tmp\fR.
+.sp
+The default list includes
+\fI/dev/shm\fR. You can also enable this option by setting the environment variable
+MTR_MEM[=\fIdir_name\fR]. If
+\fIdir_name\fR
+is given, it is added to the beginning of the list of locations to search, so it takes precedence over any built\-in locations.
+.sp
+This option was added in MySQL 4.1.22, 5.0.30, and 5.1.13.
+.TP 3n
+\(bu
+\fB\-\-mysqld=\fR\fB\fIstr\fR\fR
+.sp
+Extra options to pass to
+\fBmysqld\fR.
+.TP 3n
+\(bu
+\fB\-\-ndb\-connectstring=\fR\fB\fIstr\fR\fR
+.sp
+Pass
+\fB\-\-ndb\-connectstring=\fR\fB\fIstr\fR\fR
+to the master MySQL server. This option also prevents
+\fBmysql\-test\-run.pl\fR
+from starting a cluster. It is assumed that there is already a cluster running to which the server can connect with the given connectstring.
+.TP 3n
+\(bu
+\fB\-\-ndb\-connectstring\-slave=\fR\fB\fIstr\fR\fR
+.sp
+Pass
+\fB\-\-ndb\-connectstring=\fR\fB\fIstr\fR\fR
+to slave MySQL servers. This option also prevents
+\fBmysql\-test\-run.pl\fR
+from starting a cluster. It is assumed that there is already a cluster running to which the server can connect with the given connectstring.
+.TP 3n
+\(bu
+\fB\-\-ndb\-extra\-test\fR
+.sp
+Unknown.
+.TP 3n
+\(bu
+\fB\-\-ndbcluster\-port=\fR\fB\fIport_num\fR\fR,
+\fB\-\-ndbcluster_port=\fR\fB\fIport_num\fR\fR
+.sp
+Specify the TCP/IP port number that NDB Cluster should use.
+.TP 3n
+\(bu
+\fB\-\-ndbcluster\-port\-slave=\fR\fB\fIport_num\fR\fR
+.sp
+Specify the TCP/IP port number that the slave NDB Cluster should use.
+.TP 3n
+\(bu
+\fB\-\-netware\fR
+.sp
+Run
+\fBmysqld\fR
+with options needed on NetWare.
+.TP 3n
+\(bu
+\fB\-\-notimer\fR
+.sp
+Cause
+\fBmysqltest\fR
+not to generate a timing file.
+.TP 3n
+\(bu
+\fB\-\-ps\-protocol\fR
+.sp
+Pass the
+\fB\-\-ps\-protocol\fR
+option to
+\fBmysqltest\fR.
+.TP 3n
+\(bu
+\fB\-\-record\fR
+.sp
+Pass the
+\fB\-\-record\fR
+option to
+\fBmysqltest\fR. This option requires a specific test case to be named on the command line.
+.TP 3n
+\(bu
+\fB\-\-reorder\fR
+.sp
+Reorder tests to minimize the number of server restarts needed.
+.TP 3n
+\(bu
+\fB\-\-report\-features\fR
+.sp
+Display the output of
+SHOW ENGINES
+and
+SHOW VARIABLES. This can be used to verify that binaries are built with all required features.
+.sp
+This option was added in MySQL 4.1.23, 5.0.30, and 5.1.14.
+.TP 3n
+\(bu
+\fB\-\-script\-debug\fR
+.sp
+Enable debug output for
+\fBmysql\-test\-run.pl\fR
+itself.
+.TP 3n
+\(bu
+\fB\-\-skip\-im\fR
+.sp
+Do not start Instance Manager; skip Instance Manager test cases.
+.TP 3n
+\(bu
+\fB\-\-skip\-master\-binlog\fR
+.sp
+Do not enable master server binary logging.
+.TP 3n
+\(bu
+\fB\-\-skip\-ndbcluster\fR,
+\fB\-\-skip\-ndb\fR
+.sp
+Do not start NDB Cluster; skip Cluster test cases.
+.TP 3n
+\(bu
+\fB\-\-skip\-ndbcluster\-slave\fR,
+\fB\-\-skip\-ndb\-slave\fR
+.sp
+Do not start an NDB Cluster slave.
+.TP 3n
+\(bu
+\fB\-\-skip\-rpl\fR
+.sp
+Skip replication test cases.
+.TP 3n
+\(bu
+\fB\-\-skip\-slave\-binlog\fR
+.sp
+Do not enable master server binary logging.
+.TP 3n
+\(bu
+\fB\-\-skip\-ssl\fR
+.sp
+Do not start
+\fBmysqld\fR
+with support for SSL connections.
+.TP 3n
+\(bu
+\fB\-\-skip\-test=\fR\fB\fIregex\fR\fR
+.sp
+Specify a regular expression to be applied to test case names. Cases with names that match the expression are skipped. tests to skip.
+.TP 3n
+\(bu
+\fB\-\-skip\-*\fR
+.sp
+\fB\-\-skip\-*\fR
+options not otherwise recognized by
+\fBmysql\-test\-run.pl\fR
+are passed to the master server.
+.TP 3n
+\(bu
+\fB\-\-slave\-binary=\fR\fB\fIpath\fR\fR
+.sp
+Specify the path of the
+\fBmysqld\fR
+binary to use for slave servers.
+.TP 3n
+\(bu
+\fB\-\-slave_port=\fR\fB\fIport_num\fR\fR
+.sp
+Specify the TCP/IP port number for the first master server to use. Observe that the option name has an underscore and not a dash.
+.TP 3n
+\(bu
+\fB\-\-sleep=\fR\fB\fIN\fR\fR
+.sp
+Pass
+\fB\-\-sleep=\fR\fB\fIN\fR\fR
+to
+\fBmysqltest\fR.
+.TP 3n
+\(bu
+\fB\-\-small\-bench\fR
+.sp
+Run the benchmarks with the
+\fB\-\-small\-tests\fR
+and
+\fB\-\-small\-tables\fR
+options.
+.TP 3n
+\(bu
+\fB\-\-socket=\fR\fB\fIfile_name\fR\fR
+.sp
+For connections to
+localhost, the Unix socket file to use, or, on Windows, the name of the named pipe to use.
+.TP 3n
+\(bu
+\fB\-\-sp\-protocol\fR
+.sp
+Pass the
+\fB\-\-sp\-protocol\fR
+option to
+\fBmysqltest\fR.
+.TP 3n
+\(bu
+\fB\-\-ssl\fR
+.sp
+If
+\fBmysql\-test\-run.pl\fR
+is started with the
+\fB\-\-ssl\fR
+option, it sets up a secure conection for all test cases. In this case, if
+\fBmysqld\fR
+does not support SSL,
+\fBmysql\-test\-run.pl\fR
+exits with an error message:
+Couldn't find support for SSL
+.TP 3n
+\(bu
+\fB\-\-start\-and\-exit\fR
+.sp
+Initialize and start servers with the startup settings for the specified test case or cases, if any, and then exit.
+.TP 3n
+\(bu
+\fB\-\-start\-dirty\fR
+.sp
+Start servers (without initialization) for the specified test case or cases, if any, and then exit. You can then manually run the test cases.
+.TP 3n
+\(bu
+\fB\-\-start\-from=\fR\fB\fItest_name\fR\fR
+.sp
+\fBmysql\-test\-run.pl\fR
+sorts the list of names of the test cases to be run, and then begins with
+\fItest_name\fR.
+.TP 3n
+\(bu
+\fB\-\-strace\-client\fR
+.sp
+Create
+\fBstrace\fR
+output for
+\fBmysqltest\fR.
+.TP 3n
+\(bu
+\fB\-\-stress\fR
+.sp
+Run the stress test. The other
+\fB\-\-stress\-\fR\fB\fIxxx\fR\fR
+options apply in this case.
+.TP 3n
+\(bu
+\fB\-\-stress\-init\-file=\fR\fB\fIfile_name\fR\fR
+.sp
+\fIfile_name\fR
+is the location of the file that contains the list of tests. The default file is
+\fIstress_init.txt\fR
+in the test suite directory.
+.TP 3n
+\(bu
+\fB\-\-stress\-loop\-count=\fR\fB\fIN\fR\fR
+.sp
+In sequential stress\-test mode, the number of loops to execute before exiting.
+.TP 3n
+\(bu
+\fB\-\-stress\-mode=\fR\fB\fImode\fR\fR
+.sp
+This option indicates the test order in stress\-test mode. The
+\fImode\fR
+value is either
+random
+to select tests in random order or
+seq
+to run tests in each thread in the order specified in the test list file. The default mode is
+random.
+.TP 3n
+\(bu
+\fB\-\-stress\-suite=\fR\fB\fIsuite_name\fR\fR
+.sp
+The name of the test suite to use for stress testing. The default suite name is
+main
+(the regular test suite located in the
+\fImysql\-test\fR
+directory).
+.TP 3n
+\(bu
+\fB\-\-stress\-test\-count=\fR\fB\fIN\fR\fR
+.sp
+For stress testing, the number of tests to execute before exiting.
+.TP 3n
+\(bu
+\fB\-\-stress\-test\-duration=\fR\fB\fIN\fR\fR
+.sp
+For stress testing, the duration of stress testing in seconds.
+.TP 3n
+\(bu
+\fB\-\-stress\-test\-file=\fR\fB\fIfile_name\fR\fR
+.sp
+The file that contains the list of tests to use in stress testing. The tests should be named without the
+\fI.test\fR
+extension. The default file is
+\fIstress_tests.txt\fR
+in the test suite directory.
+.TP 3n
+\(bu
+\fB\-\-stress\-threads=\fR\fB\fIN\fR\fR
+.sp
+The number of threads to use in stress testing. The default is 5.
+.TP 3n
+\(bu
+\fB\-\-suite=\fR\fB\fIsuite_name\fR\fR
+.sp
+Run the named test suite. The default name is
+main
+(the regular test suite located in the
+\fImysql\-test\fR
+directory).
+.TP 3n
+\(bu
+\fB\-\-suite\-timeout=\fR\fB\fIminutes\fR\fR
+.sp
+Specify the maximum test suite runtime.
+.TP 3n
+\(bu
+\fB\-\-testcase\-timeout\fR
+.sp
+Specify the maximum test case runtime.
+.TP 3n
+\(bu
+\fB\-\-timer\fR
+.sp
+Cause
+\fBmysqltest\fR
+to generate a timing file. The default file is named
+\fI./var/log/timer\fR.
+.TP 3n
+\(bu
+\fB\-\-tmpdir=\fR\fB\fIpath\fR\fR
+.sp
+The directory where temporary file are stored. The default location is
+\fI./var/tmp\fR.
+.TP 3n
+\(bu
+\fB\-\-unified\-diff\fR,
+\fB\-\-udiff\fR
+.sp
+Use unified diff format when presenting differences between expected and actual test case results.
+.TP 3n
+\(bu
+\fB\-\-use\-old\-data\fR
+.sp
+Do not install the test databases. (Use existing ones.)
+.TP 3n
+\(bu
+\fB\-\-user\-test=\fR\fB\fIval\fR\fR
+.sp
+Unused.
+.TP 3n
+\(bu
+\fB\-\-user=\fR\fB\fIuser_name\fR\fR
+.sp
+The MySQL username to use when connecting to the server.
+.TP 3n
+\(bu
+\fB\-\-valgrind\fR
+.sp
+Run
+\fBmysqltest\fR
+and
+\fBmysqld\fR
+with
+\fBvalgrind\fR.
+.TP 3n
+\(bu
+\fB\-\-valgrind\-all\fR
+.sp
+Like
+\fB\-\-valgrind\fR, but passes the
+\fB\-\-verbose\fR
+and
+\fB\-\-show\-reachable\fR
+options to
+\fBvalgrind\fR.
+.TP 3n
+\(bu
+\fB\-\-valgrind\-mysqltest\fR
+.sp
+Run
+\fBmysqltest\fR
+with
+\fBvalgrind\fR.
+.TP 3n
+\(bu
+\fB\-\-valgrind\-mysqltest\-all\fR
+.sp
+Like
+\fB\-\-valgrind\-mysqltest\fR, but passes the
+\fB\-\-verbose\fR
+and
+\fB\-\-show\-reachable\fR
+options to
+\fBvalgrind\fR.
+.TP 3n
+\(bu
+\fB\-\-valgrind\-options=\fR\fB\fIstr\fR\fR
+.sp
+Extra options to pass to
+\fBvalgrind\fR.
+.TP 3n
+\(bu
+\fB\-\-valgrind\-path=\fR\fB\fIpath\fR\fR
+.sp
+Specify the pathname to the
+\fBvalgrind\fR
+executable.
+.TP 3n
+\(bu
+\fB\-\-vardir=\fR\fB\fIpath\fR\fR
+.sp
+Specify the path where files generated during the test run are stored. The default location is
+\fI./var\fR.
+.TP 3n
+\(bu
+\fB\-\-view\-protocol\fR
+.sp
+Pass the
+\fB\-\-view\-protocol\fR
+option to
+\fBmysqltest\fR.
+.TP 3n
+\(bu
+\fB\-\-vs\-config=\fR\fB\fIconfig_val\fR\fR
+.sp
+Specify the configuration used to build MySQL (for example,
+\fB\-\-vs\-config=debug\fR
+\fB\-\-vs\-config=release\fR). This option is for Windows only. It is available as of MySQL 4.1.23, 5.0.30, and 5.1.14.
+.TP 3n
+\(bu
+\fB\-\-wait\-timeout=\fR\fB\fIN\fR\fR
+.sp
+Unused?
+.TP 3n
+\(bu
+\fB\-\-warnings\fR
+.sp
+This option is a synonym for
+\fB\-\-log\-warnings\fR.
+.TP 3n
+\(bu
+\fB\-\-with\-ndbcluster\fR
+.sp
+Use NDB Cluster and enable test cases that require it.
+.TP 3n
+\(bu
+\fB\-\-with\-ndbcluster\-all\fR
+.sp
+Use NDB Cluster in all tests.
+.TP 3n
+\(bu
+\fB\-\-with\-ndbcluster\-only\fR
+.sp
+Run only test cases that have
+ndb
+in their name.
+.TP 3n
+\(bu
+\fB\-\-with\-ndbcluster\-slave\fR
+.sp
+Unknown.
+.TP 3n
+\(bu
+\fB\-\-with\-openssl\fR
+.sp
+This option is a synonym for
+\fB\-\-ssl\fR.
+.sp
+.RE
+.sp
+.it 1 an-trap
+.nr an-no-space-flag 1
+.nr an-break-flag 1
+.br
+\fBNote\fR
+.PP
+\fBmysql\-test\-run\fR
+supports the following options not supported by
+\fBmysql\-test\-run.pl\fR:
+\fB\-\-local\fR,
+\fB\-\-local\-master\fR,
+\fB\-\-ndb\-verbose\fR,
+\fB\-\-ndb_mgm\-extra\-opts\fR,
+\fB\-\-ndb_mgmd\-extra\-opts\fR,
+\fB\-\-ndbd\-extra\-opts\fR,
+\fB\-\-old\-master\fR,
+\fB\-\-purify\fR,
+\fB\-\-use\-old\-data\fR,
+\fB\-\-valgrind\-mysqltest\-all\fR.
+.PP
+Conversely,
+\fBmysql\-test\-run.pl\fR
+supports the following options not supported by
+\fBmysql\-test\-run\fR:
+\fB\-\-benchdir\fR,
+\fB\-\-check\-testcases\fR,
+\fB\-\-client\-ddd\fR,
+\fB\-\-client\-debugger\fR,
+\fB\-\-cursor\-protocol\fR,
+\fB\-\-debugger\fR,
+\fB\-\-im\-mysqld1\-port\fR,
+\fB\-\-im\-mysqld2\-port\fR,
+\fB\-\-im\-port\fR,
+\fB\-\-manual\-debug\fR,
+\fB\-\-netware\fR,
+\fB\-\-notimer\fR,
+\fB\-\-reorder\fR,
+\fB\-\-script\-debug\fR,
+\fB\-\-skip\-im\fR,
+\fB\-\-skip\-ssl\fR,
+\fB\-\-sp\-protocol\fR,
+\fB\-\-start\-dirty\fR,
+\fB\-\-suite\fR,
+\fB\-\-suite\-timeout\fR,
+\fB\-\-testcase\-timeout\fR,
+\fB\-\-udiff\fR,
+\fB\-\-unified\-diff\fR,,
+\fB\-\-valgrind\-path\fR,
+\fB\-\-vardir\fR,
+\fB\-\-view\-protocol\fR.
+.SH "COPYRIGHT"
+.PP
+Copyright 2007 MySQL AB
+.PP
+This documentation is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License.
+.PP
+This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
+.PP
+You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110\-1301 USA or see http://www.gnu.org/licenses/.
+.PP
+Please email
+<docs at mysql.com>
+for more information or if you are interested in doing a translation.
+.SH "REFERENCES"
+.TP 3
+1.\ Typical configure Options
+\%http://dev.mysql.com/doc/refman/5.1/en/configure\-options.html
+.SH "SEE ALSO"
+For more information, please refer to the MySQL Reference Manual,
+which may already be installed locally and which is also available
+online at http://dev.mysql.com/doc/.
+.SH AUTHOR
+MySQL AB (http://www.mysql.com/).
Added: branches/sid-5.0/debian/manpages/mysql.1
===================================================================
--- branches/sid-5.0/debian/manpages/mysql.1 (rev 0)
+++ branches/sid-5.0/debian/manpages/mysql.1 2007-11-26 12:34:29 UTC (rev 1020)
@@ -0,0 +1,1417 @@
+.\" Title: \fBmysql\fR
+.\" Author:
+.\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
+.\" Date: 11/25/2007
+.\" Manual: MySQL Database System
+.\" Source: MySQL 5.0
+.\"
+.TH "\fBMYSQL\fR" "1" "11/25/2007" "MySQL 5.0" "MySQL Database System"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
+.SH "NAME"
+mysql \- the MySQL command\-line tool
+.SH "SYNOPSIS"
+.HP 24
+\fBmysql [\fR\fB\fIoptions\fR\fR\fB] \fR\fB\fIdb_name\fR\fR
+.SH "DESCRIPTION"
+.PP
+\fBmysql\fR
+is a simple SQL shell (with GNU
+readline
+capabilities). It supports interactive and non\-interactive use. When used interactively, query results are presented in an ASCII\-table format. When used non\-interactively (for example, as a filter), the result is presented in tab\-separated format. The output format can be changed using command options.
+.PP
+If you have problems due to insufficient memory for large result sets, use the
+\fB\-\-quick\fR
+option. This forces
+\fBmysql\fR
+to retrieve results from the server a row at a time rather than retrieving the entire result set and buffering it in memory before displaying it. This is done by returning the result set using the
+\fBmysql_use_result()\fR
+C API function in the client/server library rather than
+\fBmysql_store_result()\fR.
+.PP
+Using
+\fBmysql\fR
+is very easy. Invoke it from the prompt of your command interpreter as follows:
+.sp
+.RS 3n
+.nf
+shell> \fBmysql \fR\fB\fIdb_name\fR\fR
+.fi
+.RE
+.PP
+Or:
+.sp
+.RS 3n
+.nf
+shell> \fBmysql \-\-user=\fR\fB\fIuser_name\fR\fR\fB \-\-password=\fR\fB\fIyour_password\fR\fR\fB \fR\fB\fIdb_name\fR\fR
+.fi
+.RE
+.PP
+Then type an SQL statement, end it with
+\(lq;\(rq,
+\\g, or
+\\G
+and press Enter.
+.PP
+As of MySQL 5.0.25, typing Control\-C causes
+\fBmysql\fR
+to attempt to kill the current statement. If this cannot be done, or Control\-C is typed again before the statement is killed,
+\fBmysql\fR
+exits. Previously, Control\-C caused
+\fBmysql\fR
+to exit in all cases.
+.PP
+You can execute SQL statements in a script file (batch file) like this:
+.sp
+.RS 3n
+.nf
+shell> \fBmysql \fR\fB\fIdb_name\fR\fR\fB < \fR\fB\fIscript.sql\fR\fR\fB > \fR\fB\fIoutput.tab\fR\fR
+.fi
+.RE
+.SH "\fBMYSQL\fR OPTIONS"
+.PP
+\fBmysql\fR
+supports the following options:
+.TP 3n
+\(bu
+\fB\-\-help\fR,
+\fB\-?\fR
+.sp
+Display a help message and exit.
+.TP 3n
+\(bu
+\fB\-\-auto\-rehash\fR
+.sp
+Enable automatic rehashing. This option is on by default, which enables table and column name completion. Use
+\fB\-\-skip\-auto\-rehash\fR
+to disable rehashing. That causes
+\fBmysql\fR
+to start faster, but you must issue the
+rehash
+command if you want to use table and column name completion.
+.TP 3n
+\(bu
+\fB\-\-batch\fR,
+\fB\-B\fR
+.sp
+Print results using tab as the column separator, with each row on a new line. With this option,
+\fBmysql\fR
+does not use the history file.
+.TP 3n
+\(bu
+\fB\-\-character\-sets\-dir=\fR\fB\fIpath\fR\fR
+.sp
+The directory where character sets are installed. See
+Section\ 2, \(lqThe Character Set Used for Data and Sorting\(rq.
+.TP 3n
+\(bu
+\fB\-\-column\-names\fR
+.sp
+Write column names in results.
+.TP 3n
+\(bu
+\fB\-\-comments\fR,
+\fB\-c\fR
+.sp
+Whether to preserve comments in statements sent to the server. The default is \-\-skip\-comments (discard comments), enable with \-\-comments (preserve comments). This option was added in MySQL 5.0.52.
+.TP 3n
+\(bu
+\fB\-\-compress\fR,
+\fB\-C\fR
+.sp
+Compress all information sent between the client and the server if both support compression.
+.TP 3n
+\(bu
+\fB\-\-database=\fR\fB\fIdb_name\fR\fR,
+\fB\-D \fR\fB\fIdb_name\fR\fR
+.sp
+The database to use. This is useful primarily in an option file.
+.TP 3n
+\(bu
+\fB\-\-debug[=\fR\fB\fIdebug_options\fR\fR\fB]\fR,
+\fB\-# [\fR\fB\fIdebug_options\fR\fR\fB]\fR
+.sp
+Write a debugging log. The
+\fIdebug_options\fR
+string often is
+\'d:t:o,\fIfile_name\fR'. The default is
+\'d:t:o,/tmp/mysql.trace'.
+.TP 3n
+\(bu
+\fB\-\-debug\-info\fR,
+\fB\-T\fR
+.sp
+Print some debugging information when the program exits.
+.TP 3n
+\(bu
+\fB\-\-default\-character\-set=\fR\fB\fIcharset_name\fR\fR
+.sp
+Use
+\fIcharset_name\fR
+as the default character set. See
+Section\ 2, \(lqThe Character Set Used for Data and Sorting\(rq.
+.TP 3n
+\(bu
+\fB\-\-delimiter=\fR\fB\fIstr\fR\fR
+.sp
+Set the statement delimiter. The default is the semicolon character (\(lq;\(rq).
+.TP 3n
+\(bu
+\fB\-\-execute=\fR\fB\fIstatement\fR\fR,
+\fB\-e \fR\fB\fIstatement\fR\fR
+.sp
+Execute the statement and quit. The default output format is like that produced with
+\fB\-\-batch\fR. See
+Section\ 3.1, \(lqUsing Options on the Command Line\(rq, for some examples.
+.TP 3n
+\(bu
+\fB\-\-force\fR,
+\fB\-f\fR
+.sp
+Continue even if an SQL error occurs.
+.TP 3n
+\(bu
+\fB\-\-host=\fR\fB\fIhost_name\fR\fR,
+\fB\-h \fR\fB\fIhost_name\fR\fR
+.sp
+Connect to the MySQL server on the given host.
+.TP 3n
+\(bu
+\fB\-\-html\fR,
+\fB\-H\fR
+.sp
+Produce HTML output.
+.TP 3n
+\(bu
+\fB\-\-ignore\-spaces\fR,
+\fB\-i\fR
+.sp
+Ignore spaces after function names. The effect of this is described in the discussion for the
+IGNORE_SPACE
+SQL mode (see
+the section called \(lqSQL MODES\(rq).
+.TP 3n
+\(bu
+\fB\-\-line\-numbers\fR
+.sp
+Write line numbers for errors. Disable this with
+\fB\-\-skip\-line\-numbers\fR.
+.TP 3n
+\(bu
+\fB\-\-local\-infile[={0|1}]\fR
+.sp
+Enable or disable
+LOCAL
+capability for
+LOAD DATA INFILE. With no value, the option enables
+LOCAL. The option may be given as
+\fB\-\-local\-infile=0\fR
+or
+\fB\-\-local\-infile=1\fR
+to explicitly disable or enable
+LOCAL. Enabling
+LOCAL
+has no effect if the server does not also support it.
+.TP 3n
+\(bu
+\fB\-\-named\-commands\fR,
+\fB\-G\fR
+.sp
+Enable named
+\fBmysql\fR
+commands. Long\-format commands are allowed, not just short\-format commands. For example,
+quit
+and
+\\q
+both are recognized. Use
+\fB\-\-skip\-named\-commands\fR
+to disable named commands. See
+the section called \(lq\fBMYSQL\fR COMMANDS\(rq.
+.TP 3n
+\(bu
+\fB\-\-no\-auto\-rehash\fR,
+\fB\-A\fR
+.sp
+Deprecated form of
+\fB\-skip\-auto\-rehash\fR. See the description for
+\fB\-\-auto\-rehash\fR.
+.TP 3n
+\(bu
+\fB\-\-no\-beep\fR,
+\fB\-b\fR
+.sp
+Do not beep when errors occur.
+.TP 3n
+\(bu
+\fB\-\-no\-named\-commands\fR,
+\fB\-g\fR
+.sp
+Disable named commands. Use the
+\\*
+form only, or use named commands only at the beginning of a line ending with a semicolon (\(lq;\(rq).
+\fBmysql\fR
+starts with this option
+\fIenabled\fR
+by default. However, even with this option, long\-format commands still work from the first line. See
+the section called \(lq\fBMYSQL\fR COMMANDS\(rq.
+.TP 3n
+\(bu
+\fB\-\-no\-pager\fR
+.sp
+Deprecated form of
+\fB\-\-skip\-pager\fR. See the
+\fB\-\-pager\fR
+option.
+.TP 3n
+\(bu
+\fB\-\-no\-tee\fR
+.sp
+Do not copy output to a file.
+the section called \(lq\fBMYSQL\fR COMMANDS\(rq, discusses tee files further.
+.TP 3n
+\(bu
+\fB\-\-one\-database\fR,
+\fB\-o\fR
+.sp
+Ignore statements except those for the default database named on the command line. This is useful for skipping updates to other databases in the binary log.
+.TP 3n
+\(bu
+\fB\-\-pager[=\fR\fB\fIcommand\fR\fR\fB]\fR
+.sp
+Use the given command for paging query output. If the command is omitted, the default pager is the value of your
+PAGER
+environment variable. Valid pagers are
+\fBless\fR,
+\fBmore\fR,
+\fBcat [> filename]\fR, and so forth. This option works only on Unix. It does not work in batch mode. To disable paging, use
+\fB\-\-skip\-pager\fR.
+the section called \(lq\fBMYSQL\fR COMMANDS\(rq, discusses output paging further.
+.TP 3n
+\(bu
+\fB\-\-password[=\fR\fB\fIpassword\fR\fR\fB]\fR,
+\fB\-p[\fR\fB\fIpassword\fR\fR\fB]\fR
+.sp
+The password to use when connecting to the server. If you use the short option form (\fB\-p\fR), you
+\fIcannot\fR
+have a space between the option and the password. If you omit the
+\fIpassword\fR
+value following the
+\fB\-\-password\fR
+or
+\fB\-p\fR
+option on the command line, you are prompted for one.
+.sp
+Specifying a password on the command line should be considered insecure. See
+Section\ 6.6, \(lqKeeping Your Password Secure\(rq.
+.TP 3n
+\(bu
+\fB\-\-port=\fR\fB\fIport_num\fR\fR,
+\fB\-P \fR\fB\fIport_num\fR\fR
+.sp
+The TCP/IP port number to use for the connection.
+.TP 3n
+\(bu
+\fB\-\-prompt=\fR\fB\fIformat_str\fR\fR
+.sp
+Set the prompt to the specified format. The default is
+mysql>. The special sequences that the prompt can contain are described in
+the section called \(lq\fBMYSQL\fR COMMANDS\(rq.
+.TP 3n
+\(bu
+\fB\-\-protocol={TCP|SOCKET|PIPE|MEMORY}\fR
+.sp
+The connection protocol to use.
+.TP 3n
+\(bu
+\fB\-\-quick\fR,
+\fB\-q\fR
+.sp
+Do not cache each query result, print each row as it is received. This may slow down the server if the output is suspended. With this option,
+\fBmysql\fR
+does not use the history file.
+.TP 3n
+\(bu
+\fB\-\-raw\fR,
+\fB\-r\fR
+.sp
+Write column values without escape conversion. Often used with the
+\fB\-\-batch\fR
+option.
+.TP 3n
+\(bu
+\fB\-\-reconnect\fR
+.sp
+If the connection to the server is lost, automatically try to reconnect. A single reconnect attempt is made each time the connection is lost. To suppress reconnection behavior, use
+\fB\-\-skip\-reconnect\fR.
+.TP 3n
+\(bu
+\fB\-\-safe\-updates\fR,
+\fB\-\-i\-am\-a\-dummy\fR,
+\fB\-U\fR
+.sp
+Allow only those
+UPDATE
+and
+DELETE
+statements that specify which rows to modify by using key values. If you have set this option in an option file, you can override it by using
+\fB\-\-safe\-updates\fR
+on the command line. See
+the section called \(lq\fBMYSQL\fR TIPS\(rq, for more information about this option.
+.TP 3n
+\(bu
+\fB\-\-secure\-auth\fR
+.sp
+Do not send passwords to the server in old (pre\-4.1.1) format. This prevents connections except for servers that use the newer password format.
+.TP 3n
+\(bu
+\fB\-\-show\-warnings\fR
+.sp
+Cause warnings to be shown after each statement if there are any. This option applies to interactive and batch mode. This option was added in MySQL 5.0.6.
+.TP 3n
+\(bu
+\fB\-\-sigint\-ignore\fR
+.sp
+Ignore
+SIGINT
+signals (typically the result of typing Control\-C).
+.TP 3n
+\(bu
+\fB\-\-silent\fR,
+\fB\-s\fR
+.sp
+Silent mode. Produce less output. This option can be given multiple times to produce less and less output.
+.TP 3n
+\(bu
+\fB\-\-skip\-column\-names\fR,
+\fB\-N\fR
+.sp
+Do not write column names in results.
+.TP 3n
+\(bu
+\fB\-\-skip\-line\-numbers\fR,
+\fB\-L\fR
+.sp
+Do not write line numbers for errors. Useful when you want to compare result files that include error messages.
+.TP 3n
+\(bu
+\fB\-\-socket=\fR\fB\fIpath\fR\fR,
+\fB\-S \fR\fB\fIpath\fR\fR
+.sp
+For connections to
+localhost, the Unix socket file to use, or, on Windows, the name of the named pipe to use.
+.TP 3n
+\(bu
+\fB\-\-ssl*\fR
+.sp
+Options that begin with
+\fB\-\-ssl\fR
+specify whether to connect to the server via SSL and indicate where to find SSL keys and certificates. See
+Section\ 6.7.3, \(lqSSL Command Options\(rq.
+.TP 3n
+\(bu
+\fB\-\-table\fR,
+\fB\-t\fR
+.sp
+Display output in table format. This is the default for interactive use, but can be used to produce table output in batch mode.
+.TP 3n
+\(bu
+\fB\-\-tee=\fR\fB\fIfile_name\fR\fR
+.sp
+Append a copy of output to the given file. This option does not work in batch mode. in
+the section called \(lq\fBMYSQL\fR COMMANDS\(rq, discusses tee files further.
+.TP 3n
+\(bu
+\fB\-\-unbuffered\fR,
+\fB\-n\fR
+.sp
+Flush the buffer after each query.
+.TP 3n
+\(bu
+\fB\-\-user=\fR\fB\fIuser_name\fR\fR,
+\fB\-u \fR\fB\fIuser_name\fR\fR
+.sp
+The MySQL username to use when connecting to the server.
+.TP 3n
+\(bu
+\fB\-\-verbose\fR,
+\fB\-v\fR
+.sp
+Verbose mode. Produce more output about what the program does. This option can be given multiple times to produce more and more output. (For example,
+\fB\-v \-v \-v\fR
+produces table output format even in batch mode.)
+.TP 3n
+\(bu
+\fB\-\-version\fR,
+\fB\-V\fR
+.sp
+Display version information and exit.
+.TP 3n
+\(bu
+\fB\-\-vertical\fR,
+\fB\-E\fR
+.sp
+Print query output rows vertically (one line per column value). Without this option, you can specify vertical output for individual statements by terminating them with
+\\G.
+.TP 3n
+\(bu
+\fB\-\-wait\fR,
+\fB\-w\fR
+.sp
+If the connection cannot be established, wait and retry instead of aborting.
+.TP 3n
+\(bu
+\fB\-\-xml\fR,
+\fB\-X\fR
+.sp
+Produce XML output.
+.sp
+.it 1 an-trap
+.nr an-no-space-flag 1
+.nr an-break-flag 1
+.br
+\fBNote\fR
+Prior to MySQL 5.0.26, there was no differentiation in the output when using this option between columns containing the
+NULL
+value and columns containing the string literal
+\'NULL'; both were represented as
+.sp
+.RS 3n
+.nf
+<field name="\fIcolumn_name\fR">NULL</field>
+.fi
+.RE
+Beginning with MySQL 5.0.26, the output when
+\fB\-\-xml\fR
+is used with
+\fBmysql\fR
+matches that of
+\fBmysqldump \fR\fB\fB\-\-xml\fR\fR. See
+the section of the Manual which discusses the \fB\-\-xml\fR option for \fBmysqldump\fR
+for details.
+.sp
+Beginning with MySQL 5.0.40, the XML output also uses an XML namespace, as shown here:
+.sp
+.RS 3n
+.nf
+shell> \fBmysql \-\-xml \-uroot \-e "SHOW VARIABLES LIKE 'version%'"\fR
+<?xml version="1.0"?>
+<resultset statement="SHOW VARIABLES LIKE 'version%'" xmlns:xsi="http://www.w3.org/2001/XMLSchema\-instance">
+<row>
+<field name="Variable_name">version</field>
+<field name="Value">5.0.40\-debug</field>
+</row>
+<row>
+<field name="Variable_name">version_comment</field>
+<field name="Value">Source distribution</field>
+</row>
+<row>
+<field name="Variable_name">version_compile_machine</field>
+<field name="Value">i686</field>
+</row>
+<row>
+<field name="Variable_name">version_compile_os</field>
+<field name="Value">suse\-linux\-gnu</field>
+</row>
+</resultset>
+.fi
+.RE
+.sp
+(See
+[1]\&\fIBug#25946\fR.)
+.sp
+.RE
+.PP
+You can also set the following variables by using
+\fB\-\-\fR\fB\fIvar_name\fR\fR\fB=\fR\fB\fIvalue\fR\fR
+syntax:
+.TP 3n
+\(bu
+connect_timeout
+.sp
+The number of seconds before connection timeout. (Default value is
+0.)
+.TP 3n
+\(bu
+max_allowed_packet
+.sp
+The maximum packet length to send to or receive from the server. (Default value is 16MB.)
+.TP 3n
+\(bu
+max_join_size
+.sp
+The automatic limit for rows in a join when using
+\fB\-\-safe\-updates\fR. (Default value is 1,000,000.)
+.TP 3n
+\(bu
+net_buffer_length
+.sp
+The buffer size for TCP/IP and socket communication. (Default value is 16KB.)
+.TP 3n
+\(bu
+select_limit
+.sp
+The automatic limit for
+SELECT
+statements when using
+\fB\-\-safe\-updates\fR. (Default value is 1,000.)
+.sp
+.RE
+.PP
+It is also possible to set variables by using
+\fB\-\-set\-variable=\fR\fB\fIvar_name\fR\fR\fB=\fR\fB\fIvalue\fR\fR
+or
+\fB\-O \fR\fB\fIvar_name\fR\fR\fB=\fR\fB\fIvalue\fR\fR
+syntax.
+\fIThis syntax is deprecated\fR.
+.PP
+On Unix, the
+\fBmysql\fR
+client writes a record of executed statements to a history file. By default, the history file is named
+\fI.mysql_history\fR
+and is created in your home directory. To specify a different file, set the value of the
+MYSQL_HISTFILE
+environment variable.
+.PP
+If you do not want to maintain a history file, first remove
+\fI.mysql_history\fR
+if it exists, and then use either of the following techniques:
+.TP 3n
+\(bu
+Set the
+MYSQL_HISTFILE
+variable to
+\fI/dev/null\fR. To cause this setting to take effect each time you log in, put the setting in one of your shell's startup files.
+.TP 3n
+\(bu
+Create
+\fI.mysql_history\fR
+as a symbolic link to
+\fI/dev/null\fR:
+.sp
+.RS 3n
+.nf
+shell> \fBln \-s /dev/null $HOME/.mysql_history\fR
+.fi
+.RE
+You need do this only once.
+.SH "\fBMYSQL\fR COMMANDS"
+.PP
+\fBmysql\fR
+sends each SQL statement that you issue to the server to be executed. There is also a set of commands that
+\fBmysql\fR
+itself interprets. For a list of these commands, type
+help
+or
+\\h
+at the
+mysql>
+prompt:
+.sp
+.RS 3n
+.nf
+mysql> \fBhelp\fR
+List of all MySQL commands:
+Note that all text commands must be first on line and end with ';'
+? (\\?) Synonym for `help'.
+charset (\\C) Switch to another charset. Might be needed for processing
+ binlog with multi\-byte charsets.
+clear (\\c) Clear command.
+connect (\\r) Reconnect to the server. Optional arguments are db and host.
+delimiter (\\d) Set statement delimiter. NOTE: Takes the rest of the line as
+ new delimiter.
+edit (\\e) Edit command with $EDITOR.
+ego (\\G) Send command to mysql server, display result vertically.
+exit (\\q) Exit mysql. Same as quit.
+go (\\g) Send command to mysql server.
+help (\\h) Display this help.
+nopager (\\n) Disable pager, print to stdout.
+notee (\\t) Don't write into outfile.
+pager (\\P) Set PAGER [to_pager]. Print the query results via PAGER.
+print (\\p) Print current command.
+prompt (\\R) Change your mysql prompt.
+quit (\\q) Quit mysql.
+rehash (\\#) Rebuild completion hash.
+source (\\.) Execute an SQL script file. Takes a file name as an argument.
+status (\\s) Get status information from the server.
+system (\\!) Execute a system shell command.
+tee (\\T) Set outfile [to_outfile]. Append everything into given
+ outfile.
+use (\\u) Use another database. Takes database name as argument.
+warnings (\\W) Show warnings after every statement.
+nowarning (\\w) Don't show warnings after every statement.
+For server side help, type 'help contents'
+.fi
+.RE
+.PP
+Each command has both a long and short form. The long form is not case sensitive; the short form is. The long form can be followed by an optional semicolon terminator, but the short form should not.
+.PP
+The use of short\-form commands within multi\-line
+/* ... */
+comments is not supported.
+.PP
+If you provide an argument to the
+help
+command,
+\fBmysql\fR
+uses it as a search string to access server\-side help from the contents of the MySQL Reference Manual. For more information, see
+the section called \(lq\fBMYSQL\fR SERVER\-SIDE HELP\(rq.
+.PP
+The
+charset
+command changes the default character set and issues a
+SET NAMES
+statement. This enables the character set to remain synchronized on the client and server if
+\fBmysql\fR
+is run with auto\-reconnect enabled (which is not recommended), because the changed character set is used for reconnects. This command was added in MySQL 5.0.25.
+.PP
+In the
+delimiter
+command, you should avoid the use of the backslash (\(lq\\\(rq) character because that is the escape character for MySQL.
+.PP
+The
+\fBedit\fR,
+\fBnopager\fR,
+\fBpager\fR, and
+\fBsystem\fR
+commands work only in Unix.
+.PP
+The
+status
+command provides some information about the connection and the server you are using. If you are running in
+\fB\-\-safe\-updates\fR
+mode,
+status
+also prints the values for the
+\fBmysql\fR
+variables that affect your queries.
+.PP
+To log queries and their output, use the
+\fBtee\fR
+command. All the data displayed on the screen is appended into a given file. This can be very useful for debugging purposes also. You can enable this feature on the command line with the
+\fB\-\-tee\fR
+option, or interactively with the
+\fBtee\fR
+command. The
+\fBtee\fR
+file can be disabled interactively with the
+\fBnotee\fR
+command. Executing
+\fBtee\fR
+again re\-enables logging. Without a parameter, the previous file is used. Note that
+\fBtee\fR
+flushes query results to the file after each statement, just before
+\fBmysql\fR
+prints its next prompt.
+.PP
+By using the
+\fB\-\-pager\fR
+option, it is possible to browse or search query results in interactive mode with Unix programs such as
+\fBless\fR,
+\fBmore\fR, or any other similar program. If you specify no value for the option,
+\fBmysql\fR
+checks the value of the
+PAGER
+environment variable and sets the pager to that. Output paging can be enabled interactively with the
+\fBpager\fR
+command and disabled with
+\fBnopager\fR. The command takes an optional argument; if given, the paging program is set to that. With no argument, the pager is set to the pager that was set on the command line, or
+stdout
+if no pager was specified.
+.PP
+Output paging works only in Unix because it uses the
+popen()
+function, which does not exist on Windows. For Windows, the
+\fBtee\fR
+option can be used instead to save query output, although this is not as convenient as
+\fBpager\fR
+for browsing output in some situations.
+.PP
+Here are a few tips about the
+\fBpager\fR
+command:
+.TP 3n
+\(bu
+You can use it to write to a file and the results go only to the file:
+.sp
+.RS 3n
+.nf
+mysql> \fBpager cat > /tmp/log.txt\fR
+.fi
+.RE
+You can also pass any options for the program that you want to use as your pager:
+.sp
+.RS 3n
+.nf
+mysql> \fBpager less \-n \-i \-S\fR
+.fi
+.RE
+.TP 3n
+\(bu
+In the preceding example, note the
+\fB\-S\fR
+option. You may find it very useful for browsing wide query results. Sometimes a very wide result set is difficult to read on the screen. The
+\fB\-S\fR
+option to
+\fBless\fR
+can make the result set much more readable because you can scroll it horizontally using the left\-arrow and right\-arrow keys. You can also use
+\fB\-S\fR
+interactively within
+\fBless\fR
+to switch the horizontal\-browse mode on and off. For more information, read the
+\fBless\fR
+manual page:
+.sp
+.RS 3n
+.nf
+shell> \fBman less\fR
+.fi
+.RE
+.TP 3n
+\(bu
+You can specify very complex pager commands for handling query output:
+.sp
+.RS 3n
+.nf
+mysql> \fBpager cat | tee /dr1/tmp/res.txt \\\fR
+ \fB| tee /dr2/tmp/res2.txt | less \-n \-i \-S\fR
+.fi
+.RE
+In this example, the command would send query results to two files in two different directories on two different filesystems mounted on
+\fI/dr1\fR
+and
+\fI/dr2\fR, yet still display the results onscreen via
+\fBless\fR.
+.sp
+.RE
+.PP
+You can also combine the
+\fBtee\fR
+and
+\fBpager\fR
+functions. Have a
+\fBtee\fR
+file enabled and
+\fBpager\fR
+set to
+\fBless\fR, and you are able to browse the results using the
+\fBless\fR
+program and still have everything appended into a file the same time. The difference between the Unix
+\fBtee\fR
+used with the
+\fBpager\fR
+command and the
+\fBmysql\fR
+built\-in
+\fBtee\fR
+command is that the built\-in
+\fBtee\fR
+works even if you do not have the Unix
+\fBtee\fR
+available. The built\-in
+\fBtee\fR
+also logs everything that is printed on the screen, whereas the Unix
+\fBtee\fR
+used with
+\fBpager\fR
+does not log quite that much. Additionally,
+\fBtee\fR
+file logging can be turned on and off interactively from within
+\fBmysql\fR. This is useful when you want to log some queries to a file, but not others.
+.PP
+The default
+mysql>
+prompt can be reconfigured. The string for defining the prompt can contain the following special sequences:
+.TS
+allbox tab(:);
+l l
+l l
+l l
+l l
+l l
+l l
+l l
+l l
+l l
+l l
+l l
+l l
+l l
+l l
+l l
+l l
+l l
+l l
+l l
+l l
+l l
+l l
+l l
+l l
+l l
+l l
+l l
+l l.
+T{
+\fBOption\fR
+T}:T{
+\fBDescription\fR
+T}
+T{
+\\t
+T}:T{
+A tab character
+T}
+T{
+\\\
+T}:T{
+A space (a space follows the backslash)
+T}
+T{
+\\_
+T}:T{
+A space
+T}
+T{
+\\R
+T}:T{
+The current time, in 24\-hour military time (0\-23)
+T}
+T{
+\\r
+T}:T{
+The current time, standard 12\-hour time (1\-12)
+T}
+T{
+\\m
+T}:T{
+Minutes of the current time
+T}
+T{
+\\y
+T}:T{
+The current year, two digits
+T}
+T{
+\\Y
+T}:T{
+The current year, four digits
+T}
+T{
+\\D
+T}:T{
+The full current date
+T}
+T{
+\\s
+T}:T{
+Seconds of the current time
+T}
+T{
+\\v
+T}:T{
+The server version
+T}
+T{
+\\w
+T}:T{
+The current day of the week in three\-letter format (Mon, Tue, \&...)
+T}
+T{
+\\P
+T}:T{
+am/pm
+T}
+T{
+\\o
+T}:T{
+The current month in numeric format
+T}
+T{
+\\O
+T}:T{
+The current month in three\-letter format (Jan, Feb, \&...)
+T}
+T{
+\\c
+T}:T{
+A counter that increments for each statement you issue
+T}
+T{
+\\l
+T}:T{
+The current delimiter. (New in 5.0.25)
+T}
+T{
+\\S
+T}:T{
+Semicolon
+T}
+T{
+\\'
+T}:T{
+Single quote
+T}
+T{
+\\"
+T}:T{
+Double quote
+T}
+T{
+\\d
+T}:T{
+The default database
+T}
+T{
+\\h
+T}:T{
+The server host
+T}
+T{
+\\p
+T}:T{
+The current TCP/IP port or socket file
+T}
+T{
+\\u
+T}:T{
+Your username
+T}
+T{
+\\U
+T}:T{
+Your full
+ \fIuser_name\fR@\fIhost_name\fR
+ account name
+T}
+T{
+\\\\
+T}:T{
+A literal \(lq\\\(rq backslash character
+T}
+T{
+\\n
+T}:T{
+A newline character
+T}
+.TE
+.sp
+.PP
+\(lq\\\(rq
+followed by any other letter just becomes that letter.
+.PP
+If you specify the
+prompt
+command with no argument,
+\fBmysql\fR
+resets the prompt to the default of
+mysql>.
+.PP
+You can set the prompt in several ways:
+.TP 3n
+\(bu
+\fIUse an environment variable.\fR
+You can set the
+MYSQL_PS1
+environment variable to a prompt string. For example:
+.sp
+.RS 3n
+.nf
+shell> \fBexport MYSQL_PS1="(\\u@\\h) [\\d]> "\fR
+.fi
+.RE
+.TP 3n
+\(bu
+\fIUse a command\-line option.\fR
+You can set the
+\fB\-\-prompt\fR
+option on the command line to
+\fBmysql\fR. For example:
+.sp
+.RS 3n
+.nf
+shell> \fBmysql \-\-prompt="(\\u@\\h) [\\d]> "\fR
+(user at host) [database]>
+.fi
+.RE
+.TP 3n
+\(bu
+\fIUse an option file.\fR
+You can set the
+prompt
+option in the
+[mysql]
+group of any MySQL option file, such as
+\fI/etc/my.cnf\fR
+or the
+\fI.my.cnf\fR
+file in your home directory. For example:
+.sp
+.RS 3n
+.nf
+[mysql]
+prompt=(\\\\u@\\\\h) [\\\\d]>\\\\_
+.fi
+.RE
+In this example, note that the backslashes are doubled. If you set the prompt using the
+prompt
+option in an option file, it is advisable to double the backslashes when using the special prompt options. There is some overlap in the set of allowable prompt options and the set of special escape sequences that are recognized in option files. (These sequences are listed in
+Section\ 3.2, \(lqUsing Option Files\(rq.) The overlap may cause you problems if you use single backslashes. For example,
+\\s
+is interpreted as a space rather than as the current seconds value. The following example shows how to define a prompt within an option file to include the current time in
+HH:MM:SS>
+format:
+.sp
+.RS 3n
+.nf
+[mysql]
+prompt="\\\\r:\\\\m:\\\\s> "
+.fi
+.RE
+.TP 3n
+\(bu
+\fISet the prompt interactively.\fR
+You can change your prompt interactively by using the
+prompt
+(or
+\\R) command. For example:
+.sp
+.RS 3n
+.nf
+mysql> \fBprompt (\\u@\\h) [\\d]>\\_\fR
+PROMPT set to '(\\u@\\h) [\\d]>\\_'
+(\fIuser\fR@\fIhost\fR) [\fIdatabase\fR]>
+(\fIuser\fR@\fIhost\fR) [\fIdatabase\fR]> prompt
+Returning to default PROMPT of mysql>
+mysql>
+.fi
+.RE
+.SH "\fBMYSQL\fR SERVER\-SIDE HELP"
+.sp
+.RS 3n
+.nf
+mysql> \fBhelp \fR\fB\fIsearch_string\fR\fR
+.fi
+.RE
+.PP
+If you provide an argument to the
+help
+command,
+\fBmysql\fR
+uses it as a search string to access server\-side help from the contents of the MySQL Reference Manual. The proper operation of this command requires that the help tables in the
+mysql
+database be initialized with help topic information (see
+the section called \(lqSERVER\-SIDE HELP\(rq).
+.PP
+If there is no match for the search string, the search fails:
+.sp
+.RS 3n
+.nf
+mysql> \fBhelp me\fR
+Nothing found
+Please try to run 'help contents' for a list of all accessible topics
+.fi
+.RE
+.PP
+Use
+\fBhelp contents\fR
+to see a list of the help categories:
+.sp
+.RS 3n
+.nf
+mysql> \fBhelp contents\fR
+You asked for help about help category: "Contents"
+For more information, type 'help <item>', where <item> is one of the
+following categories:
+ Account Management
+ Administration
+ Data Definition
+ Data Manipulation
+ Data Types
+ Functions
+ Functions and Modifiers for Use with GROUP BY
+ Geographic Features
+ Language Structure
+ Storage Engines
+ Stored Routines
+ Table Maintenance
+ Transactions
+ Triggers
+.fi
+.RE
+.PP
+If the search string matches multiple items,
+\fBmysql\fR
+shows a list of matching topics:
+.sp
+.RS 3n
+.nf
+mysql> \fBhelp logs\fR
+Many help items for your request exist.
+To make a more specific request, please type 'help <item>',
+where <item> is one of the following topics:
+ SHOW
+ SHOW BINARY LOGS
+ SHOW ENGINE
+ SHOW LOGS
+.fi
+.RE
+.PP
+Use a topic as the search string to see the help entry for that topic:
+.sp
+.RS 3n
+.nf
+mysql> \fBhelp show binary logs\fR
+Name: 'SHOW BINARY LOGS'
+Description:
+Syntax:
+SHOW BINARY LOGS
+SHOW MASTER LOGS
+Lists the binary log files on the server. This statement is used as
+part of the procedure described in [purge\-master\-logs], that shows how
+to determine which logs can be purged.
+mysql> SHOW BINARY LOGS;
++\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-+
+| Log_name | File_size |
++\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-+
+| binlog.000015 | 724935 |
+| binlog.000016 | 733481 |
++\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-+
+.fi
+.RE
+.SH "EXECUTING SQL STATEMENTS FROM A TEXT FILE"
+.PP
+The
+\fBmysql\fR
+client typically is used interactively, like this:
+.sp
+.RS 3n
+.nf
+shell> \fBmysql \fR\fB\fIdb_name\fR\fR
+.fi
+.RE
+.PP
+However, it is also possible to put your SQL statements in a file and then tell
+\fBmysql\fR
+to read its input from that file. To do so, create a text file
+\fItext_file\fR
+that contains the statements you wish to execute. Then invoke
+\fBmysql\fR
+as shown here:
+.sp
+.RS 3n
+.nf
+shell> \fBmysql \fR\fB\fIdb_name\fR\fR\fB < \fR\fB\fItext_file\fR\fR
+.fi
+.RE
+.PP
+If you place a
+USE \fIdb_name\fR
+statement as the first statement in the file, it is unnecessary to specify the database name on the command line:
+.sp
+.RS 3n
+.nf
+shell> \fBmysql < text_file\fR
+.fi
+.RE
+.PP
+If you are already running
+\fBmysql\fR, you can execute an SQL script file using the
+source
+command or
+\\.
+command:
+.sp
+.RS 3n
+.nf
+mysql> \fBsource \fR\fB\fIfile_name\fR\fR
+mysql> \fB\\. \fR\fB\fIfile_name\fR\fR
+.fi
+.RE
+.PP
+Sometimes you may want your script to display progress information to the user. For this you can insert statements like this:
+.sp
+.RS 3n
+.nf
+SELECT '<info_to_display>' AS ' ';
+.fi
+.RE
+.PP
+The statement shown outputs
+<info_to_display>.
+.PP
+For more information about batch mode, see
+Section\ 5, \(lqUsing \fBmysql\fR in Batch Mode\(rq.
+.SH "\fBMYSQL\fR TIPS"
+.PP
+This section describes some techniques that can help you use
+\fBmysql\fR
+more effectively.
+.SS "Displaying Query Results Vertically"
+.PP
+Some query results are much more readable when displayed vertically, instead of in the usual horizontal table format. Queries can be displayed vertically by terminating the query with \\G instead of a semicolon. For example, longer text values that include newlines often are much easier to read with vertical output:
+.sp
+.RS 3n
+.nf
+mysql> \fBSELECT * FROM mails WHERE LENGTH(txt) < 300 LIMIT 300,1\\G\fR
+*************************** 1. row ***************************
+ msg_nro: 3068
+ date: 2000\-03\-01 23:29:50
+time_zone: +0200
+mail_from: Monty
+ reply: monty at no.spam.com
+ mail_to: "Thimble Smith" <tim at no.spam.com>
+ sbj: UTF\-8
+ txt: >>>>> "Thimble" == Thimble Smith writes:
+Thimble> Hi. I think this is a good idea. Is anyone familiar
+Thimble> with UTF\-8 or Unicode? Otherwise, I'll put this on my
+Thimble> TODO list and see what happens.
+Yes, please do that.
+Regards,
+Monty
+ file: inbox\-jani\-1
+ hash: 190402944
+1 row in set (0.09 sec)
+.fi
+.RE
+.\" end of SS subsection "Displaying Query Results Vertically"
+.SS "Using the \-\-safe\-updates Option"
+.PP
+For beginners, a useful startup option is
+\fB\-\-safe\-updates\fR
+(or
+\fB\-\-i\-am\-a\-dummy\fR, which has the same effect). It is helpful for cases when you might have issued a
+DELETE FROM \fItbl_name\fR
+statement but forgotten the
+WHERE
+clause. Normally, such a statement deletes all rows from the table. With
+\fB\-\-safe\-updates\fR, you can delete rows only by specifying the key values that identify them. This helps prevent accidents.
+.PP
+When you use the
+\fB\-\-safe\-updates\fR
+option,
+\fBmysql\fR
+issues the following statement when it connects to the MySQL server:
+.sp
+.RS 3n
+.nf
+SET SQL_SAFE_UPDATES=1,SQL_SELECT_LIMIT=1000, SQL_MAX_JOIN_SIZE=1000000;
+.fi
+.RE
+.PP
+See
+Section\ 5.3, \(lqSET Syntax\(rq.
+.PP
+The
+SET
+statement has the following effects:
+.TP 3n
+\(bu
+You are not allowed to execute an
+UPDATE
+or
+DELETE
+statement unless you specify a key constraint in the
+WHERE
+clause or provide a
+LIMIT
+clause (or both). For example:
+.sp
+.RS 3n
+.nf
+UPDATE \fItbl_name\fR SET \fInot_key_column\fR=\fIval\fR WHERE \fIkey_column\fR=\fIval\fR;
+UPDATE \fItbl_name\fR SET \fInot_key_column\fR=\fIval\fR LIMIT 1;
+.fi
+.RE
+.TP 3n
+\(bu
+The server limits all large
+SELECT
+results to 1,000 rows unless the statement includes a
+LIMIT
+clause.
+.TP 3n
+\(bu
+The server aborts multiple\-table
+SELECT
+statements that probably need to examine more than 1,000,000 row combinations.
+.sp
+.RE
+.PP
+To specify limits different from 1,000 and 1,000,000, you can override the defaults by using the
+\fB\-\-select_limit\fR
+and
+\fB\-\-max_join_size\fR
+options:
+.sp
+.RS 3n
+.nf
+shell> \fBmysql \-\-safe\-updates \-\-select_limit=500 \-\-max_join_size=10000\fR
+.fi
+.RE
+.\" end of SS subsection "Using the \-\-safe\-updates Option"
+.SS "Disabling mysql Auto\-Reconnect"
+.PP
+If the
+\fBmysql\fR
+client loses its connection to the server while sending a statement, it immediately and automatically tries to reconnect once to the server and send the statement again. However, even if
+\fBmysql\fR
+succeeds in reconnecting, your first connection has ended and all your previous session objects and settings are lost: temporary tables, the autocommit mode, and user\-defined and session variables. Also, any current transaction rolls back. This behavior may be dangerous for you, as in the following example where the server was shut down and restarted between the first and second statements without you knowing it:
+.sp
+.RS 3n
+.nf
+mysql> \fBSET @a=1;\fR
+Query OK, 0 rows affected (0.05 sec)
+mysql> \fBINSERT INTO t VALUES(@a);\fR
+ERROR 2006: MySQL server has gone away
+No connection. Trying to reconnect...
+Connection id: 1
+Current database: test
+Query OK, 1 row affected (1.30 sec)
+mysql> \fBSELECT * FROM t;\fR
++\-\-\-\-\-\-+
+| a |
++\-\-\-\-\-\-+
+| NULL |
++\-\-\-\-\-\-+
+1 row in set (0.05 sec)
+.fi
+.RE
+.PP
+The
+ at a
+user variable has been lost with the connection, and after the reconnection it is undefined. If it is important to have
+\fBmysql\fR
+terminate with an error if the connection has been lost, you can start the
+\fBmysql\fR
+client with the
+\fB\-\-skip\-reconnect\fR
+option.
+.PP
+For more information about auto\-reconnect and its effect on state information when a reconnection occurs, see
+Section\ 2.13, \(lqControlling Automatic Reconnect Behavior\(rq.
+.\" end of SS subsection "Disabling mysql Auto\-Reconnect"
+.SH "COPYRIGHT"
+.PP
+Copyright 2007 MySQL AB
+.PP
+This documentation is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License.
+.PP
+This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
+.PP
+You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110\-1301 USA or see http://www.gnu.org/licenses/.
+.PP
+Please email
+<docs at mysql.com>
+for more information or if you are interested in doing a translation.
+.SH "REFERENCES"
+.TP 3
+1.\ Bug#25946
+\%http://bugs.mysql.com/25946
+.SH "SEE ALSO"
+For more information, please refer to the MySQL Reference Manual,
+which may already be installed locally and which is also available
+online at http://dev.mysql.com/doc/.
+.SH AUTHOR
+MySQL AB (http://www.mysql.com/).
Added: branches/sid-5.0/debian/manpages/mysql.server.1
===================================================================
--- branches/sid-5.0/debian/manpages/mysql.server.1 (rev 0)
+++ branches/sid-5.0/debian/manpages/mysql.server.1 2007-11-26 12:34:29 UTC (rev 1020)
@@ -0,0 +1,115 @@
+.\" Title: \fBmysql.server\fR
+.\" Author:
+.\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
+.\" Date: 11/25/2007
+.\" Manual: MySQL Database System
+.\" Source: MySQL 5.0
+.\"
+.TH "\fBMYSQL.SERVER\fR" "1" "11/25/2007" "MySQL 5.0" "MySQL Database System"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
+.SH "NAME"
+mysql.server \- MySQL server startup script
+.SH "SYNOPSIS"
+.HP 19
+\fBmysql {start|stop}\fR
+.SH "DESCRIPTION"
+.PP
+MySQL distributions on Unix include a script named
+\fBmysql.server\fR. It can be used on systems such as Linux and Solaris that use System V\-style run directories to start and stop system services. It is also used by the Mac OS X Startup Item for MySQL.
+.PP
+\fBmysql.server\fR
+can be found in the
+\fIsupport\-files\fR
+directory under your MySQL installation directory or in a MySQL source distribution.
+.PP
+If you use the Linux server RPM package (MySQL\-server\-\fIVERSION\fR.rpm), the
+\fBmysql.server\fR
+script will be installed in the
+\fI/etc/init.d\fR
+directory with the name
+\fImysql\fR. You need not install it manually. See
+Section\ 4.9, \(lqInstalling MySQL from RPM Packages on Linux\(rq, for more information on the Linux RPM packages.
+.PP
+Some vendors provide RPM packages that install a startup script under a different name such as
+\fBmysqld\fR.
+.PP
+If you install MySQL from a source distribution or using a binary distribution format that does not install
+\fBmysql.server\fR
+automatically, you can install it manually. Instructions are provided in
+Section\ 4.16.2.2, \(lqStarting and Stopping MySQL Automatically\(rq.
+.PP
+\fBmysql.server\fR
+reads options from the
+[mysql.server]
+and
+[mysqld]
+sections of option files. For backward compatibility, it also reads
+[mysql_server]
+sections, although you should rename such sections to
+[mysql.server]
+when using MySQL 5.0.
+.PP
+\fBmysql.server\fR
+understands the following options:
+.TP 3n
+\(bu
+\fB\-\-basedir=\fR\fB\fIpath\fR\fR
+.sp
+The path to the MySQL installation directory.
+.TP 3n
+\(bu
+\fB\-\-datadir=\fR\fB\fIpath\fR\fR
+.sp
+The path to the MySQL data directory.
+.TP 3n
+\(bu
+\fB\-\-pid\-file=\fR\fB\fIfile_name\fR\fR
+.sp
+The pathname of the file in which the server should write its process ID.
+.TP 3n
+\(bu
+\fB\-\-service\-startup\-timeout=\fR\fB\fIfile_name\fR\fR
+.sp
+How long in seconds to wait for confirmation of server startup. If the server does not start within this time,
+\fBmysql.server\fR
+exits with an error. The default value is 900. A value of 0 means not to wait at all for startup. Negative values mean to wait forever (no timeout). This option was added in MySQL 5.0.40. Before that, a value of 900 is always used.
+.TP 3n
+\(bu
+\fB\-\-use\-mysqld_safe\fR
+.sp
+Use
+\fBmysqld_safe\fR
+to start the server. This is the default. This option was added in MySQL 5.0.4.
+.TP 3n
+\(bu
+\fB\-\-use\-manager\fR
+.sp
+Use Instance Manager to start the server. This option was added in MySQL 5.0.4.
+.TP 3n
+\(bu
+\fB\-\-user=\fR\fB\fIuser_name\fR\fR
+.sp
+The login username to use for running
+\fBmysqld\fR. This option was added in MySQL 5.0.4.
+.SH "COPYRIGHT"
+.PP
+Copyright 2007 MySQL AB
+.PP
+This documentation is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License.
+.PP
+This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
+.PP
+You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110\-1301 USA or see http://www.gnu.org/licenses/.
+.PP
+Please email
+<docs at mysql.com>
+for more information or if you are interested in doing a translation.
+.SH "SEE ALSO"
+For more information, please refer to the MySQL Reference Manual,
+which may already be installed locally and which is also available
+online at http://dev.mysql.com/doc/.
+.SH AUTHOR
+MySQL AB (http://www.mysql.com/).
Added: branches/sid-5.0/debian/manpages/mysql_client_test.1
===================================================================
--- branches/sid-5.0/debian/manpages/mysql_client_test.1 (rev 0)
+++ branches/sid-5.0/debian/manpages/mysql_client_test.1 2007-11-26 12:34:29 UTC (rev 1020)
@@ -0,0 +1,170 @@
+.\" Title: \fBmysql_client_test\fR
+.\" Author:
+.\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
+.\" Date: 11/21/2007
+.\" Manual: MySQL Database System
+.\" Source: MySQL
+.\"
+.TH "\fBMYSQL_CLIENT_TEST" "1" "11/21/2007" "MySQL" "MySQL Database System"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
+.SH "NAME"
+mysql_client_test \- test client API
+.br
+mysql_client_test_embedded \- test client API for embedded server
+.SH "SYNOPSIS"
+.HP 44
+\fBmysql_client_test [\fR\fB\fIoptions\fR\fR\fB] [\fR\fB\fItest_name\fR\fR\fB] ...\fR
+.HP 53
+\fBmysql_client_test_embedded [\fR\fB\fIoptions\fR\fR\fB] [\fR\fB\fItest_name\fR\fR\fB] ...\fR
+.SH "DESCRIPTION"
+.PP
+The
+\fBmysql_client_test\fR
+program is used for testing aspects of the MySQL client API that cannot be tested using
+\fBmysqltest\fR
+and its test language.
+\fBmysql_client_test_embedded\fR
+is similar but used for testing the embedded server. Both programs are run as part of the test suite.
+.PP
+The source code for the programs can be found in in
+\fItest/mysql_client_test.c\fR
+in a source distribution. The program serves as a good source of examples illustrating how to use various features of the client API.
+.PP
+\fBmysql_client_test\fR
+supports the following options:
+.TP 3n
+\(bu
+\fB\-\-help\fR,
+\fB\-?\fR
+.sp
+Display a help message and exit.
+.TP 3n
+\(bu
+\fB\-b \fR\fB\fIdir_name\fR\fR,
+\fB\-\-basedir=\fR\fB\fIdir_name\fR\fR
+.sp
+The base directory for the tests.
+.TP 3n
+\(bu
+\fB\-t \fR\fB\fIcount\fR\fR,
+\fB\-\-count=\fR\fB\fIcount\fR\fR
+.sp
+The number of times to execute the tests.
+.TP 3n
+\(bu
+\fB\-\-database=\fR\fB\fIdb_name\fR\fR,
+\fB\-D \fR\fB\fIdb_name\fR\fR
+.sp
+The database to use.
+.TP 3n
+\(bu
+\fB\-\-debug[=\fR\fB\fIdebug_options\fR\fR\fB]\fR,
+\fB\-#[\fR\fB\fIdebug_options\fR\fR\fB]\fR
+.sp
+Write a debugging log if MySQL is built with debugging support. The default
+\fIdebug_options\fR
+value is
+\'d:t:o,/tmp/mysql_client_test.trace'.
+.TP 3n
+\(bu
+\fB\-g \fR\fB\fIoption\fR\fR,
+\fB\-\-getopt\-ll\-test=\fR\fB\fIoption\fR\fR
+.sp
+Option to use for testing bugs in the
+getopt
+library.
+.TP 3n
+\(bu
+\fB\-\-host=\fR\fB\fIhost_name\fR\fR,
+\fB\-h \fR\fB\fIhost_name\fR\fR
+.sp
+Connect to the MySQL server on the given host.
+.TP 3n
+\(bu
+\fB\-\-password[=\fR\fB\fIpassword\fR\fR\fB]\fR,
+\fB\-p[\fR\fB\fIpassword\fR\fR\fB]\fR
+.sp
+The password to use when connecting to the server. If you use the short option form (\fB\-p\fR), you
+\fIcannot\fR
+have a space between the option and the password. If you omit the
+\fIpassword\fR
+value following the
+\fB\-\-password\fR
+or
+\fB\-p\fR
+option on the command line, you are prompted for one.
+.TP 3n
+\(bu
+\fB\-\-port=\fR\fB\fIport_num\fR\fR,
+\fB\-P \fR\fB\fIport_num\fR\fR
+.sp
+The TCP/IP port number to use for the connection.
+.TP 3n
+\(bu
+\fB\-A \fR\fB\fIarg\fR\fR,
+\fB\-\-server\-arg=\fR\fB\fIarg\fR\fR
+.sp
+Argument to send to the embedded server.
+.TP 3n
+\(bu
+\fB\-T\fR,
+\fB\-\-show\-tests\fR
+.sp
+Show all test names.
+.TP 3n
+\(bu
+\fB\-\-silent\fR,
+\fB\-s\fR
+.sp
+Be more silent.
+.TP 3n
+\(bu
+\fB\-\-socket=\fR\fB\fIpath\fR\fR,
+\fB\-S \fR\fB\fIpath\fR\fR
+.sp
+The socket file to use when connecting to
+localhost
+(which is the default host).
+.TP 3n
+\(bu
+\fB\-c\fR,
+\fB\-\-testcase\fR
+.sp
+The option may disable some code when run as a
+\fBmysql\-test\-run.pl\fR
+test case.
+.TP 3n
+\(bu
+\fB\-\-user=\fR\fB\fIuser_name\fR\fR,
+\fB\-u \fR\fB\fIuser_name\fR\fR
+.sp
+The MySQL username to use when connecting to the server.
+.TP 3n
+\(bu
+\fB\-v \fR\fB\fIdir_name\fR\fR,
+\fB\-\-vardir=\fR\fB\fIdir_name\fR\fR
+.sp
+The data directory for tests. The default is
+\fImysql\-test/var\fR.
+.SH "COPYRIGHT"
+.PP
+Copyright 2007 MySQL AB
+.PP
+This documentation is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License.
+.PP
+This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
+.PP
+You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110\-1301 USA or see http://www.gnu.org/licenses/.
+.PP
+Please email
+<docs at mysql.com>
+for more information or if you are interested in doing a translation.
+.SH "SEE ALSO"
+For more information, please refer to the MySQL Reference Manual,
+which may already be installed locally and which is also available
+online at http://dev.mysql.com/doc/.
+.SH AUTHOR
+MySQL AB (http://www.mysql.com/).
Added: branches/sid-5.0/debian/manpages/mysql_client_test_embedded.1
===================================================================
--- branches/sid-5.0/debian/manpages/mysql_client_test_embedded.1 (rev 0)
+++ branches/sid-5.0/debian/manpages/mysql_client_test_embedded.1 2007-11-26 12:34:29 UTC (rev 1020)
@@ -0,0 +1 @@
+.so man1/mysql_client_test.1
Added: branches/sid-5.0/debian/manpages/mysql_config.1
===================================================================
--- branches/sid-5.0/debian/manpages/mysql_config.1 (rev 0)
+++ branches/sid-5.0/debian/manpages/mysql_config.1 2007-11-26 12:34:29 UTC (rev 1020)
@@ -0,0 +1,130 @@
+.\" Title: \fBmysql_config\fR
+.\" Author:
+.\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
+.\" Date: 11/25/2007
+.\" Manual: MySQL Database System
+.\" Source: MySQL 5.0
+.\"
+.TH "\fBMYSQL_CONFIG\fR" "1" "11/25/2007" "MySQL 5.0" "MySQL Database System"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
+.SH "NAME"
+mysql_config \- get compile options for compiling clients
+.SH "SYNOPSIS"
+.HP 21
+\fBmysql_config \fR\fB\fIoptions\fR\fR
+.SH "DESCRIPTION"
+.PP
+\fBmysql_config\fR
+provides you with useful information for compiling your MySQL client and connecting it to MySQL.
+.PP
+\fBmysql_config\fR
+supports the following options:
+.TP 3n
+\(bu
+\fB\-\-cflags\fR
+.sp
+Compiler flags to find include files and critical compiler flags and defines used when compiling the
+libmysqlclient
+library.
+.TP 3n
+\(bu
+\fB\-\-include\fR
+.sp
+Compiler options to find MySQL include files. (Note that normally you would use
+\fB\-\-cflags\fR
+instead of this option.)
+.TP 3n
+\(bu
+\fB\-\-libmysqld\-libs\fR,
+\fB\-\-embedded\fR
+.sp
+Libraries and options required to link with the MySQL embedded server.
+.TP 3n
+\(bu
+\fB\-\-libs\fR
+.sp
+Libraries and options required to link with the MySQL client library.
+.TP 3n
+\(bu
+\fB\-\-libs_r\fR
+.sp
+Libraries and options required to link with the thread\-safe MySQL client library.
+.TP 3n
+\(bu
+\fB\-\-port\fR
+.sp
+The default TCP/IP port number, defined when configuring MySQL.
+.TP 3n
+\(bu
+\fB\-\-socket\fR
+.sp
+The default Unix socket file, defined when configuring MySQL.
+.TP 3n
+\(bu
+\fB\-\-version\fR
+.sp
+Version number for the MySQL distribution.
+.sp
+.RE
+.PP
+If you invoke
+\fBmysql_config\fR
+with no options, it displays a list of all options that it supports, and their values:
+.sp
+.RS 3n
+.nf
+shell> \fBmysql_config\fR
+Usage: /usr/local/mysql/bin/mysql_config [options]
+Options:
+ \-\-cflags [\-I/usr/local/mysql/include/mysql \-mcpu=pentiumpro]
+ \-\-include [\-I/usr/local/mysql/include/mysql]
+ \-\-libs [\-L/usr/local/mysql/lib/mysql \-lmysqlclient \-lz
+ \-lcrypt \-lnsl \-lm \-L/usr/lib \-lssl \-lcrypto]
+ \-\-libs_r [\-L/usr/local/mysql/lib/mysql \-lmysqlclient_r
+ \-lpthread \-lz \-lcrypt \-lnsl \-lm \-lpthread]
+ \-\-socket [/tmp/mysql.sock]
+ \-\-port [3306]
+ \-\-version [4.0.16]
+ \-\-libmysqld\-libs [\-L/usr/local/mysql/lib/mysql \-lmysqld \-lpthread \-lz
+ \-lcrypt \-lnsl \-lm \-lpthread \-lrt]
+.fi
+.RE
+.PP
+You can use
+\fBmysql_config\fR
+within a command line to include the value that it displays for a particular option. For example, to compile a MySQL client program, use
+\fBmysql_config\fR
+as follows:
+.sp
+.RS 3n
+.nf
+shell> \fBCFG=/usr/local/mysql/bin/mysql_config\fR
+shell> \fBsh \-c "gcc \-o progname `$CFG \-\-cflags` progname.c `$CFG \-\-libs`"\fR
+.fi
+.RE
+.PP
+When you use
+\fBmysql_config\fR
+this way, be sure to invoke it within backtick (\(lq`\(rq) characters. That tells the shell to execute it and substitute its output into the surrounding command.
+.SH "COPYRIGHT"
+.PP
+Copyright 2007 MySQL AB
+.PP
+This documentation is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License.
+.PP
+This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
+.PP
+You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110\-1301 USA or see http://www.gnu.org/licenses/.
+.PP
+Please email
+<docs at mysql.com>
+for more information or if you are interested in doing a translation.
+.SH "SEE ALSO"
+For more information, please refer to the MySQL Reference Manual,
+which may already be installed locally and which is also available
+online at http://dev.mysql.com/doc/.
+.SH AUTHOR
+MySQL AB (http://www.mysql.com/).
Added: branches/sid-5.0/debian/manpages/mysql_convert_table_format.1
===================================================================
--- branches/sid-5.0/debian/manpages/mysql_convert_table_format.1 (rev 0)
+++ branches/sid-5.0/debian/manpages/mysql_convert_table_format.1 2007-11-26 12:34:29 UTC (rev 1020)
@@ -0,0 +1,121 @@
+.\" Title: \fBmysql_convert_table_format\fR
+.\" Author:
+.\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
+.\" Date: 11/25/2007
+.\" Manual: MySQL Database System
+.\" Source: MySQL 5.0
+.\"
+.TH "\fBMYSQL_CONVERT_TAB" "1" "11/25/2007" "MySQL 5.0" "MySQL Database System"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
+.SH "NAME"
+mysql_convert_table_format \- convert tables to use a given storage engine
+.SH "SYNOPSIS"
+.HP 45
+\fBmysql_convert_table_format [\fR\fB\fIoptions\fR\fR\fB] \fR\fB\fIdb_name\fR\fR
+.SH "DESCRIPTION"
+.PP
+\fBmysql_convert_table_format\fR
+converts the tables in a database to use a particular storage engine (MyISAM
+by default).
+\fBmysql_convert_table_format\fR
+is written in Perl and requires that the
+DBI
+and
+DBD::mysql
+Perl modules be installed (see
+Section\ 4.21, \(lqPerl Installation Notes\(rq).
+.PP
+Invoke
+\fBmysql_convert_table_format\fR
+like this:
+.sp
+.RS 3n
+.nf
+shell> \fBmysql_convert_table_format [\fR\fB\fIoptions\fR\fR\fB]\fR\fB\fIdb_name\fR\fR
+.fi
+.RE
+.PP
+The
+\fIdb_name\fR
+argument indicates the database containing the tables to be converted.
+.PP
+\fBmysql_convert_table_format\fR
+understands the options described in the following list.
+.TP 3n
+\(bu
+\fB\-\-help\fR
+.sp
+Display a help message and exit.
+.TP 3n
+\(bu
+\fB\-\-force\fR
+.sp
+Continue even if errors occur.
+.TP 3n
+\(bu
+\fB\-\-host=\fR\fB\fIhost_name\fR\fR
+.sp
+Connect to the MySQL server on the given host.
+.TP 3n
+\(bu
+\fB\-\-password=\fR\fB\fIpassword\fR\fR
+.sp
+The password to use when connecting to the server. Note that the password value is not optional for this option, unlike for other MySQL programs. You can use an option file to avoid giving the password on the command line.
+.sp
+Specifying a password on the command line should be considered insecure. See
+Section\ 6.6, \(lqKeeping Your Password Secure\(rq.
+.TP 3n
+\(bu
+\fB\-\-port=\fR\fB\fIport_num\fR\fR
+.sp
+The TCP/IP port number to use for the connection.
+.TP 3n
+\(bu
+\fB\-\-socket=\fR\fB\fIpath\fR\fR
+.sp
+For connections to
+localhost, the Unix socket file to use.
+.TP 3n
+\(bu
+\fB\-\-type=\fR\fB\fIengine_name\fR\fR
+.sp
+Specify the storage engine that the tables should be converted to use. The default is
+MyISAM
+if this option is not given.
+.TP 3n
+\(bu
+\fB\-\-user=\fR\fB\fIuser_name\fR\fR
+.sp
+The MySQL username to use when connecting to the server.
+.TP 3n
+\(bu
+\fB\-\-verbose\fR
+.sp
+Verbose mode. Print more information about what the program does.
+.TP 3n
+\(bu
+\fB\-\-version\fR
+.sp
+Display version information and exit.
+.SH "COPYRIGHT"
+.PP
+Copyright 2007 MySQL AB
+.PP
+This documentation is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License.
+.PP
+This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
+.PP
+You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110\-1301 USA or see http://www.gnu.org/licenses/.
+.PP
+Please email
+<docs at mysql.com>
+for more information or if you are interested in doing a translation.
+.SH "SEE ALSO"
+For more information, please refer to the MySQL Reference Manual,
+which may already be installed locally and which is also available
+online at http://dev.mysql.com/doc/.
+.SH AUTHOR
+MySQL AB (http://www.mysql.com/).
Added: branches/sid-5.0/debian/manpages/mysql_explain_log.1
===================================================================
--- branches/sid-5.0/debian/manpages/mysql_explain_log.1 (rev 0)
+++ branches/sid-5.0/debian/manpages/mysql_explain_log.1 2007-11-26 12:34:29 UTC (rev 1020)
@@ -0,0 +1,114 @@
+.\" Title: \fBmysql_explain_log\fR
+.\" Author:
+.\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
+.\" Date: 11/25/2007
+.\" Manual: MySQL Database System
+.\" Source: MySQL 5.0
+.\"
+.TH "\fBMYSQL_EXPLAIN_LOG" "1" "11/25/2007" "MySQL 5.0" "MySQL Database System"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
+.SH "NAME"
+mysql_explain_log \- use EXPLAIN on statements in query log
+.SH "SYNOPSIS"
+.HP 39
+\fBmysql_explain_log [\fR\fB\fIoptions\fR\fR\fB] < \fR\fB\fIlog_file\fR\fR
+.SH "DESCRIPTION"
+.PP
+\fBmysql_explain_log\fR
+reads its standard input for query log contents. It uses
+EXPLAIN
+to analyze
+SELECT
+statements found in the input.
+UPDATE
+statements are rewritten to
+SELECT
+statements and also analyzed with
+EXPLAIN.
+\fBmysql_explain_log\fR
+then displays a summary of its results.
+.PP
+The results may assist you in determining which queries result in table scans and where it would be beneficial to add indexes to your tables.
+.PP
+Invoke
+\fBmysql_explain_log\fR
+like this, where
+\fIlog_file\fR
+contains all or part of a MySQL query log:
+.sp
+.RS 3n
+.nf
+shell> \fBmysql_explain_log [\fR\fB\fIoptions\fR\fR\fB] < \fR\fB\fIlog_file\fR\fR
+.fi
+.RE
+.PP
+\fBmysql_explain_log\fR
+understands the following options:
+.TP 3n
+\(bu
+\fB\-\-help\fR,
+\fB\-?\fR
+.sp
+Display a help message and exit.
+.TP 3n
+\(bu
+\fB\-\-date=\fR\fB\fIYYMMDD\fR\fR,
+\fB\-d \fR\fB\fIYYMMDD\fR\fR
+.sp
+Select entries from the log only for the given date.
+.TP 3n
+\(bu
+\fB\-\-host=\fR\fB\fIhost_name\fR\fR,
+\fB\-h \fR\fB\fIhost_name\fR\fR
+.sp
+Connect to the MySQL server on the given host.
+.TP 3n
+\(bu
+\fB\-\-password=\fR\fB\fIpassword\fR\fR,
+\fB\-p \fR\fB\fIpassword\fR\fR
+.sp
+The password to use when connecting to the server.
+.sp
+Specifying a password on the command line should be considered insecure. See
+Section\ 6.6, \(lqKeeping Your Password Secure\(rq.
+.TP 3n
+\(bu
+\fB\-\-printerror=1\fR,
+\fB\-e 1\fR
+.sp
+Enable error output.
+.TP 3n
+\(bu
+\fB\-\-socket=\fR\fB\fIpath\fR\fR,
+\fB\-S \fR\fB\fIpath\fR\fR
+.sp
+For connections to
+localhost, the Unix socket file to use, or, on Windows, the name of the named pipe to use.
+.TP 3n
+\(bu
+\fB\-\-user=\fR\fB\fIuser_name\fR\fR,
+\fB\-u \fR\fB\fIuser_name\fR\fR
+.sp
+The MySQL username to use when connecting to the server.
+.SH "COPYRIGHT"
+.PP
+Copyright 2007 MySQL AB
+.PP
+This documentation is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License.
+.PP
+This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
+.PP
+You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110\-1301 USA or see http://www.gnu.org/licenses/.
+.PP
+Please email
+<docs at mysql.com>
+for more information or if you are interested in doing a translation.
+.SH "SEE ALSO"
+For more information, please refer to the MySQL Reference Manual,
+which may already be installed locally and which is also available
+online at http://dev.mysql.com/doc/.
+.SH AUTHOR
+MySQL AB (http://www.mysql.com/).
Added: branches/sid-5.0/debian/manpages/mysql_find_rows.1
===================================================================
--- branches/sid-5.0/debian/manpages/mysql_find_rows.1 (rev 0)
+++ branches/sid-5.0/debian/manpages/mysql_find_rows.1 2007-11-26 12:34:29 UTC (rev 1020)
@@ -0,0 +1,102 @@
+.\" Title: \fBmysql_find_rows\fR
+.\" Author:
+.\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
+.\" Date: 11/25/2007
+.\" Manual: MySQL Database System
+.\" Source: MySQL 5.0
+.\"
+.TH "\fBMYSQL_FIND_ROWS\\F" "1" "11/25/2007" "MySQL 5.0" "MySQL Database System"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
+.SH "NAME"
+mysql_find_rows \- extract SQL statements from files
+.SH "SYNOPSIS"
+.HP 42
+\fBmysql_find_rows [\fR\fB\fIoptions\fR\fR\fB] [\fR\fB\fIfile_name\fR\fR\fB ...]\fR
+.SH "DESCRIPTION"
+.PP
+\fBmysql_find_rows\fR
+reads files containing SQL statements and extracts statements that match a given regular expression or that contain
+USE \fIdb_name\fR
+or
+SET
+statements. The utility was written for use with update log files, but it can be used with other files that contain SQL statements.
+.PP
+Invoke
+\fBmysql_find_rows\fR
+like this:
+.sp
+.RS 3n
+.nf
+shell> \fBmysql_find_rows [\fR\fB\fIoptions\fR\fR\fB] [\fR\fB\fIfile_name\fR\fR\fB ...]\fR
+.fi
+.RE
+.PP
+Each
+\fIfile_name\fR
+argument should be the name of file containing SQL statements. If no filenames are given,
+\fBmysql_find_rows\fR
+reads the standard input.
+.PP
+Examples:
+.sp
+.RS 3n
+.nf
+mysql_find_rows \-\-regexp=problem_table \-\-rows=20 < update.log
+mysql_find_rows \-\-regexp=problem_table update\-log.1 update\-log.2
+.fi
+.RE
+.PP
+\fBmysql_find_rows\fR
+supports the following options:
+.TP 3n
+\(bu
+\fB\-\-help\fR,
+\fB\-\-Information\fR
+.sp
+Display a help message and exit.
+.TP 3n
+\(bu
+\fB\-\-regexp=\fR\fB\fIpattern\fR\fR
+.sp
+Display queries that match the pattern.
+.TP 3n
+\(bu
+\fB\-\-rows=\fR\fB\fIN\fR\fR
+.sp
+Quit after displaying
+\fIN\fR
+queries.
+.TP 3n
+\(bu
+\fB\-\-skip\-use\-db\fR
+.sp
+Do not include
+USE \fIdb_name\fR
+statements in the output.
+.TP 3n
+\(bu
+\fB\-\-start_row=\fR\fB\fIN\fR\fR
+.sp
+Start output from this row.
+.SH "COPYRIGHT"
+.PP
+Copyright 2007 MySQL AB
+.PP
+This documentation is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License.
+.PP
+This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
+.PP
+You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110\-1301 USA or see http://www.gnu.org/licenses/.
+.PP
+Please email
+<docs at mysql.com>
+for more information or if you are interested in doing a translation.
+.SH "SEE ALSO"
+For more information, please refer to the MySQL Reference Manual,
+which may already be installed locally and which is also available
+online at http://dev.mysql.com/doc/.
+.SH AUTHOR
+MySQL AB (http://www.mysql.com/).
Added: branches/sid-5.0/debian/manpages/mysql_fix_extensions.1
===================================================================
--- branches/sid-5.0/debian/manpages/mysql_fix_extensions.1 (rev 0)
+++ branches/sid-5.0/debian/manpages/mysql_fix_extensions.1 2007-11-26 12:34:29 UTC (rev 1020)
@@ -0,0 +1,65 @@
+.\" Title: \fBmysql_fix_extensions\fR
+.\" Author:
+.\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
+.\" Date: 11/25/2007
+.\" Manual: MySQL Database System
+.\" Source: MySQL 5.0
+.\"
+.TH "\fBMYSQL_FIX_EXTENSI" "1" "11/25/2007" "MySQL 5.0" "MySQL Database System"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
+.SH "NAME"
+mysql_fix_extensions \- make table filename extensions lowercase
+.SH "SYNOPSIS"
+.HP 30
+\fBmysql_fix_extensions \fR\fB\fIdata_dir\fR\fR
+.SH "DESCRIPTION"
+.PP
+\fBmysql_fix_extensions\fR
+converts the extensions for
+MyISAM
+table files to lowercase. It looks for files with an extension that that matches any lettercase variant of
+\fI.frm\fR,
+\fI.myd\fR,
+\fI.myi\fR,
+\fI.isd\fR, and
+\fI.ism\fR
+and renames them to have extensionsn of
+\fI.frm\fR,
+\fI.MYD\fR,
+\fI.MYI\fR,
+\fI.ISD\fR, and
+\fI.ISM\fR, respectively. This can be useful after transferring the files from a system with case\-insensitive filenames (such as Windows) to a system with case\-sensitive filenames.
+.PP
+Invoke
+\fBmysql_fix_extensions\fR
+like this, where
+\fIdata_dir\fR
+is the pathname to the MySQL data directory.
+.sp
+.RS 3n
+.nf
+shell> \fBmysql_fix_extensions \fR\fB\fIdata_dir\fR\fR
+.fi
+.RE
+.SH "COPYRIGHT"
+.PP
+Copyright 2007 MySQL AB
+.PP
+This documentation is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License.
+.PP
+This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
+.PP
+You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110\-1301 USA or see http://www.gnu.org/licenses/.
+.PP
+Please email
+<docs at mysql.com>
+for more information or if you are interested in doing a translation.
+.SH "SEE ALSO"
+For more information, please refer to the MySQL Reference Manual,
+which may already be installed locally and which is also available
+online at http://dev.mysql.com/doc/.
+.SH AUTHOR
+MySQL AB (http://www.mysql.com/).
Added: branches/sid-5.0/debian/manpages/mysql_fix_privilege_tables.1
===================================================================
--- branches/sid-5.0/debian/manpages/mysql_fix_privilege_tables.1 (rev 0)
+++ branches/sid-5.0/debian/manpages/mysql_fix_privilege_tables.1 2007-11-26 12:34:29 UTC (rev 1020)
@@ -0,0 +1,127 @@
+.\" Title: \fBmysql_fix_privilege_tables\fR
+.\" Author:
+.\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
+.\" Date: 11/25/2007
+.\" Manual: MySQL Database System
+.\" Source: MySQL 5.0
+.\"
+.TH "\fBMYSQL_FIX_PRIVILE" "1" "11/25/2007" "MySQL 5.0" "MySQL Database System"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
+.SH "NAME"
+mysql_fix_privilege_tables \- upgrade MySQL system tables
+.SH "SYNOPSIS"
+.HP 52
+\fBmysql_fix_privilege_tables \-\-password=\fR\fB\fIroot_password\fR\fR
+.SH "DESCRIPTION"
+.PP
+Some releases of MySQL introduce changes to the structure of the system tables in the
+mysql
+database to add new privileges or support new features. When you update to a new version of MySQL, you should update your system tables as well to make sure that their structure is up to date. Otherwise, there might be capabilities that you cannot take advantage of. First, make a backup of your
+mysql
+database, and then use the following procedure.
+.sp
+.it 1 an-trap
+.nr an-no-space-flag 1
+.nr an-break-flag 1
+.br
+\fBNote\fR
+.PP
+As of MySQL 5.0.19,
+\fBmysql_fix_privilege_tables\fR
+is superseded by
+\fBmysql_upgrade\fR, which should be used instead. See
+\fBmysql_upgrade\fR(1).
+.PP
+On Unix or Unix\-like systems, update the system tables by running the
+\fBmysql_fix_privilege_tables\fR
+script:
+.sp
+.RS 3n
+.nf
+shell> \fBmysql_fix_privilege_tables\fR
+.fi
+.RE
+.PP
+You must run this script while the server is running. It attempts to connect to the server running on the local host as
+root. If your
+root
+account requires a password, indicate the password on the command line like this:
+.sp
+.RS 3n
+.nf
+shell> \fBmysql_fix_privilege_tables \-\-password=\fR\fB\fIroot_password\fR\fR
+.fi
+.RE
+.PP
+The
+\fBmysql_fix_privilege_tables\fR
+script performs any actions necessary to convert your system tables to the current format. You might see some
+Duplicate column name
+warnings as it runs; you can ignore them.
+.PP
+After running the script, stop the server and restart it so that it uses any changes that were made to the system tables.
+.PP
+On Windows systems, MySQL distributions include a
+\fImysql_fix_privilege_tables.sql\fR
+SQL script that you can run using the
+\fBmysql\fR
+client. For example, if your MySQL installation is located at
+\fIC:\\Program Files\\MySQL\\MySQL Server 5.0\fR, the commands look like this:
+.sp
+.RS 3n
+.nf
+C:\\> \fBcd "C:\\Program Files\\MySQL\\MySQL Server 5.0"\fR
+C:\\> \fBbin\\mysql \-u root \-p mysql\fR
+mysql> \fBSOURCE share/mysql_fix_privilege_tables.sql\fR
+.fi
+.RE
+.sp
+.it 1 an-trap
+.nr an-no-space-flag 1
+.nr an-break-flag 1
+.br
+\fBNote\fR
+.PP
+Prior to version 5.0.38, this script is found in the
+\fIscripts\fR
+directory.
+.PP
+The
+\fBmysql\fR
+command will prompt you for the
+root
+password; enter it when prompted.
+.PP
+If your installation is located in some other directory, adjust the pathnames appropriately.
+.PP
+As with the Unix procedure, you might see some
+Duplicate column name
+warnings as
+\fBmysql\fR
+processes the statements in the
+\fImysql_fix_privilege_tables.sql\fR
+script; you can ignore them.
+.PP
+After running the script, stop the server and restart it.
+.SH "COPYRIGHT"
+.PP
+Copyright 2007 MySQL AB
+.PP
+This documentation is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License.
+.PP
+This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
+.PP
+You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110\-1301 USA or see http://www.gnu.org/licenses/.
+.PP
+Please email
+<docs at mysql.com>
+for more information or if you are interested in doing a translation.
+.SH "SEE ALSO"
+For more information, please refer to the MySQL Reference Manual,
+which may already be installed locally and which is also available
+online at http://dev.mysql.com/doc/.
+.SH AUTHOR
+MySQL AB (http://www.mysql.com/).
Added: branches/sid-5.0/debian/manpages/mysql_install_db.1
===================================================================
--- branches/sid-5.0/debian/manpages/mysql_install_db.1 (rev 0)
+++ branches/sid-5.0/debian/manpages/mysql_install_db.1 2007-11-26 12:34:29 UTC (rev 1020)
@@ -0,0 +1,140 @@
+.\" Title: \fBmysql_install_db\fR
+.\" Author:
+.\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
+.\" Date: 11/25/2007
+.\" Manual: MySQL Database System
+.\" Source: MySQL 5.0
+.\"
+.TH "\fBMYSQL_INSTALL_DB\\" "1" "11/25/2007" "MySQL 5.0" "MySQL Database System"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
+.SH "NAME"
+mysql_install_db \- initialize MySQL data directory
+.SH "SYNOPSIS"
+.HP 27
+\fBmysql_install_db [\fR\fB\fIoptions\fR\fR\fB]\fR
+.SH "DESCRIPTION"
+.PP
+\fBmysql_install_db\fR
+initializes the MySQL data directory and creates the system tables that it contains, if they do not exist. Because the MySQL server,
+\fBmysqld\fR, needs to access the data directory when it runs later, you should either run
+\fBmysql_install_db\fR
+from the same account that will be used for running
+\fBmysqld\fR
+or run it as
+root
+and use the
+\fB\-\-user\fR
+option to indicate the username that
+\fBmysqld\fR
+will run as.
+.PP
+To invoke
+\fBmysql_install_db\fR, use the following syntax:
+.sp
+.RS 3n
+.nf
+shell> \fBmysql_install_db [\fR\fB\fIoptions\fR\fR\fB]\fR
+.fi
+.RE
+.PP
+\fBmysql_install_db\fR
+needs to invoke
+\fBmysqld\fR
+with the
+\fB\-\-bootstrap\fR
+and
+\fB\-\-skip\-grant\-tables\fR
+options (see
+Section\ 4.15.2, \(lqTypical \fBconfigure\fR Options\(rq). If MySQL was configured with the
+\fB\-\-disable\-grant\-options\fR
+option,
+\fB\-\-bootstrap\fR
+and
+\fB\-\-skip\-grant\-tables\fR
+will be disabled. To handle this, set the
+MYSQLD_BOOTSTRAP
+environment variable to the full pathname of a server that has all options enabled.
+\fBmysql_install_db\fR
+will use that server.
+.PP
+\fBmysql_install_db\fR
+supports the following options:
+.TP 3n
+\(bu
+\fB\-\-basedir=\fR\fB\fIpath\fR\fR
+.sp
+The path to the MySQL installation directory.
+.TP 3n
+\(bu
+\fB\-\-force\fR
+.sp
+Causes
+\fBmysql_install_db\fR
+to run even if DNS does not work. In that case, grant table entries that normally use hostnames will use IP addresses.
+.TP 3n
+\(bu
+\fB\-\-datadir=\fR\fB\fIpath\fR\fR,
+\fB\-\-ldata=\fR\fB\fIpath\fR\fR
+.sp
+The path to the MySQL data directory.
+.TP 3n
+\(bu
+\fB\-\-rpm\fR
+.sp
+For internal use. This option is used by RPM files during the MySQL installation process.
+.TP 3n
+\(bu
+\fB\-\-skip\-name\-resolve\fR
+.sp
+Use IP addresses rather than hostnames when creating grant table entries. This option can be useful if your DNS does not work.
+.TP 3n
+\(bu
+\fB\-\-srcdir=\fR\fB\fIpath\fR\fR
+.sp
+For internal use. The directory under which
+\fBmysql_install_db\fR
+looks for support files such as the error message file and the file for populating the help tables. This option was added in MySQL 5.0.32.
+.TP 3n
+\(bu
+\fB\-\-user=\fR\fB\fIuser_name\fR\fR
+.sp
+The login username to use for running
+\fBmysqld\fR. Files and directories created by
+\fBmysqld\fR
+will be owned by this user. You must be
+root
+to use this option. By default,
+\fBmysqld\fR
+runs using your current login name and files and directories that it creates will be owned by you.
+.TP 3n
+\(bu
+\fB\-\-verbose\fR
+.sp
+Verbose mode. Print more information about what the program does.
+.TP 3n
+\(bu
+\fB\-\-windows\fR
+.sp
+For internal use. This option is used for creating Windows distributions.
+.SH "COPYRIGHT"
+.PP
+Copyright 2007 MySQL AB
+.PP
+This documentation is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License.
+.PP
+This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
+.PP
+You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110\-1301 USA or see http://www.gnu.org/licenses/.
+.PP
+Please email
+<docs at mysql.com>
+for more information or if you are interested in doing a translation.
+.SH "SEE ALSO"
+For more information, please refer to the MySQL Reference Manual,
+which may already be installed locally and which is also available
+online at http://dev.mysql.com/doc/.
+.SH AUTHOR
+MySQL AB (http://www.mysql.com/).
Added: branches/sid-5.0/debian/manpages/mysql_secure_installation.1
===================================================================
--- branches/sid-5.0/debian/manpages/mysql_secure_installation.1 (rev 0)
+++ branches/sid-5.0/debian/manpages/mysql_secure_installation.1 2007-11-26 12:34:29 UTC (rev 1020)
@@ -0,0 +1,71 @@
+.\" Title: \fBmysql_secure_installation\fR
+.\" Author:
+.\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
+.\" Date: 11/25/2007
+.\" Manual: MySQL Database System
+.\" Source: MySQL 5.0
+.\"
+.TH "\fBMYSQL_SECURE_INST" "1" "11/25/2007" "MySQL 5.0" "MySQL Database System"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
+.SH "NAME"
+mysql_secure_installation \- improve MySQL installation security
+.SH "SYNOPSIS"
+.HP 26
+\fBmysql_secure_installation\fR
+.SH "DESCRIPTION"
+.PP
+This program enables you to improve the security of your MySQL installation in the following ways:
+.TP 3n
+\(bu
+You can set a password for
+root
+accounts.
+.TP 3n
+\(bu
+You can remove
+root
+accounts that are accessible from outside the local host.
+.TP 3n
+\(bu
+You can remove anonymous\-user accounts.
+.TP 3n
+\(bu
+You can remove the
+test
+database, which by default can be accessed by anonymous users.
+.sp
+.RE
+.PP
+Invoke
+\fBmysql_secure_installation\fR
+without arguments:
+.sp
+.RS 3n
+.nf
+shell> \fBmysql_secure_installation\fR
+.fi
+.RE
+.PP
+The script will prompt you to determine which actions to perform.
+.SH "COPYRIGHT"
+.PP
+Copyright 2007 MySQL AB
+.PP
+This documentation is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License.
+.PP
+This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
+.PP
+You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110\-1301 USA or see http://www.gnu.org/licenses/.
+.PP
+Please email
+<docs at mysql.com>
+for more information or if you are interested in doing a translation.
+.SH "SEE ALSO"
+For more information, please refer to the MySQL Reference Manual,
+which may already be installed locally and which is also available
+online at http://dev.mysql.com/doc/.
+.SH AUTHOR
+MySQL AB (http://www.mysql.com/).
Added: branches/sid-5.0/debian/manpages/mysql_setpermission.1
===================================================================
--- branches/sid-5.0/debian/manpages/mysql_setpermission.1 (rev 0)
+++ branches/sid-5.0/debian/manpages/mysql_setpermission.1 2007-11-26 12:34:29 UTC (rev 1020)
@@ -0,0 +1,108 @@
+.\" Title: \fBmysql_setpermission\fR
+.\" Author:
+.\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
+.\" Date: 11/25/2007
+.\" Manual: MySQL Database System
+.\" Source: MySQL 5.0
+.\"
+.TH "\fBMYSQL_SETPERMISSI" "1" "11/25/2007" "MySQL 5.0" "MySQL Database System"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
+.SH "NAME"
+mysql_setpermission \- interactively set permissions in grant tables
+.SH "SYNOPSIS"
+.HP 30
+\fBmysql_setpermission [\fR\fB\fIoptions\fR\fR\fB]\fR
+.SH "DESCRIPTION"
+.PP
+\fBmysql_setpermission\fR
+is a Perl script that was originally written and contributed by Luuk de Boer. It interactively sets permissions in the MySQL grant tables.
+\fBmysql_setpermission\fR
+is written in Perl and requires that the
+DBI
+and
+DBD::mysql
+Perl modules be installed (see
+Section\ 4.21, \(lqPerl Installation Notes\(rq).
+.PP
+Invoke
+\fBmysql_setpermission\fR
+like this:
+.sp
+.RS 3n
+.nf
+shell> \fBmysql_setpermission [\fR\fB\fIoptions\fR\fR\fB]\fR
+.fi
+.RE
+.PP
+\fIoptions\fR
+should be either
+\fB\-\-help\fR
+to display the help message, or options that indicate how to connect to the MySQL server. The account used when you connect determines which permissions you have when attempting to modify existing permissions in the grant tables.
+.PP
+\fBmysql_setpermissions\fR
+also reads options from the
+[client]
+and
+[perl]
+groups in the
+\fI.my.cnf\fR
+file in your home directory, if the file exists.
+.PP
+\fBmysql_setpermission\fR
+understands the following options:
+.TP 3n
+\(bu
+\fB\-\-help\fR
+.sp
+Display a help message and exit.
+.TP 3n
+\(bu
+\fB\-\-host=\fR\fB\fIhost_name\fR\fR
+.sp
+Connect to the MySQL server on the given host.
+.TP 3n
+\(bu
+\fB\-\-password=\fR\fB\fIpassword\fR\fR
+.sp
+The password to use when connecting to the server. Note that the password value is not optional for this option, unlike for other MySQL programs. You can use an option file to avoid giving the password on the command line.
+.sp
+Specifying a password on the command line should be considered insecure. See
+Section\ 6.6, \(lqKeeping Your Password Secure\(rq.
+.TP 3n
+\(bu
+\fB\-\-port=\fR\fB\fIport_num\fR\fR
+.sp
+The TCP/IP port number to use for the connection.
+.TP 3n
+\(bu
+\fB\-\-socket=\fR\fB\fIpath\fR\fR
+.sp
+For connections to
+localhost, the Unix socket file to use.
+.TP 3n
+\(bu
+\fB\-\-user=\fR\fB\fIuser_name\fR\fR
+.sp
+The MySQL username to use when connecting to the server.
+.SH "COPYRIGHT"
+.PP
+Copyright 2007 MySQL AB
+.PP
+This documentation is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License.
+.PP
+This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
+.PP
+You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110\-1301 USA or see http://www.gnu.org/licenses/.
+.PP
+Please email
+<docs at mysql.com>
+for more information or if you are interested in doing a translation.
+.SH "SEE ALSO"
+For more information, please refer to the MySQL Reference Manual,
+which may already be installed locally and which is also available
+online at http://dev.mysql.com/doc/.
+.SH AUTHOR
+MySQL AB (http://www.mysql.com/).
Added: branches/sid-5.0/debian/manpages/mysql_tableinfo.1
===================================================================
--- branches/sid-5.0/debian/manpages/mysql_tableinfo.1 (rev 0)
+++ branches/sid-5.0/debian/manpages/mysql_tableinfo.1 2007-11-26 12:34:29 UTC (rev 1020)
@@ -0,0 +1,192 @@
+.\" Title: \fBmysql_tableinfo\fR
+.\" Author:
+.\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
+.\" Date: 11/25/2007
+.\" Manual: MySQL Database System
+.\" Source: MySQL 5.0
+.\"
+.TH "\fBMYSQL_TABLEINFO\\F" "1" "11/25/2007" "MySQL 5.0" "MySQL Database System"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
+.SH "NAME"
+mysql_tableinfo \- generate database metadata
+.SH "SYNOPSIS"
+.HP 55
+\fBmysql_tableinfo [\fR\fB\fIoptions\fR\fR\fB] \fR\fB\fIdb_name\fR\fR\fB [\fR\fB\fIdb_like\fR\fR\fB [\fR\fB\fItbl_like\fR\fR\fB]]\fR
+.SH "DESCRIPTION"
+.PP
+\fBmysql_tableinfo\fR
+creates tables and populates them with database metadata. It uses
+SHOW DATABASES,
+SHOW TABLES,
+SHOW TABLE STATUS,
+SHOW COLUMNS, and
+SHOW INDEX
+to obtain the metadata.
+.PP
+In MySQL 5.0 and up, the
+INFORMATION_SCHEMA
+database contains the same kind of information in the
+SCHEMATA,
+TABLES,
+COLUMNS, and
+STATISTICS
+tables. See
+Chapter\ 21, INFORMATION_SCHEMA Tables.
+.PP
+Invoke
+\fBmysql_tableinfo\fR
+like this:
+.sp
+.RS 3n
+.nf
+shell> \fBmysql_tableinfo [\fR\fB\fIoptions\fR\fR\fB] \fR\fB\fIdb_name\fR\fR\fB [\fR\fB\fIdb_like\fR\fR\fB [\fR\fB\fItbl_like\fR\fR\fB]]\fR
+.fi
+.RE
+.PP
+The
+\fIdb_name\fR
+argument indicates which database
+\fBmysql_tableinfo\fR
+should use as the location for the metadata tables. The database will be created if it does not exist. The tables will be named
+db,
+tbl
+(or
+tbl_status),
+col, and
+idx.
+.PP
+If the
+\fIdb_like\fR
+or
+\fItbl_like\fR
+arguments are given, they are used as patterns and metadata is generated only for databases or tables that match the patterns. These arguments default to
+%
+if not given.
+.PP
+Examples:
+.sp
+.RS 3n
+.nf
+mysql_tableinfo info
+mysql_tableinfo info world
+mysql_tableinfo info mydb tmp%
+.fi
+.RE
+.PP
+Each of the commands stores information into tables in the
+info
+database. The first stores information for all databases and tables. The second stores information for all tables in the
+world
+database. The third stores information for tables in the
+mydb
+database that have names matching the pattern
+tmp%.
+.PP
+\fBmysql_tableinfo\fR
+supports the following options:
+.TP 3n
+\(bu
+\fB\-\-help\fR
+.sp
+Display a help message and exit.
+.TP 3n
+\(bu
+\fB\-\-clear\fR
+.sp
+Before populating each metadata table, drop it if it exists.
+.TP 3n
+\(bu
+\fB\-\-clear\-only\fR
+.sp
+Similar to
+\fB\-\-clear\fR, but exits after dropping the metadata tables to be populated.
+.TP 3n
+\(bu
+\fB\-\-col\fR
+.sp
+Generate column metadata into the
+col
+table.
+.TP 3n
+\(bu
+\fB\-\-host=\fR\fB\fIhost_name\fR\fR,
+\fB\-h \fR\fB\fIhost_name\fR\fR
+.sp
+Connect to the MySQL server on the given host.
+.TP 3n
+\(bu
+\fB\-\-idx\fR
+.sp
+Generate index metadata into the
+idx
+table.
+.TP 3n
+\(bu
+\fB\-\-password=\fR\fB\fIpassword\fR\fR,
+\fB\-p\fR\fB\fIpassword\fR\fR
+.sp
+The password to use when connecting to the server. Note that the password value is not optional for this option, unlike for other MySQL programs. You can use an option file to avoid giving the password on the command line.
+.sp
+Specifying a password on the command line should be considered insecure. See
+Section\ 6.6, \(lqKeeping Your Password Secure\(rq.
+.TP 3n
+\(bu
+\fB\-\-port=\fR\fB\fIport_num\fR\fR,
+\fB\-P \fR\fB\fIport_num\fR\fR
+.sp
+The TCP/IP port number to use for the connection.
+.TP 3n
+\(bu
+\fB\-\-prefix=\fR\fB\fIprefix_str\fR\fR
+.sp
+Add
+\fIprefix_str\fR
+at the beginning of each metadata table name.
+.TP 3n
+\(bu
+\fB\-\-quiet\fR,
+\fB\-q\fR
+.sp
+Be silent except for errors.
+.TP 3n
+\(bu
+\fB\-\-socket=\fR\fB\fIpath\fR\fR,
+\fB\-S \fR\fB\fIpath\fR\fR
+.sp
+The Unix socket file to use for the connection.
+.TP 3n
+\(bu
+\fB\-\-tbl\-status\fR
+.sp
+Use
+SHOW TABLE STATUS
+instead of
+SHOW TABLES. This provides more complete information, but is slower.
+.TP 3n
+\(bu
+\fB\-\-user=\fR\fB\fIuser_name\fR\fR,
+\fB\-u \fR\fB\fIuser_name\fR\fR
+.sp
+The MySQL username to use when connecting to the server.
+.SH "COPYRIGHT"
+.PP
+Copyright 2007 MySQL AB
+.PP
+This documentation is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License.
+.PP
+This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
+.PP
+You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110\-1301 USA or see http://www.gnu.org/licenses/.
+.PP
+Please email
+<docs at mysql.com>
+for more information or if you are interested in doing a translation.
+.SH "SEE ALSO"
+For more information, please refer to the MySQL Reference Manual,
+which may already be installed locally and which is also available
+online at http://dev.mysql.com/doc/.
+.SH AUTHOR
+MySQL AB (http://www.mysql.com/).
Added: branches/sid-5.0/debian/manpages/mysql_tzinfo_to_sql.1
===================================================================
--- branches/sid-5.0/debian/manpages/mysql_tzinfo_to_sql.1 (rev 0)
+++ branches/sid-5.0/debian/manpages/mysql_tzinfo_to_sql.1 2007-11-26 12:34:29 UTC (rev 1020)
@@ -0,0 +1,104 @@
+.\" Title: \fBmysql_tzinfo_to_sql\fR
+.\" Author:
+.\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
+.\" Date: 11/25/2007
+.\" Manual: MySQL Database System
+.\" Source: MySQL 5.0
+.\"
+.TH "\fBMYSQL_TZINFO_TO_S" "1" "11/25/2007" "MySQL 5.0" "MySQL Database System"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
+.SH "NAME"
+mysql_tzinfo_to_sql \- load the time zone tables
+.SH "SYNOPSIS"
+.HP 30
+\fBmysql_tzinfo_to_sql \fR\fB\fIarguments\fR\fR
+.SH "DESCRIPTION"
+.PP
+The
+\fBmysql_tzinfo_to_sql\fR
+program loads the time zone tables in the
+mysql
+database. It is used on systems that have a
+zoneinfo
+database (the set of files describing time zones). Examples of such systems are Linux, FreeBSD, Sun Solaris, and Mac OS X. One likely location for these files is the
+\fI/usr/share/zoneinfo\fR
+directory. If your system does not have a zoneinfo database, you can use the downloadable package described in
+Section\ 9, \(lqMySQL Server Time Zone Support\(rq.
+.PP
+\fBmysql_tzinfo_to_sql\fR
+can be invoked several ways:
+.sp
+.RS 3n
+.nf
+shell> \fBmysql_tzinfo_to_sql \fR\fB\fItz_dir\fR\fR
+shell> \fBmysql_tzinfo_to_sql \fR\fB\fItz_file tz_name\fR\fR
+shell> \fBmysql_tzinfo_to_sql \-\-leap \fR\fB\fItz_file\fR\fR
+.fi
+.RE
+.PP
+For the first invocation syntax, pass the zoneinfo directory pathname to
+\fBmysql_tzinfo_to_sql\fR
+and send the output into the
+\fBmysql\fR
+program. For example:
+.sp
+.RS 3n
+.nf
+shell> \fBmysql_tzinfo_to_sql /usr/share/zoneinfo | mysql \-u root mysql\fR
+.fi
+.RE
+.PP
+\fBmysql_tzinfo_to_sql\fR
+reads your system's time zone files and generates SQL statements from them.
+\fBmysql\fR
+processes those statements to load the time zone tables.
+.PP
+The second syntax causes
+\fBmysql_tzinfo_to_sql\fR
+to load a single time zone file
+\fItz_file\fR
+that corresponds to a time zone name
+\fItz_name\fR:
+.sp
+.RS 3n
+.nf
+shell> \fBmysql_tzinfo_to_sql \fR\fB\fItz_file\fR\fR\fB \fR\fB\fItz_name\fR\fR\fB | mysql \-u root mysql\fR
+.fi
+.RE
+.PP
+If your time zone needs to account for leap seconds, invoke
+\fBmysql_tzinfo_to_sql\fR
+using the third syntax, which initializes the leap second information.
+\fItz_file\fR
+is the name of your time zone file:
+.sp
+.RS 3n
+.nf
+shell> \fBmysql_tzinfo_to_sql \-\-leap \fR\fB\fItz_file\fR\fR\fB | mysql \-u root mysql\fR
+.fi
+.RE
+.PP
+After running
+\fBmysql_tzinfo_to_sql\fR, it is best to restart the server so that it does not continue to use any previously cached time zone data.
+.SH "COPYRIGHT"
+.PP
+Copyright 2007 MySQL AB
+.PP
+This documentation is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License.
+.PP
+This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
+.PP
+You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110\-1301 USA or see http://www.gnu.org/licenses/.
+.PP
+Please email
+<docs at mysql.com>
+for more information or if you are interested in doing a translation.
+.SH "SEE ALSO"
+For more information, please refer to the MySQL Reference Manual,
+which may already be installed locally and which is also available
+online at http://dev.mysql.com/doc/.
+.SH AUTHOR
+MySQL AB (http://www.mysql.com/).
Added: branches/sid-5.0/debian/manpages/mysql_upgrade.1
===================================================================
--- branches/sid-5.0/debian/manpages/mysql_upgrade.1 (rev 0)
+++ branches/sid-5.0/debian/manpages/mysql_upgrade.1 2007-11-26 12:34:29 UTC (rev 1020)
@@ -0,0 +1,154 @@
+.\" Title: \fBmysql_upgrade\fR
+.\" Author:
+.\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
+.\" Date: 11/25/2007
+.\" Manual: MySQL Database System
+.\" Source: MySQL 5.0
+.\"
+.TH "\fBMYSQL_UPGRADE\fR" "1" "11/25/2007" "MySQL 5.0" "MySQL Database System"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
+.SH "NAME"
+mysql_upgrade \- check tables for MySQL upgrade
+.SH "SYNOPSIS"
+.HP 24
+\fBmysql_upgrade [\fR\fB\fIoptions\fR\fR\fB]\fR
+.SH "DESCRIPTION"
+.PP
+\fBmysql_upgrade\fR
+should be executed each time you upgrade MySQL. It checks all tables in all databases for incompatibilities with the current version of MySQL Server. If a table is found to have a possible incompatibility, it is checked. If any problems are found, the table is repaired.
+\fBmysql_upgrade\fR
+also upgrades the system tables so that you can take advantage of new privileges or capabilities that might have been added.
+.PP
+All checked and repaired tables are marked with the current MySQL version number. This ensures that next time you run
+\fBmysql_upgrade\fR
+with the same version of the server, it can tell whether there is any need to check or repair the table again.
+.PP
+\fBmysql_upgrade\fR
+also saves the MySQL version number in a file named
+\fImysql_upgrade_info\fR
+in the data directory. This is used to quickly check if all tables have been checked for this release so that table\-checking can be skipped. To ignore this file, use the
+\fB\-\-force\fR
+option.
+.PP
+To check and repair tables and to upgrade the system tables,
+\fBmysql_upgrade\fR
+executes the following commands:
+.sp
+.RS 3n
+.nf
+mysqlcheck \-\-check\-upgrade \-\-all\-databases \-\-auto\-repair
+mysql_fix_privilege_tables
+.fi
+.RE
+.PP
+\fBmysql_upgrade\fR
+supersedes the older
+\fBmysql_fix_privilege_tables\fR
+script. In MySQL 5.0.19,
+\fBmysql_upgrade \fR
+was added as a shell script and worked only for Unix systems. As of MySQL 5.0.25,
+\fBmysql_upgrade\fR
+is an executable binary and is available on all systems. On systems older than those supporting
+\fBmysql_upgrade\fR, you can execute the
+\fBmysqlcheck\fR
+command manually, and then upgrade your system tables as described in
+\fBmysql_fix_privilege_tables\fR(1).
+.PP
+If you install MySQL from RPM packages on Linux, you must install the server and client RPMs.
+\fBmysql_upgrade\fR
+is included in the server RPM but requires the client RPM because the latter includes
+\fBmysqlcheck\fR. (See
+Section\ 4.9, \(lqInstalling MySQL from RPM Packages on Linux\(rq.)
+.PP
+For details about what is checked, see the description of the
+FOR UPGRADE
+option of the
+CHECK TABLE
+statement (see
+Section\ 5.2.3, \(lqCHECK TABLE Syntax\(rq).
+.PP
+To use
+\fBmysql_upgrade\fR, make sure that the server is running, and then invoke it like this:
+.sp
+.RS 3n
+.nf
+shell> \fBmysql_upgrade [\fR\fB\fIoptions\fR\fR\fB]\fR
+.fi
+.RE
+.PP
+After running
+\fBmysql_upgrade\fR, stop the server and restart it so that it uses any changes that were made to the system tables.
+.PP
+\fBmysql_upgrade\fR
+reads options from the command line and from the
+[mysql_upgrade]
+group in option files. It supports the following options:
+.TP 3n
+\(bu
+\fB\-\-help\fR
+.sp
+Display a short help message and exit.
+.TP 3n
+\(bu
+\fB\-\-basedir=\fR\fB\fIpath\fR\fR
+.sp
+The path to the MySQL installation directory.
+.TP 3n
+\(bu
+\fB\-\-datadir=\fR\fB\fIpath\fR\fR
+.sp
+The path to the data directory.
+.TP 3n
+\(bu
+\fB\-\-force\fR
+.sp
+Force execution of
+\fBmysqlcheck\fR
+even if
+\fBmysql_upgrade\fR
+has already been executed for the current version of MySQL. (In other words, this option causes the
+\fImysql_upgrade_info\fR
+file to be ignored.)
+.TP 3n
+\(bu
+\fB\-\-user=\fR\fB\fIuser_name\fR\fR,
+\fB\-u \fR\fB\fIuser_name\fR\fR
+.sp
+The MySQL username to use when connecting to the server. The default username is
+root.
+.TP 3n
+\(bu
+\fB\-\-verbose\fR
+.sp
+Verbose mode. Print more information about what the program does.
+.sp
+.RE
+.PP
+Other options are passed to
+\fBmysqlcheck\fR
+and to
+\fBmysql_fix_privilege_tables\fR. For example, it might be necessary to specify the
+\fB\-\-password[=\fR\fB\fIpassword\fR\fR\fB]\fR
+option.
+.SH "COPYRIGHT"
+.PP
+Copyright 2007 MySQL AB
+.PP
+This documentation is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License.
+.PP
+This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
+.PP
+You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110\-1301 USA or see http://www.gnu.org/licenses/.
+.PP
+Please email
+<docs at mysql.com>
+for more information or if you are interested in doing a translation.
+.SH "SEE ALSO"
+For more information, please refer to the MySQL Reference Manual,
+which may already be installed locally and which is also available
+online at http://dev.mysql.com/doc/.
+.SH AUTHOR
+MySQL AB (http://www.mysql.com/).
Added: branches/sid-5.0/debian/manpages/mysql_waitpid.1
===================================================================
--- branches/sid-5.0/debian/manpages/mysql_waitpid.1 (rev 0)
+++ branches/sid-5.0/debian/manpages/mysql_waitpid.1 2007-11-26 12:34:29 UTC (rev 1020)
@@ -0,0 +1,95 @@
+.\" Title: \fBmysql_waitpid\fR
+.\" Author:
+.\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
+.\" Date: 11/25/2007
+.\" Manual: MySQL Database System
+.\" Source: MySQL 5.0
+.\"
+.TH "\fBMYSQL_WAITPID\fR" "1" "11/25/2007" "MySQL 5.0" "MySQL Database System"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
+.SH "NAME"
+mysql_waitpid \- kill process and wait for its termination
+.SH "SYNOPSIS"
+.HP 38
+\fBmysql_waitpid [\fR\fB\fIoptions\fR\fR\fB] \fR\fB\fIpid\fR\fR\fB \fR\fB\fIwait_time\fR\fR
+.SH "DESCRIPTION"
+.PP
+\fBmysql_waitpid\fR
+signals a process to terminate and waits for the process to exit. It uses the
+kill()
+system call and Unix signals, so it runs on Unix and Unix\-like systems.
+.PP
+Invoke
+\fBmysql_waitpid\fR
+like this:
+.sp
+.RS 3n
+.nf
+shell> \fBmysql_waitpid [\fR\fB\fIoptions\fR\fR\fB] \fR\fB\fIpid\fR\fR\fB \fR\fB\fIwait_time\fR\fR
+.fi
+.RE
+.PP
+\fBmysql_waitpid\fR
+sends signal 0 to the process identified by
+\fIpid\fR
+and waits up to
+\fIwait_time\fR
+seconds for the process to terminate.
+\fIpid\fR
+and
+\fIwait_time\fR
+must be positive integers.
+.PP
+If process termination occurs within the wait time or the process does not exist,
+\fBmysql_waitpid\fR
+returns 0. Otherwise, it returns 1.
+.PP
+If the
+kill()
+system call cannot handle signal 0,
+\fBmysql_waitpid()\fR
+uses signal 1 instead.
+.PP
+\fBmysql_waitpid\fR
+understands the following options:
+.TP 3n
+\(bu
+\fB\-\-help\fR,
+\fB\-?\fR,
+\fB\-I\fR
+.sp
+Display a help message and exit.
+.TP 3n
+\(bu
+\fB\-\-verbose\fR,
+\fB\-v\fR
+.sp
+Verbose mode. Display a warning if signal 0 could not be used and signal 1 is used instead.
+.TP 3n
+\(bu
+\fB\-\-version\fR,
+\fB\-V\fR
+.sp
+Display version information and exit.
+.SH "COPYRIGHT"
+.PP
+Copyright 2007 MySQL AB
+.PP
+This documentation is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License.
+.PP
+This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
+.PP
+You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110\-1301 USA or see http://www.gnu.org/licenses/.
+.PP
+Please email
+<docs at mysql.com>
+for more information or if you are interested in doing a translation.
+.SH "SEE ALSO"
+For more information, please refer to the MySQL Reference Manual,
+which may already be installed locally and which is also available
+online at http://dev.mysql.com/doc/.
+.SH AUTHOR
+MySQL AB (http://www.mysql.com/).
Added: branches/sid-5.0/debian/manpages/mysql_zap.1
===================================================================
--- branches/sid-5.0/debian/manpages/mysql_zap.1 (rev 0)
+++ branches/sid-5.0/debian/manpages/mysql_zap.1 2007-11-26 12:34:29 UTC (rev 1020)
@@ -0,0 +1,97 @@
+.\" Title: \fBmysql_zap\fR
+.\" Author:
+.\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
+.\" Date: 11/25/2007
+.\" Manual: MySQL Database System
+.\" Source: MySQL 5.0
+.\"
+.TH "\fBMYSQL_ZAP\fR" "1" "11/25/2007" "MySQL 5.0" "MySQL Database System"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
+.SH "NAME"
+mysql_zap \- kill processes that match a pattern
+.SH "SYNOPSIS"
+.HP 36
+\fBmysql_zap [\-\fR\fB\fIsignal\fR\fR\fB] [\-?Ift] \fR\fB\fIpattern\fR\fR
+.SH "DESCRIPTION"
+.PP
+\fBmysql_zap\fR
+kills processes that match a pattern. It uses the
+\fBps\fR
+command and Unix signals, so it runs on Unix and Unix\-like systems.
+.PP
+Invoke
+\fBmysql_zap\fR
+like this:
+.sp
+.RS 3n
+.nf
+shell> \fBmysql_zap [\-\fR\fB\fIsignal\fR\fR\fB] [\-?Ift] \fR\fB\fIpattern\fR\fR
+.fi
+.RE
+.PP
+A process matches if its output line from the
+\fBps\fR
+command contains the pattern. By default,
+\fBmysql_zap\fR
+asks for confirmation for each process. Respond
+y
+to kill the process, or
+q
+to exit
+\fBmysql_zap\fR. For any other response,
+\fBmysql_zap\fR
+does not attempt to kill the process.
+.PP
+If the
+\fB\-\fR\fB\fIsignal\fR\fR
+option is given, it specifies the name or number of the signal to send to each process. Otherwise,
+\fBmysql_zap\fR
+tries first with
+TERM
+(signal 15) and then with
+KILL
+(signal 9).
+.PP
+\fBmysql_zap\fR
+understands the following additional options:
+.TP 3n
+\(bu
+\fB\-\-help\fR,
+\fB\-?\fR,
+\fB\-I\fR
+.sp
+Display a help message and exit.
+.TP 3n
+\(bu
+\fB\-f\fR
+.sp
+Force mode.
+\fBmysql_zap\fR
+attempts to kill each process without confirmation.
+.TP 3n
+\(bu
+\fB\-t\fR
+.sp
+Test mode. Display information about each process but do not kill it.
+.SH "COPYRIGHT"
+.PP
+Copyright 2007 MySQL AB
+.PP
+This documentation is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License.
+.PP
+This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
+.PP
+You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110\-1301 USA or see http://www.gnu.org/licenses/.
+.PP
+Please email
+<docs at mysql.com>
+for more information or if you are interested in doing a translation.
+.SH "SEE ALSO"
+For more information, please refer to the MySQL Reference Manual,
+which may already be installed locally and which is also available
+online at http://dev.mysql.com/doc/.
+.SH AUTHOR
+MySQL AB (http://www.mysql.com/).
Added: branches/sid-5.0/debian/manpages/mysqlaccess.1
===================================================================
--- branches/sid-5.0/debian/manpages/mysqlaccess.1 (rev 0)
+++ branches/sid-5.0/debian/manpages/mysqlaccess.1 2007-11-26 12:34:29 UTC (rev 1020)
@@ -0,0 +1,222 @@
+.\" Title: \fBmysqlaccess\fR
+.\" Author:
+.\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
+.\" Date: 11/25/2007
+.\" Manual: MySQL Database System
+.\" Source: MySQL 5.0
+.\"
+.TH "\fBMYSQLACCESS\fR" "1" "11/25/2007" "MySQL 5.0" "MySQL Database System"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
+.SH "NAME"
+mysqlaccess \- client for checking access privileges
+.SH "SYNOPSIS"
+.HP 56
+\fBmysqlaccess [\fR\fB\fIhost_name\fR\fR\fB [\fR\fB\fIuser_name\fR\fR\fB [\fR\fB\fIdb_name\fR\fR\fB]]] [\fR\fB\fIoptions\fR\fR\fB]\fR
+.SH "DESCRIPTION"
+.PP
+\fBmysqlaccess\fR
+is a diagnostic tool that Yves Carlier has provided for the MySQL distribution. It checks the access privileges for a hostname, username, and database combination. Note that
+\fBmysqlaccess\fR
+checks access using only the
+user,
+db, and
+host
+tables. It does not check table, column, or routine privileges specified in the
+tables_priv,
+columns_priv, or
+procs_priv
+tables.
+.PP
+Invoke
+\fBmysqlaccess\fR
+like this:
+.sp
+.RS 3n
+.nf
+shell> \fBmysqlaccess [\fR\fB\fIhost_name\fR\fR\fB [\fR\fB\fIuser_name\fR\fR\fB [\fR\fB\fIdb_name\fR\fR\fB]]] [\fR\fB\fIoptions\fR\fR\fB]\fR
+.fi
+.RE
+.PP
+\fBmysqlaccess\fR
+understands the following options:
+.TP 3n
+\(bu
+\fB\-\-help\fR,
+\fB\-?\fR
+.sp
+Display a help message and exit.
+.TP 3n
+\(bu
+\fB\-\-brief\fR,
+\fB\-b\fR
+.sp
+Generate reports in single\-line tabular format.
+.TP 3n
+\(bu
+\fB\-\-commit\fR
+.sp
+Copy the new access privileges from the temporary tables to the original grant tables. The grant tables must be flushed for the new privileges to take effect. (For example, execute a
+\fBmysqladmin reload\fR
+command.)
+.TP 3n
+\(bu
+\fB\-\-copy\fR
+.sp
+Reload the temporary grant tables from original ones.
+.TP 3n
+\(bu
+\fB\-\-db=\fR\fB\fIdb_name\fR\fR,
+\fB\-d \fR\fB\fIdb_name\fR\fR
+.sp
+Specify the database name.
+.TP 3n
+\(bu
+\fB\-\-debug=\fR\fB\fIN\fR\fR
+.sp
+Specify the debug level.
+\fIN\fR
+can be an integer from 0 to 3.
+.TP 3n
+\(bu
+\fB\-\-host=\fR\fB\fIhost_name\fR\fR,
+\fB\-h \fR\fB\fIhost_name\fR\fR
+.sp
+The hostname to use in the access privileges.
+.TP 3n
+\(bu
+\fB\-\-howto\fR
+.sp
+Display some examples that show how to use
+\fBmysqlaccess\fR.
+.TP 3n
+\(bu
+\fB\-\-old_server\fR
+.sp
+Assume that the server is an old MySQL server (before MySQL 3.21) that does not yet know how to handle full
+WHERE
+clauses.
+.TP 3n
+\(bu
+\fB\-\-password[=\fR\fB\fIpassword\fR\fR\fB]\fR,
+\fB\-p[\fR\fB\fIpassword\fR\fR\fB]\fR
+.sp
+The password to use when connecting to the server. If you omit the
+\fIpassword\fR
+value following the
+\fB\-\-password\fR
+or
+\fB\-p\fR
+option on the command line, you are prompted for one.
+.sp
+Specifying a password on the command line should be considered insecure. See
+Section\ 6.6, \(lqKeeping Your Password Secure\(rq.
+.TP 3n
+\(bu
+\fB\-\-plan\fR
+.sp
+Display suggestions and ideas for future releases.
+.TP 3n
+\(bu
+\fB\-\-preview\fR
+.sp
+Show the privilege differences after making changes to the temporary grant tables.
+.TP 3n
+\(bu
+\fB\-\-relnotes\fR
+.sp
+Display the release notes.
+.TP 3n
+\(bu
+\fB\-\-rhost=\fR\fB\fIhost_name\fR\fR,
+\fB\-H \fR\fB\fIhost_name\fR\fR
+.sp
+Connect to the MySQL server on the given host.
+.TP 3n
+\(bu
+\fB\-\-rollback\fR
+.sp
+Undo the most recent changes to the temporary grant tables.
+.TP 3n
+\(bu
+\fB\-\-spassword[=\fR\fB\fIpassword\fR\fR\fB]\fR,
+\fB\-P[\fR\fB\fIpassword\fR\fR\fB]\fR
+.sp
+The password to use when connecting to the server as the superuser. If you omit the
+\fIpassword\fR
+value following the
+\fB\-\-password\fR
+or
+\fB\-p\fR
+option on the command line, you are prompted for one.
+.sp
+Specifying a password on the command line should be considered insecure. See
+Section\ 6.6, \(lqKeeping Your Password Secure\(rq.
+.TP 3n
+\(bu
+\fB\-\-superuser=\fR\fB\fIuser_name\fR\fR,
+\fB\-U \fR\fB\fIuser_name\fR\fR
+.sp
+Specify the username for connecting as the superuser.
+.TP 3n
+\(bu
+\fB\-\-table\fR,
+\fB\-t\fR
+.sp
+Generate reports in table format.
+.TP 3n
+\(bu
+\fB\-\-user=\fR\fB\fIuser_name\fR\fR,
+\fB\-u \fR\fB\fIuser_name\fR\fR
+.sp
+The username to use in the access privileges.
+.TP 3n
+\(bu
+\fB\-\-version\fR,
+\fB\-v\fR
+.sp
+Display version information and exit.
+.sp
+.RE
+.PP
+If your MySQL distribution is installed in some non\-standard location, you must change the location where
+\fBmysqlaccess\fR
+expects to find the
+\fBmysql\fR
+client. Edit the
+\fImysqlaccess\fR
+script at approximately line 18. Search for a line that looks like this:
+.sp
+.RS 3n
+.nf
+$MYSQL = '/usr/local/bin/mysql'; # path to mysql executable
+.fi
+.RE
+.PP
+Change the path to reflect the location where
+\fBmysql\fR
+actually is stored on your system. If you do not do this, a
+Broken pipe
+error will occur when you run
+\fBmysqlaccess\fR.
+.SH "COPYRIGHT"
+.PP
+Copyright 2007 MySQL AB
+.PP
+This documentation is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License.
+.PP
+This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
+.PP
+You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110\-1301 USA or see http://www.gnu.org/licenses/.
+.PP
+Please email
+<docs at mysql.com>
+for more information or if you are interested in doing a translation.
+.SH "SEE ALSO"
+For more information, please refer to the MySQL Reference Manual,
+which may already be installed locally and which is also available
+online at http://dev.mysql.com/doc/.
+.SH AUTHOR
+MySQL AB (http://www.mysql.com/).
Added: branches/sid-5.0/debian/manpages/mysqladmin.1
===================================================================
--- branches/sid-5.0/debian/manpages/mysqladmin.1 (rev 0)
+++ branches/sid-5.0/debian/manpages/mysqladmin.1 2007-11-26 12:34:29 UTC (rev 1020)
@@ -0,0 +1,474 @@
+.\" Title: \fBmysqladmin\fR
+.\" Author:
+.\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
+.\" Date: 11/25/2007
+.\" Manual: MySQL Database System
+.\" Source: MySQL 5.0
+.\"
+.TH "\fBMYSQLADMIN\fR" "1" "11/25/2007" "MySQL 5.0" "MySQL Database System"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
+.SH "NAME"
+mysqladmin \- client for administering a MySQL server
+.SH "SYNOPSIS"
+.HP 79
+\fBmysqladmin [\fR\fB\fIoptions\fR\fR\fB] \fR\fB\fIcommand\fR\fR\fB [\fR\fB\fIcommand\-options\fR\fR\fB] [\fR\fB\fIcommand\fR\fR\fB [\fR\fB\fIcommand\-options\fR\fR\fB]] ...\fR
+.SH "DESCRIPTION"
+.PP
+\fBmysqladmin\fR
+is a client for performing administrative operations. You can use it to check the server's configuration and current status, to create and drop databases, and more.
+.PP
+Invoke
+\fBmysqladmin\fR
+like this:
+.sp
+.RS 3n
+.nf
+shell> \fBmysqladmin [\fR\fB\fIoptions\fR\fR\fB] \fR\fB\fIcommand\fR\fR\fB [\fR\fB\fIcommand\-arg\fR\fR\fB] [\fR\fB\fIcommand\fR\fR\fB [\fR\fB\fIcommand\-arg\fR\fR\fB]] ...\fR
+.fi
+.RE
+.PP
+\fBmysqladmin\fR
+supports the commands described in the following list. Some of the commands take an argument following the command name.
+.TP 3n
+\(bu
+create \fIdb_name\fR
+.sp
+Create a new database named
+\fIdb_name\fR.
+.TP 3n
+\(bu
+debug
+.sp
+Tell the server to write debug information to the error log.
+.TP 3n
+\(bu
+drop \fIdb_name\fR
+.sp
+Delete the database named
+\fIdb_name\fR
+and all its tables.
+.TP 3n
+\(bu
+extended\-status
+.sp
+Display the server status variables and their values.
+.TP 3n
+\(bu
+flush\-hosts
+.sp
+Flush all information in the host cache.
+.TP 3n
+\(bu
+flush\-logs
+.sp
+Flush all logs.
+.TP 3n
+\(bu
+flush\-privileges
+.sp
+Reload the grant tables (same as
+reload).
+.TP 3n
+\(bu
+flush\-status
+.sp
+Clear status variables.
+.TP 3n
+\(bu
+flush\-tables
+.sp
+Flush all tables.
+.TP 3n
+\(bu
+flush\-threads
+.sp
+Flush the thread cache.
+.TP 3n
+\(bu
+kill \fIid\fR,\fIid\fR,...
+.sp
+Kill server threads. If multiple thread ID values are given, there must be no spaces in the list.
+.TP 3n
+\(bu
+old\-password \fInew\-password\fR
+.sp
+This is like the
+password
+command but stores the password using the old (pre\-4.1) password\-hashing format. (See
+Section\ 5.9, \(lqPassword Hashing as of MySQL 4.1\(rq.)
+.TP 3n
+\(bu
+password \fInew\-password\fR
+.sp
+Set a new password. This changes the password to
+\fInew\-password\fR
+for the account that you use with
+\fBmysqladmin\fR
+for connecting to the server. Thus, the next time you invoke
+\fBmysqladmin\fR
+(or any other client program) using the same account, you will need to specify the new password.
+.sp
+If the
+\fInew\-password\fR
+value contains spaces or other characters that are special to your command interpreter, you need to enclose it within quotes. On Windows, be sure to use double quotes rather than single quotes; single quotes are not stripped from the password, but rather are interpreted as part of the password. For example:
+.sp
+.RS 3n
+.nf
+shell> \fBmysqladmin password "my new password"\fR
+.fi
+.RE
+.TP 3n
+\(bu
+ping
+.sp
+Check whether the server is alive. The return status from
+\fBmysqladmin\fR
+is 0 if the server is running, 1 if it is not. This is 0 even in case of an error such as
+Access denied, because this means that the server is running but refused the connection, which is different from the server not running.
+.TP 3n
+\(bu
+processlist
+.sp
+Show a list of active server threads. This is like the output of the
+SHOW PROCESSLIST
+statement. If the
+\fB\-\-verbose\fR
+option is given, the output is like that of
+SHOW FULL PROCESSLIST. (See
+Section\ 5.4.21, \(lqSHOW PROCESSLIST Syntax\(rq.)
+.TP 3n
+\(bu
+reload
+.sp
+Reload the grant tables.
+.TP 3n
+\(bu
+refresh
+.sp
+Flush all tables and close and open log files.
+.TP 3n
+\(bu
+shutdown
+.sp
+Stop the server.
+.TP 3n
+\(bu
+start\-slave
+.sp
+Start replication on a slave server.
+.TP 3n
+\(bu
+status
+.sp
+Display a short server status message.
+.TP 3n
+\(bu
+stop\-slave
+.sp
+Stop replication on a slave server.
+.TP 3n
+\(bu
+variables
+.sp
+Display the server system variables and their values.
+.TP 3n
+\(bu
+version
+.sp
+Display version information from the server.
+.sp
+.RE
+.PP
+All commands can be shortened to any unique prefix. For example:
+.sp
+.RS 3n
+.nf
+shell> \fBmysqladmin proc stat\fR
++\-\-\-\-+\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-+\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-+\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+
+| Id | User | Host | db | Command | Time | State | Info |
++\-\-\-\-+\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-+\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-+\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+
+| 51 | monty | localhost | | Query | 0 | | show processlist |
++\-\-\-\-+\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-+\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-+\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+
+Uptime: 1473624 Threads: 1 Questions: 39487
+Slow queries: 0 Opens: 541 Flush tables: 1
+Open tables: 19 Queries per second avg: 0.0268
+.fi
+.RE
+.PP
+The
+\fBmysqladmin status\fR
+command result displays the following values:
+.TP 3n
+\(bu
+Uptime
+.sp
+The number of seconds the MySQL server has been running.
+.TP 3n
+\(bu
+Threads
+.sp
+The number of active threads (clients).
+.TP 3n
+\(bu
+Questions
+.sp
+The number of questions (queries) from clients since the server was started.
+.TP 3n
+\(bu
+Slow queries
+.sp
+The number of queries that have taken more than
+long_query_time
+seconds. See
+Section\ 8.4, \(lqThe Slow Query Log\(rq.
+.TP 3n
+\(bu
+Opens
+.sp
+The number of tables the server has opened.
+.TP 3n
+\(bu
+Flush tables
+.sp
+The number of
+flush\-*,
+refresh, and
+reload
+commands the server has executed.
+.TP 3n
+\(bu
+Open tables
+.sp
+The number of tables that currently are open.
+.TP 3n
+\(bu
+Memory in use
+.sp
+The amount of memory allocated directly by
+\fBmysqld\fR. This value is displayed only when MySQL has been compiled with
+\fB\-\-with\-debug=full\fR.
+.TP 3n
+\(bu
+Maximum memory used
+.sp
+The maximum amount of memory allocated directly by
+\fBmysqld\fR. This value is displayed only when MySQL has been compiled with
+\fB\-\-with\-debug=full\fR.
+.sp
+.RE
+.PP
+If you execute
+\fBmysqladmin shutdown\fR
+when connecting to a local server using a Unix socket file,
+\fBmysqladmin\fR
+waits until the server's process ID file has been removed, to ensure that the server has stopped properly.
+.PP
+\fBmysqladmin\fR
+supports the following options:
+.TP 3n
+\(bu
+\fB\-\-help\fR,
+\fB\-?\fR
+.sp
+Display a help message and exit.
+.TP 3n
+\(bu
+\fB\-\-character\-sets\-dir=\fR\fB\fIpath\fR\fR
+.sp
+The directory where character sets are installed. See
+Section\ 2, \(lqThe Character Set Used for Data and Sorting\(rq.
+.TP 3n
+\(bu
+\fB\-\-compress\fR,
+\fB\-C\fR
+.sp
+Compress all information sent between the client and the server if both support compression.
+.TP 3n
+\(bu
+\fB\-\-count=\fR\fB\fIN\fR\fR,
+\fB\-c \fR\fB\fIN\fR\fR
+.sp
+The number of iterations to make for repeated command execution. This works only with the
+\fB\-\-sleep\fR
+option.
+.TP 3n
+\(bu
+\fB\-\-debug[=\fR\fB\fIdebug_options\fR\fR\fB]\fR,
+\fB\-# [\fR\fB\fIdebug_options\fR\fR\fB]\fR
+.sp
+Write a debugging log. The
+\fIdebug_options\fR
+string often is
+\'d:t:o,\fIfile_name\fR'. The default is
+\'d:t:o,/tmp/mysqladmin.trace'.
+.TP 3n
+\(bu
+\fB\-\-default\-character\-set=\fR\fB\fIcharset_name\fR\fR
+.sp
+Use
+\fIcharset_name\fR
+as the default character set. See
+Section\ 2, \(lqThe Character Set Used for Data and Sorting\(rq.
+.TP 3n
+\(bu
+\fB\-\-force\fR,
+\fB\-f\fR
+.sp
+Do not ask for confirmation for the
+drop \fIdb_name\fR
+command. With multiple commands, continue even if an error occurs.
+.TP 3n
+\(bu
+\fB\-\-host=\fR\fB\fIhost_name\fR\fR,
+\fB\-h \fR\fB\fIhost_name\fR\fR
+.sp
+Connect to the MySQL server on the given host.
+.TP 3n
+\(bu
+\fB\-\-password[=\fR\fB\fIpassword\fR\fR\fB]\fR,
+\fB\-p[\fR\fB\fIpassword\fR\fR\fB]\fR
+.sp
+The password to use when connecting to the server. If you use the short option form (\fB\-p\fR), you
+\fIcannot\fR
+have a space between the option and the password. If you omit the
+\fIpassword\fR
+value following the
+\fB\-\-password\fR
+or
+\fB\-p\fR
+option on the command line, you are prompted for one.
+.sp
+Specifying a password on the command line should be considered insecure. See
+Section\ 6.6, \(lqKeeping Your Password Secure\(rq.
+.TP 3n
+\(bu
+\fB\-\-port=\fR\fB\fIport_num\fR\fR,
+\fB\-P \fR\fB\fIport_num\fR\fR
+.sp
+The TCP/IP port number to use for the connection.
+.TP 3n
+\(bu
+\fB\-\-protocol={TCP|SOCKET|PIPE|MEMORY}\fR
+.sp
+The connection protocol to use.
+.TP 3n
+\(bu
+\fB\-\-relative\fR,
+\fB\-r\fR
+.sp
+Show the difference between the current and previous values when used with the
+\fB\-\-sleep\fR
+option. Currently, this option works only with the
+extended\-status
+command.
+.TP 3n
+\(bu
+\fB\-\-silent\fR,
+\fB\-s\fR
+.sp
+Exit silently if a connection to the server cannot be established.
+.TP 3n
+\(bu
+\fB\-\-sleep=\fR\fB\fIdelay\fR\fR,
+\fB\-i \fR\fB\fIdelay\fR\fR
+.sp
+Execute commands repeatedly, sleeping for
+\fIdelay\fR
+seconds in between. The
+\fB\-\-count\fR
+option determines the number of iterations.
+.TP 3n
+\(bu
+\fB\-\-socket=\fR\fB\fIpath\fR\fR,
+\fB\-S \fR\fB\fIpath\fR\fR
+.sp
+For connections to
+localhost, the Unix socket file to use, or, on Windows, the name of the named pipe to use.
+.TP 3n
+\(bu
+\fB\-\-ssl*\fR
+.sp
+Options that begin with
+\fB\-\-ssl\fR
+specify whether to connect to the server via SSL and indicate where to find SSL keys and certificates. See
+Section\ 6.7.3, \(lqSSL Command Options\(rq.
+.TP 3n
+\(bu
+\fB\-\-user=\fR\fB\fIuser_name\fR\fR,
+\fB\-u \fR\fB\fIuser_name\fR\fR
+.sp
+The MySQL username to use when connecting to the server.
+.TP 3n
+\(bu
+\fB\-\-verbose\fR,
+\fB\-v\fR
+.sp
+Verbose mode. Print more information about what the program does.
+.TP 3n
+\(bu
+\fB\-\-version\fR,
+\fB\-V\fR
+.sp
+Display version information and exit.
+.TP 3n
+\(bu
+\fB\-\-vertical\fR,
+\fB\-E\fR
+.sp
+Print output vertically. This is similar to
+\fB\-\-relative\fR, but prints output vertically.
+.TP 3n
+\(bu
+\fB\-\-wait[=\fR\fB\fIcount\fR\fR\fB]\fR,
+\fB\-w[\fR\fB\fIcount\fR\fR\fB]\fR
+.sp
+If the connection cannot be established, wait and retry instead of aborting. If a
+\fIcount\fR
+value is given, it indicates the number of times to retry. The default is one time.
+.sp
+.RE
+.PP
+You can also set the following variables by using
+\fB\-\-\fR\fB\fIvar_name\fR\fR\fB=\fR\fB\fIvalue\fR\fR
+syntax:
+.TP 3n
+\(bu
+connect_timeout
+.sp
+The maximum number of seconds before connection timeout. The default value is 43200 (12 hours).
+.TP 3n
+\(bu
+shutdown_timeout
+.sp
+The maximum number of seconds to wait for server shutdown. The default value is 3600 (1 hour).
+.sp
+.RE
+.PP
+It is also possible to set variables by using
+\fB\-\-set\-variable=\fR\fB\fIvar_name\fR\fR\fB=\fR\fB\fIvalue\fR\fR
+or
+\fB\-O \fR\fB\fIvar_name\fR\fR\fB=\fR\fB\fIvalue\fR\fR
+syntax.
+\fIThis syntax is deprecated\fR.
+.SH "COPYRIGHT"
+.PP
+Copyright 2007 MySQL AB
+.PP
+This documentation is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License.
+.PP
+This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
+.PP
+You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110\-1301 USA or see http://www.gnu.org/licenses/.
+.PP
+Please email
+<docs at mysql.com>
+for more information or if you are interested in doing a translation.
+.SH "SEE ALSO"
+For more information, please refer to the MySQL Reference Manual,
+which may already be installed locally and which is also available
+online at http://dev.mysql.com/doc/.
+.SH AUTHOR
+MySQL AB (http://www.mysql.com/).
Added: branches/sid-5.0/debian/manpages/mysqlbinlog.1
===================================================================
--- branches/sid-5.0/debian/manpages/mysqlbinlog.1 (rev 0)
+++ branches/sid-5.0/debian/manpages/mysqlbinlog.1 2007-11-26 12:34:29 UTC (rev 1020)
@@ -0,0 +1,781 @@
+.\" Title: \fBmysqlbinlog\fR
+.\" Author:
+.\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
+.\" Date: 11/25/2007
+.\" Manual: MySQL Database System
+.\" Source: MySQL 5.0
+.\"
+.TH "\fBMYSQLBINLOG\fR" "1" "11/25/2007" "MySQL 5.0" "MySQL Database System"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
+.SH "NAME"
+mysqlbinlog \- utility for processing binary log files
+.SH "SYNOPSIS"
+.HP 35
+\fBmysqlbinlog [\fR\fBoptions\fR\fB] \fR\fB\fIlog_file\fR\fR\fB ...\fR
+.SH "DESCRIPTION"
+.PP
+The binary log files that the server generates are written in binary format. To examine these files in text format, use the
+\fBmysqlbinlog\fR
+utility. You can also use
+\fBmysqlbinlog\fR
+to read relay log files written by a slave server in a replication setup. Relay logs have the same format as binary log files.
+.PP
+Invoke
+\fBmysqlbinlog\fR
+like this:
+.sp
+.RS 3n
+.nf
+shell> \fBmysqlbinlog [\fR\fB\fIoptions\fR\fR\fB] \fR\fB\fIlog_file\fR\fR\fB ...\fR
+.fi
+.RE
+.PP
+For example, to display the contents of the binary log file named
+\fIbinlog.000003\fR, use this command:
+.sp
+.RS 3n
+.nf
+shell> \fBmysqlbinlog binlog.0000003\fR
+.fi
+.RE
+.PP
+The output includes all events contained in
+\fIbinlog.000003\fR. Event information includes the statement executed, the time the statement took, the thread ID of the client that issued it, the timestamp when it was executed, and so forth.
+.PP
+The output from
+\fBmysqlbinlog\fR
+can be re\-executed (for example, by using it as input to
+\fBmysql\fR) to reapply the statements in the log. This is useful for recovery operations after a server crash. For other usage examples, see the discussion later in this section.
+.PP
+Normally, you use
+\fBmysqlbinlog\fR
+to read binary log files directly and apply them to the local MySQL server. It is also possible to read binary logs from a remote server by using the
+\fB\-\-read\-from\-remote\-server\fR
+option. When you read remote binary logs, the connection parameter options can be given to indicate how to connect to the server. These options are
+\fB\-\-host\fR,
+\fB\-\-password\fR,
+\fB\-\-port\fR,
+\fB\-\-protocol\fR,
+\fB\-\-socket\fR, and
+\fB\-\-user\fR; they are ignored except when you also use the
+\fB\-\-read\-from\-remote\-server\fR
+option.
+.PP
+Binary logs and relay logs are discussed further in
+Section\ 8.3, \(lqThe Binary Log\(rq, and
+Section\ 4.2, \(lqReplication Relay and Status Files\(rq.
+.PP
+\fBmysqlbinlog\fR
+supports the following options:
+.TP 3n
+\(bu
+\fB\-\-help\fR,
+\fB\-?\fR
+.sp
+Display a help message and exit.
+.TP 3n
+\(bu
+\fB\-\-character\-sets\-dir=\fR\fB\fIpath\fR\fR
+.sp
+The directory where character sets are installed. See
+Section\ 2, \(lqThe Character Set Used for Data and Sorting\(rq.
+.TP 3n
+\(bu
+\fB\-\-database=\fR\fB\fIdb_name\fR\fR,
+\fB\-d \fR\fB\fIdb_name\fR\fR
+.sp
+List entries for just this database (local log only). You can only specify one database with this option \- if you specify multiple
+\fB\-\-database\fR
+options, only the last one is used. This option forces
+\fBmysqlbinlog\fR
+to output entries from the binary log where the default database (that is, the one selected by
+USE) is
+\fIdb_name\fR. Note that this does not replicate cross\-database statements such as
+UPDATE \fIsome_db.some_table\fR SET foo='bar'
+while having selected a different database or no database.
+.TP 3n
+\(bu
+\fB\-\-debug[=\fR\fB\fIdebug_options\fR\fR\fB]\fR,
+\fB\-# [\fR\fB\fIdebug_options\fR\fR\fB]\fR
+.sp
+Write a debugging log. A typical
+\fIdebug_options\fR
+string is often
+\'d:t:o,\fIfile_name\fR'.
+.TP 3n
+\(bu
+\fB\-\-disable\-log\-bin\fR,
+\fB\-D\fR
+.sp
+Disable binary logging. This is useful for avoiding an endless loop if you use the
+\fB\-\-to\-last\-log\fR
+option and are sending the output to the same MySQL server. This option also is useful when restoring after a crash to avoid duplication of the statements you have logged.
+.sp
+This option requires that you have the
+SUPER
+privilege. It causes
+\fBmysqlbinlog\fR
+to include a
+SET SQL_LOG_BIN=0
+statement in its output to disable binary logging of the remaining output. The
+SET
+statement is ineffective unless you have the
+SUPER
+privilege.
+.TP 3n
+\(bu
+\fB\-\-force\-read\fR,
+\fB\-f\fR
+.sp
+With this option, if
+\fBmysqlbinlog\fR
+reads a binary log event that it does not recognize, it prints a warning, ignores the event, and continues. Without this option,
+\fBmysqlbinlog\fR
+stops if it reads such an event.
+.TP 3n
+\(bu
+\fB\-\-hexdump\fR,
+\fB\-H\fR
+.sp
+Display a hex dump of the log in comments. This output can be helpful for replication debugging. Hex dump format is discussed later in this section. This option was added in MySQL 5.0.16.
+.TP 3n
+\(bu
+\fB\-\-host=\fR\fB\fIhost_name\fR\fR,
+\fB\-h \fR\fB\fIhost_name\fR\fR
+.sp
+Get the binary log from the MySQL server on the given host.
+.TP 3n
+\(bu
+\fB\-\-local\-load=\fR\fB\fIpath\fR\fR,
+\fB\-l \fR\fB\fIpath\fR\fR
+.sp
+Prepare local temporary files for
+LOAD DATA INFILE
+in the specified directory.
+.TP 3n
+\(bu
+\fB\-\-offset=\fR\fB\fIN\fR\fR,
+\fB\-o \fR\fB\fIN\fR\fR
+.sp
+Skip the first
+\fIN\fR
+entries in the log.
+.TP 3n
+\(bu
+\fB\-\-password[=\fR\fB\fIpassword\fR\fR\fB]\fR,
+\fB\-p[\fR\fB\fIpassword\fR\fR\fB]\fR
+.sp
+The password to use when connecting to the server. If you use the short option form (\fB\-p\fR), you
+\fIcannot\fR
+have a space between the option and the password. If you omit the
+\fIpassword\fR
+value following the
+\fB\-\-password\fR
+or
+\fB\-p\fR
+option on the command line, you are prompted for one.
+.sp
+Specifying a password on the command line should be considered insecure. See
+Section\ 6.6, \(lqKeeping Your Password Secure\(rq.
+.TP 3n
+\(bu
+\fB\-\-port=\fR\fB\fIport_num\fR\fR,
+\fB\-P \fR\fB\fIport_num\fR\fR
+.sp
+The TCP/IP port number to use for connecting to a remote server.
+.TP 3n
+\(bu
+\fB\-\-position=\fR\fB\fIN\fR\fR,
+\fB\-j \fR\fB\fIN\fR\fR
+.sp
+Deprecated. Use
+\fB\-\-start\-position\fR
+instead.
+.TP 3n
+\(bu
+\fB\-\-protocol={TCP|SOCKET|PIPE|MEMORY}\fR
+.sp
+The connection protocol to use.
+.TP 3n
+\(bu
+\fB\-\-read\-from\-remote\-server\fR,
+\fB\-R\fR
+.sp
+Read the binary log from a MySQL server rather than reading a local log file. Any connection parameter options are ignored unless this option is given as well. These options are
+\fB\-\-host\fR,
+\fB\-\-password\fR,
+\fB\-\-port\fR,
+\fB\-\-protocol\fR,
+\fB\-\-socket\fR, and
+\fB\-\-user\fR.
+.TP 3n
+\(bu
+\fB\-\-result\-file=\fR\fB\fIname\fR\fR,
+\fB\-r \fR\fB\fIname\fR\fR
+.sp
+Direct output to the given file.
+.TP 3n
+\(bu
+\fB\-\-set\-charset=\fR\fB\fIcharset_name\fR\fR
+.sp
+Add a
+SET NAMES \fIcharset_name\fR
+statement to the output to specify the character set to be used for processing log files. This option was added in MySQL 5.0.23.
+.TP 3n
+\(bu
+\fB\-\-short\-form\fR,
+\fB\-s\fR
+.sp
+Display only the statements contained in the log, without any extra information.
+.TP 3n
+\(bu
+\fB\-\-socket=\fR\fB\fIpath\fR\fR,
+\fB\-S \fR\fB\fIpath\fR\fR
+.sp
+For connections to
+localhost, the Unix socket file to use, or, on Windows, the name of the named pipe to use.
+.TP 3n
+\(bu
+\fB\-\-start\-datetime=\fR\fB\fIdatetime\fR\fR
+.sp
+Start reading the binary log at the first event having a timestamp equal to or later than the
+\fIdatetime\fR
+argument. The
+\fIdatetime\fR
+value is relative to the local time zone on the machine where you run
+\fBmysqlbinlog\fR. The value should be in a format accepted for the
+DATETIME
+or
+TIMESTAMP
+data types. For example:
+.sp
+.RS 3n
+.nf
+shell> \fBmysqlbinlog \-\-start\-datetime="2005\-12\-25 11:25:56" binlog.000003\fR
+.fi
+.RE
+This option is useful for point\-in\-time recovery. See
+Section\ 7.2, \(lqExample Backup and Recovery Strategy\(rq.
+.TP 3n
+\(bu
+\fB\-\-stop\-datetime=\fR\fB\fIdatetime\fR\fR
+.sp
+Stop reading the binary log at the first event having a timestamp equal or posterior to the
+\fIdatetime\fR
+argument. This option is useful for point\-in\-time recovery. See the description of the
+\fB\-\-start\-datetime\fR
+option for information about the
+\fIdatetime\fR
+value.
+.TP 3n
+\(bu
+\fB\-\-start\-position=\fR\fB\fIN\fR\fR
+.sp
+Start reading the binary log at the first event having a position equal to the
+\fIN\fR
+argument. This option applies to the first log file named on the command line.
+.TP 3n
+\(bu
+\fB\-\-stop\-position=\fR\fB\fIN\fR\fR
+.sp
+Stop reading the binary log at the first event having a position equal or greater than the
+\fIN\fR
+argument. This option applies to the last log file named on the command line.
+.TP 3n
+\(bu
+\fB\-\-to\-last\-log\fR,
+\fB\-t\fR
+.sp
+Do not stop at the end of the requested binary log from a MySQL server, but rather continue printing until the end of the last binary log. If you send the output to the same MySQL server, this may lead to an endless loop. This option requires
+\fB\-\-read\-from\-remote\-server\fR.
+.TP 3n
+\(bu
+\fB\-\-user=\fR\fB\fIuser_name\fR\fR,
+\fB\-u \fR\fB\fIuser_name\fR\fR
+.sp
+The MySQL username to use when connecting to a remote server.
+.TP 3n
+\(bu
+\fB\-\-version\fR,
+\fB\-V\fR
+.sp
+Display version information and exit.
+.sp
+.RE
+.PP
+You can also set the following variable by using
+\fB\-\-\fR\fB\fIvar_name\fR\fR\fB=\fR\fB\fIvalue\fR\fR
+syntax:
+.TP 3n
+\(bu
+open_files_limit
+.sp
+Specify the number of open file descriptors to reserve.
+.sp
+.RE
+.PP
+It is also possible to set variables by using
+\fB\-\-set\-variable=\fR\fB\fIvar_name\fR\fR\fB=\fR\fB\fIvalue\fR\fR
+or
+\fB\-O \fR\fB\fIvar_name\fR\fR\fB=\fR\fB\fIvalue\fR\fR
+syntax.
+\fIThis syntax is deprecated\fR.
+.PP
+You can pipe the output of
+\fBmysqlbinlog\fR
+into the
+\fBmysql\fR
+client to execute the statements contained in the binary log. This is used to recover from a crash when you have an old backup (see
+Section\ 7.1, \(lqDatabase Backups\(rq). For example:
+.sp
+.RS 3n
+.nf
+shell> \fBmysqlbinlog binlog.000001 | mysql\fR
+.fi
+.RE
+.PP
+Or:
+.sp
+.RS 3n
+.nf
+shell> \fBmysqlbinlog binlog.[0\-9]* | mysql\fR
+.fi
+.RE
+.PP
+You can also redirect the output of
+\fBmysqlbinlog\fR
+to a text file instead, if you need to modify the statement log first (for example, to remove statements that you do not want to execute for some reason). After editing the file, execute the statements that it contains by using it as input to the
+\fBmysql\fR
+program.
+.PP
+\fBmysqlbinlog\fR
+has the
+\fB\-\-start\-position\fR
+option, which prints only those statements with an offset in the binary log greater than or equal to a given position (the given position must match the start of one event). It also has options to stop and start when it sees an event with a given date and time. This enables you to perform point\-in\-time recovery using the
+\fB\-\-stop\-datetime\fR
+option (to be able to say, for example,
+\(lqroll forward my databases to how they were today at 10:30 a.m.\(rq).
+.PP
+If you have more than one binary log to execute on the MySQL server, the safe method is to process them all using a single connection to the server. Here is an example that demonstrates what may be
+\fIunsafe\fR:
+.sp
+.RS 3n
+.nf
+shell> \fBmysqlbinlog binlog.000001 | mysql # DANGER!!\fR
+shell> \fBmysqlbinlog binlog.000002 | mysql # DANGER!!\fR
+.fi
+.RE
+.PP
+Processing binary logs this way using different connections to the server causes problems if the first log file contains a
+CREATE TEMPORARY TABLE
+statement and the second log contains a statement that uses the temporary table. When the first
+\fBmysql\fR
+process terminates, the server drops the temporary table. When the second
+\fBmysql\fR
+process attempts to use the table, the server reports
+\(lqunknown table.\(rq
+.PP
+To avoid problems like this, use a
+\fIsingle\fR
+connection to execute the contents of all binary logs that you want to process. Here is one way to do so:
+.sp
+.RS 3n
+.nf
+shell> \fBmysqlbinlog binlog.000001 binlog.000002 | mysql\fR
+.fi
+.RE
+.PP
+Another approach is to write all the logs to a single file and then process the file:
+.sp
+.RS 3n
+.nf
+shell> \fBmysqlbinlog binlog.000001 > /tmp/statements.sql\fR
+shell> \fBmysqlbinlog binlog.000002 >> /tmp/statements.sql\fR
+shell> \fBmysql \-e "source /tmp/statements.sql"\fR
+.fi
+.RE
+.PP
+\fBmysqlbinlog\fR
+can produce output that reproduces a
+LOAD DATA INFILE
+operation without the original data file.
+\fBmysqlbinlog\fR
+copies the data to a temporary file and writes a
+LOAD DATA LOCAL INFILE
+statement that refers to the file. The default location of the directory where these files are written is system\-specific. To specify a directory explicitly, use the
+\fB\-\-local\-load\fR
+option.
+.PP
+Because
+\fBmysqlbinlog\fR
+converts
+LOAD DATA INFILE
+statements to
+LOAD DATA LOCAL INFILE
+statements (that is, it adds
+LOCAL), both the client and the server that you use to process the statements must be configured to allow
+LOCAL
+capability. See
+Section\ 4.4, \(lqSecurity Issues with LOAD DATA LOCAL\(rq.
+.sp
+.it 1 an-trap
+.nr an-no-space-flag 1
+.nr an-break-flag 1
+.br
+\fBWarning\fR
+.PP
+The temporary files created for
+LOAD DATA LOCAL
+statements are
+\fInot\fR
+automatically deleted because they are needed until you actually execute those statements. You should delete the temporary files yourself after you no longer need the statement log. The files can be found in the temporary file directory and have names like
+\fIoriginal_file_name\-#\-#\fR.
+.PP
+The
+\fB\-\-hexdump\fR
+option produces a hex dump of the log contents in comments:
+.sp
+.RS 3n
+.nf
+shell> \fBmysqlbinlog \-\-hexdump master\-bin.000001\fR
+.fi
+.RE
+.PP
+With the preceding command, the output might look like this:
+.sp
+.RS 3n
+.nf
+/*!40019 SET @@session.max_insert_delayed_threads=0*/;
+/*!50003 SET @OLD_COMPLETION_TYPE=@@COMPLETION_TYPE,COMPLETION_TYPE=0*/;
+# at 4
+#051024 17:24:13 server id 1 end_log_pos 98
+# Position Timestamp Type Master ID Size Master Pos Flags
+# 00000004 9d fc 5c 43 0f 01 00 00 00 5e 00 00 00 62 00 00 00 00 00
+# 00000017 04 00 35 2e 30 2e 31 35 2d 64 65 62 75 67 2d 6c |..5.0.15.debug.l|
+# 00000027 6f 67 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |og..............|
+# 00000037 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
+# 00000047 00 00 00 00 9d fc 5c 43 13 38 0d 00 08 00 12 00 |.......C.8......|
+# 00000057 04 04 04 04 12 00 00 4b 00 04 1a |.......K...|
+# Start: binlog v 4, server v 5.0.15\-debug\-log created 051024 17:24:13
+# at startup
+ROLLBACK;
+.fi
+.RE
+.PP
+Hex dump output currently contains the following elements. This format might change in the future.
+.TP 3n
+\(bu
+Position: The byte position within the log file.
+.TP 3n
+\(bu
+Timestamp: The event timestamp. In the example shown,
+\'9d fc 5c 43'
+is the representation of
+\'051024 17:24:13'
+in hexadecimal.
+.TP 3n
+\(bu
+Type: The type of the log event. In the example shown,
+\'0f'
+means that the example event is a
+FORMAT_DESCRIPTION_EVENT. The following table lists the possible types.
+.TS
+allbox tab(:);
+l l l
+l l l
+l l l
+l l l
+l l l
+l l l
+l l l
+l l l
+l l l
+l l l
+l l l
+l l l
+l l l
+l l l
+l l l
+l l l
+l l l
+l l l
+l l l
+l l l
+l l l
+l l l
+l l l
+l l l.
+T{
+Type
+T}:T{
+Name
+T}:T{
+Meaning
+T}
+T{
+08
+T}:T{
+CREATE_FILE_EVENT
+T}:T{
+Used for LOAD DATA INFILE statements. This indicates
+ the start of execution of such a statement. A
+ temporary file is created on the slave. Used in
+ MySQL 4 only.
+T}
+T{
+09
+T}:T{
+APPEND_BLOCK_EVENT
+T}:T{
+Contains data for use in a LOAD DATA INFILE
+ statement. The data is stored in the temporary
+ file on the slave.
+T}
+T{
+0a
+T}:T{
+EXEC_LOAD_EVENT
+T}:T{
+Used for LOAD DATA INFILE statements. The contents of
+ the temporary file is stored in the table on the
+ slave. Used in MySQL 4 only.
+T}
+T{
+0b
+T}:T{
+DELETE_FILE_EVENT
+T}:T{
+Rollback of a LOAD DATA INFILE statement. The
+ temporary file should be deleted on slave.
+T}
+T{
+0c
+T}:T{
+NEW_LOAD_EVENT
+T}:T{
+Used for LOAD DATA INFILE in MySQL 4 and earlier.
+T}
+T{
+0d
+T}:T{
+RAND_EVENT
+T}:T{
+Used to send information about random values if the
+ RAND() function is used in the
+ statement.
+T}
+T{
+0e
+T}:T{
+USER_VAR_EVENT
+T}:T{
+Used to replicate user variables.
+T}
+T{
+0f
+T}:T{
+FORMAT_DESCRIPTION_EVENT
+T}:T{
+This indicates the start of a log file written by MySQL 5 or later.
+T}
+T{
+10
+T}:T{
+XID_EVENT
+T}:T{
+Event indicating commit of an XA transaction.
+T}
+T{
+11
+T}:T{
+BEGIN_LOAD_QUERY_EVENT
+T}:T{
+Used for LOAD DATA INFILE statements in MySQL 5 and
+ later.
+T}
+T{
+00
+T}:T{
+UNKNOWN_EVENT
+T}:T{
+This event should never be present in the log.
+T}
+T{
+12
+T}:T{
+EXECUTE_LOAD_QUERY_EVENT
+T}:T{
+Used for LOAD DATA INFILE statements in MySQL 5 and
+ later.
+T}
+T{
+13
+T}:T{
+TABLE_MAP_EVENT
+T}:T{
+Reserved for future use.
+T}
+T{
+14
+T}:T{
+WRITE_ROWS_EVENT
+T}:T{
+Reserved for future use.
+T}
+T{
+15
+T}:T{
+UPDATE_ROWS_EVENT
+T}:T{
+Reserved for future use.
+T}
+T{
+16
+T}:T{
+DELETE_ROWS_EVENT
+T}:T{
+Reserved for future use.
+T}
+T{
+01
+T}:T{
+START_EVENT_V3
+T}:T{
+This indicates the start of a log file written by MySQL 4 or earlier.
+T}
+T{
+02
+T}:T{
+QUERY_EVENT
+T}:T{
+The most common type of events. These contain statements executed on the
+ master.
+T}
+T{
+03
+T}:T{
+STOP_EVENT
+T}:T{
+Indicates that master has stopped.
+T}
+T{
+04
+T}:T{
+ROTATE_EVENT
+T}:T{
+Written when the master switches to a new log file.
+T}
+T{
+05
+T}:T{
+INTVAR_EVENT
+T}:T{
+Used mainly for AUTO_INCREMENT values and when the
+ \fBLAST_INSERT_ID()\fR
+ function is used in the statement.
+T}
+T{
+06
+T}:T{
+LOAD_EVENT
+T}:T{
+Used for LOAD DATA INFILE in MySQL 3.23.
+T}
+T{
+07
+T}:T{
+SLAVE_EVENT
+T}:T{
+Reserved for future use.
+T}
+.TE
+.sp
+.TP 3n
+\(bu
+Master ID: The server id of the master that created the event.
+.TP 3n
+\(bu
+Size: The size in bytes of the event.
+.TP 3n
+\(bu
+Master Pos: The position of the event in the original master log file.
+.TP 3n
+\(bu
+Flags: 16 flags. Currently, the following flags are used. The others are reserved for the future.
+.TS
+allbox tab(:);
+l l l
+l l l
+l l l
+l l l
+l l l.
+T{
+Flag
+T}:T{
+Name
+T}:T{
+Meaning
+T}
+T{
+01
+T}:T{
+LOG_EVENT_BINLOG_IN_USE_F
+T}:T{
+Log file correctly closed. (Used only in
+ FORMAT_DESCRIPTION_EVENT.) If
+ this flag is set (if the flags are, for example,
+ '01 00') in a
+ FORMAT_DESCRIPTION_EVENT, the
+ log file has not been properly closed. Most
+ probably this is because of a master crash (for
+ example, due to power failure).
+T}
+T{
+02
+T}:T{
+\
+T}:T{
+Reserved for future use.
+T}
+T{
+04
+T}:T{
+LOG_EVENT_THREAD_SPECIFIC_F
+T}:T{
+Set if the event is dependent on the connection it was executed in (for
+ example, '04 00'), for example,
+ if the event uses temporary tables.
+T}
+T{
+08
+T}:T{
+LOG_EVENT_SUPPRESS_USE_F
+T}:T{
+Set in some circumstances when the event is not dependent on the default
+ database.
+T}
+.TE
+.sp
+The other flags are reserved for future use.
+.SH "COPYRIGHT"
+.PP
+Copyright 2007 MySQL AB
+.PP
+This documentation is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License.
+.PP
+This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
+.PP
+You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110\-1301 USA or see http://www.gnu.org/licenses/.
+.PP
+Please email
+<docs at mysql.com>
+for more information or if you are interested in doing a translation.
+.SH "SEE ALSO"
+For more information, please refer to the MySQL Reference Manual,
+which may already be installed locally and which is also available
+online at http://dev.mysql.com/doc/.
+.SH AUTHOR
+MySQL AB (http://www.mysql.com/).
Added: branches/sid-5.0/debian/manpages/mysqlcheck.1
===================================================================
--- branches/sid-5.0/debian/manpages/mysqlcheck.1 (rev 0)
+++ branches/sid-5.0/debian/manpages/mysqlcheck.1 2007-11-26 12:34:29 UTC (rev 1020)
@@ -0,0 +1,378 @@
+.\" Title: \fBmysqlcheck\fR
+.\" Author:
+.\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
+.\" Date: 11/25/2007
+.\" Manual: MySQL Database System
+.\" Source: MySQL 5.0
+.\"
+.TH "\fBMYSQLCHECK\fR" "1" "11/25/2007" "MySQL 5.0" "MySQL Database System"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
+.SH "NAME"
+mysqlcheck \- a table maintenance and repair program
+.SH "SYNOPSIS"
+.HP 46
+\fBmysqlcheck [\fR\fB\fIoptions\fR\fR\fB] [\fR\fB\fIdb_name\fR\fR\fB [\fR\fB\fItbl_name\fR\fR\fB ...]]\fR
+.SH "DESCRIPTION"
+.PP
+The
+\fBmysqlcheck\fR
+client checks, repairs, optimizes, and analyzes tables.
+.PP
+\fBmysqlcheck\fR
+is similar in function to
+\fBmyisamchk\fR, but works differently. The main operational difference is that
+\fBmysqlcheck\fR
+must be used when the
+\fBmysqld\fR
+server is running, whereas
+\fBmyisamchk\fR
+should be used when it is not. The benefit of using
+\fBmysqlcheck\fR
+is that you do not have to stop the server to check or repair your tables.
+.PP
+\fBmysqlcheck\fR
+uses the SQL statements
+CHECK TABLE,
+REPAIR TABLE,
+ANALYZE TABLE, and
+OPTIMIZE TABLE
+in a convenient way for the user. It determines which statements to use for the operation you want to perform, and then sends the statements to the server to be executed. For details about which storage engines each statement works with, see the descriptions for those statements in
+Chapter\ 12, SQL Statement Syntax.
+.PP
+The
+MyISAM
+storage engine supports all four statements, so
+\fBmysqlcheck\fR
+can be used to perform all four operations on
+MyISAM
+tables. Other storage engines do not necessarily support all operations. In such cases, an error message is displayed. For example, if
+test.t
+is a
+MEMORY
+table, an attempt to check it produces this result:
+.sp
+.RS 3n
+.nf
+shell> \fBmysqlcheck test t\fR
+test.t
+note : The storage engine for the table doesn't support check
+.fi
+.RE
+.sp
+.it 1 an-trap
+.nr an-no-space-flag 1
+.nr an-break-flag 1
+.br
+\fBCaution\fR
+.PP
+It is best to make a backup of a table before performing a table repair operation; under some circumstances the operation might cause data loss. Possible causes include but are not limited to filesystem errors.
+.PP
+There are three general ways to invoke
+\fBmysqlcheck\fR:
+.sp
+.RS 3n
+.nf
+shell> \fBmysqlcheck [\fR\fB\fIoptions\fR\fR\fB] \fR\fB\fIdb_name\fR\fR\fB [\fR\fB\fItables\fR\fR\fB]\fR
+shell> \fBmysqlcheck [\fR\fB\fIoptions\fR\fR\fB] \-\-databases \fR\fB\fIdb_name1\fR\fR\fB [\fR\fB\fIdb_name2\fR\fR\fB \fR\fB\fIdb_name3\fR\fR\fB...]\fR
+shell> \fBmysqlcheck [\fR\fB\fIoptions\fR\fR\fB] \-\-all\-databases\fR
+.fi
+.RE
+.PP
+If you do not name any tables following
+\fIdb_name\fR
+or if you use the
+\fB\-\-databases\fR
+or
+\fB\-\-all\-databases\fR
+option, entire databases are checked.
+.PP
+\fBmysqlcheck\fR
+has a special feature compared to other client programs. The default behavior of checking tables (\fB\-\-check\fR) can be changed by renaming the binary. If you want to have a tool that repairs tables by default, you should just make a copy of
+\fBmysqlcheck\fR
+named
+\fBmysqlrepair\fR, or make a symbolic link to
+\fBmysqlcheck\fR
+named
+\fBmysqlrepair\fR. If you invoke
+\fBmysqlrepair\fR, it repairs tables.
+.PP
+The following names can be used to change
+\fBmysqlcheck\fR
+default behavior:
+.TS
+allbox tab(:);
+l l
+l l
+l l.
+T{
+\fBmysqlrepair\fR
+T}:T{
+The default option is \fB\-\-repair\fR
+T}
+T{
+\fBmysqlanalyze\fR
+T}:T{
+The default option is \fB\-\-analyze\fR
+T}
+T{
+\fBmysqloptimize\fR
+T}:T{
+The default option is \fB\-\-optimize\fR
+T}
+.TE
+.sp
+.PP
+\fBmysqlcheck\fR
+supports the following options:
+.TP 3n
+\(bu
+\fB\-\-help\fR,
+\fB\-?\fR
+.sp
+Display a help message and exit.
+.TP 3n
+\(bu
+\fB\-\-all\-databases\fR,
+\fB\-A\fR
+.sp
+Check all tables in all databases. This is the same as using the
+\fB\-\-databases\fR
+option and naming all the databases on the command line.
+.TP 3n
+\(bu
+\fB\-\-all\-in\-1\fR,
+\fB\-1\fR
+.sp
+Instead of issuing a statement for each table, execute a single statement for each database that names all the tables from that database to be processed.
+.TP 3n
+\(bu
+\fB\-\-analyze\fR,
+\fB\-a\fR
+.sp
+Analyze the tables.
+.TP 3n
+\(bu
+\fB\-\-auto\-repair\fR
+.sp
+If a checked table is corrupted, automatically fix it. Any necessary repairs are done after all tables have been checked.
+.TP 3n
+\(bu
+\fB\-\-character\-sets\-dir=\fR\fB\fIpath\fR\fR
+.sp
+The directory where character sets are installed. See
+Section\ 2, \(lqThe Character Set Used for Data and Sorting\(rq.
+.TP 3n
+\(bu
+\fB\-\-check\fR,
+\fB\-c\fR
+.sp
+Check the tables for errors. This is the default operation.
+.TP 3n
+\(bu
+\fB\-\-check\-only\-changed\fR,
+\fB\-C\fR
+.sp
+Check only tables that have changed since the last check or that have not been closed properly.
+.TP 3n
+\(bu
+\fB\-\-check\-upgrade\fR,
+\fB\-g\fR
+.sp
+Invoke
+CHECK TABLE
+with the
+FOR UPGRADE
+option to check tables for incompatibilities with the current version of the server. This option was added in MySQL 5.0.19.
+.TP 3n
+\(bu
+\fB\-\-compress\fR
+.sp
+Compress all information sent between the client and the server if both support compression.
+.TP 3n
+\(bu
+\fB\-\-databases\fR,
+\fB\-B\fR
+.sp
+Process all tables in the named databases. Normally,
+\fBmysqlcheck\fR
+treats the first name argument on the command line as a database name and following names as table names. With this option, it treats all name arguments as database names.
+.TP 3n
+\(bu
+\fB\-\-debug[=\fR\fB\fIdebug_options\fR\fR\fB]\fR,
+\fB\-# [\fR\fB\fIdebug_options\fR\fR\fB]\fR
+.sp
+Write a debugging log. A typical
+\fIdebug_options\fR
+string is often
+\'d:t:o,\fIfile_name\fR'.
+.TP 3n
+\(bu
+\fB\-\-default\-character\-set=\fR\fB\fIcharset_name\fR\fR
+.sp
+Use
+\fIcharset_name\fR
+as the default character set. See
+Section\ 2, \(lqThe Character Set Used for Data and Sorting\(rq.
+.TP 3n
+\(bu
+\fB\-\-extended\fR,
+\fB\-e\fR
+.sp
+If you are using this option to check tables, it ensures that they are 100% consistent but takes a long time.
+.sp
+If you are using this option to repair tables, it runs an extended repair that may not only take a long time to execute, but may produce a lot of garbage rows also!
+.TP 3n
+\(bu
+\fB\-\-fast\fR,
+\fB\-F\fR
+.sp
+Check only tables that have not been closed properly.
+.TP 3n
+\(bu
+\fB\-\-force\fR,
+\fB\-f\fR
+.sp
+Continue even if an SQL error occurs.
+.TP 3n
+\(bu
+\fB\-\-host=\fR\fB\fIhost_name\fR\fR,
+\fB\-h \fR\fB\fIhost_name\fR\fR
+.sp
+Connect to the MySQL server on the given host.
+.TP 3n
+\(bu
+\fB\-\-medium\-check\fR,
+\fB\-m\fR
+.sp
+Do a check that is faster than an
+\fB\-\-extended\fR
+operation. This finds only 99.99% of all errors, which should be good enough in most cases.
+.TP 3n
+\(bu
+\fB\-\-optimize\fR,
+\fB\-o\fR
+.sp
+Optimize the tables.
+.TP 3n
+\(bu
+\fB\-\-password[=\fR\fB\fIpassword\fR\fR\fB]\fR,
+\fB\-p[\fR\fB\fIpassword\fR\fR\fB]\fR
+.sp
+The password to use when connecting to the server. If you use the short option form (\fB\-p\fR), you
+\fIcannot\fR
+have a space between the option and the password. If you omit the
+\fIpassword\fR
+value following the
+\fB\-\-password\fR
+or
+\fB\-p\fR
+option on the command line, you are prompted for one.
+.sp
+Specifying a password on the command line should be considered insecure. See
+Section\ 6.6, \(lqKeeping Your Password Secure\(rq.
+.TP 3n
+\(bu
+\fB\-\-port=\fR\fB\fIport_num\fR\fR,
+\fB\-P \fR\fB\fIport_num\fR\fR
+.sp
+The TCP/IP port number to use for the connection.
+.TP 3n
+\(bu
+\fB\-\-protocol={TCP|SOCKET|PIPE|MEMORY}\fR
+.sp
+The connection protocol to use.
+.TP 3n
+\(bu
+\fB\-\-quick\fR,
+\fB\-q\fR
+.sp
+If you are using this option to check tables, it prevents the check from scanning the rows to check for incorrect links. This is the fastest check method.
+.sp
+If you are using this option to repair tables, it tries to repair only the index tree. This is the fastest repair method.
+.TP 3n
+\(bu
+\fB\-\-repair\fR,
+\fB\-r\fR
+.sp
+Perform a repair that can fix almost anything except unique keys that are not unique.
+.TP 3n
+\(bu
+\fB\-\-silent\fR,
+\fB\-s\fR
+.sp
+Silent mode. Print only error messages.
+.TP 3n
+\(bu
+\fB\-\-socket=\fR\fB\fIpath\fR\fR,
+\fB\-S \fR\fB\fIpath\fR\fR
+.sp
+For connections to
+localhost, the Unix socket file to use, or, on Windows, the name of the named pipe to use.
+.TP 3n
+\(bu
+\fB\-\-ssl*\fR
+.sp
+Options that begin with
+\fB\-\-ssl\fR
+specify whether to connect to the server via SSL and indicate where to find SSL keys and certificates. See
+Section\ 6.7.3, \(lqSSL Command Options\(rq.
+.TP 3n
+\(bu
+\fB\-\-tables\fR
+.sp
+Overrides the
+\fB\-\-databases\fR
+or
+\fB\-B\fR
+option. All name arguments following the option are regarded as table names.
+.TP 3n
+\(bu
+\fB\-\-use\-frm\fR
+.sp
+For repair operations on
+MyISAM
+tables, get the table structure from the
+\fI.frm\fR
+file so that the table can be repaired even if the
+\fI.MYI\fR
+header is corrupted.
+.TP 3n
+\(bu
+\fB\-\-user=\fR\fB\fIuser_name\fR\fR,
+\fB\-u \fR\fB\fIuser_name\fR\fR
+.sp
+The MySQL username to use when connecting to the server.
+.TP 3n
+\(bu
+\fB\-\-verbose\fR,
+\fB\-v\fR
+.sp
+Verbose mode. Print information about the various stages of program operation.
+.TP 3n
+\(bu
+\fB\-\-version\fR,
+\fB\-V\fR
+.sp
+Display version information and exit.
+.SH "COPYRIGHT"
+.PP
+Copyright 2007 MySQL AB
+.PP
+This documentation is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License.
+.PP
+This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
+.PP
+You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110\-1301 USA or see http://www.gnu.org/licenses/.
+.PP
+Please email
+<docs at mysql.com>
+for more information or if you are interested in doing a translation.
+.SH "SEE ALSO"
+For more information, please refer to the MySQL Reference Manual,
+which may already be installed locally and which is also available
+online at http://dev.mysql.com/doc/.
+.SH AUTHOR
+MySQL AB (http://www.mysql.com/).
Added: branches/sid-5.0/debian/manpages/mysqld.8
===================================================================
--- branches/sid-5.0/debian/manpages/mysqld.8 (rev 0)
+++ branches/sid-5.0/debian/manpages/mysqld.8 2007-11-26 12:34:29 UTC (rev 1020)
@@ -0,0 +1,11680 @@
+.\" Title: \fBmysqld\fR
+.\" Author:
+.\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
+.\" Date: 11/25/2007
+.\" Manual: MySQL Database System
+.\" Source: MySQL 5.0
+.\"
+.TH "\fBMYSQLD\fR" "8" "11/25/2007" "MySQL 5.0" "MySQL Database System"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
+.SH "NAME"
+mysqld \- the MySQL server
+.SH "SYNOPSIS"
+.HP 17
+\fBmysqld [\fR\fB\fIoptions\fR\fR\fB]\fR
+.SH "DESCRIPTION"
+.PP
+\fBmysqld\fR
+is the MySQL server. The following discussion covers these MySQL server configuration topics:
+.TP 3n
+\(bu
+Startup options that the server supports
+.TP 3n
+\(bu
+Server system variables
+.TP 3n
+\(bu
+Server status variables
+.TP 3n
+\(bu
+How to set the server SQL mode
+.TP 3n
+\(bu
+The server shutdown process
+.sp
+.RE
+.sp
+.it 1 an-trap
+.nr an-no-space-flag 1
+.nr an-break-flag 1
+.br
+\fBNote\fR
+.PP
+Not all storage engines are supported by all MySQL server binaries and configurations. To find out how to determine which storage engines are supported by your MySQL server installation, see
+Section\ 5.4.10, \(lqSHOW ENGINES Syntax\(rq.
+.SH "COMMAND OPTIONS"
+.PP
+When you start the
+\fBmysqld\fR
+server, you can specify program options using any of the methods described in
+Section\ 3, \(lqSpecifying Program Options\(rq. The most common methods are to provide options in an option file or on the command line. However, in most cases it is desirable to make sure that the server uses the same options each time it runs. The best way to ensure this is to list them in an option file. See
+Section\ 3.2, \(lqUsing Option Files\(rq.
+.PP
+\fBmysqld\fR
+reads options from the
+[mysqld]
+and
+[server]
+groups.
+\fBmysqld_safe\fR
+reads options from the
+[mysqld],
+[server],
+[mysqld_safe], and
+[safe_mysqld]
+groups.
+\fBmysql.server\fR
+reads options from the
+[mysqld]
+and
+[mysql.server]
+groups.
+.PP
+An embedded MySQL server usually reads options from the
+[server],
+[embedded], and
+[\fIxxxxx\fR_SERVER]
+groups, where
+\fIxxxxx\fR
+is the name of the application into which the server is embedded.
+.PP
+\fBmysqld\fR
+accepts many command options. For a brief summary, execute
+\fBmysqld \-\-help\fR. To see the full list, use
+\fBmysqld \-\-verbose \-\-help\fR.
+.PP
+The following list shows some of the most common server options. Additional options are described in other sections:
+.TP 3n
+\(bu
+Options that affect security: See
+Section\ 4.3, \(lqSecurity\-Related \fBmysqld\fR Options\(rq.
+.TP 3n
+\(bu
+SSL\-related options: See
+Section\ 6.7.3, \(lqSSL Command Options\(rq.
+.TP 3n
+\(bu
+Binary log control options: See
+Section\ 8.3, \(lqThe Binary Log\(rq.
+.TP 3n
+\(bu
+Replication\-related options: See
+Section\ 1.2, \(lqReplication Startup Options and Variables\(rq.
+.TP 3n
+\(bu
+Options specific to particular storage engines: See
+Section\ 1.1, \(lqMyISAM Startup Options\(rq,
+Section\ 5.3, \(lqBDB Startup Options\(rq,
+Section\ 2.4, \(lqInnoDB Startup Options and System Variables\(rq, and
+Section\ 5.2.1, \(lqMySQL Cluster\-Related Command Options for \fBmysqld\fR\(rq.
+.sp
+.RE
+.PP
+You can also set the values of server system variables by using variable names as options, as described later in this section.
+.TP 3n
+\(bu
+\fB\-\-help\fR,
+\fB\-?\fR
+.sp
+Display a short help message and exit. Use both the
+\fB\-\-verbose\fR
+and
+\fB\-\-help\fR
+options to see the full message.
+.TP 3n
+\(bu
+\fB\-\-abort\-slave\-event\-count\fR
+.sp
+This option is used internally by the MySQL test suite for replication testing and debugging.
+.TP 3n
+\(bu
+\fB\-\-allow\-suspicious\-udfs\fR
+.sp
+This option controls whether user\-defined functions that have only an
+xxx
+symbol for the main function can be loaded. By default, the option is off and 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. This option was added in version 5.0.3. See
+Section\ 2.4.6, \(lqUser\-Defined Function Security Precautions\(rq.
+.TP 3n
+\(bu
+\fB\-\-ansi\fR
+.sp
+Use standard (ANSI) SQL syntax instead of MySQL syntax. For more precise control over the server SQL mode, use the
+\fB\-\-sql\-mode\fR
+option instead. See
+Section\ 8.3, \(lqRunning MySQL in ANSI Mode\(rq, and
+the section called \(lqSQL MODES\(rq.
+.TP 3n
+\(bu
+\fB\-\-basedir=\fR\fB\fIpath\fR\fR,
+\fB\-b \fR\fB\fIpath\fR\fR
+.sp
+The path to the MySQL installation directory. All paths are usually resolved relative to this directory.
+.TP 3n
+\(bu
+\fBbig\-tables\fR
+.sp
+Allow large result sets by saving all temporary sets in files. This option prevents most
+\(lqtable full\(rq
+errors, but also slows down queries for which in\-memory tables would suffice. Since MySQL 3.23.2, the server is able to handle large result sets automatically by using memory for small temporary tables and switching to disk tables where necessary.
+.TP 3n
+\(bu
+\fB\-\-bind\-address=\fR\fB\fIIP\fR\fR
+.sp
+The IP address to bind to. Only one address can be selected. If this option is specified multiple times, the last address given is used.
+.TP 3n
+\(bu
+\fB\-\-bootstrap\fR
+.sp
+This option is used by the
+\fBmysql_install_db\fR
+script to create the MySQL privilege tables without having to start a full MySQL server.
+.sp
+This option is unavailable if MySQL was configured with the
+\fB\-\-disable\-grant\-options\fR
+option. See
+Section\ 4.15.2, \(lqTypical \fBconfigure\fR Options\(rq.
+.TP 3n
+\(bu
+\fB\-\-character\-sets\-dir=\fR\fB\fIpath\fR\fR
+.sp
+The directory where character sets are installed. See
+Section\ 2, \(lqThe Character Set Used for Data and Sorting\(rq.
+.TP 3n
+\(bu
+\fB\-\-character\-set\-client\-handshake\fR
+.sp
+Don't ignore character set information sent by the client. To ignore client information and use the default server character set, use
+\fB\-\-skip\-character\-set\-client\-handshake\fR; this makes MySQL behave like MySQL 4.0.
+.TP 3n
+\(bu
+\fB\-\-character\-set\-filesystem=\fR\fB\fIcharset_name\fR\fR
+.sp
+The filesystem character set. This option sets the
+character_set_filesystem
+system variable. It was added in MySQL 5.0.19.
+.TP 3n
+\(bu
+\fB\-\-character\-set\-server=\fR\fB\fIcharset_name\fR\fR,
+\fB\-C \fR\fB\fIcharset_name\fR\fR
+.sp
+Use
+\fIcharset_name\fR
+as the default server character set. See
+Section\ 2, \(lqThe Character Set Used for Data and Sorting\(rq. If you use this option to specify a non\-default character set, you should also use
+\fB\-\-collation\-server\fR
+to specify the collation.
+.TP 3n
+\(bu
+\fB\-\-chroot=\fR\fB\fIpath\fR\fR
+.sp
+Put the
+\fBmysqld\fR
+server in a closed environment during startup by using the
+chroot()
+system call. This is a recommended security measure. Note that use of this option somewhat limits
+LOAD DATA INFILE
+and
+SELECT ... INTO OUTFILE.
+.TP 3n
+\(bu
+\fB\-\-collation\-server=\fR\fB\fIcollation_name\fR\fR
+.sp
+Use
+\fIcollation_name\fR
+as the default server collation. See
+Section\ 2, \(lqThe Character Set Used for Data and Sorting\(rq.
+.TP 3n
+\(bu
+\fB\-\-console\fR
+.sp
+(Windows only.) Write error log messages to
+stderr
+and
+stdout
+even if
+\fB\-\-log\-error\fR
+is specified.
+\fBmysqld\fR
+does not close the console window if this option is used.
+.TP 3n
+\(bu
+\fB\-\-core\-file\fR
+.sp
+Write a core file if
+\fBmysqld\fR
+dies. For some systems, you must also specify the
+\fB\-\-core\-file\-size\fR
+option to
+\fBmysqld_safe\fR. See
+\fBmysqld_safe\fR(1). Note that on some systems, such as Solaris, you do not get a core file if you are also using the
+\fB\-\-user\fR
+option.
+.TP 3n
+\(bu
+\fB\-\-datadir=\fR\fB\fIpath\fR\fR,
+\fB\-h \fR\fB\fIpath\fR\fR
+.sp
+The path to the data directory.
+.TP 3n
+\(bu
+\fB\-\-debug[=\fR\fB\fIdebug_options\fR\fR\fB]\fR,
+\fB\-# [\fR\fB\fIdebug_options\fR\fR\fB]\fR
+.sp
+If MySQL is configured with
+\fB\-\-with\-debug\fR, you can use this option to get a trace file of what
+\fBmysqld\fR
+is doing. The
+\fIdebug_options\fR
+string often is
+\'d:t:o,\fIfile_name\fR'. The default is
+\'d:t:i:o,mysqld.trace'. See
+[1]\&\fIMySQL Internals: Porting\fR.
+.sp
+As of MySQL 5.0.25, using
+\fB\-\-with\-debug\fR
+to configure MySQL with debugging support enables you to use the
+\fB\-\-debug="d,parser_debug"\fR
+option when you start the server. This causes the Bison parser that is used to process SQL statements to dump a parser trace to the server's standard error output. Typically, this output is written to the error log.
+.TP 3n
+\(bu
+\fB\-\-default\-character\-set=\fR\fB\fIcharset_name\fR\fR
+(\fIDEPRECATED\fR)
+.sp
+Use
+\fIcharset_name\fR
+as the default character set. This option is deprecated in favor of
+\fB\-\-character\-set\-server\fR. See
+Section\ 2, \(lqThe Character Set Used for Data and Sorting\(rq.
+.TP 3n
+\(bu
+\fB\-\-default\-collation=\fR\fB\fIcollation_name\fR\fR
+.sp
+Use
+\fIcollation_name\fR
+as the default collation. This option is deprecated in favor of
+\fB\-\-collation\-server\fR. See
+Section\ 2, \(lqThe Character Set Used for Data and Sorting\(rq.
+.TP 3n
+\(bu
+\fB\-\-default\-storage\-engine=\fR\fB\fItype\fR\fR
+.sp
+Set the default storage engine (table type) for tables. See
+Chapter\ 13, Storage Engines.
+.TP 3n
+\(bu
+\fB\-\-default\-table\-type=\fR\fB\fItype\fR\fR
+.sp
+This option is a synonym for
+\fB\-\-default\-storage\-engine\fR.
+.TP 3n
+\(bu
+\fB\-\-default\-time\-zone=\fR\fB\fItimezone\fR\fR
+.sp
+Set the default server time zone. This option sets the global
+time_zone
+system variable. If this option is not given, the default time zone is the same as the system time zone (given by the value of the
+system_time_zone
+system variable.
+.TP 3n
+\(bu
+\fB\-\-delay\-key\-write[={OFF|ON|ALL}]\fR
+.sp
+Specify how to use delayed key writes. Delayed key writing causes key buffers not to be flushed between writes for
+MyISAM
+tables.
+OFF
+disables delayed key writes.
+ON
+enables delayed key writes for those tables that were created with the
+DELAY_KEY_WRITE
+option.
+ALL
+delays key writes for all
+MyISAM
+tables. See
+Section\ 5.2, \(lqTuning Server Parameters\(rq, and
+Section\ 1.1, \(lqMyISAM Startup Options\(rq.
+.sp
+.it 1 an-trap
+.nr an-no-space-flag 1
+.nr an-break-flag 1
+.br
+\fBNote\fR
+If you set this variable to
+ALL, you should not use
+MyISAM
+tables from within another program (such as another MySQL server or
+\fBmyisamchk\fR) when the tables are in use. Doing so leads to index corruption.
+.TP 3n
+\(bu
+\fB\-\-des\-key\-file=\fR\fB\fIfile_name\fR\fR
+.sp
+Read the default DES keys from this file. These keys are used by the
+\fBDES_ENCRYPT()\fR
+and
+\fBDES_DECRYPT()\fR
+functions.
+.TP 3n
+\(bu
+\fB\-\-disconnect\-slave\-event\-count\fR
+.sp
+This option is used internally by the MySQL test suite for replication testing and debugging.
+.TP 3n
+\(bu
+\fB\-\-enable\-named\-pipe\fR
+.sp
+Enable support for named pipes. This option can be used only with the
+\fBmysqld\-nt\fR
+and
+\fBmysqld\-debug\fR
+servers that support named\-pipe connections.
+.TP 3n
+\(bu
+\fB\-\-exit\-info[=\fR\fB\fIflags\fR\fR\fB]\fR,
+\fB\-T [\fR\fB\fIflags\fR\fR\fB]\fR
+.sp
+This is a bit mask of different flags that you can use for debugging the
+\fBmysqld\fR
+server. Do not use this option unless you know
+\fIexactly\fR
+what it does!
+.TP 3n
+\(bu
+\fB\-\-external\-locking\fR
+.sp
+Enable external locking (system locking), which is disabled by default as of MySQL 4.0. Note that if you use this option on a system on which
+lockd
+does not fully work (such as Linux), it is easy for
+\fBmysqld\fR
+to deadlock. This option previously was named
+\fB\-\-enable\-locking\fR.
+.sp
+For more information about external locking, including conditions under which it can and cannot be used, see
+Section\ 3.4, \(lqExternal Locking\(rq.
+.TP 3n
+\(bu
+\fB\-\-flush\fR
+.sp
+Flush (synchronize) all changes to disk after each SQL statement. Normally, MySQL does a write of all changes to disk only after each SQL statement and lets the operating system handle the synchronizing to disk. See
+Section\ 1.4.2, \(lqWhat to Do If MySQL Keeps Crashing\(rq.
+.TP 3n
+\(bu
+\fB\-\-enable\-pstack\fR
+.sp
+Print a symbolic stack trace on failure.
+.TP 3n
+\(bu
+\fB\-\-gdb\fR
+.sp
+Install an interrupt handler for
+SIGINT
+(needed to stop
+\fBmysqld\fR
+with
+^C
+to set breakpoints) and disable stack tracing and core file handling. See
+[1]\&\fIMySQL Internals: Porting\fR.
+.TP 3n
+\(bu
+\fB\-\-init\-file=\fR\fB\fIfile_name\fR\fR
+.sp
+Read SQL statements from this file at startup. Each statement must be on a single line and should not include comments.
+.sp
+This option is unavailable if MySQL was configured with the
+\fB\-\-disable\-grant\-options\fR
+option. See
+Section\ 4.15.2, \(lqTypical \fBconfigure\fR Options\(rq.
+.TP 3n
+\(bu
+\fB\-\-innodb\-safe\-binlog\fR
+.sp
+Adds consistency guarantees between the content of
+InnoDB
+tables and the binary log. See
+Section\ 8.3, \(lqThe Binary Log\(rq. This option was removed in MySQL 5.0.3, having been made obsolete by the introduction of XA transaction support.
+.TP 3n
+\(bu
+\fB\-\-innodb\-\fR\fB\fIxxx\fR\fR
+.sp
+The
+InnoDB
+options are listed in
+Section\ 2.4, \(lqInnoDB Startup Options and System Variables\(rq.
+.TP 3n
+\(bu
+\fB\-\-language=\fR\fB\fIlang_name\fR\fR\fB, \-L \fR\fB\fIlang_name\fR\fR
+.sp
+Return client error messages in the given language.
+\fIlang_name\fR
+can be given as the language name or as the full pathname to the directory where the language files are installed. See
+Section\ 3, \(lqSetting the Error Message Language\(rq.
+.TP 3n
+\(bu
+\fB\-\-large\-pages\fR
+.sp
+Some hardware/operating system architectures support memory pages greater than the default (usually 4KB). The actual implementation of this support depends on the underlying hardware and OS. Applications that perform a lot of memory accesses may obtain performance improvements by using large pages due to reduced Translation Lookaside Buffer (TLB) misses.
+.sp
+Currently, MySQL supports only the Linux implementation of large pages support (which is called HugeTLB in Linux). We have plans to extend this support to FreeBSD, Solaris and possibly other platforms.
+.sp
+Before large pages can be used on Linux, it is necessary to configure the HugeTLB memory pool. For reference, consult the
+\fIhugetlbpage.txt\fR
+file in the Linux kernel source.
+.sp
+This option is disabled by default. It was added in MySQL 5.0.3.
+.TP 3n
+\(bu
+\fB\-\-log[=\fR\fB\fIfile_name\fR\fR\fB]\fR,
+\fB\-l [\fR\fB\fIfile_name\fR\fR\fB]\fR
+.sp
+Log connections and SQL statements received from clients to this file. See
+Section\ 8.2, \(lqThe General Query Log\(rq. If you omit the filename, MySQL uses
+\fI\fIhost_name\fR\fR\fI.log\fR
+as the filename.
+.TP 3n
+\(bu
+\fB\-\-log\-bin[=\fR\fB\fIbase_name\fR\fR\fB]\fR
+.sp
+Enable binary logging. The server logs all statements that change data to the binary log, which is used for backup and replication. See
+Section\ 8.3, \(lqThe Binary Log\(rq.
+.sp
+The option value, if given, is the basename for the log sequence. The server creates binary log files in sequence by adding a numeric suffix to the basename. It is recommended that you specify a basename (see
+Section\ 1.8.1, \(lqOpen Issues in MySQL\(rq, for the reason). Otherwise, MySQL uses
+\fI\fIhost_name\fR\fR\fI\-bin\fR
+as the basename.
+.TP 3n
+\(bu
+\fB\-\-log\-bin\-index[=\fR\fB\fIfile_name\fR\fR\fB]\fR
+.sp
+The index file for binary log filenames. See
+Section\ 8.3, \(lqThe Binary Log\(rq. If you omit the filename, and if you didn't specify one with
+\fB\-\-log\-bin\fR, MySQL uses
+\fI\fIhost_name\fR\fR\fI\-bin.index\fR
+as the filename.
+.TP 3n
+\(bu
+\fB\-\-log\-bin\-trust\-function\-creators[={0|1}]\fR
+.sp
+With no argument or an argument of 1, this option sets the
+log_bin_trust_function_creators
+system variable to 1. With an argument of 0, this option sets the system variable to 0.
+log_bin_trust_function_creators
+affects how MySQL enforces restrictions on stored function creation. See
+Section\ 4, \(lqBinary Logging of Stored Routines and Triggers\(rq.
+.sp
+This option was added in MySQL 5.0.16.
+.TP 3n
+\(bu
+\fB\-\-log\-bin\-trust\-routine\-creators[={0|1}]\fR
+.sp
+This is the old name for
+\fB\-\-log\-bin\-trust\-function\-creators\fR. Before MySQL 5.0.16, it also applies to stored procedures, not just stored functions and sets the
+log_bin_trust_routine_creators
+system variable. As of 5.0.16, this option is deprecated. It is recognized for backward compatibility but its use results in a warning.
+.sp
+This option was added in MySQL 5.0.6.
+.TP 3n
+\(bu
+\fB\-\-log\-error[=\fR\fB\fIfile_name\fR\fR\fB]\fR
+.sp
+Log errors and startup messages to this file. See
+Section\ 8.1, \(lqThe Error Log\(rq. If you omit the filename, MySQL uses
+\fI\fIhost_name\fR\fR\fI.err\fR. If the filename has no extension, the server adds an extension of
+\fI.err\fR.
+.TP 3n
+\(bu
+\fB\-\-log\-isam[=\fR\fB\fIfile_name\fR\fR\fB]\fR
+.sp
+Log all
+MyISAM
+changes to this file (used only when debugging
+MyISAM).
+.TP 3n
+\(bu
+\fB\-\-log\-long\-format\fR
+(\fIDEPRECATED\fR)
+.sp
+Log extra information to the update log, binary update log, and slow query log, if they have been activated. For example, the username and timestamp are logged for all queries. This option is deprecated, as it now represents the default logging behavior. (See the description for
+\fB\-\-log\-short\-format\fR.) The
+\fB\-\-log\-queries\-not\-using\-indexes\fR
+option is available for the purpose of logging queries that do not use indexes to the slow query log.
+.TP 3n
+\(bu
+\fB\-\-log\-queries\-not\-using\-indexes\fR
+.sp
+If you are using this option with
+\fB\-\-log\-slow\-queries\fR, queries that do not use indexes are logged to the slow query log. See
+Section\ 8.4, \(lqThe Slow Query Log\(rq.
+.TP 3n
+\(bu
+\fB\-\-log\-short\-format\fR
+.sp
+Log less information to the update log, binary update log, and slow query log, if they have been activated. For example, the username and timestamp are not logged for queries.
+.TP 3n
+\(bu
+\fB\-\-log\-slow\-admin\-statements\fR
+.sp
+Log slow administrative statements such as
+OPTIMIZE TABLE,
+ANALYZE TABLE, and
+ALTER TABLE
+to the slow query log.
+.TP 3n
+\(bu
+\fB\-\-log\-slow\-queries[=\fR\fB\fIfile_name\fR\fR\fB]\fR
+.sp
+Log all queries that have taken more than
+long_query_time
+seconds to execute to this file. See
+Section\ 8.4, \(lqThe Slow Query Log\(rq. See the descriptions of the
+\fB\-\-log\-long\-format\fR
+and
+\fB\-\-log\-short\-format\fR
+options for details.
+.TP 3n
+\(bu
+\fB\-\-log\-tc=\fR\fB\fIfile_name\fR\fR
+.sp
+The name of the memory\-mapped transaction coordinator log file (for XA transactions that affect multiple storage engines when the binary log is disabled). The default name is
+\fItc.log\fR. The file is created under the data directory if not given as a full pathname. Currently, this option is unused. Added in MySQL 5.0.3.
+.TP 3n
+\(bu
+\fB\-\-log\-tc\-size=\fR\fB\fIsize\fR\fR
+.sp
+The size in bytes of the memory\-mapped transaction coordinator log. The default size is 24KB. Added in MySQL 5.0.3.
+.TP 3n
+\(bu
+\fB\-\-log\-warnings[=\fR\fB\fIlevel\fR\fR\fB]\fR,
+\fB\-W [\fR\fB\fIlevel\fR\fR\fB]\fR
+.sp
+Print out warnings such as
+Aborted connection...
+to the error log. Enabling this option is recommended, for example, if you use replication (you get more information about what is happening, such as messages about network failures and reconnections). This option is enabled (1) by default, and the default
+\fIlevel\fR
+value if omitted is 1. To disable this option, use
+\fB\-\-log\-warnings=0\fR. If the value is greater than 1, aborted connections are written to the error log. See
+Section\ 1.2.11, \(lqCommunication Errors and Aborted Connections\(rq.
+.TP 3n
+\(bu
+\fB\-\-low\-priority\-updates\fR
+.sp
+Give table\-modifying operations (INSERT,
+REPLACE,
+DELETE,
+UPDATE) lower priority than selects. This can also be done via
+{INSERT | REPLACE | DELETE | UPDATE} LOW_PRIORITY ...
+to lower the priority of only one query, or by
+SET LOW_PRIORITY_UPDATES=1
+to change the priority in one thread. This affects only storage engines that use only table\-level locking (MyISAM,
+MEMORY,
+MERGE). See
+Section\ 3.2, \(lqTable Locking Issues\(rq.
+.TP 3n
+\(bu
+\fB\-\-max\-binlog\-dump\-events\fR
+.sp
+This option is used internally by the MySQL test suite for replication testing and debugging.
+.TP 3n
+\(bu
+\fB\-\-memlock\fR
+.sp
+Lock the
+\fBmysqld\fR
+process in memory. This works on systems such as Solaris that support the
+mlockall()
+system call. This might help if you have a problem where the operating system is causing
+\fBmysqld\fR
+to swap on disk. Note that use of this option requires that you run the server as
+root, which is normally not a good idea for security reasons. See
+Section\ 4.5, \(lqHow to Run MySQL as a Normal User\(rq.
+.TP 3n
+\(bu
+\fB\-\-myisam\-recover[=\fR\fB\fIoption\fR\fR\fB[,\fR\fB\fIoption\fR\fR\fB]...]]\fR
+.sp
+Set the
+MyISAM
+storage engine recovery mode. The option value is any combination of the values of
+DEFAULT,
+BACKUP,
+FORCE, or
+QUICK. If you specify multiple values, separate them by commas. You can also use a value of
+""
+to disable this option. If this option is used, each time
+\fBmysqld\fR
+opens a
+MyISAM
+table, it checks whether the table is marked as crashed or wasn't closed properly. (The last option works only if you are running with external locking disabled.) If this is the case,
+\fBmysqld\fR
+runs a check on the table. If the table was corrupted,
+\fBmysqld\fR
+attempts to repair it.
+.sp
+The following options affect how the repair works:
+.TS
+allbox tab(:);
+l l
+l l
+l l
+l l
+l l.
+T{
+\fBOption\fR
+T}:T{
+\fBDescription\fR
+T}
+T{
+DEFAULT
+T}:T{
+The same as not giving any option to \fB\-\-myisam\-recover\fR.
+T}
+T{
+BACKUP
+T}:T{
+If the data file was changed during recovery, save a backup of the
+ \fI\fItbl_name\fR\fR\fI.MYD\fR
+ file as
+ \fI\fItbl_name\-datetime\fR\fR\fI.BAK\fR.
+T}
+T{
+FORCE
+T}:T{
+Run recovery even if we would lose more than one row from the
+ \fI.MYD\fR file.
+T}
+T{
+QUICK
+T}:T{
+Don't check the rows in the table if there aren't any delete blocks.
+T}
+.TE
+.sp
+Before the server automatically repairs a table, it writes a note about the repair to the error log. If you want to be able to recover from most problems without user intervention, you should use the options
+BACKUP,FORCE. This forces a repair of a table even if some rows would be deleted, but it keeps the old data file as a backup so that you can later examine what happened.
+.sp
+See
+Section\ 1.1, \(lqMyISAM Startup Options\(rq.
+.TP 3n
+\(bu
+\fB\-\-ndb\-connectstring=\fR\fB\fIconnect_string\fR\fR
+.sp
+When using the
+NDB
+storage engine, it is possible to point out the management server that distributes the cluster configuration by setting the connect string option. See
+Section\ 3.4.2, \(lqThe Cluster Connectstring\(rq, for syntax.
+.TP 3n
+\(bu
+\fB\-\-ndbcluster\fR
+.sp
+If the binary includes support for the
+NDB Cluster
+storage engine, this option enables the engine, which is disabled by default. See
+Chapter\ 16, MySQL Cluster.
+.TP 3n
+\(bu
+\fB\-\-old\-passwords\fR
+.sp
+Force the server to generate short (pre\-4.1) password hashes for new passwords. This is useful for compatibility when the server must support older client programs. See
+Section\ 5.9, \(lqPassword Hashing as of MySQL 4.1\(rq.
+.TP 3n
+\(bu
+\fB\-\-one\-thread\fR
+.sp
+Only use one thread (for debugging under Linux). This option is available only if the server is built with debugging enabled. See
+[1]\&\fIMySQL Internals: Porting\fR.
+.TP 3n
+\(bu
+\fB\-\-open\-files\-limit=\fR\fB\fIcount\fR\fR
+.sp
+Change the number of file descriptors available to
+\fBmysqld\fR. If this option is not set or is set to 0,
+\fBmysqld\fR
+uses the value to reserve file descriptors with
+setrlimit(). If the value is 0,
+\fBmysqld\fR
+reserves
+max_connections\(mu5
+or
+max_connections + table_open_cache\(mu2
+files (whichever is larger). You should try increasing this value if
+\fBmysqld\fR
+gives you the error
+Too many open files.
+.TP 3n
+\(bu
+\fB\-\-pid\-file=\fR\fB\fIpath\fR\fR
+.sp
+The pathname of the process ID file. This file is used by other programs such as
+\fBmysqld_safe\fR
+to determine the server's process ID.
+.TP 3n
+\(bu
+\fB\-\-port=\fR\fB\fIport_num\fR\fR,
+\fB\-P \fR\fB\fIport_num\fR\fR
+.sp
+The port number to use when listening for TCP/IP connections. The port number must be 1024 or higher unless the server is started by the
+root
+system user.
+.TP 3n
+\(bu
+\fB\-\-port\-open\-timeout=\fR\fB\fInum\fR\fR
+.sp
+On some systems, when the server is stopped, the TCP/IP port might not become available immediately. If the server is restarted quickly afterward, its attempt to reopen the port can fail. This option indicates how many seconds the server should wait for the TCP/IP port to become free if it cannot be opened. The default is not to wait. This option was added in MySQL 5.0.19.
+.TP 3n
+\(bu
+\fB\-\-safe\-mode\fR
+.sp
+Skip some optimization stages.
+.TP 3n
+\(bu
+\fB\-\-safe\-show\-database\fR
+(\fIDEPRECATED\fR)
+.sp
+See
+Section\ 5.3, \(lqPrivileges Provided by MySQL\(rq.
+.TP 3n
+\(bu
+\fB\-\-safe\-user\-create\fR
+.sp
+If this option is enabled, a user cannot create new MySQL users by using the
+GRANT
+statement unless the user has the
+INSERT
+privilege for the
+mysql.user
+table or any column in the table. If you want a user to have the ability to create new users that have those privileges that the user has the right to grant, you should grant the user the following privilege:
+.sp
+.RS 3n
+.nf
+GRANT INSERT(user) ON mysql.user TO '\fIuser_name\fR'@'\fIhost_name\fR';
+.fi
+.RE
+This ensures that the user cannot change any privilege columns directly, but has to use the
+GRANT
+statement to give privileges to other users.
+.TP 3n
+\(bu
+\fB\-\-secure\-auth\fR
+.sp
+Disallow authentication by clients that attempt to use accounts that have old (pre\-4.1) passwords.
+.TP 3n
+\(bu
+\fB\-\-secure\-file\-priv=\fR\fB\fIpath\fR\fR
+.sp
+This option limits the effect of the
+LOAD_FILE()
+function and the
+LOAD DATA
+and
+SELECT ... INTO OUTFILE
+statements to work only with files in the specified directory.
+.sp
+This option was added in MySQL 5.0.38.
+.TP 3n
+\(bu
+\fB\-\-shared\-memory\fR
+.sp
+Enable shared\-memory connections by local clients. This option is available only on Windows.
+.TP 3n
+\(bu
+\fB\-\-shared\-memory\-base\-name=\fR\fB\fIname\fR\fR
+.sp
+The name of shared memory to use for shared\-memory connections. This option is available only on Windows. The default name is
+MYSQL. The name is case sensitive.
+.TP 3n
+\(bu
+\fB\-\-skip\-bdb\fR
+.sp
+Disable the
+BDB
+storage engine. This saves memory and might speed up some operations. Do not use this option if you require
+BDB
+tables.
+.TP 3n
+\(bu
+\fB\-\-skip\-concurrent\-insert\fR
+.sp
+Turn off the ability to select and insert at the same time on
+MyISAM
+tables. (This is to be used only if you think you have found a bug in this feature.) See
+Section\ 3.3, \(lqConcurrent Inserts\(rq.
+.TP 3n
+\(bu
+\fB\-\-skip\-external\-locking\fR
+.sp
+Do not use external locking (system locking). For more information about external locking, including conditions under which it can and cannot be used, see
+Section\ 3.4, \(lqExternal Locking\(rq.
+.sp
+External locking has been disabled by default since MySQL 4.0.
+.TP 3n
+\(bu
+\fB\-\-skip\-grant\-tables\fR
+.sp
+This option causes the server not to use the privilege system at all, which gives anyone with access to the server
+\fIunrestricted access to all databases\fR. You can cause a running server to start using the grant tables again by executing
+\fBmysqladmin flush\-privileges\fR
+or
+\fBmysqladmin reload\fR
+command from a system shell, or by issuing a MySQL
+FLUSH PRIVILEGES
+statement after connecting to the server. This option also suppresses loading of user\-defined functions (UDFs).
+.sp
+This option is unavailable if MySQL was configured with the
+\fB\-\-disable\-grant\-options\fR
+option. See
+Section\ 4.15.2, \(lqTypical \fBconfigure\fR Options\(rq.
+.TP 3n
+\(bu
+\fB\-\-skip\-host\-cache\fR
+.sp
+Do not use the internal hostname cache for faster name\-to\-IP resolution. Instead, query the DNS server every time a client connects. See
+Section\ 5.9, \(lqHow MySQL Uses DNS\(rq.
+.TP 3n
+\(bu
+\fB\-\-skip\-innodb\fR
+.sp
+Disable the
+InnoDB
+storage engine. This saves memory and disk space and might speed up some operations. Do not use this option if you require
+InnoDB
+tables.
+.TP 3n
+\(bu
+\fB\-\-skip\-merge\fR
+.sp
+Disable the
+MERGE
+storage engine. This option was added in MySQL 5.0.24. It can be used if the following behavior is undesirable: If a user has access to
+MyISAM
+table
+\fIt\fR, that user can create a
+MERGE
+table
+\fIm\fR
+that accesses
+\fIt\fR. However, if the user's privileges on
+\fIt\fR
+are subsequently revoked, the user can continue to access
+\fIt\fR
+by doing so through
+\fIm\fR.
+.TP 3n
+\(bu
+\fB\-\-skip\-name\-resolve\fR
+.sp
+Do not resolve hostnames when checking client connections. Use only IP numbers. If you use this option, all
+Host
+column values in the grant tables must be IP numbers or
+localhost. See
+Section\ 5.9, \(lqHow MySQL Uses DNS\(rq.
+.TP 3n
+\(bu
+\fB\-\-skip\-ndbcluster\fR
+.sp
+Disable the
+NDB Cluster
+storage engine. This is the default for binaries that were built with
+NDB Cluster
+storage engine support; the server allocates memory and other resources for this storage engine only if the
+\fB\-\-ndbcluster\fR
+option is given explicitly. See
+Section\ 3.3, \(lqQuick Test Setup of MySQL Cluster\(rq, for an example of usage.
+.TP 3n
+\(bu
+\fB\-\-skip\-networking\fR
+.sp
+Don't listen for TCP/IP connections at all. All interaction with
+\fBmysqld\fR
+must be made via named pipes or shared memory (on Windows) or Unix socket files (on Unix). This option is highly recommended for systems where only local clients are allowed. See
+Section\ 5.9, \(lqHow MySQL Uses DNS\(rq.
+.TP 3n
+\(bu
+\fB\-\-sporadic\-binlog\-dump\-fail\fR
+.sp
+This option is used internally by the MySQL test suite for replication testing and debugging.
+.TP 3n
+\(bu
+\fB\-\-ssl*\fR
+.sp
+Options that begin with
+\fB\-\-ssl\fR
+specify whether to allow clients to connect via SSL and indicate where to find SSL keys and certificates. See
+Section\ 6.7.3, \(lqSSL Command Options\(rq.
+.TP 3n
+\(bu
+\fB\-\-standalone\fR
+.sp
+Instructs the MySQL server not to run as a service.
+.TP 3n
+\(bu
+\fB\-\-symbolic\-links\fR,
+\fB\-\-skip\-symbolic\-links\fR
+.sp
+Enable or disable symbolic link support. This option has different effects on Windows and Unix:
+.RS 3n
+.TP 3n
+\(bu
+On Windows, enabling symbolic links allows you to establish a symbolic link to a database directory by creating a
+\fI\fIdb_name\fR\fR\fI.sym\fR
+file that contains the path to the real directory. See
+Section\ 6.1.3, \(lqUsing Symbolic Links for Databases on Windows\(rq.
+.TP 3n
+\(bu
+On Unix, enabling symbolic links means that you can link a
+MyISAM
+index file or data file to another directory with the
+INDEX DIRECTORY
+or
+DATA DIRECTORY
+options of the
+CREATE TABLE
+statement. If you delete or rename the table, the files that its symbolic links point to also are deleted or renamed. See
+Section\ 6.1.2, \(lqUsing Symbolic Links for Tables on Unix\(rq.
+.RE
+.TP 3n
+\(bu
+\fB\-\-skip\-safemalloc\fR
+.sp
+If MySQL is configured with
+\fB\-\-with\-debug=full\fR, all MySQL programs check for memory overruns during each memory allocation and memory freeing operation. This checking is very slow, so for the server you can avoid it when you don't need it by using the
+\fB\-\-skip\-safemalloc\fR
+option.
+.TP 3n
+\(bu
+\fB\-\-skip\-show\-database\fR
+.sp
+With this option, the
+SHOW DATABASES
+statement is allowed only to users who have the
+SHOW DATABASES
+privilege, and the statement displays all database names. Without this option,
+SHOW DATABASES
+is allowed to all users, but displays each database name only if the user has the
+SHOW DATABASES
+privilege or some privilege for the database. Note that
+\fIany\fR
+global privilege is considered a privilege for the database.
+.TP 3n
+\(bu
+\fB\-\-skip\-stack\-trace\fR
+.sp
+Don't write stack traces. This option is useful when you are running
+\fBmysqld\fR
+under a debugger. On some systems, you also must use this option to get a core file. See
+[1]\&\fIMySQL Internals: Porting\fR.
+.TP 3n
+\(bu
+\fB\-\-skip\-thread\-priority\fR
+.sp
+Disable using thread priorities for faster response time.
+.TP 3n
+\(bu
+\fB\-\-socket=\fR\fB\fIpath\fR\fR
+.sp
+On Unix, this option specifies the Unix socket file to use when listening for local connections. The default value is
+\fI/tmp/mysql.sock\fR. On Windows, the option specifies the pipe name to use when listening for local connections that use a named pipe. The default value is
+MySQL
+(not case sensitive).
+.TP 3n
+\(bu
+\fB\-\-sql\-mode=\fR\fB\fIvalue\fR\fR\fB[,\fR\fB\fIvalue\fR\fR\fB[,\fR\fB\fIvalue\fR\fR\fB...]]\fR
+.sp
+Set the SQL mode. See
+the section called \(lqSQL MODES\(rq.
+.TP 3n
+\(bu
+\fB\-\-sysdate\-is\-now\fR
+.sp
+As of MySQL 5.0.13,
+SYSDATE()
+by default returns the time at which it executes, not the time at which the statement in which it occurs begins executing. This differs from the behavior of
+NOW(). This option causes
+SYSDATE()
+to be an alias for
+NOW(). For information about the implications for binary logging and replication, see the description for
+SYSDATE()
+in
+Section\ 6, \(lqDate and Time Functions\(rq
+and for
+SET TIMESTAMP
+in
+Section\ 5.3, \(lqSET Syntax\(rq.
+.sp
+This option was added in MySQL 5.0.20.
+.TP 3n
+\(bu
+\fB\-\-tc\-heuristic\-recover={COMMIT|ROLLBACK}\fR
+.sp
+The type of decision to use in the heuristic recovery process. Currently, this option is unused. Added in MySQL 5.0.3.
+.TP 3n
+\(bu
+\fB\-\-temp\-pool\fR
+.sp
+This option causes most temporary files created by the server to use a small set of names, rather than a unique name for each new file. This works around a problem in the Linux kernel dealing with creating many new files with different names. With the old behavior, Linux seems to
+\(lqleak\(rq
+memory, because it is being allocated to the directory entry cache rather than to the disk cache.
+.TP 3n
+\(bu
+\fB\-\-transaction\-isolation=\fR\fB\fIlevel\fR\fR
+.sp
+Sets the default transaction isolation level. The
+level
+value can be
+READ\-UNCOMMITTED,
+READ\-COMMITTED,
+REPEATABLE\-READ, or
+SERIALIZABLE. See
+Section\ 4.6, \(lqSET TRANSACTION Syntax\(rq.
+.TP 3n
+\(bu
+\fB\-\-tmpdir=\fR\fB\fIpath\fR\fR,
+\fB\-t \fR\fB\fIpath\fR\fR
+.sp
+The path of the directory to use for creating temporary files. It might be useful if your default
+/tmp
+directory resides on a partition that is too small to hold temporary tables. This option accepts several paths that are used in round\-robin fashion. Paths should be separated by colon characters (\(lq:\(rq) on Unix and semicolon characters (\(lq;\(rq) on Windows, NetWare, and OS/2. If the MySQL server is acting as a replication slave, you should not set
+\fB\-\-tmpdir\fR
+to point to a directory on a memory\-based filesystem or to a directory that is cleared when the server host restarts. For more information about the storage location of temporary files, see
+Section\ 1.4.4, \(lqWhere MySQL Stores Temporary Files\(rq. A replication slave needs some of its temporary files to survive a machine restart so that it can replicate temporary tables or
+LOAD DATA INFILE
+operations. If files in the temporary file directory are lost when the server restarts, replication fails.
+.TP 3n
+\(bu
+\fB\-\-user={\fR\fB\fIuser_name\fR\fR\fB|\fR\fB\fIuser_id\fR\fR\fB}\fR,
+\fB\-u {\fR\fB\fIuser_name\fR\fR\fB|\fR\fB\fIuser_id\fR\fR\fB}\fR
+.sp
+Run the
+\fBmysqld\fR
+server as the user having the name
+\fIuser_name\fR
+or the numeric user ID
+\fIuser_id\fR. (\(lqUser\(rq
+in this context refers to a system login account, not a MySQL user listed in the grant tables.)
+.sp
+This option is
+\fImandatory\fR
+when starting
+\fBmysqld\fR
+as
+root. The server changes its user ID during its startup sequence, causing it to run as that particular user rather than as
+root. See
+Section\ 4.1, \(lqGeneral Security Guidelines\(rq.
+.sp
+To avoid a possible security hole where a user adds a
+\fB\-\-user=root\fR
+option to a
+\fImy.cnf\fR
+file (thus causing the server to run as
+root),
+\fBmysqld\fR
+uses only the first
+\fB\-\-user\fR
+option specified and produces a warning if there are multiple
+\fB\-\-user\fR
+options. Options in
+\fI/etc/my.cnf\fR
+and
+\fI$MYSQL_HOME/my.cnf\fR
+are processed before command\-line options, so it is recommended that you put a
+\fB\-\-user\fR
+option in
+\fI/etc/my.cnf\fR
+and specify a value other than
+root. The option in
+\fI/etc/my.cnf\fR
+is found before any other
+\fB\-\-user\fR
+options, which ensures that the server runs as a user other than
+root, and that a warning results if any other
+\fB\-\-user\fR
+option is found.
+.TP 3n
+\(bu
+\fB\-\-version\fR,
+\fB\-V\fR
+.sp
+Display version information and exit.
+.sp
+.RE
+.PP
+You can assign a value to a server system variable by using an option of the form
+\fB\-\-\fR\fB\fIvar_name\fR\fR\fB=\fR\fB\fIvalue\fR\fR. For example,
+\fB\-\-key_buffer_size=32M\fR
+sets the
+key_buffer_size
+variable to a value of 32MB.
+.PP
+Note that when you assign a value to a variable, MySQL might automatically correct the value to stay within a given range, or adjust the value to the closest allowable value if only certain values are allowed.
+.PP
+If you want to restrict the maximum value to which a variable can be set at runtime with
+SET, you can define this by using the
+\fB\-\-maximum\-\fR\fB\fIvar_name\fR\fR\fB=\fR\fB\fIvalue\fR\fR
+command\-line option.
+.PP
+It is also possible to set variables by using
+\fB\-\-set\-variable=\fR\fB\fIvar_name\fR\fR\fB=\fR\fB\fIvalue\fR\fR
+or
+\fB\-O \fR\fB\fIvar_name\fR\fR\fB=\fR\fB\fIvalue\fR\fR
+syntax.
+\fIThis syntax is deprecated\fR.
+.PP
+You can change the values of most system variables for a running server with the
+SET
+statement. See
+Section\ 5.3, \(lqSET Syntax\(rq.
+.PP
+the section called \(lqSYSTEM VARIABLES\(rq, provides a full description for all variables, and additional information for setting them at server startup and runtime.
+Section\ 5.2, \(lqTuning Server Parameters\(rq, includes information on optimizing the server by tuning system variables.
+.SH "SYSTEM VARIABLES"
+.PP
+The MySQL server maintains many system variables that indicate how it is configured. Each system variable has a default value. System variables can be set at server startup using options on the command line or in an option file. Most of them can be changed dynamically while the server is running by means of the
+SET
+statement, which enables you to modify operation of the server without having to stop and restart it. You can refer to system variable values in expressions.
+.PP
+There are several ways to see the names and values of system variables:
+.TP 3n
+\(bu
+To see the values that a server will use based on its compiled\-in defaults and any option files that it reads, use this command:
+.sp
+.RS 3n
+.nf
+mysqld \-\-verbose \-\-help
+.fi
+.RE
+.TP 3n
+\(bu
+To see the values that a server will use based on its compiled\-in defaults, ignoring the settings in any option files, use this command:
+.sp
+.RS 3n
+.nf
+mysqld \-\-no\-defaults \-\-verbose \-\-help
+.fi
+.RE
+.TP 3n
+\(bu
+To see the current values used by a running server, use the
+SHOW VARIABLES
+statement.
+.sp
+.RE
+.PP
+This section provides a description of each system variable. Variables with no version indicated are present in all MySQL 5.0 releases. For historical information concerning their implementation, please see
+\fI\%http://dev.mysql.com/doc/refman/4.1/en/\fR.
+.PP
+The following table lists all available system variables:
+.TS
+allbox tab(:);
+lB cB cB.
+T{
+\fBVariable Name\fR
+T}:T{
+\fBVariable Scope\fR
+T}:T{
+\fBDynamic?\fR
+T}
+.T&
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c.
+T{
+auto_increment_increment
+T}:T{
+GLOBAL | SESSION
+T}:T{
+no
+T}
+T{
+bdb_shared_data
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+innodb_log_files_in_group
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+innodb_log_group_home_dir
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+innodb_max_dirty_pages_pct
+T}:T{
+GLOBAL
+T}:T{
+yes
+T}
+T{
+innodb_max_purge_lag
+T}:T{
+GLOBAL
+T}:T{
+yes
+T}
+T{
+innodb_mirrored_log_groups
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+innodb_open_files
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+innodb_rollback_on_timeout
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+innodb_status_file
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+innodb_support_xa
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+innodb_sync_spin_loops
+T}:T{
+GLOBAL
+T}:T{
+yes
+T}
+T{
+bdb_tmpdir
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+innodb_table_locks
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+innodb_thread_concurrency
+T}:T{
+GLOBAL
+T}:T{
+yes
+T}
+T{
+innodb_thread_sleep_delay
+T}:T{
+GLOBAL
+T}:T{
+yes
+T}
+T{
+insert_id
+T}:T{
+SESSION
+T}:T{
+yes
+T}
+T{
+interactive_timeout
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+join_buffer_size
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+keep_files_on_create
+T}:T{
+GLOBAL
+T}:T{
+yes
+T}
+T{
+key_buffer_size
+T}:T{
+GLOBAL
+T}:T{
+yes
+T}
+T{
+key_cache_age_threshold
+T}:T{
+GLOBAL
+T}:T{
+yes
+T}
+T{
+key_cache_block_size
+T}:T{
+GLOBAL
+T}:T{
+yes
+T}
+T{
+bdb_cache_size
+T}:T{
+GLOBAL | SESSION
+T}:T{
+no
+T}
+T{
+key_cache_division_limit
+T}:T{
+GLOBAL
+T}:T{
+yes
+T}
+T{
+language
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+large_pages
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+large_files_support
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+large_page_size
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+last_insert_id
+T}:T{
+SESSION
+T}:T{
+yes
+T}
+T{
+lc_time_names
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+license
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+local_infile
+T}:T{
+GLOBAL
+T}:T{
+yes
+T}
+T{
+log
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+bdb_log_buffer_size
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+log_bin
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+log\-bin\-index
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+log_bin_trust_function_creators
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+log_bin_trust_routine_creators
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+log_error
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+log\-isam
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+log_queries_not_using_indexes
+T}:T{
+GLOBAL
+T}:T{
+yes
+T}
+T{
+log_slave_updates
+T}:T{
+GLOBAL | SESSION
+T}:T{
+no
+T}
+T{
+log_slow_queries
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+log_warnings
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+bdb_max_lock
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+long_query_time
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+low_priority_updates
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+lower_case_file_system
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+lower_case_table_names
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+master\-connect\-retry
+T}:T{
+\
+T}:T{
+no
+T}
+T{
+max_allowed_packet
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+max_binlog_cache_size
+T}:T{
+GLOBAL
+T}:T{
+yes
+T}
+T{
+max_binlog_size
+T}:T{
+GLOBAL
+T}:T{
+yes
+T}
+T{
+max_connect_errors
+T}:T{
+GLOBAL
+T}:T{
+yes
+T}
+T{
+max_connections
+T}:T{
+GLOBAL
+T}:T{
+yes
+T}
+T{
+big_tables
+T}:T{
+GLOBAL
+T}:T{
+yes
+T}
+T{
+max_delayed_threads
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+max_error_count
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+max_heap_table_size
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+max_insert_delayed_threads
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+max_join_size
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+max_length_for_sort_data
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+max_prepared_stmt_count
+T}:T{
+GLOBAL
+T}:T{
+yes
+T}
+T{
+max_relay_log_size
+T}:T{
+GLOBAL
+T}:T{
+yes
+T}
+T{
+max_seeks_for_key
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+max_sort_length
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+binlog_cache_size
+T}:T{
+GLOBAL
+T}:T{
+yes
+T}
+T{
+max_sp_recursion_depth
+T}:T{
+GLOBAL
+T}:T{
+yes
+T}
+T{
+max_tmp_tables
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+max_user_connections
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+max_write_lock_count
+T}:T{
+GLOBAL
+T}:T{
+yes
+T}
+T{
+locked_in_memory
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+merge
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+multi_range_count
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+multi_read_range
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+myisam\-recover
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+myisam_block_size
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+bulk_insert_buffer_size
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+myisam_data_pointer_size
+T}:T{
+GLOBAL
+T}:T{
+yes
+T}
+T{
+myisam_max_extra_sort_file_size
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+myisam_max_sort_file_size
+T}:T{
+GLOBAL
+T}:T{
+yes
+T}
+T{
+myisam_repair_threads
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+myisam_sort_buffer_size
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+myisam_stats_method
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+ndb_autoincrement_prefetch_sz
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+ndb_cache_check_time
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+ndb_force_send
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+ndb_use_exact_count
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+character_set_filesystem
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+ndbcluster
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+net_buffer_length
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+net_read_timeout
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+net_retry_count
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+net_write_timeout
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+new
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+old_passwords
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+open_files_limit
+T}:T{
+GLOBAL
+T}:T{
+yes
+T}
+T{
+optimizer_prune_level
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+optimizer_search_depth
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+character_set_server
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+pid\-file
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+port
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+preload_buffer_size
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+prepared_stmt_count
+T}:T{
+GLOBAL | SESSION
+T}:T{
+no
+T}
+T{
+profiling
+T}:T{
+SESSION
+T}:T{
+no
+T}
+T{
+profiling_history_size
+T}:T{
+SESSION
+T}:T{
+yes
+T}
+T{
+protocol_version
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+query_alloc_block_size
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+query_cache_limit
+T}:T{
+GLOBAL
+T}:T{
+yes
+T}
+T{
+query_cache_min_res_unit
+T}:T{
+GLOBAL
+T}:T{
+yes
+T}
+T{
+auto_increment_offset
+T}:T{
+GLOBAL | SESSION
+T}:T{
+no
+T}
+T{
+character_sets_dir
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+query_cache_size
+T}:T{
+GLOBAL
+T}:T{
+yes
+T}
+T{
+query_cache_type
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+query_cache_wlock_invalidate
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+query_prealloc_size
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+range_alloc_block_size
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+read_buffer_size
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+read_only
+T}:T{
+GLOBAL
+T}:T{
+yes
+T}
+T{
+read_rnd_buffer_size
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+relay\-log
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+relay_log_purge
+T}:T{
+GLOBAL
+T}:T{
+yes
+T}
+T{
+character_set_client
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+relay_log_space_limit
+T}:T{
+GLOBAL
+T}:T{
+yes
+T}
+T{
+report\-password
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+rpl_recovery_rank
+T}:T{
+GLOBAL
+T}:T{
+yes
+T}
+T{
+secure_auth
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+secure_file_priv
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+server_id
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+skip_external_locking
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+skip\-log\-warnings
+T}:T{
+GLOBAL | SESSION
+T}:T{
+no
+T}
+T{
+skip\-merge
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+skip_networking
+T}:T{
+GLOBAL
+T}:T{
+yes
+T}
+T{
+character_set_connection
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+skip\-new
+T}:T{
+GLOBAL
+T}:T{
+yes
+T}
+T{
+skip_show_database
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+skip\-sync\-bdb\-logs
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+slave_load_tmpdir
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+slave_net_timeout
+T}:T{
+GLOBAL
+T}:T{
+yes
+T}
+T{
+slave_skip_errors
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+slave_compressed_protocol
+T}:T{
+GLOBAL
+T}:T{
+yes
+T}
+T{
+slave_transaction_retries
+T}:T{
+GLOBAL
+T}:T{
+yes
+T}
+T{
+slow_launch_time
+T}:T{
+GLOBAL
+T}:T{
+yes
+T}
+T{
+socket
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+character_set_database
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+sort_buffer_size
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+sql_mode
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+sql_auto_is_null
+T}:T{
+SESSION
+T}:T{
+no
+T}
+T{
+sql_big_selects
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+sql_big_tables
+T}:T{
+SESSION
+T}:T{
+yes
+T}
+T{
+sql_buffer_result
+T}:T{
+SESSION
+T}:T{
+yes
+T}
+T{
+sql_log_bin
+T}:T{
+SESSION
+T}:T{
+yes
+T}
+T{
+sql_log_off
+T}:T{
+SESSION
+T}:T{
+yes
+T}
+T{
+sql_log_update
+T}:T{
+SESSION
+T}:T{
+yes
+T}
+T{
+sql_low_priority_updates
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+character_set_results
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+sql_max_join_size
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+sql_notes
+T}:T{
+SESSION
+T}:T{
+yes
+T}
+T{
+sql_quote_show_create
+T}:T{
+SESSION
+T}:T{
+yes
+T}
+T{
+sql_safe_updates
+T}:T{
+SESSION
+T}:T{
+yes
+T}
+T{
+sql_select_limit
+T}:T{
+SESSION
+T}:T{
+yes
+T}
+T{
+sql_slave_skip_counter
+T}:T{
+GLOBAL
+T}:T{
+yes
+T}
+T{
+sql_warnings
+T}:T{
+SESSION
+T}:T{
+yes
+T}
+T{
+ssl
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+ssl_ca
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+ssl_capath
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+character_set_system
+T}:T{
+GLOBAL
+T}:T{
+yes
+T}
+T{
+ssl_cert
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+ssl_cipher
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+ssl_key
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+storage_engine
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+sync\-bdb\-logs
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+sync_binlog
+T}:T{
+GLOBAL
+T}:T{
+yes
+T}
+T{
+sync_frm
+T}:T{
+GLOBAL
+T}:T{
+yes
+T}
+T{
+system_time_zone
+T}:T{
+GLOBAL
+T}:T{
+yes
+T}
+T{
+table_cache
+T}:T{
+GLOBAL
+T}:T{
+yes
+T}
+T{
+table_lock_wait_timeout
+T}:T{
+GLOBAL
+T}:T{
+yes
+T}
+T{
+collation_connection
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+table_open_cache
+T}:T{
+GLOBAL
+T}:T{
+yes
+T}
+T{
+table_type
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+thread_cache_size
+T}:T{
+GLOBAL
+T}:T{
+yes
+T}
+T{
+thread_concurrency
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+thread_stack
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+time_format
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+time_zone
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+timed_mutexes
+T}:T{
+GLOBAL
+T}:T{
+yes
+T}
+T{
+timestamp
+T}:T{
+SESSION
+T}:T{
+yes
+T}
+T{
+tmp_table_size
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+collation_database
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+tmpdir
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+transaction_alloc_block_size
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+transaction_prealloc_size
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+tx_isolation
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+unique_checks
+T}:T{
+SESSION
+T}:T{
+yes
+T}
+T{
+updatable_views_with_limit
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+version
+T}:T{
+GLOBAL | SESSION
+T}:T{
+no
+T}
+T{
+version_comment
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+version_compile_machine
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+version_compile_os
+T}:T{
+GLOBAL
+T}:T{
+yes
+T}
+T{
+collation_server
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+wait_timeout
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+warning_count
+T}:T{
+SESSION
+T}:T{
+no
+T}
+T{
+completion_type
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+autocommit
+T}:T{
+SESSION
+T}:T{
+yes
+T}
+T{
+concurrent_insert
+T}:T{
+GLOBAL
+T}:T{
+yes
+T}
+T{
+connect_timeout
+T}:T{
+GLOBAL
+T}:T{
+yes
+T}
+T{
+datadir
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+date_format
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+datetime_format
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+default_week_format
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+delay_key_write
+T}:T{
+GLOBAL
+T}:T{
+yes
+T}
+T{
+delayed_insert_limit
+T}:T{
+GLOBAL
+T}:T{
+yes
+T}
+T{
+delayed_insert_timeout
+T}:T{
+GLOBAL
+T}:T{
+yes
+T}
+T{
+delayed_queue_size
+T}:T{
+GLOBAL
+T}:T{
+yes
+T}
+T{
+automatic_sp_privileges
+T}:T{
+GLOBAL
+T}:T{
+yes
+T}
+T{
+des\-key\-file
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+div_precision_increment
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+engine_condition_pushdown
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+error_count
+T}:T{
+SESSION
+T}:T{
+no
+T}
+T{
+expire_logs_days
+T}:T{
+GLOBAL
+T}:T{
+yes
+T}
+T{
+flush
+T}:T{
+GLOBAL
+T}:T{
+yes
+T}
+T{
+flush_time
+T}:T{
+GLOBAL
+T}:T{
+yes
+T}
+T{
+foreign_key_checks
+T}:T{
+SESSION
+T}:T{
+yes
+T}
+T{
+ft_boolean_syntax
+T}:T{
+GLOBAL
+T}:T{
+yes
+T}
+T{
+ft_max_word_len
+T}:T{
+GLOBAL
+T}:T{
+yes
+T}
+T{
+back_log
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+ft_min_word_len
+T}:T{
+GLOBAL
+T}:T{
+yes
+T}
+T{
+ft_query_expansion_limit
+T}:T{
+GLOBAL
+T}:T{
+yes
+T}
+T{
+ft_stopword_file
+T}:T{
+GLOBAL
+T}:T{
+yes
+T}
+T{
+group_concat_max_len
+T}:T{
+GLOBAL | SESSION
+T}:T{
+yes
+T}
+T{
+have_archive
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+have_bdb
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+have_blackhole_engine
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+have_compress
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+have_crypt
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+have_csv
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+basedir
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+have_example_engine
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+have_federated_engine
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+have_geometry
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+have_innodb
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+have_isam
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+have_merge_engine
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+have_ndbcluster
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+have_openssl
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+have_query_cache
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+have_raid
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+bdb_home
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+have_rtree_keys
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+have_ssl
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+have_symlink
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+hostname
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+identity
+T}:T{
+SESSION
+T}:T{
+yes
+T}
+T{
+init_file
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+init_connect
+T}:T{
+GLOBAL
+T}:T{
+yes
+T}
+T{
+init_slave
+T}:T{
+GLOBAL
+T}:T{
+yes
+T}
+T{
+innodb_additional_mem_pool_size
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+innodb_autoextend_increment
+T}:T{
+GLOBAL
+T}:T{
+yes
+T}
+T{
+bdb\-lock\-detect
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+innodb_buffer_pool_awe_mem_mb
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+innodb_buffer_pool_size
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+innodb_checksums
+T}:T{
+GLOBAL
+T}:T{
+yes
+T}
+T{
+innodb_commit_concurrency
+T}:T{
+GLOBAL
+T}:T{
+yes
+T}
+T{
+innodb_concurrency_tickets
+T}:T{
+GLOBAL
+T}:T{
+yes
+T}
+T{
+innodb_data_file_path
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+innodb_data_home_dir
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+innodb_doublewrite
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+innodb_fast_shutdown
+T}:T{
+GLOBAL
+T}:T{
+yes
+T}
+T{
+innodb_file_io_threads
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+bdb_logdir
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+innodb_file_per_table
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+innodb_flush_log_at_trx_commit
+T}:T{
+GLOBAL
+T}:T{
+yes
+T}
+T{
+innodb_flush_method
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+innodb_force_recovery
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+innodb_lock_wait_timeout
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+innodb_locks_unsafe_for_binlog
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+innodb_log_arch_dir
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+innodb_log_archive
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+innodb_log_buffer_size
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+T{
+innodb_log_file_size
+T}:T{
+GLOBAL
+T}:T{
+no
+T}
+.TE
+.sp
+.PP
+For additional system variable information, see these sections:
+.TP 3n
+\(bu
+the section called \(lqUSING SYSTEM VARIABLES\(rq, discusses the syntax for setting and displaying system variable values.
+.TP 3n
+\(bu
+the section called \(lqDynamic System Variables\(rq, lists the variables that can be set at runtime.
+.TP 3n
+\(bu
+Information on tuning system variables can be found in
+Section\ 5.2, \(lqTuning Server Parameters\(rq.
+.TP 3n
+\(bu
+Section\ 2.4, \(lqInnoDB Startup Options and System Variables\(rq, lists
+InnoDB
+system variables.
+.sp
+.RE
+.sp
+.it 1 an-trap
+.nr an-no-space-flag 1
+.nr an-break-flag 1
+.br
+\fBNote\fR
+.PP
+Some of the following variable descriptions refer to
+\(lqenabling\(rq
+or
+\(lqdisabling\(rq
+a variable. These variables can be enabled with the
+SET
+statement by setting them to
+ON
+or
+1, or disabled by setting them to
+OFF
+or
+0. However, to set such a variable on the command line or in an option file, you must set it to
+1
+or
+0; setting it to
+ON
+or
+OFF
+will not work. For example, on the command line,
+\fB\-\-delay_key_write=1\fR
+works but
+\fB\-\-delay_key_write=ON\fR
+does not.
+.PP
+Values for buffer sizes, lengths, and stack sizes are given in bytes unless otherwise specified.
+.TP 3n
+\(bu
+auto_increment_increment
+.sp
+auto_increment_increment
+and
+auto_increment_offset
+are intended for use with master\-to\-master replication, and can be used to control the operation of
+AUTO_INCREMENT
+columns. Both variables can be set globally or locally, and each can assume an integer value between 1 and 65,535 inclusive. Setting the value of either of these two variables to 0 causes its value to be set to 1 instead. Attempting to set the value of either of these two variables to an integer greater than 65,535 or less than 0 causes its value to be set to 65,535 instead. Attempting to set the value of
+auto_increment_increment
+or
+auto_increment_offset
+to a non\-integer value gives rise to an error, and the actual value of the variable remains unchanged.
+.sp
+These two variables affect
+AUTO_INCREMENT
+column behavior as follows:
+.RS 3n
+.TP 3n
+\(bu
+auto_increment_increment
+controls the interval between successive column values. For example:
+.sp
+.RS 3n
+.nf
+mysql> \fBSHOW VARIABLES LIKE 'auto_inc%';\fR
++\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-+
+| Variable_name | Value |
++\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-+
+| auto_increment_increment | 1 |
+| auto_increment_offset | 1 |
++\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-+
+2 rows in set (0.00 sec)
+mysql> \fBCREATE TABLE autoinc1\fR
+ \-> \fB(col INT NOT NULL AUTO_INCREMENT PRIMARY KEY);\fR
+ Query OK, 0 rows affected (0.04 sec)
+mysql> \fBSET @@auto_increment_increment=10;\fR
+Query OK, 0 rows affected (0.00 sec)
+mysql> \fBSHOW VARIABLES LIKE 'auto_inc%';\fR
++\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-+
+| Variable_name | Value |
++\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-+
+| auto_increment_increment | 10 |
+| auto_increment_offset | 1 |
++\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-+
+2 rows in set (0.01 sec)
+mysql> \fBINSERT INTO autoinc1 VALUES (NULL), (NULL), (NULL), (NULL);\fR
+Query OK, 4 rows affected (0.00 sec)
+Records: 4 Duplicates: 0 Warnings: 0
+mysql> \fBSELECT col FROM autoinc1;\fR
++\-\-\-\-\-+
+| col |
++\-\-\-\-\-+
+| 1 |
+| 11 |
+| 21 |
+| 31 |
++\-\-\-\-\-+
+4 rows in set (0.00 sec)
+.fi
+.RE
+(Note how
+SHOW VARIABLES
+is used here to obtain the current values for these variables.)
+.TP 3n
+\(bu
+auto_increment_offset
+determines the starting point for the
+AUTO_INCREMENT
+column value. Consider the following, assuming that these statements are executed during the same session as the example given in the description for
+auto_increment_increment:
+.sp
+.RS 3n
+.nf
+mysql> \fBSET @@auto_increment_offset=5;\fR
+Query OK, 0 rows affected (0.00 sec)
+mysql> \fBSHOW VARIABLES LIKE 'auto_inc%';\fR
++\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-+
+| Variable_name | Value |
++\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-+
+| auto_increment_increment | 10 |
+| auto_increment_offset | 5 |
++\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-+
+2 rows in set (0.00 sec)
+mysql> \fBCREATE TABLE autoinc2\fR
+ \-> \fB(col INT NOT NULL AUTO_INCREMENT PRIMARY KEY);\fR
+Query OK, 0 rows affected (0.06 sec)
+mysql> \fBINSERT INTO autoinc2 VALUES (NULL), (NULL), (NULL), (NULL);\fR
+Query OK, 4 rows affected (0.00 sec)
+Records: 4 Duplicates: 0 Warnings: 0
+mysql> \fBSELECT col FROM autoinc2;\fR
++\-\-\-\-\-+
+| col |
++\-\-\-\-\-+
+| 5 |
+| 15 |
+| 25 |
+| 35 |
++\-\-\-\-\-+
+4 rows in set (0.02 sec)
+.fi
+.RE
+If the value of
+auto_increment_offset
+is greater than that of
+auto_increment_increment, the value of
+auto_increment_offset
+is ignored.
+.RE
+.IP "" 3n
+Should one or both of these variables be changed and then new rows inserted into a table containing an
+AUTO_INCREMENT
+column, the results may seem counterintuitive because the series of
+AUTO_INCREMENT
+values is calculated without regard to any values already present in the column, and the next value inserted is the least value in the series that is greater than the maximum existing value in the
+AUTO_INCREMENT
+column. In other words, the series is calculated like so:
+.sp
+auto_increment_offset + \fIN\fR \(mu auto_increment_increment
+.sp
+where
+\fIN\fR
+is a positive integer value in the series [1, 2, 3, ...]. For example:
+.sp
+.RS 3n
+.nf
+mysql> \fBSHOW VARIABLES LIKE 'auto_inc%';\fR
++\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-+
+| Variable_name | Value |
++\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-+
+| auto_increment_increment | 10 |
+| auto_increment_offset | 5 |
++\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-+
+2 rows in set (0.00 sec)
+mysql> \fBSELECT col FROM autoinc1;\fR
++\-\-\-\-\-+
+| col |
++\-\-\-\-\-+
+| 1 |
+| 11 |
+| 21 |
+| 31 |
++\-\-\-\-\-+
+4 rows in set (0.00 sec)
+mysql> \fBINSERT INTO autoinc1 VALUES (NULL), (NULL), (NULL), (NULL);\fR
+Query OK, 4 rows affected (0.00 sec)
+Records: 4 Duplicates: 0 Warnings: 0
+mysql> \fBSELECT col FROM autoinc1;\fR
++\-\-\-\-\-+
+| col |
++\-\-\-\-\-+
+| 1 |
+| 11 |
+| 21 |
+| 31 |
+| 35 |
+| 45 |
+| 55 |
+| 65 |
++\-\-\-\-\-+
+8 rows in set (0.00 sec)
+.fi
+.RE
+The values shown for
+auto_increment_increment
+and
+auto_increment_offset
+generate the series 5 +
+\fIN\fR
+\(mu 10, that is, [5, 15, 25, 35, 45, ...]. The greatest value present in the
+col
+column prior to the
+INSERT
+is 31, and the next available value in the
+AUTO_INCREMENT
+series is 35, so the inserted values for
+col
+begin at that point and the results are as shown for the
+SELECT
+query.
+.sp
+It is important to remember that it is not possible to confine the effects of these two variables to a single table, and thus they do not take the place of the sequences offered by some other database management systems; these variables control the behavior of all
+AUTO_INCREMENT
+columns in
+\fIall\fR
+tables on the MySQL server. If one of these variables is set globally, its effects persist until the global value is changed or overridden by setting them locally, or until
+\fBmysqld\fR
+is restarted. If set locally, the new value affects
+AUTO_INCREMENT
+columns for all tables into which new rows are inserted by the current user for the duration of the session, unless the values are changed during that session.
+.sp
+The
+auto_increment_increment
+variable was added in MySQL 5.0.2. Its default value is 1. See
+[2]\&\fIAuto\-Increment in Multiple\-Master Replication\fR.
+.sp
+auto_increment_increment
+is supported for use with
+NDB
+tables beginning with MySQL 5.0.46. Previously, setting it when using MySQL Cluster tables produced unpredictable results.
+.TP 3n
+\(bu
+auto_increment_offset
+.sp
+This variable was introduced in MySQL 5.0.2. Its default value is 1. For particulars, see the description for
+auto_increment_increment.
+.sp
+auto_increment_offset
+is supported for use with
+NDB
+tables beginning with MySQL 5.0.46. Previously, setting it when using MySQL Cluster tables produced unpredictable results.
+.TP 3n
+\(bu
+automatic_sp_privileges
+.sp
+When this variable has a value of 1 (the default), the server automatically grants the
+EXECUTE
+and
+ALTER ROUTINE
+privileges to the creator of a stored routine, if the user cannot already execute and alter or drop the routine. (The
+ALTER ROUTINE
+privileges is required to drop the routine.) The server also automatically drops those privileges when the creator drops the routine. If
+automatic_sp_privileges
+is 0, the server does not automatically add and drop these privileges. This variable was added in MySQL 5.0.3.
+.TP 3n
+\(bu
+back_log
+.sp
+The number of outstanding connection requests MySQL can have. This comes into play when the main MySQL thread gets very many connection requests in a very short time. It then takes some time (although very little) for the main thread to check the connection and start a new thread. The
+back_log
+value indicates how many requests can be stacked during this short time before MySQL momentarily stops answering new requests. You need to increase this only if you expect a large number of connections in a short period of time.
+.sp
+In other words, this value is the size of the listen queue for incoming TCP/IP connections. Your operating system has its own limit on the size of this queue. The manual page for the Unix
+listen()
+system call should have more details. Check your OS documentation for the maximum value for this variable.
+back_log
+cannot be set higher than your operating system limit.
+.TP 3n
+\(bu
+basedir
+.sp
+The MySQL installation base directory. This variable can be set with the
+\fB\-\-basedir\fR
+option.
+.TP 3n
+\(bu
+bdb_cache_size
+.sp
+The size of the buffer that is allocated for caching indexes and rows for
+BDB
+tables. If you don't use
+BDB
+tables, you should start
+\fBmysqld\fR
+with
+\fB\-\-skip\-bdb\fR
+to not allocate memory for this cache.
+.TP 3n
+\(bu
+bdb_home
+.sp
+The base directory for
+BDB
+tables. This should be assigned the same value as the
+datadir
+variable.
+.TP 3n
+\(bu
+bdb_log_buffer_size
+.sp
+The size of the buffer that is allocated for caching indexes and rows for
+BDB
+tables. If you don't use
+BDB
+tables, you should set this to 0 or start
+\fBmysqld\fR
+with
+\fB\-\-skip\-bdb\fR
+to not allocate memory for this cache.
+.TP 3n
+\(bu
+bdb_logdir
+.sp
+The directory where the
+BDB
+storage engine writes its log files. This variable can be set with the
+\fB\-\-bdb\-logdir\fR
+option.
+.TP 3n
+\(bu
+bdb_max_lock
+.sp
+The maximum number of locks that can be active for a
+BDB
+table (10,000 by default). You should increase this value if errors such as the following occur when you perform long transactions or when
+\fBmysqld\fR
+has to examine many rows to calculate a query:
+.sp
+.RS 3n
+.nf
+bdb: Lock table is out of available locks
+Got error 12 from ...
+.fi
+.RE
+.TP 3n
+\(bu
+bdb_shared_data
+.sp
+This is
+ON
+if you are using
+\fB\-\-bdb\-shared\-data\fR
+to start Berkeley DB in multi\-process mode. (Do not use
+DB_PRIVATE
+when initializing Berkeley DB.)
+.TP 3n
+\(bu
+bdb_tmpdir
+.sp
+The
+BDB
+temporary file directory.
+.TP 3n
+\(bu
+binlog_cache_size
+.sp
+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 if the server has the binary log enabled (\fB\-\-log\-bin\fR
+option). If you often use large, multiple\-statement transactions, you can increase this cache size to get more performance. The
+Binlog_cache_use
+and
+Binlog_cache_disk_use
+status variables can be useful for tuning the size of this variable. See
+Section\ 8.3, \(lqThe Binary Log\(rq.
+.TP 3n
+\(bu
+bulk_insert_buffer_size
+.sp
+MyISAM
+uses a special tree\-like cache to make bulk inserts faster for
+INSERT ... SELECT,
+INSERT ... VALUES (...), (...), ..., and
+LOAD DATA INFILE
+when adding data to non\-empty tables. This variable limits the size of the cache tree in bytes per thread. Setting it to 0 disables this optimization. The default value is 8MB.
+.TP 3n
+\(bu
+character_set_client
+.sp
+The character set for statements that arrive from the client.
+.TP 3n
+\(bu
+character_set_connection
+.sp
+The character set used for literals that do not have a character set introducer and for number\-to\-string conversion.
+.TP 3n
+\(bu
+character_set_database
+.sp
+The character set used by the default database. The server sets this variable whenever the default database changes. If there is no default database, the variable has the same value as
+character_set_server.
+.TP 3n
+\(bu
+character_set_filesystem
+.sp
+The filesystem character set. This variable is used to interpret string literals that refer to filenames, such as in the
+LOAD DATA INFILE
+and
+SELECT ... INTO OUTFILE
+statements and the
+LOAD_FILE()
+function. Such filenames are converted from
+character_set_client
+to
+character_set_filesystem
+before the file opening attempt occurs. The default value is
+binary, which means that no conversion occurs. For systems on which multi\-byte filenames are allowed, a different value may be more appropriate. For example, if the system represents filenames using UTF\-8, set
+character_set_filesystem
+to
+\'utf8'. This variable was added in MySQL 5.0.19.
+.TP 3n
+\(bu
+character_set_results
+.sp
+The character set used for returning query results to the client.
+.TP 3n
+\(bu
+character_set_server
+.sp
+The server's default character set.
+.TP 3n
+\(bu
+character_set_system
+.sp
+The character set used by the server for storing identifiers. The value is always
+utf8.
+.TP 3n
+\(bu
+character_sets_dir
+.sp
+The directory where character sets are installed.
+.TP 3n
+\(bu
+collation_connection
+.sp
+The collation of the connection character set.
+.TP 3n
+\(bu
+collation_database
+.sp
+The collation used by the default database. The server sets this variable whenever the default database changes. If there is no default database, the variable has the same value as
+collation_server.
+.TP 3n
+\(bu
+collation_server
+.sp
+The server's default collation.
+.TP 3n
+\(bu
+completion_type
+.sp
+The transaction completion type:
+.RS 3n
+.TP 3n
+\(bu
+If the value is 0 (the default),
+COMMIT
+and
+ROLLBACK
+are unaffected.
+.TP 3n
+\(bu
+If the value is 1,
+COMMIT
+and
+ROLLBACK
+are equivalent to
+COMMIT AND CHAIN
+and
+ROLLBACK AND CHAIN, respectively. (A new transaction starts immediately with the same isolation level as the just\-terminated transaction.)
+.TP 3n
+\(bu
+If the value is 2,
+COMMIT
+and
+ROLLBACK
+are equivalent to
+COMMIT RELEASE
+and
+ROLLBACK RELEASE, respectively. (The server disconnects after terminating the transaction.)
+.RE
+.IP "" 3n
+This variable was added in MySQL 5.0.3
+.TP 3n
+\(bu
+concurrent_insert
+.sp
+If 1 (the default), MySQL allows
+INSERT
+and
+SELECT
+statements to run concurrently for
+MyISAM
+tables that have no free blocks in the middle of the data file. You can turn this option off by starting
+\fBmysqld\fR
+with
+\fB\-\-safe\fR
+or
+\fB\-\-skip\-new\fR.
+.sp
+In MySQL 5.0.6, this variable was changed to take three integer values:
+.TS
+allbox tab(:);
+l l
+l l
+l l
+l l.
+T{
+\fBValue\fR
+T}:T{
+\fBDescription\fR
+T}
+T{
+0
+T}:T{
+Off
+T}
+T{
+1
+T}:T{
+(Default) Enables concurrent insert for MyISAM tables
+ that don't have holes
+T}
+T{
+2
+T}:T{
+Enables concurrent inserts for all MyISAM tables,
+ even those that have holes. For a table with a
+ hole, new rows are inserted at the end of the
+ table if it is in use by another thread.
+ Otherwise, MySQL acquires a normal write lock and
+ inserts the row into the hole.
+T}
+.TE
+.sp
+See also
+Section\ 3.3, \(lqConcurrent Inserts\(rq.
+.TP 3n
+\(bu
+connect_timeout
+.sp
+The number of seconds that the
+\fBmysqld\fR
+server waits for a connect packet before responding with
+Bad handshake. The default value is 10 seconds as of MySQL 5.0.52 and 5 seconds before that.
+.sp
+Increasing the
+connect_timeout
+value might help if clients frequently encounter errors of the form
+Lost connection to MySQL server at '\fIXXX\fR', system error: \fIerrno\fR.
+.TP 3n
+\(bu
+datadir
+.sp
+The MySQL data directory. This variable can be set with the
+\fB\-\-datadir\fR
+option.
+.TP 3n
+\(bu
+date_format
+.sp
+This variable is not implemented.
+.TP 3n
+\(bu
+datetime_format
+.sp
+This variable is not implemented.
+.TP 3n
+\(bu
+default_week_format
+.sp
+The default mode value to use for the
+WEEK()
+function. See
+Section\ 6, \(lqDate and Time Functions\(rq.
+.TP 3n
+\(bu
+delay_key_write
+.sp
+This option applies only to
+MyISAM
+tables. It can have one of the following values to affect handling of the
+DELAY_KEY_WRITE
+table option that can be used in
+CREATE TABLE
+statements.
+.TS
+allbox tab(:);
+l l
+l l
+l l
+l l.
+T{
+\fBOption\fR
+T}:T{
+\fBDescription\fR
+T}
+T{
+OFF
+T}:T{
+DELAY_KEY_WRITE is ignored.
+T}
+T{
+ON
+T}:T{
+MySQL honors any DELAY_KEY_WRITE option specified in
+ CREATE TABLE statements. This
+ is the default value.
+T}
+T{
+ALL
+T}:T{
+All new opened tables are treated as if they were created with the
+ DELAY_KEY_WRITE option enabled.
+T}
+.TE
+.sp
+If
+DELAY_KEY_WRITE
+is enabled for a table, the key buffer is not flushed for the table on every index update, but only when the table is closed. This speeds up writes on keys a lot, but if you use this feature, you should add automatic checking of all
+MyISAM
+tables by starting the server with the
+\fB\-\-myisam\-recover\fR
+option (for example,
+\fB\-\-myisam\-recover=BACKUP,FORCE\fR). See
+the section called \(lqCOMMAND OPTIONS\(rq, and
+Section\ 1.1, \(lqMyISAM Startup Options\(rq.
+.sp
+Note that if you enable external locking with
+\fB\-\-external\-locking\fR, there is no protection against index corruption for tables that use delayed key writes.
+.TP 3n
+\(bu
+delayed_insert_limit
+.sp
+After inserting
+delayed_insert_limit
+delayed rows, the
+INSERT DELAYED
+handler thread checks whether there are any
+SELECT
+statements pending. If so, it allows them to execute before continuing to insert delayed rows.
+.TP 3n
+\(bu
+delayed_insert_timeout
+.sp
+How many seconds an
+INSERT DELAYED
+handler thread should wait for
+INSERT
+statements before terminating.
+.TP 3n
+\(bu
+delayed_queue_size
+.sp
+This is a per\-table limit on the number of rows to queue when handling
+INSERT DELAYED
+statements. If the queue becomes full, any client that issues an
+INSERT DELAYED
+statement waits until there is room in the queue again.
+.TP 3n
+\(bu
+div_precision_increment
+.sp
+This variable indicates the number of digits by which to increase the scale of the result of division operations performed with the
+/
+operator. The default value is 4. The minimum and maximum values are 0 and 30, respectively. The following example illustrates the effect of increasing the default value.
+.sp
+.RS 3n
+.nf
+mysql> \fBSELECT 1/7;\fR
++\-\-\-\-\-\-\-\-+
+| 1/7 |
++\-\-\-\-\-\-\-\-+
+| 0.1429 |
++\-\-\-\-\-\-\-\-+
+mysql> \fBSET div_precision_increment = 12;\fR
+mysql> \fBSELECT 1/7;\fR
++\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+
+| 1/7 |
++\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+
+| 0.142857142857 |
++\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+
+.fi
+.RE
+This variable was added in MySQL 5.0.6.
+.TP 3n
+\(bu
+engine_condition_pushdown
+.sp
+This variable applies to NDB. By default it is 0 (OFF): If you execute a query such as
+SELECT * FROM t WHERE mycol = 42, where
+mycol
+is a non\-indexed column, the query is executed as a full table scan on every NDB node. Each node sends every row to the MySQL server, which applies the
+WHERE
+condition. If
+engine_condition_pushdown
+is set to 1 (ON), the condition is
+\(lqpushed down\(rq
+to the storage engine and sent to the NDB nodes. Each node uses the condition to perform the scan, and only sends back to the MySQL server the rows that match the condition.
+.sp
+This variable was added in MySQL 5.0.3. Before that, the default
+NDB
+behavior is the same as for a value of
+OFF.
+.TP 3n
+\(bu
+expire_logs_days
+.sp
+The number of days for automatic binary log removal. The default is 0, which means
+\(lqno automatic removal.\(rq
+Possible removals happen at startup and at binary log rotation.
+.TP 3n
+\(bu
+flush
+.sp
+If
+ON, the server flushes (synchronizes) all changes to disk after each SQL statement. Normally, MySQL does a write of all changes to disk only after each SQL statement and lets the operating system handle the synchronizing to disk. See
+Section\ 1.4.2, \(lqWhat to Do If MySQL Keeps Crashing\(rq. This variable is set to
+ON
+if you start
+\fBmysqld\fR
+with the
+\fB\-\-flush\fR
+option.
+.TP 3n
+\(bu
+flush_time
+.sp
+If this is set to a non\-zero value, all tables are closed every
+flush_time
+seconds to free up resources and synchronize unflushed data to disk. We recommend that this option be used only on systems with minimal resources.
+.TP 3n
+\(bu
+ft_boolean_syntax
+.sp
+The list of operators supported by boolean full\-text searches performed using
+IN BOOLEAN MODE. See
+Section\ 8.2, \(lqBoolean Full\-Text Searches\(rq.
+.sp
+The default variable value is
+\'+\ \-><()~*:""&|'. The rules for changing the value are as follows:
+.RS 3n
+.TP 3n
+\(bu
+Operator function is determined by position within the string.
+.TP 3n
+\(bu
+The replacement value must be 14 characters.
+.TP 3n
+\(bu
+Each character must be an ASCII non\-alphanumeric character.
+.TP 3n
+\(bu
+Either the first or second character must be a space.
+.TP 3n
+\(bu
+No duplicates are allowed except the phrase quoting operators in positions 11 and 12. These two characters are not required to be the same, but they are the only two that may be.
+.TP 3n
+\(bu
+Positions 10, 13, and 14 (which by default are set to
+\(lq:\(rq,
+\(lq&\(rq, and
+\(lq|\(rq) are reserved for future extensions.
+.RE
+.TP 3n
+\(bu
+ft_max_word_len
+.sp
+The maximum length of the word to be included in a
+FULLTEXT
+index.
+.sp
+.it 1 an-trap
+.nr an-no-space-flag 1
+.nr an-break-flag 1
+.br
+\fBNote\fR
+FULLTEXT
+indexes must be rebuilt after changing this variable. Use
+REPAIR TABLE \fItbl_name\fR QUICK.
+.TP 3n
+\(bu
+ft_min_word_len
+.sp
+The minimum length of the word to be included in a
+FULLTEXT
+index.
+.sp
+.it 1 an-trap
+.nr an-no-space-flag 1
+.nr an-break-flag 1
+.br
+\fBNote\fR
+FULLTEXT
+indexes must be rebuilt after changing this variable. Use
+REPAIR TABLE \fItbl_name\fR QUICK.
+.TP 3n
+\(bu
+ft_query_expansion_limit
+.sp
+The number of top matches to use for full\-text searches performed using
+WITH QUERY EXPANSION.
+.TP 3n
+\(bu
+ft_stopword_file
+.sp
+The file from which to read the list of stopwords for full\-text searches. All the words from the file are used; comments are
+\fInot\fR
+honored. By default, a built\-in list of stopwords is used (as defined in the
+\fImyisam/ft_static.c\fR
+file). Setting this variable to the empty string ('') disables stopword filtering.
+.sp
+.it 1 an-trap
+.nr an-no-space-flag 1
+.nr an-break-flag 1
+.br
+\fBNote\fR
+FULLTEXT
+indexes must be rebuilt after changing this variable or the contents of the stopword file. Use
+REPAIR TABLE \fItbl_name\fR QUICK.
+.TP 3n
+\(bu
+group_concat_max_len
+.sp
+The maximum allowed result length for the
+\fBGROUP_CONCAT()\fR
+function. The default is 1024.
+.TP 3n
+\(bu
+have_archive
+.sp
+YES
+if
+\fBmysqld\fR
+supports
+ARCHIVE
+tables,
+NO
+if not.
+.TP 3n
+\(bu
+have_bdb
+.sp
+YES
+if
+\fBmysqld\fR
+supports
+BDB
+tables.
+DISABLED
+if
+\fB\-\-skip\-bdb\fR
+is used.
+.TP 3n
+\(bu
+have_blackhole_engine
+.sp
+YES
+if
+\fBmysqld\fR
+supports
+BLACKHOLE
+tables,
+NO
+if not.
+.TP 3n
+\(bu
+have_compress
+.sp
+YES
+if the
+zlib
+compression library is available to the server,
+NO
+if not. If not, the
+\fBCOMPRESS()\fR
+and
+\fBUNCOMPRESS()\fR
+functions cannot be used.
+.TP 3n
+\(bu
+have_crypt
+.sp
+YES
+if the
+\fBcrypt()\fR
+system call is available to the server,
+NO
+if not. If not, the
+\fBENCRYPT()\fR
+function cannot be used.
+.TP 3n
+\(bu
+have_csv
+.sp
+YES
+if
+\fBmysqld\fR
+supports
+CSV
+tables,
+NO
+if not.
+.TP 3n
+\(bu
+have_example_engine
+.sp
+YES
+if
+\fBmysqld\fR
+supports
+EXAMPLE
+tables,
+NO
+if not.
+.sp
+have_federated_engine
+.sp
+YES
+if
+\fBmysqld\fR
+supports
+FEDERATED
+tables,
+NO
+if not. This variable was added in MySQL 5.0.3.
+.TP 3n
+\(bu
+have_geometry
+.sp
+YES
+if the server supports spatial data types,
+NO
+if not.
+.TP 3n
+\(bu
+have_innodb
+.sp
+YES
+if
+\fBmysqld\fR
+supports
+InnoDB
+tables.
+DISABLED
+if
+\fB\-\-skip\-innodb\fR
+is used.
+.TP 3n
+\(bu
+have_isam
+.sp
+In MySQL 5.0, this variable appears only for reasons of backward compatibility. It is always
+NO
+because
+ISAM
+tables are no longer supported.
+.TP 3n
+\(bu
+have_merge_engine
+.sp
+YES
+if
+\fBmysqld\fR
+supports
+MERGE
+tables.
+DISABLED
+if
+\fB\-\-skip\-merge\fR
+is used. This variable was added in MySQL 5.0.24.
+.TP 3n
+\(bu
+have_ndbcluster
+.sp
+YES
+if
+\fBmysqld\fR
+supports
+NDB Cluster
+tables.
+DISABLED
+if
+\fB\-\-skip\-ndbcluster\fR
+is used.
+.TP 3n
+\(bu
+have_openssl
+.sp
+YES
+if
+\fBmysqld\fR
+supports SSL connections,
+NO
+if not. As of MySQL 5.0.38, this variable is an alias for
+have_ssl.
+.TP 3n
+\(bu
+have_query_cache
+.sp
+YES
+if
+\fBmysqld\fR
+supports the query cache,
+NO
+if not.
+.TP 3n
+\(bu
+have_raid
+.sp
+In MySQL 5.0, this variable appears only for reasons of backward compatibility. It is always
+NO
+because
+RAID
+tables are no longer supported.
+.TP 3n
+\(bu
+have_rtree_keys
+.sp
+YES
+if
+RTREE
+indexes are available,
+NO
+if not. (These are used for spatial indexes in
+MyISAM
+tables.)
+.TP 3n
+\(bu
+have_ssl
+.sp
+YES
+if
+\fBmysqld\fR
+supports SSL connections,
+NO
+if not. This variable was added in MySQL 5.0.38. Before that, use
+have_openssl.
+.TP 3n
+\(bu
+have_symlink
+.sp
+YES
+if symbolic link support is enabled,
+NO
+if not. This is required on Unix for support of the
+DATA DIRECTORY
+and
+INDEX DIRECTORY
+table options, and on Windows for support of data directory symlinks.
+.TP 3n
+\(bu
+hostname
+.sp
+The server sets this variable to the server hostname at startup. This variable was added in MySQL 5.0.38.
+.TP 3n
+\(bu
+init_connect
+.sp
+A string to be executed by the server for each client that connects. The string consists of one or more SQL statements. To specify multiple statements, separate them by semicolon characters. For example, each client begins by default with autocommit mode enabled. There is no global system variable to specify that autocommit should be disabled by default, but
+init_connect
+can be used to achieve the same effect:
+.sp
+.RS 3n
+.nf
+SET GLOBAL init_connect='SET AUTOCOMMIT=0';
+.fi
+.RE
+This variable can also be set on the command line or in an option file. To set the variable as just shown using an option file, include these lines:
+.sp
+.RS 3n
+.nf
+[mysqld]
+init_connect='SET AUTOCOMMIT=0'
+.fi
+.RE
+Note that the content of
+init_connect
+is not executed for users that have the
+SUPER
+privilege. This is done so that an erroneous value for
+init_connect
+does not prevent all clients from connecting. For example, the value might contain a statement that has a syntax error, thus causing client connections to fail. Not executing
+init_connect
+for users that have the
+SUPER
+privilege enables them to open a connection and fix the
+init_connect
+value.
+.TP 3n
+\(bu
+init_file
+.sp
+The name of the file specified with the
+\fB\-\-init\-file\fR
+option when you start the server. This should be a file containing SQL statements that you want the server to execute when it starts. Each statement must be on a single line and should not include comments.
+.sp
+Note that the
+\fB\-\-init\-file\fR
+option is unavailable if MySQL was configured with the
+\fB\-\-disable\-grant\-options\fR
+option. See
+Section\ 4.15.2, \(lqTypical \fBconfigure\fR Options\(rq.
+.TP 3n
+\(bu
+init_slave
+.sp
+This variable is similar to
+init_connect, but is a string to be executed by a slave server each time the SQL thread starts. The format of the string is the same as for the
+init_connect
+variable.
+.TP 3n
+\(bu
+innodb_\fIxxx\fR
+.sp
+InnoDB
+system variables are listed in
+Section\ 2.4, \(lqInnoDB Startup Options and System Variables\(rq.
+.TP 3n
+\(bu
+interactive_timeout
+.sp
+The number of seconds the server waits for activity on an interactive connection before closing it. An interactive client is defined as a client that uses the
+CLIENT_INTERACTIVE
+option to
+\fBmysql_real_connect()\fR. See also
+wait_timeout.
+.TP 3n
+\(bu
+join_buffer_size
+.sp
+The size of the buffer that is used for joins that do not use indexes and thus perform full table scans. Normally, the best way to get fast joins is to add indexes. Increase the value of
+join_buffer_size
+to get a faster full join when adding indexes is not possible. One join buffer is allocated for each full join between two tables. For a complex join between several tables for which indexes are not used, multiple join buffers might be necessary.
+.sp
+The maximum allowable setting for
+join_buffer_size
+is 4GB.
+.TP 3n
+\(bu
+keep_files_on_create
+.sp
+If a
+MyISAM
+table is created with no
+DATA DIRECTORY
+option, the
+\fI.MYD\fR
+file is created in the database directory. By default, if
+MyISAM
+finds an existing
+\fI.MYD\fR
+file in this case, it overwrites it. The same applies to
+\fI.MYI\fR
+files for tables created with no
+INDEX DIRECTORY
+option. To suppress this behavior, set the
+keep_files_on_create
+variable to
+ON
+(1), in which case
+MyISAM
+will not overwrite existing files and returns an error instead. The default value is
+OFF
+(0).
+.sp
+If a
+MyISAM
+table is created with a
+DATA DIRECTORY
+or
+INDEX DIRECTORY
+option and an existing
+\fI.MYD\fR
+or
+\fI.MYI\fR
+file is found, MyISAM always returns an error. It will not overwrite a file in the specified directory.
+.sp
+This variable was added in MySQL 5.0.48.
+.TP 3n
+\(bu
+key_buffer_size
+.sp
+Index blocks for
+MyISAM
+tables are buffered and are shared by all threads.
+key_buffer_size
+is the size of the buffer used for index blocks. The key buffer is also known as the key cache.
+.sp
+The maximum allowable setting for
+key_buffer_size
+is 4GB on 32\-bit platforms. As of MySQL 5.0.52, 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). The effective maximum size might be less, depending on your available physical RAM and per\-process RAM limits imposed by your operating system or hardware platform.
+.sp
+Increase the value to get better index handling (for all reads and multiple writes) to as much as you can afford. Using a value that is 25% of total memory on a machine that mainly runs MySQL is quite common. However, if you make the value too large (for example, more than 50% of your total memory) your system might start to page and become extremely slow. MySQL relies on the operating system to perform filesystem caching for data reads, so you must leave some room for the filesystem cache. Consider also the memory requirements of other storage engines.
+.sp
+For even more speed when writing many rows at the same time, use
+LOCK TABLES. See
+Section\ 2.17, \(lqSpeed of INSERT Statements\(rq.
+.sp
+You can check the performance of the key buffer by issuing a
+SHOW STATUS
+statement and examining the
+Key_read_requests,
+Key_reads,
+Key_write_requests, and
+Key_writes
+status variables. (See
+Section\ 5.4, \(lqSHOW Syntax\(rq.) The
+Key_reads/Key_read_requests
+ratio should normally be less than 0.01. The
+Key_writes/Key_write_requests
+ratio is usually near 1 if you are using mostly updates and deletes, but might be much smaller if you tend to do updates that affect many rows at the same time or if you are using the
+DELAY_KEY_WRITE
+table option.
+.sp
+The fraction of the key buffer in use can be determined using
+key_buffer_size
+in conjunction with the
+Key_blocks_unused
+status variable and the buffer block size, which is available from the
+key_cache_block_size
+system variable:
+.sp
+.RS 3n
+.nf
+1 \- ((Key_blocks_unused \(mu key_cache_block_size) / key_buffer_size)
+.fi
+.RE
+This value is an approximation because some space in the key buffer may be allocated internally for administrative structures.
+.sp
+It is possible to create multiple
+MyISAM
+key caches. The size limit of 4GB applies to each cache individually, not as a group. See
+Section\ 4.6, \(lqThe MyISAM Key Cache\(rq.
+.TP 3n
+\(bu
+key_cache_age_threshold
+.sp
+This value controls the demotion of buffers from the hot sub\-chain of a key cache to the warm sub\-chain. Lower values cause demotion to happen more quickly. The minimum value is 100. The default value is 300. See
+Section\ 4.6, \(lqThe MyISAM Key Cache\(rq.
+.TP 3n
+\(bu
+key_cache_block_size
+.sp
+The size in bytes of blocks in the key cache. The default value is 1024. See
+Section\ 4.6, \(lqThe MyISAM Key Cache\(rq.
+.TP 3n
+\(bu
+key_cache_division_limit
+.sp
+The division point between the hot and warm sub\-chains of the key cache buffer chain. The value is the percentage of the buffer chain to use for the warm sub\-chain. Allowable values range from 1 to 100. The default value is 100. See
+Section\ 4.6, \(lqThe MyISAM Key Cache\(rq.
+.TP 3n
+\(bu
+language
+.sp
+The language used for error messages.
+.TP 3n
+\(bu
+large_files_support
+.sp
+Whether
+\fBmysqld\fR
+was compiled with options for large file support.
+.TP 3n
+\(bu
+large_pages
+.sp
+Whether large page support is enabled. This variable was added in MySQL 5.0.3.
+.sp
+For more information, see
+the entry for the \fB\-\-large\-pages\fR server option.
+.TP 3n
+\(bu
+large_page_size
+.sp
+If large page support is enabled, this shows the size of memory pages. Currently, large memory pages are supported only on Linux; on other platforms, the value of this variable is always 0. This variable was added in MySQL 5.0.3.
+.sp
+For more information, see
+the entry for the \fB\-\-large\-pages\fR server option.
+.TP 3n
+\(bu
+lc_time_names
+.sp
+This variable specifies the locale that controls the language used to display day and month names and abbreviations. This variable affects the output from the
+DATE_FORMAT(),
+DAYNAME()
+and
+MONTHNAME()
+functions. Locale names are POSIX\-style values such as
+\'ja_JP'
+or
+\'pt_BR'. The default value is
+\'en_US'
+regardless of your system's locale setting. For further information, see
+Section\ 10, \(lqMySQL Server Locale Support\(rq. This variable was added in MySQL 5.0.25.
+.TP 3n
+\(bu
+license
+.sp
+The type of license the server has.
+.TP 3n
+\(bu
+local_infile
+.sp
+Whether
+LOCAL
+is supported for
+LOAD DATA INFILE
+statements. See
+Section\ 4.4, \(lqSecurity Issues with LOAD DATA LOCAL\(rq.
+.TP 3n
+\(bu
+locked_in_memory
+.sp
+Whether
+\fBmysqld\fR
+was locked in memory with
+\fB\-\-memlock\fR.
+.TP 3n
+\(bu
+log
+.sp
+Whether logging of all statements to the general query log is enabled. See
+Section\ 8.2, \(lqThe General Query Log\(rq.
+.TP 3n
+\(bu
+log_bin
+.sp
+Whether the binary log is enabled. See
+Section\ 8.3, \(lqThe Binary Log\(rq.
+.TP 3n
+\(bu
+log_bin_trust_function_creators
+.sp
+This variable applies when binary logging is enabled. It controls whether stored function creators can be trusted not to create stored functions that will cause unsafe events to be written to the binary log. If set to 0 (the default), users are not allowed to create or alter stored functions unless they have the
+SUPER
+privilege in addition to the
+CREATE ROUTINE
+or
+ALTER ROUTINE
+privilege. A setting of 0 also enforces the restriction that a function must be declared with the
+DETERMINISTIC
+characteristic, or with the
+READS SQL DATA
+or
+NO SQL
+characteristic. If the variable is set to 1, MySQL does not enforce these restrictions on stored function creation. See
+Section\ 4, \(lqBinary Logging of Stored Routines and Triggers\(rq.
+.sp
+This variable was added in MySQL 5.0.16.
+.TP 3n
+\(bu
+log_bin_trust_routine_creators
+.sp
+This is the old name for
+log_bin_trust_function_creators. Before MySQL 5.0.16, it also applies to stored procedures, not just stored functions. As of 5.0.16, this variable is deprecated. It is recognized for backward compatibility but its use results in a warning.
+.sp
+This variable was added in MySQL 5.0.6.
+.TP 3n
+\(bu
+log_error
+.sp
+The location of the error log.
+.TP 3n
+\(bu
+log_queries_not_using_indexes
+.sp
+Whether queries that do not use indexes are logged to the slow query log. See
+Section\ 8.4, \(lqThe Slow Query Log\(rq. This variable was added in MySQL 5.0.23.
+.TP 3n
+\(bu
+log_slave_updates
+.sp
+Whether updates received by a slave server from a master server should be logged to the slave's own binary log. Binary logging must be enabled on the slave for this variable to have any effect. See
+Section\ 1.2, \(lqReplication Startup Options and Variables\(rq.
+.TP 3n
+\(bu
+log_slow_queries
+.sp
+Whether slow queries should be logged.
+\(lqSlow\(rq
+is determined by the value of the
+long_query_time
+variable. See
+Section\ 8.4, \(lqThe Slow Query Log\(rq.
+.TP 3n
+\(bu
+log_warnings
+.sp
+Whether to produce additional warning messages. It is enabled (1) by default and can be disabled by setting it to 0. Aborted connections are not logged to the error log unless the value is greater than 1.
+.TP 3n
+\(bu
+long_query_time
+.sp
+If a query takes longer than this many seconds, the server increments the
+Slow_queries
+status variable. If you are using the
+\fB\-\-log\-slow\-queries\fR
+option, the query is logged to the slow query log file. This value is measured in real time, not CPU time, so a query that is under the threshold on a lightly loaded system might be above the threshold on a heavily loaded one. The minimum value is 1. The default is 10. See
+Section\ 8.4, \(lqThe Slow Query Log\(rq.
+.TP 3n
+\(bu
+low_priority_updates
+.sp
+If set to
+1, all
+INSERT,
+UPDATE,
+DELETE, and
+LOCK TABLE WRITE
+statements wait until there is no pending
+SELECT
+or
+LOCK TABLE READ
+on the affected table. This affects only storage engines that use only table\-level locking (MyISAM,
+MEMORY,
+MERGE). This variable previously was named
+sql_low_priority_updates.
+.TP 3n
+\(bu
+lower_case_file_system
+.sp
+This variable describes the case sensitivity of filenames on the filesystem where the data directory is located.
+OFF
+means filenames are case sensitive,
+ON
+means they are not case sensitive.
+.TP 3n
+\(bu
+lower_case_table_names
+.sp
+If set to 1, table names are stored in lowercase on disk and table name comparisons are not case sensitive. If set to 2 table names are stored as given but compared in lowercase. This option also applies to database names and table aliases. See
+Section\ 2.2, \(lqIdentifier Case Sensitivity\(rq.
+.sp
+If you are using
+InnoDB
+tables, you should set this variable to 1 on all platforms to force names to be converted to lowercase.
+.sp
+You should
+\fInot\fR
+set this variable to 0 if you are running MySQL on a system that does not have case\-sensitive filenames (such as Windows or Mac OS X). If this variable is not set at startup and the filesystem on which the data directory is located does not have case\-sensitive filenames, MySQL automatically sets
+lower_case_table_names
+to 2.
+.TP 3n
+\(bu
+max_allowed_packet
+.sp
+The maximum size of one packet or any generated/intermediate string.
+.sp
+The packet message buffer is initialized to
+net_buffer_length
+bytes, but can grow up to
+max_allowed_packet
+bytes when needed. This value by default is small, to catch large (possibly incorrect) packets.
+.sp
+You must increase this value if you are using large
+BLOB
+columns or long strings. It should be as big as the largest
+BLOB
+you want to use. The protocol limit for
+max_allowed_packet
+is 1GB.
+.TP 3n
+\(bu
+max_binlog_cache_size
+.sp
+If a multiple\-statement transaction requires more than this many bytes of memory, the server generates a
+Multi\-statement transaction required more than 'max_binlog_cache_size' bytes of storage
+error. The minimum value is 4096, the maximum and default values are 4GB.
+.TP 3n
+\(bu
+max_binlog_size
+.sp
+If a write to the binary log causes the current log file size to exceed the value of this variable, the server rotates the binary logs (closes the current file and opens the next one). You cannot set this variable to more than 1GB or to less than 4096 bytes. The default value is 1GB.
+.sp
+A transaction is written in one chunk to the binary log, so it is never split between several binary logs. Therefore, if you have big transactions, you might see binary logs larger than
+max_binlog_size.
+.sp
+If
+max_relay_log_size
+is 0, the value of
+max_binlog_size
+applies to relay logs as well.
+.TP 3n
+\(bu
+max_connect_errors
+.sp
+If there are more than this number of interrupted connections from a host, that host is blocked from further connections. You can unblock blocked hosts with the
+FLUSH HOSTS
+statement.
+.TP 3n
+\(bu
+max_connections
+.sp
+The number of simultaneous client connections allowed. By default, this is 100. See
+Section\ 1.2.7, \(lqToo many connections\(rq, for more information.
+.sp
+Increasing this value increases the number of file descriptors that
+\fBmysqld\fR
+requires. See
+Section\ 4.8, \(lqHow MySQL Opens and Closes Tables\(rq, for comments on file descriptor limits.
+.TP 3n
+\(bu
+max_delayed_threads
+.sp
+Do not start more than this number of threads to handle
+INSERT DELAYED
+statements. If you try to insert data into a new table after all
+INSERT DELAYED
+threads are in use, the row is inserted as if the
+DELAYED
+attribute wasn't specified. If you set this to 0, MySQL never creates a thread to handle
+DELAYED
+rows; in effect, this disables
+DELAYED
+entirely.
+.TP 3n
+\(bu
+max_error_count
+.sp
+The maximum number of error, warning, and note messages to be stored for display by the
+SHOW ERRORS
+and
+SHOW WARNINGS
+statements.
+.TP 3n
+\(bu
+max_heap_table_size
+.sp
+This variable sets the maximum size to which
+MEMORY
+tables are allowed to grow. The value of the variable is used to calculate
+MEMORY
+table
+MAX_ROWS
+values. Setting this variable has no effect on any existing
+MEMORY
+table, unless the table is re\-created with a statement such as
+CREATE TABLE
+or altered with
+ALTER TABLE
+or
+TRUNCATE TABLE.
+.TP 3n
+\(bu
+max_insert_delayed_threads
+.sp
+This variable is a synonym for
+max_delayed_threads.
+.TP 3n
+\(bu
+max_join_size
+.sp
+Do not allow
+SELECT
+statements that probably need to examine more than
+max_join_size
+rows (for single\-table statements) or row combinations (for multiple\-table statements) or that are likely to do more than
+max_join_size
+disk seeks. By setting this value, you can catch
+SELECT
+statements where keys are not used properly and that would probably take a long time. Set it if your users tend to perform joins that lack a
+WHERE
+clause, that take a long time, or that return millions of rows.
+.sp
+Setting this variable to a value other than
+DEFAULT
+resets the value of
+SQL_BIG_SELECTS
+to
+0. If you set the
+SQL_BIG_SELECTS
+value again, the
+max_join_size
+variable is ignored.
+.sp
+If a query result is in the query cache, no result size check is performed, because the result has previously been computed and it does not burden the server to send it to the client.
+.sp
+This variable previously was named
+sql_max_join_size.
+.TP 3n
+\(bu
+max_length_for_sort_data
+.sp
+The cutoff on the size of index values that determines which
+filesort
+algorithm to use. See
+Section\ 2.11, \(lqORDER BY Optimization\(rq.
+.TP 3n
+\(bu
+max_prepared_stmt_count
+.sp
+This variable limits the total number of prepared statements in the server. It can be used in environments where there is the potential for denial\-of\-service attacks based on running the server out of memory by preparing huge numbers of statements. The default value is 16,382. The allowable range of values is from 0 to 1 million. If the value is set lower than the current number of prepared statements, existing statements are not affected and can be used, but no new statements can be prepared until the current number drops below the limit. This variable was added in MySQL 5.0.21.
+.TP 3n
+\(bu
+max_relay_log_size
+.sp
+If a write by a replication slave to its relay log causes 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
+max_relay_log_size
+is 0, the server uses
+max_binlog_size
+for both the binary log and the relay log. If
+max_relay_log_size
+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
+max_relay_log_size
+to between 4096 bytes and 1GB (inclusive), or to 0. The default value is 0. See
+Section\ 4.1, \(lqReplication Implementation Details\(rq.
+.TP 3n
+\(bu
+max_seeks_for_key
+.sp
+Limit the assumed maximum number of seeks when looking up rows based on a key. The MySQL optimizer assumes that no more than this number of key seeks are required when searching for matching rows in a table by scanning an index, regardless of the actual cardinality of the index (see
+Section\ 5.4.13, \(lqSHOW INDEX Syntax\(rq). By setting this to a low value (say, 100), you can force MySQL to prefer indexes instead of table scans.
+.TP 3n
+\(bu
+max_sort_length
+.sp
+The number of bytes to use when sorting
+BLOB
+or
+TEXT
+values. Only the first
+max_sort_length
+bytes of each value are used; the rest are ignored.
+.TP 3n
+\(bu
+max_sp_recursion_depth
+.sp
+The number of times that a stored procedure may call itself. The default value for this option is 0, which completely disallows recursion in stored procedures. The maximum value is 255.
+.sp
+This variable can be set globally and per session.
+.TP 3n
+\(bu
+max_tmp_tables
+.sp
+The maximum number of temporary tables a client can keep open at the same time. (This option does not yet do anything.)
+.TP 3n
+\(bu
+max_user_connections
+.sp
+The maximum number of simultaneous connections allowed to any given MySQL account. A value of 0 means
+\(lqno limit.\(rq
+.sp
+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
+MAX_USER_CONNECTIONS
+resource limit. In that case, the session value reflects the account limit.
+.TP 3n
+\(bu
+max_write_lock_count
+.sp
+After this many write locks, allow some pending read lock requests to be processed in between.
+.TP 3n
+\(bu
+multi_range_count
+.sp
+The maximum number of ranges to send to a table handler at once during range selects. The default value is 256. Sending multiple ranges to a handler at once can improve the performance of certain selects dramatically. This especially true for the NDB Cluster table handler, which needs to send the range requests to all nodes. Sending a batch of those requests at once reduces the communication costs significantly. This variable was added in MySQL 5.0.3.
+.TP 3n
+\(bu
+myisam_block_size
+.sp
+The block size to be used for
+MyISAM
+index pages.
+.TP 3n
+\(bu
+myisam_data_pointer_size
+.sp
+The default pointer size in bytes, to be used by
+CREATE TABLE
+for
+MyISAM
+tables when no
+MAX_ROWS
+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
+Section\ 1.2.12, \(lqThe table is full\(rq.
+.TP 3n
+\(bu
+myisam_max_extra_sort_file_size
+(\fIDEPRECATED\fR)
+.sp
+If the temporary file used for fast
+MyISAM
+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.
+.sp
+.it 1 an-trap
+.nr an-no-space-flag 1
+.nr an-break-flag 1
+.br
+\fBNote\fR
+This variable was removed in MySQL 5.0.6.
+.TP 3n
+\(bu
+myisam_max_sort_file_size
+.sp
+The maximum size of the temporary file that MySQL is allowed to use while re\-creating a
+MyISAM
+index (during
+REPAIR TABLE,
+ALTER TABLE, or
+LOAD DATA INFILE). If the file size would be larger than this value, the index is created using the key cache instead, which is slower. The value is given in bytes.
+.sp
+The default value is 2GB. If
+MyISAM
+index files exceed this size and disk space is available, increasing the value may help performance.
+.TP 3n
+\(bu
+myisam_recover_options
+.sp
+The value of the
+\fB\-\-myisam\-recover\fR
+option. See
+the section called \(lqCOMMAND OPTIONS\(rq.
+.TP 3n
+\(bu
+myisam_repair_threads
+.sp
+If this value is greater than 1,
+MyISAM
+table indexes are created in parallel (each index in its own thread) during the
+Repair by sorting
+process. The default value is 1.
+.sp
+.it 1 an-trap
+.nr an-no-space-flag 1
+.nr an-break-flag 1
+.br
+\fBNote\fR
+Multi\-threaded repair is still
+\fIbeta\-quality\fR
+code.
+.TP 3n
+\(bu
+myisam_sort_buffer_size
+.sp
+The size of the buffer that is allocated when sorting
+MyISAM
+indexes during a
+REPAIR TABLE
+or when creating indexes with
+CREATE INDEX
+or
+ALTER TABLE.
+.sp
+The maximum allowable setting for
+myisam_sort_buffer_size
+is 4GB.
+.TP 3n
+\(bu
+myisam_stats_method
+.sp
+How the server treats
+NULL
+values when collecting statistics about the distribution of index values for
+MyISAM
+tables. This variable has two possible values,
+nulls_equal
+and
+nulls_unequal. For
+nulls_equal, all
+NULL
+index values are considered equal and form a single value group that has a size equal to the number of
+NULL
+values. For
+nulls_unequal,
+NULL
+values are considered unequal, and each
+NULL
+forms a distinct value group of size 1.
+.sp
+The method that is used for generating table statistics influences how the optimizer chooses indexes for query execution, as described in
+Section\ 4.7, \(lqMyISAM Index Statistics Collection\(rq.
+.sp
+This variable was added in MySQL 5.0.14. For older versions, the statistics collection method is equivalent to
+nulls_equal.
+.TP 3n
+\(bu
+multi_read_range
+.sp
+Specifies the maximum number of ranges to send to a storage engine during range selects. The default value is 256. Sending multiple ranges to an engine is a feature that can improve the performance of certain selects dramatically, particularly for
+NDBCLUSTER. 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.
+.TP 3n
+\(bu
+named_pipe
+.sp
+(Windows only.) Indicates whether the server supports connections over named pipes.
+.TP 3n
+\(bu
+ndb_autoincrement_prefetch_sz
+.sp
+Determines the probability of gaps in an autoincremented column. Set to
+1
+to minimize this. Set to a high value for optimization \(em makes inserts faster, but decreases the likelihood that consecutive autoincrement numbers will be used in a batch of inserts. Default value:
+32. Mimimum value:
+1.
+.TP 3n
+\(bu
+ndb_cache_check_time
+.sp
+The number of milliseconds to wait before checking the
+NDB
+query cache. Setting this to
+0
+(the default and minimum value) means that the
+NDB
+query cache will be checked for validation on every query.
+.sp
+The recommended maximum value for this variable is
+1000, which means that the query cache is checked once per second. A larger value means the
+NDB
+query cache is less often checked and invalidated due to updates on a different
+\fBmysqld\fR. It is generally not desirable to set this to a value greater than
+2000.
+.TP 3n
+\(bu
+ndb_force_send
+.sp
+Forces sending of buffers to
+NDB
+immediately, without waiting for other threads. Defaults to
+ON.
+.TP 3n
+\(bu
+ndb_index_stat_cache_entries
+.sp
+Sets the granularity of the statistics by determining the number of starting and ending keys to store in the statistics memory cache. Zero means no caching takes place; in this case, the data nodes are always queried directly. Default value:
+32.
+.TP 3n
+\(bu
+ndb_index_stat_enable
+.sp
+Use
+NDB
+index statistics in query optimization. Defaults to
+ON.
+.TP 3n
+\(bu
+ndb_index_stat_update_freq
+.sp
+How often to query data nodes instead of the statistics cache. For example, a value of
+20
+(the default) means to direct every 20th
+query to the data nodes.
+.TP 3n
+\(bu
+ndb_optimized_node_selection
+.sp
+Causes an SQL node to use a data node on the same host machine as transaction coordinator. Enabled by default. Set to
+0
+or
+OFF
+to disable, in which case the SQL node uses each data node in the cluster in succession. When this option is disabled, or if there is no data node process running on the same host as the SQL node, the SQL node attempts to use a given data node 8 times before proceeding to the next one.
+.TP 3n
+\(bu
+ndb_report_thresh_binlog_epoch_slip
+.sp
+This is a threshold on the number of epochs to be behind before reporting binlog status. For example, a value of
+3
+(the default) means that if the difference between which epoch has been received from the storage nodes and which epoch has been applied to the binlog is 3 or more, a status message will be sent to the cluster log.
+.TP 3n
+\(bu
+ndb_report_thresh_binlog_mem_usage
+.sp
+This is a threshold on the percentage of free memory remaining before reporting binlog status. For example, a value of
+10
+(the default) means that if the amount of available memory for receiving binlog data from the data nodes falls below 10%, a status message will be sent to the cluster log.
+.TP 3n
+\(bu
+ndb_use_exact_count
+.sp
+Forces
+NDB
+to use a count of records during
+SELECT COUNT(*)
+query planning to speed up this type of query. The default value is
+ON. For faster queries overall, disable this feature by setting the value of
+ndb_use_exact_count
+to
+OFF.
+.TP 3n
+\(bu
+ndb_use_transactions
+.sp
+You can disable
+NDB
+transaction support by setting this variable's values to
+OFF
+(not recommended). The default is
+ON.
+.TP 3n
+\(bu
+net_buffer_length
+.sp
+Each client thread is associated with a connection buffer and result buffer. Both begin with a size given by
+net_buffer_length
+but are dynamically enlarged up to
+max_allowed_packet
+bytes as needed. The result buffer shrinks to
+net_buffer_length
+after each SQL statement.
+.sp
+This variable should not normally be changed, but if you have very little memory, you can set it to the expected length of statements sent by clients. If statements exceed this length, the connection buffer is automatically enlarged. The maximum value to which
+net_buffer_length
+can be set is 1MB.
+.TP 3n
+\(bu
+net_read_timeout
+.sp
+The number of seconds to wait for more data from a connection before aborting the read. This timeout applies only to TCP/IP connections, not to connections made via Unix socket files, named pipes, or shared memory. When the server is reading from the client,
+net_read_timeout
+is the timeout value controlling when to abort. When the server is writing to the client,
+net_write_timeout
+is the timeout value controlling when to abort. See also
+slave_net_timeout.
+.TP 3n
+\(bu
+net_retry_count
+.sp
+If a read on a communication port is interrupted, retry this many times before giving up. This value should be set quite high on FreeBSD because internal interrupts are sent to all threads.
+.TP 3n
+\(bu
+net_write_timeout
+.sp
+The number of seconds to wait for a block to be written to a connection before aborting the write. This timeout applies only to TCP/IP connections, not to connections made via Unix socket files, named pipes, or shared memory. See also
+net_read_timeout.
+.TP 3n
+\(bu
+new
+.sp
+This variable was used in MySQL 4.0 to turn on some 4.1 behaviors, and is retained for backward compatibility. In MySQL 5.0, its value is always
+OFF.
+.TP 3n
+\(bu
+old_passwords
+.sp
+Whether the server should use pre\-4.1\-style passwords for MySQL user accounts. See
+Section\ 1.2.4, \(lqClient does not support authentication protocol\(rq.
+.TP 3n
+\(bu
+one_shot
+.sp
+This is not a variable, but it can be used when setting some variables. It is described in
+Section\ 5.3, \(lqSET Syntax\(rq.
+.TP 3n
+\(bu
+open_files_limit
+.sp
+The number of files that the operating system allows
+\fBmysqld\fR
+to open. This is the real value allowed by the system and might be different from the value you gave using the
+\fB\-\-open\-files\-limit\fR
+option to
+\fBmysqld\fR
+or
+\fBmysqld_safe\fR. The value is 0 on systems where MySQL can't change the number of open files.
+.TP 3n
+\(bu
+optimizer_prune_level
+.sp
+Controls the heuristics applied during query optimization to prune less\-promising partial plans from the optimizer 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.
+.TP 3n
+\(bu
+optimizer_search_depth
+.sp
+The maximum depth of search performed by the query optimizer. Values larger than the number of relations in a query result in better query plans, but take longer to generate an execution plan for a query. Values smaller than the number of relations in a query return an execution plan quicker, but the resulting plan may be far from being optimal. If set to 0, the system automatically 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.
+.TP 3n
+\(bu
+pid_file
+.sp
+The pathname of the process ID (PID) file. This variable can be set with the
+\fB\-\-pid\-file\fR
+option.
+.TP 3n
+\(bu
+port
+.sp
+The number of the port on which the server listens for TCP/IP connections. This variable can be set with the
+\fB\-\-port\fR
+option.
+.TP 3n
+\(bu
+preload_buffer_size
+.sp
+The size of the buffer that is allocated when preloading indexes.
+.TP 3n
+\(bu
+prepared_stmt_count
+.sp
+The current number of prepared statements. (The maximum number of statements is given by the
+max_prepared_stmt_count
+system variable.) This variable was added in MySQL 5.0.21. In MySQL 5.0.32, it was converted to the global
+Prepared_stmt_count
+status variable.
+.TP 3n
+\(bu
+protocol_version
+.sp
+The version of the client/server protocol used by the MySQL server.
+.TP 3n
+\(bu
+query_alloc_block_size
+.sp
+The allocation size of memory blocks that are allocated for objects created during statement parsing and execution. If you have problems with memory fragmentation, it might help to increase this a bit.
+.TP 3n
+\(bu
+query_cache_limit
+.sp
+Don't cache results that are larger than this number of bytes. The default value is 1MB.
+.TP 3n
+\(bu
+query_cache_min_res_unit
+.sp
+The minimum size (in bytes) for blocks allocated by the query cache. The default value is 4096 (4KB). Tuning information for this variable is given in
+Section\ 5.4.3, \(lqQuery Cache Configuration\(rq.
+.TP 3n
+\(bu
+query_cache_size
+.sp
+The amount of memory allocated for caching query results. The default value is 0, which disables the query cache. The allowable values are multiples of 1024; other values are rounded down to the nearest multiple. Note that
+query_cache_size
+bytes of memory are allocated even if
+query_cache_type
+is set to 0. See
+Section\ 5.4.3, \(lqQuery Cache Configuration\(rq, for more information.
+.TP 3n
+\(bu
+query_cache_type
+.sp
+Set the query cache type. Setting the
+GLOBAL
+value sets the type for all clients that connect thereafter. Individual clients can set the
+SESSION
+value to affect their own use of the query cache. Possible values are shown in the following table:
+.TS
+allbox tab(:);
+l l
+l l
+l l
+l l.
+T{
+\fBOption\fR
+T}:T{
+\fBDescription\fR
+T}
+T{
+0 or OFF
+T}:T{
+Don't cache results in or retrieve results from the query cache. Note
+ that this does not deallocate the query cache
+ buffer. To do that, you should set
+ query_cache_size to 0.
+T}
+T{
+1 or ON
+T}:T{
+Cache all query results except for those that begin with SELECT
+ SQL_NO_CACHE.
+T}
+T{
+2 or DEMAND
+T}:T{
+Cache results only for queries that begin with SELECT
+ SQL_CACHE.
+T}
+.TE
+.sp
+This variable defaults to
+ON.
+.TP 3n
+\(bu
+query_cache_wlock_invalidate
+.sp
+Normally, when one client acquires a
+WRITE
+lock on a
+MyISAM
+table, other clients are not blocked from issuing statements that read from the table if the query results are present in the query cache. Setting this variable to 1 causes acquisition of a
+WRITE
+lock for a table to invalidate any queries in the query cache that refer to the table. This forces other clients that attempt to access the table to wait while the lock is in effect.
+.TP 3n
+\(bu
+query_prealloc_size
+.sp
+The size of the persistent buffer used for statement parsing and execution. This buffer is not freed between statements. If you are running complex queries, a larger
+query_prealloc_size
+value might be helpful in improving performance, because it can reduce the need for the server to perform memory allocation during query execution operations.
+.sp
+.TP 3n
+\(bu
+range_alloc_block_size
+.sp
+The size of blocks that are allocated when doing range optimization.
+.TP 3n
+\(bu
+read_buffer_size
+.sp
+Each thread that does a sequential scan allocates a buffer of this size (in bytes) for each table it scans. If you do many sequential scans, you might want to increase this value, which defaults to 131072.
+.sp
+The maximum allowable setting for
+read_buffer_size
+is 2GB.
+.sp
+read_buffer_size
+and
+read_rnd_buffer_size
+are not specific to any storage engine and apply in a general manner for optimization. See
+Section\ 5.7, \(lqHow MySQL Uses Memory\(rq, for example.
+.TP 3n
+\(bu
+read_only
+.sp
+When this variable is set to
+ON, the server allows no updates except from users that have the
+SUPER
+privilege or (on a slave server) from updates performed by slave threads. On a slave server, this can be useful to ensure that the slave accepts updates only from its master server and not from clients. As of MySQL 5.0.16, this variable does not apply to
+TEMPORARY
+tables.
+.sp
+read_only
+exists only as a
+GLOBAL
+variable, so changes to its value require the
+SUPER
+privilege. Changes to
+read_only
+on a master server are not replicated to slave servers. The value can be set on a slave server independent of the setting on the master.
+.TP 3n
+\(bu
+read_rnd_buffer_size
+.sp
+When reading rows in sorted order following a key\-sorting operation, the rows are read through this buffer to avoid disk seeks. See
+Section\ 2.11, \(lqORDER BY Optimization\(rq. Setting the variable to a large value can improve
+ORDER BY
+performance by a lot. However, this is a buffer allocated for each client, so you should not set the global variable to a large value. Instead, change the session variable only from within those clients that need to run large queries.
+.sp
+The maximum allowable setting for
+read_rnd_buffer_size
+is 2GB.
+.sp
+read_buffer_size
+and
+read_rnd_buffer_size
+are not specific to any storage engine and apply in a general manner for optimization. See
+Section\ 5.7, \(lqHow MySQL Uses Memory\(rq, for example.
+.TP 3n
+\(bu
+relay_log_purge
+.sp
+Disables or enables automatic purging of relay log files as soon as they are not needed any more. The default value is 1 (ON).
+.TP 3n
+\(bu
+rpl_recovery_rank
+.sp
+This variable is unused.
+.TP 3n
+\(bu
+secure_auth
+.sp
+If the MySQL server has been started with the
+\fB\-\-secure\-auth\fR
+option, it blocks connections from all accounts that have passwords stored in the old (pre\-4.1) format. In that case, the value of this variable is
+ON, otherwise it is
+OFF.
+.sp
+You should enable this option if you want to prevent all use of passwords employing the old format (and hence insecure communication over the network).
+.sp
+Server startup fails with an error if this option is enabled and the privilege tables are in pre\-4.1 format. See
+Section\ 1.2.4, \(lqClient does not support authentication protocol\(rq.
+.TP 3n
+\(bu
+secure_file_priv
+.sp
+By default, this variable is empty. If set to the name of a directory, it limits the effect of the
+LOAD_FILE()
+function and the
+LOAD DATA
+and
+SELECT ... INTO OUTFILE
+statements to work only with files in that directory.
+.sp
+This variable was added in MySQL 5.0.38.
+.TP 3n
+\(bu
+server_id
+.sp
+The server ID. This value is set by the
+\fB\-\-server\-id\fR
+option. It is used for replication to enable master and slave servers to identify themselves uniquely.
+.TP 3n
+\(bu
+shared_memory
+.sp
+(Windows only.) Whether the server allows shared\-memory connections.
+.TP 3n
+\(bu
+shared_memory_base_name
+.sp
+(Windows only.) The name of shared memory to use for shared\-memory connections. This is useful when running multiple MySQL instances on a single physical machine. The default name is
+MYSQL. The name is case sensitive.
+.TP 3n
+\(bu
+skip_external_locking
+.sp
+This is
+OFF
+if
+\fBmysqld\fR
+uses external locking,
+ON
+if external locking is disabled.
+.TP 3n
+\(bu
+skip_networking
+.sp
+This is
+ON
+if the server allows only local (non\-TCP/IP) connections. On Unix, local connections use a Unix socket file. On Windows, local connections use a named pipe or shared memory. On NetWare, only TCP/IP connections are supported, so do not set this variable to
+ON. This variable can be set to
+ON
+with the
+\fB\-\-skip\-networking\fR
+option.
+.TP 3n
+\(bu
+skip_show_database
+.sp
+This prevents people from using the
+SHOW DATABASES
+statement if they do not have the
+SHOW DATABASES
+privilege. This can improve security if you have concerns about users being able to see databases belonging to other users. Its effect depends on the
+SHOW DATABASES
+privilege: If the variable value is
+ON, the
+SHOW DATABASES
+statement is allowed only to users who have the
+SHOW DATABASES
+privilege, and the statement displays all database names. If the value is
+OFF,
+SHOW DATABASES
+is allowed to all users, but displays the names of only those databases for which the user has the
+SHOW DATABASES
+or other privilege.
+.TP 3n
+\(bu
+slave_compressed_protocol
+.sp
+Whether to use compression of the slave/master protocol if both the slave and the master support it.
+.TP 3n
+\(bu
+slave_load_tmpdir
+.sp
+The name of the directory where the slave creates temporary files for replicating
+LOAD DATA INFILE
+statements.
+.TP 3n
+\(bu
+slave_net_timeout
+.sp
+The number of seconds to wait for more data from a master/slave connection before aborting the read. This timeout applies only to TCP/IP connections, not to connections made via Unix socket files, named pipes, or shared memory.
+.TP 3n
+\(bu
+slave_skip_errors
+.sp
+Normally, replication stops when an error occurs on the slave. This gives you the opportunity to resolve the inconsistency in the data manually. This variable tells the slave SQL thread to continue replication when a statement returns any of the errors listed in the variable value.
+.TP 3n
+\(bu
+slave_transaction_retries
+.sp
+If a replication slave SQL thread fails to execute a transaction because of an
+InnoDB
+deadlock or exceeded
+InnoDB's
+innodb_lock_wait_timeout
+or NDBCluster's
+TransactionDeadlockDetectionTimeout
+or
+TransactionInactiveTimeout, it automatically retries
+slave_transaction_retries
+times before stopping with an error. The default priot to MySQL 4.0.3 is 0. You must explicitly set the value greater than 0 to enable the
+\(lqretry\(rq
+behavior, which is probably a good idea. In MySQL 5.0.3 or newer, the default is 10.
+.TP 3n
+\(bu
+slow_launch_time
+.sp
+If creating a thread takes longer than this many seconds, the server increments the
+Slow_launch_threads
+status variable.
+.TP 3n
+\(bu
+socket
+.sp
+On Unix platforms, this variable is the name of the socket file that is used for local client connections. The default is
+\fI/tmp/mysql.sock\fR. (For some distribution formats, the directory might be different, such as
+\fI/var/lib/mysql\fR
+for RPMs.)
+.sp
+On Windows, this variable is the name of the named pipe that is used for local client connections. The default value is
+MySQL
+(not case sensitive).
+.TP 3n
+\(bu
+sort_buffer_size
+.sp
+Each thread that needs to do a sort allocates a buffer of this size. Increase this value for faster
+ORDER BY
+or
+GROUP BY
+operations. See
+Section\ 1.4.4, \(lqWhere MySQL Stores Temporary Files\(rq.
+.sp
+The maximum allowable setting for
+sort_buffer_size
+is 4GB.
+.TP 3n
+\(bu
+sql_mode
+.sp
+The current server SQL mode, which can be set dynamically. See
+the section called \(lqSQL MODES\(rq.
+.TP 3n
+\(bu
+sql_slave_skip_counter
+.sp
+The number of events from the master that a slave server should skip. See
+Section\ 6.2.6, \(lqSET GLOBAL SQL_SLAVE_SKIP_COUNTER Syntax\(rq.
+.TP 3n
+\(bu
+ssl_ca
+.sp
+The path to a file with a list of trusted SSL CAs. This variable was added in MySQL 5.0.23.
+.TP 3n
+\(bu
+ssl_capath
+.sp
+The path to a directory that contains trusted SSL CA certificates in PEM format. This variable was added in MySQL 5.0.23.
+.TP 3n
+\(bu
+ssl_cert
+.sp
+The name of the SSL certificate file to use for establishing a secure connection. This variable was added in MySQL 5.0.23.
+.TP 3n
+\(bu
+ssl_cipher
+.sp
+A list of allowable ciphers to use for SSL encryption. The cipher list has the same format as the
+openssl ciphers
+command. This variable was added in MySQL 5.0.23.
+.TP 3n
+\(bu
+ssl_key
+.sp
+The name of the SSL key file to use for establishing a secure connection. This variable was added in MySQL 5.0.23.
+.TP 3n
+\(bu
+storage_engine
+.sp
+The default storage engine (table type). To set the storage engine at server startup, use the
+\fB\-\-default\-storage\-engine\fR
+option. See
+the section called \(lqCOMMAND OPTIONS\(rq.
+.TP 3n
+\(bu
+sync_binlog
+.sp
+If the value of this variable is positive, the MySQL server synchronizes its binary log to disk (using
+fdatasync()) after every
+sync_binlog
+writes to the binary log. Note that there is one write to the binary log per statement if autocommit is enabled, and one write per transaction otherwise. The default value is 0, which does no synchronizing to disk. A value of 1 is the safest choice, because in the event of a crash you lose at most one statement or transaction from the binary log. However, it is also the slowest choice (unless the disk has a battery\-backed cache, which makes synchronization very fast).
+.sp
+If the value of
+sync_binlog
+is 0 (the default), no extra flushing is done. The server relies on the operating system to flush the file contents occasionaly as for any other file.
+.TP 3n
+\(bu
+sync_frm
+.sp
+If this variable is set to 1, when any non\-temporary table is created its
+\fI.frm\fR
+file is synchronized to disk (using
+fdatasync()). This is slower but safer in case of a crash. The default is 1.
+.TP 3n
+\(bu
+system_time_zone
+.sp
+The server system time zone. When the server begins executing, it inherits a time zone setting from the machine defaults, possibly modified by the environment of the account used for running the server or the startup script. The value is used to set
+system_time_zone. Typically the time zone is specified by the
+TZ
+environment variable. It also can be specified using the
+\fB\-\-timezone\fR
+option of the
+\fBmysqld_safe\fR
+script.
+.sp
+The
+system_time_zone
+variable differs from
+time_zone. Although they might have the same value, the latter variable is used to initialize the time zone for each client that connects. See
+Section\ 9, \(lqMySQL Server Time Zone Support\(rq.
+.TP 3n
+\(bu
+table_cache
+.sp
+The number of open tables for all threads. Increasing this value increases the number of file descriptors that
+\fBmysqld\fR
+requires. You can check whether you need to increase the table cache by checking the
+Opened_tables
+status variable. See
+the section called \(lqSTATUS VARIABLES\(rq. If the value of
+Opened_tables
+is large and you don't do
+FLUSH TABLES
+often (which just forces all tables to be closed and reopened), then you should increase the value of the
+table_cache
+variable. For more information about the table cache, see
+Section\ 4.8, \(lqHow MySQL Opens and Closes Tables\(rq.
+.TP 3n
+\(bu
+table_lock_wait_timeout
+.sp
+Specifies a wait timeout for table\-level locks, in seconds. The default timeout is 50 seconds. The timeout is active only if the connection has open cursors. This variable can also be set globally at runtime (you need the
+SUPER
+privilege to do this). It's available as of MySQL 5.0.10.
+.TP 3n
+\(bu
+table_type
+.sp
+This variable is a synonym for
+storage_engine. In MySQL 5.0,
+storage_engine
+is the preferred name.
+.TP 3n
+\(bu
+thread_cache_size
+.sp
+How many threads the server should cache for reuse. When a client disconnects, the client's threads are put in the cache if there are fewer than
+thread_cache_size
+threads there. Requests for threads are satisfied by reusing threads taken from the cache if possible, and only when the cache is empty is a new thread created. This variable can be increased to improve performance if you have a lot of new connections. (Normally, this doesn't provide a notable performance improvement if you have a good thread implementation.) By examining the difference between the
+Connections
+and
+Threads_created
+status variables, you can see how efficient the thread cache is. For details, see
+the section called \(lqSTATUS VARIABLES\(rq.
+.TP 3n
+\(bu
+thread_concurrency
+.sp
+On Solaris,
+\fBmysqld\fR
+calls
+thr_setconcurrency()
+with this value. This function enables applications to give the threads system a hint about the desired number of threads that should be run at the same time.
+.TP 3n
+\(bu
+thread_stack
+.sp
+The stack size for each thread. Many of the limits detected by the
+crash\-me
+test are dependent on this value. The default is large enough for normal operation. See
+Section\ 1.4, \(lqThe MySQL Benchmark Suite\(rq. The default is 192KB.
+.TP 3n
+\(bu
+time_format
+.sp
+This variable is not implemented.
+.TP 3n
+\(bu
+time_zone
+.sp
+The current time zone. This variable is used to initialize the time zone for each client that connects. By default, the initial value of this is
+\'SYSTEM'
+(which means,
+\(lquse the value of system_time_zone\(rq). The value can be specified explicitly at server startup with the
+\fB\-\-default\-time\-zone\fR
+option. See
+Section\ 9, \(lqMySQL Server Time Zone Support\(rq.
+.TP 3n
+\(bu
+timed_mutexes
+.sp
+This variable controls whether
+InnoDB
+mutexes are timed. If this variable is set to 0 or
+OFF
+(the default), mutex timing is disabled. If the variable is set to 1 or
+ON, mutex timing is enabled. With timing enabled, the
+os_wait_times
+value in the output from
+SHOW ENGINE INNODB MUTEX
+indicates the amount of time (in ms) spent in operating system waits. Otherwise, the value is 0. This variable was added in MySQL 5.0.3.
+.TP 3n
+\(bu
+tmp_table_size
+.sp
+The maximum size of internal in\-memory temporary tables. (The actual limit is determined as the smaller of
+max_heap_table_size
+and
+tmp_table_size.) If an in\-memory temporary table exceeds the limit, MySQL automatically converts it to an on\-disk
+MyISAM
+table. Increase the value of
+tmp_table_size
+(and
+max_heap_table_size
+if necessary) if you do many advanced
+GROUP BY
+queries and you have lots of memory. This variable does not apply to user\-created
+MEMORY
+tables.
+.TP 3n
+\(bu
+tmpdir
+.sp
+The directory used for temporary files and temporary tables. This variable can be set to a list of several paths that are used in round\-robin fashion. Paths should be separated by colon characters (\(lq:\(rq) on Unix and semicolon characters (\(lq;\(rq) on Windows, NetWare, and OS/2.
+.sp
+The multiple\-directory feature can be used to spread the load between several physical disks. If the MySQL server is acting as a replication slave, you should not set
+tmpdir
+to point to a directory on a memory\-based filesystem or to a directory that is cleared when the server host restarts. A replication slave needs some of its temporary files to survive a machine restart so that it can replicate temporary tables or
+LOAD DATA INFILE
+operations. If files in the temporary file directory are lost when the server restarts, replication fails. However, if you are using MySQL 4.0.0 or later, you can set the slave's temporary directory using the
+slave_load_tmpdir
+variable. In that case, the slave won't use the general
+tmpdir
+value and you can set
+tmpdir
+to a non\-permanent location.
+.TP 3n
+\(bu
+transaction_alloc_block_size
+.sp
+The amount in bytes by which to increase a per\-transaction memory pool which needs memory. See the description of
+transaction_prealloc_size.
+.TP 3n
+\(bu
+transaction_prealloc_size
+.sp
+There is a per\-transaction memory pool from which various transaction\-related allocations take memory. The initial size of the pool in bytes is
+transaction_prealloc_size. For every allocation that cannot be satisfied from the pool because it has insufficient memory available, the pool is increased by
+transaction_alloc_block_size
+bytes. When the transaction ends, the pool is truncated to
+transaction_prealloc_size
+bytes.
+.sp
+By making
+transaction_prealloc_size
+sufficiently large to contain all statements within a single transaction, you can avoid many
+malloc()
+calls.
+.TP 3n
+\(bu
+tx_isolation
+.sp
+The default transaction isolation level. Defaults to
+REPEATABLE\-READ.
+.sp
+This variable is set by the
+SET TRANSACTION ISOLATION LEVEL
+statement. See
+Section\ 4.6, \(lqSET TRANSACTION Syntax\(rq. If you set
+tx_isolation
+directly to an isolation level name that contains a space, the name should be enclosed within quotes, with the space replaced by a dash. For example:
+.sp
+.RS 3n
+.nf
+SET tx_isolation = 'READ\-COMMITTED';
+.fi
+.RE
+.TP 3n
+\(bu
+updatable_views_with_limit
+.sp
+This variable controls whether updates to a view can be made when the view does not contain all columns of the primary key defined in the underlying table, if the update statement contains a
+LIMIT
+clause. (Such updates often are generated by GUI tools.) An update is an
+UPDATE
+or
+DELETE
+statement. Primary key here means a
+PRIMARY KEY, or a
+UNIQUE
+index in which no column can contain
+NULL.
+.sp
+The variable can have two values:
+.RS 3n
+.TP 3n
+\(bu
+1
+or
+YES: Issue a warning only (not an error message). This is the default value.
+.TP 3n
+\(bu
+0
+or
+NO: Prohibit the update.
+.RE
+.IP "" 3n
+This variable was added in MySQL 5.0.2.
+.TP 3n
+\(bu
+version
+.sp
+The version number for the server.
+.sp
+Starting with MySQL 5.0.24, the version number will also indicate whether the server is a standard release (Community) or Enterprise release (for example,
+5.0.28\-enterprise\-gpl\-nt).
+.TP 3n
+\(bu
+version_bdb
+.sp
+The
+BDB
+storage engine version.
+.TP 3n
+\(bu
+version_comment
+.sp
+The
+\fBconfigure\fR
+script has a
+\fB\-\-with\-comment\fR
+option that allows a comment to be specified when building MySQL. This variable contains the value of that comment.
+.sp
+For precompiled binaries, this variable will hold the server version and license information. Starting with MySQL 5.0.24,
+version_comment
+will include the full server type and license. For community users this will appear as
+MySQL Community Edition \- Standard (GPL). For Enterprise users, the version might be displayed as
+MySQL Enterprise Server (GPL). The corresponding license for your MySQL binary is shown in parentheses. For server compiled from source, the default value will be the same as that for Community releases.
+.TP 3n
+\(bu
+version_compile_machine
+.sp
+The type of machine or architecture on which MySQL was built.
+.TP 3n
+\(bu
+version_compile_os
+.sp
+The type of operating system on which MySQL was built.
+.TP 3n
+\(bu
+wait_timeout
+.sp
+The number of seconds the server waits for activity on a non\-interactive connection before closing it. This timeout applies only to TCP/IP and Unix socket file connections, not to connections made via named pipes, or shared memory.
+.sp
+On thread startup, the session
+wait_timeout
+value is initialized from the global
+wait_timeout
+value or from the global
+interactive_timeout
+value, depending on the type of client (as defined by the
+CLIENT_INTERACTIVE
+connect option to
+\fBmysql_real_connect()\fR). See also
+interactive_timeout.
+.SH "USING SYSTEM VARIABLES"
+.PP
+The MySQL server maintains many system variables that indicate how it is configured.
+the section called \(lqSYSTEM VARIABLES\(rq, describes the meaning of these variables. Each system variable has a default value. System variables can be set at server startup using options on the command line or in an option file. Most of them can be changed dynamically while the server is running by means of the
+SET
+statement, which enables you to modify operation of the server without having to stop and restart it. You can refer to system variable values in expressions.
+.PP
+The server maintains two kinds of system variables. Global variables affect the overall operation of the server. Session variables affect its operation for individual client connections. A given system variable can have both a global and a session value. Global and session system variables are related as follows:
+.TP 3n
+\(bu
+When the server starts, it initializes all global variables to their default values. These defaults can be changed by options specified on the command line or in an option file. (See
+Section\ 3, \(lqSpecifying Program Options\(rq.)
+.TP 3n
+\(bu
+The server also maintains a set of session variables for each client that connects. The client's session variables are initialized at connect time using the current values of the corresponding global variables. For example, the client's SQL mode is controlled by the session
+sql_mode
+value, which is initialized when the client connects to the value of the global
+sql_mode
+value.
+.sp
+.RE
+.PP
+System variable values can be set globally at server startup by using options on the command line or in an option file. When you use a startup option to set a variable that takes a numeric value, the value can be given with a suffix of
+K,
+M, or
+G
+(either uppercase or lowercase) to indicate a multiplier of 1024, 10242
+or 10243; that is, units of kilobytes, megabytes, or gigabytes, respectively. Thus, the following command starts the server with a query cache size of 16 megabytes and a maximum packet size of one gigabyte:
+.sp
+.RS 3n
+.nf
+mysqld \-\-query_cache_size=16M \-\-max_allowed_packet=1G
+.fi
+.RE
+.PP
+Within an option file, those variables are set like this:
+.sp
+.RS 3n
+.nf
+[mysqld]
+query_cache_size=16M
+max_allowed_packet=1G
+.fi
+.RE
+.PP
+The lettercase of suffix letters does not matter;
+16M
+and
+16m
+are equivalent, as are
+1G
+and
+1g.
+.PP
+If you want to restrict the maximum value to which a system variable can be set at runtime with the
+SET
+statement, you can specify this maximum by using an option of the form
+\fB\-\-maximum\-\fR\fB\fIvar_name\fR\fR\fB=\fR\fB\fIvalue\fR\fR
+at server startup. For example, to prevent the value of
+query_cache_size
+from being increased to more than 32MB at runtime, use the option
+\fB\-\-maximum\-query_cache_size=32M\fR.
+.PP
+Many system variables are dynamic and can be changed while the server runs by using the
+SET
+statement. For a list, see
+the section called \(lqDynamic System Variables\(rq. To change a system variable with
+SET, refer to it as
+\fIvar_name\fR, optionally preceded by a modifier:
+.TP 3n
+\(bu
+To indicate explicitly that a variable is a global variable, precede its name by
+GLOBAL
+or
+@@global.. The
+SUPER
+privilege is required to set global variables.
+.TP 3n
+\(bu
+To indicate explicitly that a variable is a session variable, precede its name by
+SESSION,
+@@session., or
+@@. Setting a session variable requires no special privilege, but a client can change only its own session variables, not those of any other client.
+.TP 3n
+\(bu
+LOCAL
+and
+@@local.
+are synonyms for
+SESSION
+and
+@@session..
+.TP 3n
+\(bu
+If no modifier is present,
+SET
+changes the session variable.
+.sp
+.RE
+.PP
+A
+SET
+statement can contain multiple variable assignments, separated by commas. If you set several system variables, the most recent
+GLOBAL
+or
+SESSION
+modifier in the statement is used for following variables that have no modifier specified.
+.PP
+Examples:
+.sp
+.RS 3n
+.nf
+SET sort_buffer_size=10000;
+SET @@local.sort_buffer_size=10000;
+SET GLOBAL sort_buffer_size=1000000, SESSION sort_buffer_size=1000000;
+SET @@sort_buffer_size=1000000;
+SET @@global.sort_buffer_size=1000000, @@local.sort_buffer_size=1000000;
+.fi
+.RE
+.PP
+When you assign a value to a system variable with
+SET, you cannot use suffix letters in the value (as can be done with startup options). However, the value can take the form of an expression:
+.sp
+.RS 3n
+.nf
+SET sort_buffer_size = 10 * 1024 * 1024;
+.fi
+.RE
+.PP
+The
+@@\fIvar_name\fR
+syntax for system variables is supported for compatibility with some other database systems.
+.PP
+If you change a session system variable, the value remains in effect until your session ends or until you change the variable to a different value. The change is not visible to other clients.
+.PP
+If you change a global system variable, the value is remembered and used for new connections until the server restarts. (To make a global system variable setting permanent, you should set it in an option file.) The change is visible to any client that accesses that global variable. However, the change affects the corresponding session variable only for clients that connect after the change. The global variable change does not affect the session variable for any client that is currently connected (not even that of the client that issues the
+SET GLOBAL
+statement).
+.PP
+To prevent incorrect usage, MySQL produces an error if you use
+SET GLOBAL
+with a variable that can only be used with
+SET SESSION
+or if you do not specify
+GLOBAL
+(or
+@@global.) when setting a global variable.
+.PP
+To set a
+SESSION
+variable to the
+GLOBAL
+value or a
+GLOBAL
+value to the compiled\-in MySQL default value, use the
+DEFAULT
+keyword. For example, the following two statements are identical in setting the session value of
+max_join_size
+to the global value:
+.sp
+.RS 3n
+.nf
+SET max_join_size=DEFAULT;
+SET @@session.max_join_size=@@global.max_join_size;
+.fi
+.RE
+.PP
+Not all system variables can be set to
+DEFAULT. In such cases, use of
+DEFAULT
+results in an error.
+.PP
+You can refer to the values of specific global or sesson system variables in expressions by using one of the
+@@\-modifiers. For example, you can retrieve values in a
+SELECT
+statement like this:
+.sp
+.RS 3n
+.nf
+SELECT @@global.sql_mode, @@session.sql_mode, @@sql_mode;
+.fi
+.RE
+.PP
+When you refer to a system variable in an expression as
+@@\fIvar_name\fR
+(that is, when you do not specify
+@@global.
+or
+@@session.), MySQL returns the session value if it exists and the global value otherwise. (This differs from
+SET @@\fIvar_name\fR = \fIvalue\fR, which always refers to the session value.)
+.sp
+.it 1 an-trap
+.nr an-no-space-flag 1
+.nr an-break-flag 1
+.br
+\fBNote\fR
+.PP
+Some system variables can be enabled with the
+SET
+statement by setting them to
+ON
+or
+1, or disabled by setting them to
+OFF
+or
+0. However, to set such a variable on the command line or in an option file, you must set it to
+1
+or
+0; setting it to
+ON
+or
+OFF
+will not work. For example, on the command line,
+\fB\-\-delay_key_write=1\fR
+works but
+\fB\-\-delay_key_write=ON\fR
+does not.
+.PP
+To display system variable names and values, use the
+SHOW VARIABLES
+statement:
+.sp
+.RS 3n
+.nf
+mysql> \fBSHOW VARIABLES;\fR
++\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+
+| 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 |
+...
+| 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 | |
+...
+| version | 5.0.19 |
+| version_comment | MySQL Community Edition \- (GPL) |
+| version_compile_machine | i686 |
+| version_compile_os | pc\-linux\-gnu |
+| wait_timeout | 28800 |
++\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+
+.fi
+.RE
+.PP
+With a
+LIKE
+clause, the statement displays only those variables that match the pattern. To obtain a specific variable name, use a
+LIKE
+clause as shown:
+.sp
+.RS 3n
+.nf
+SHOW VARIABLES LIKE 'max_join_size';
+SHOW SESSION VARIABLES LIKE 'max_join_size';
+.fi
+.RE
+.PP
+To get a list of variables whose name match a pattern, use the
+\(lq%\(rq
+wildcard character in a
+LIKE
+clause:
+.sp
+.RS 3n
+.nf
+SHOW VARIABLES LIKE '%size%';
+SHOW GLOBAL VARIABLES LIKE '%size%';
+.fi
+.RE
+.PP
+Wildcard characters can be used in any position within the pattern to be matched. Strictly speaking, because
+\(lq_\(rq
+is a wildcard that matches any single character, you should escape it as
+\(lq\\_\(rq
+to match it literally. In practice, this is rarely necessary.
+.PP
+For
+SHOW VARIABLES, if you specify neither
+GLOBAL
+nor
+SESSION, MySQL returns
+SESSION
+values.
+.PP
+The reason for requiring the
+GLOBAL
+keyword when setting
+GLOBAL\-only variables but not when retrieving them is to prevent problems in the future. If we were to remove a
+SESSION
+variable that has the same name as a
+GLOBAL
+variable, a client with the
+SUPER
+privilege might accidentally change the
+GLOBAL
+variable rather than just the
+SESSION
+variable for its own connection. If we add a
+SESSION
+variable with the same name as a
+GLOBAL
+variable, a client that intends to change the
+GLOBAL
+variable might find only its own
+SESSION
+variable changed.
+.SS "Structured System Variables"
+.PP
+A structured variable differs from a regular system variable in two respects:
+.TP 3n
+\(bu
+Its value is a structure with components that specify server parameters considered to be closely related.
+.TP 3n
+\(bu
+There might be several instances of a given type of structured variable. Each one has a different name and refers to a different resource maintained by the server.
+.sp
+.RE
+.PP
+MySQL 5.0 supports one structured variable type, which specifies parameters governing the operation of key caches. A key cache structured variable has these components:
+.TP 3n
+\(bu
+key_buffer_size
+.TP 3n
+\(bu
+key_cache_block_size
+.TP 3n
+\(bu
+key_cache_division_limit
+.TP 3n
+\(bu
+key_cache_age_threshold
+.sp
+.RE
+.PP
+This section describes the syntax for referring to structured variables. Key cache variables are used for syntax examples, but specific details about how key caches operate are found elsewhere, in
+Section\ 4.6, \(lqThe MyISAM Key Cache\(rq.
+.PP
+To refer to a component of a structured variable instance, you can use a compound name in
+\fIinstance_name.component_name\fR
+format. Examples:
+.sp
+.RS 3n
+.nf
+hot_cache.key_buffer_size
+hot_cache.key_cache_block_size
+cold_cache.key_cache_block_size
+.fi
+.RE
+.PP
+For each structured system variable, an instance with the name of
+default
+is always predefined. If you refer to a component of a structured variable without any instance name, the
+default
+instance is used. Thus,
+default.key_buffer_size
+and
+key_buffer_size
+both refer to the same system variable.
+.PP
+Structured variable instances and components follow these naming rules:
+.TP 3n
+\(bu
+For a given type of structured variable, each instance must have a name that is unique
+\fIwithin\fR
+variables of that type. However, instance names need not be unique
+\fIacross\fR
+structured variable types. For example, each structured variable has an instance named
+default, so
+default
+is not unique across variable types.
+.TP 3n
+\(bu
+The names of the components of each structured variable type must be unique across all system variable names. If this were not true (that is, if two different types of structured variables could share component member names), it would not be clear which default structured variable to use for references to member names that are not qualified by an instance name.
+.TP 3n
+\(bu
+If a structured variable instance name is not legal as an unquoted identifier, refer to it as a quoted identifier using backticks. For example,
+hot\-cache
+is not legal, but
+`hot\-cache`
+is.
+.TP 3n
+\(bu
+global,
+session, and
+local
+are not legal instance names. This avoids a conflict with notation such as
+@@global.\fIvar_name\fR
+for referring to non\-structured system variables.
+.sp
+.RE
+.PP
+Currently, the first two rules have no possibility of being violated because the only structured variable type is the one for key caches. These rules will assume greater significance if some other type of structured variable is created in the future.
+.PP
+With one exception, you can refer to structured variable components using compound names in any context where simple variable names can occur. For example, you can assign a value to a structured variable using a command\-line option:
+.sp
+.RS 3n
+.nf
+shell> \fBmysqld \-\-hot_cache.key_buffer_size=64K\fR
+.fi
+.RE
+.PP
+In an option file, use this syntax:
+.sp
+.RS 3n
+.nf
+[mysqld]
+hot_cache.key_buffer_size=64K
+.fi
+.RE
+.PP
+If you start the server with this option, it creates a key cache named
+hot_cache
+with a size of 64KB in addition to the default key cache that has a default size of 8MB.
+.PP
+Suppose that you start the server as follows:
+.sp
+.RS 3n
+.nf
+shell> \fBmysqld \-\-key_buffer_size=256K \\\fR
+ \fB\-\-extra_cache.key_buffer_size=128K \\\fR
+ \fB\-\-extra_cache.key_cache_block_size=2048\fR
+.fi
+.RE
+.PP
+In this case, the server sets the size of the default key cache to 256KB. (You could also have written
+\fB\-\-default.key_buffer_size=256K\fR.) In addition, the server creates a second key cache named
+extra_cache
+that has a size of 128KB, with the size of block buffers for caching table index blocks set to 2048 bytes.
+.PP
+The following example starts the server with three different key caches having sizes in a 3:1:1 ratio:
+.sp
+.RS 3n
+.nf
+shell> \fBmysqld \-\-key_buffer_size=6M \\\fR
+ \fB\-\-hot_cache.key_buffer_size=2M \\\fR
+ \fB\-\-cold_cache.key_buffer_size=2M\fR
+.fi
+.RE
+.PP
+Structured variable values may be set and retrieved at runtime as well. For example, to set a key cache named
+hot_cache
+to a size of 10MB, use either of these statements:
+.sp
+.RS 3n
+.nf
+mysql> \fBSET GLOBAL hot_cache.key_buffer_size = 10*1024*1024;\fR
+mysql> \fBSET @@global.hot_cache.key_buffer_size = 10*1024*1024;\fR
+.fi
+.RE
+.PP
+To retrieve the cache size, do this:
+.sp
+.RS 3n
+.nf
+mysql> \fBSELECT @@global.hot_cache.key_buffer_size;\fR
+.fi
+.RE
+.PP
+However, the following statement does not work. The variable is not interpreted as a compound name, but as a simple string for a
+LIKE
+pattern\-matching operation:
+.sp
+.RS 3n
+.nf
+mysql> \fBSHOW GLOBAL VARIABLES LIKE 'hot_cache.key_buffer_size';\fR
+.fi
+.RE
+.PP
+This is the exception to being able to use structured variable names anywhere a simple variable name may occur.
+.\" end of SS subsection "Structured System Variables"
+.SS "Dynamic System Variables"
+.PP
+Many server system variables are dynamic and can be set at runtime using
+SET GLOBAL
+or
+SET SESSION. You can also obtain their values using
+SELECT. See
+the section called \(lqUSING SYSTEM VARIABLES\(rq.
+.PP
+The following table shows the full list of all dynamic system variables. The last column indicates for each variable whether
+GLOBAL
+or
+SESSION
+(or both) apply. The table also lists session options that can be set with the
+SET
+statement.
+Section\ 5.3, \(lqSET Syntax\(rq, discusses these options.
+.PP
+Variables that have a type of
+\(lqstring\(rq
+take a string value. Variables that have a type of
+\(lqnumeric\(rq
+take a numeric value. Variables that have a type of
+\(lqboolean\(rq
+can be set to 0, 1,
+ON
+or
+OFF. (If you set them on the command line or in an option file, use the numeric values.) Variables that are marked as
+\(lqenumeration\(rq
+normally should be set to one of the available values for the variable, but can also be set to the number that corresponds to the desired enumeration value. For enumerated system variables, the first enumeration value corresponds to 0. This differs from
+ENUM
+columns, for which the first enumeration value corresponds to 1.
+.TS
+allbox tab(:);
+lB cB cB.
+T{
+\fBVariable Name\fR
+T}:T{
+\fBVariable Type\fR
+T}:T{
+\fBVariable Scope\fR
+T}
+.T&
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c.
+T{
+autocommit
+T}:T{
+boolean
+T}:T{
+SESSION
+T}
+T{
+character_set_database
+T}:T{
+string
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+myisam_sort_buffer_size
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+myisam_stats_method
+T}:T{
+enumeration
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+ndb_autoincrement_prefetch_sz
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+ndb_cache_check_time
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+ndb_force_send
+T}:T{
+boolean
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+ndb_use_exact_count
+T}:T{
+boolean
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+ndbcluster
+T}:T{
+boolean
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+net_buffer_length
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+net_read_timeout
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+net_retry_count
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+character_set_results
+T}:T{
+string
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+net_write_timeout
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+new
+T}:T{
+boolean
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+old_passwords
+T}:T{
+boolean
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+open_files_limit
+T}:T{
+numeric
+T}:T{
+GLOBAL
+T}
+T{
+optimizer_prune_level
+T}:T{
+boolean
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+optimizer_search_depth
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+preload_buffer_size
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+profiling_history_size
+T}:T{
+numeric
+T}:T{
+SESSION
+T}
+T{
+query_alloc_block_size
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+query_cache_limit
+T}:T{
+numeric
+T}:T{
+GLOBAL
+T}
+T{
+character_set_system
+T}:T{
+string
+T}:T{
+GLOBAL
+T}
+T{
+query_cache_min_res_unit
+T}:T{
+numeric
+T}:T{
+GLOBAL
+T}
+T{
+query_cache_size
+T}:T{
+numeric
+T}:T{
+GLOBAL
+T}
+T{
+query_cache_type
+T}:T{
+enumeration
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+query_cache_wlock_invalidate
+T}:T{
+boolean
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+query_prealloc_size
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+range_alloc_block_size
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+read_buffer_size
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+read_only
+T}:T{
+numeric
+T}:T{
+GLOBAL
+T}
+T{
+read_rnd_buffer_size
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+relay\-log
+T}:T{
+filename
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+collation_connection
+T}:T{
+string
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+relay_log_purge
+T}:T{
+boolean
+T}:T{
+GLOBAL
+T}
+T{
+relay_log_space_limit
+T}:T{
+numeric
+T}:T{
+GLOBAL
+T}
+T{
+rpl_recovery_rank
+T}:T{
+numeric
+T}:T{
+GLOBAL
+T}
+T{
+secure_auth
+T}:T{
+boolean
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+server_id
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+skip_networking
+T}:T{
+\
+T}:T{
+GLOBAL
+T}
+T{
+skip\-new
+T}:T{
+\
+T}:T{
+GLOBAL
+T}
+T{
+skip_show_database
+T}:T{
+\
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+slave_net_timeout
+T}:T{
+numeric
+T}:T{
+GLOBAL
+T}
+T{
+slave_skip_errors
+T}:T{
+\
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+collation_database
+T}:T{
+string
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+slave_compressed_protocol
+T}:T{
+boolean
+T}:T{
+GLOBAL
+T}
+T{
+slave_transaction_retries
+T}:T{
+numeric
+T}:T{
+GLOBAL
+T}
+T{
+slow_launch_time
+T}:T{
+numeric
+T}:T{
+GLOBAL
+T}
+T{
+sort_buffer_size
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+sql_mode
+T}:T{
+enumeration
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+sql_big_selects
+T}:T{
+boolean
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+sql_big_tables
+T}:T{
+boolean
+T}:T{
+SESSION
+T}
+T{
+sql_buffer_result
+T}:T{
+boolean
+T}:T{
+SESSION
+T}
+T{
+sql_log_bin
+T}:T{
+boolean
+T}:T{
+SESSION
+T}
+T{
+sql_log_off
+T}:T{
+boolean
+T}:T{
+SESSION
+T}
+T{
+collation_server
+T}:T{
+string
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+sql_log_update
+T}:T{
+boolean
+T}:T{
+SESSION
+T}
+T{
+sql_low_priority_updates
+T}:T{
+boolean
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+sql_max_join_size
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+sql_notes
+T}:T{
+boolean
+T}:T{
+SESSION
+T}
+T{
+sql_quote_show_create
+T}:T{
+boolean
+T}:T{
+SESSION
+T}
+T{
+sql_safe_updates
+T}:T{
+boolean
+T}:T{
+SESSION
+T}
+T{
+sql_select_limit
+T}:T{
+numeric
+T}:T{
+SESSION
+T}
+T{
+sql_slave_skip_counter
+T}:T{
+numeric
+T}:T{
+GLOBAL
+T}
+T{
+sql_warnings
+T}:T{
+boolean
+T}:T{
+SESSION
+T}
+T{
+storage_engine
+T}:T{
+enumeration
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+completion_type
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+sync_binlog
+T}:T{
+numeric
+T}:T{
+GLOBAL
+T}
+T{
+sync_frm
+T}:T{
+boolean
+T}:T{
+GLOBAL
+T}
+T{
+system_time_zone
+T}:T{
+string
+T}:T{
+GLOBAL
+T}
+T{
+table_cache
+T}:T{
+numeric
+T}:T{
+GLOBAL
+T}
+T{
+table_lock_wait_timeout
+T}:T{
+numeric
+T}:T{
+GLOBAL
+T}
+T{
+table_open_cache
+T}:T{
+numeric
+T}:T{
+GLOBAL
+T}
+T{
+table_type
+T}:T{
+enumeration
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+thread_cache_size
+T}:T{
+numeric
+T}:T{
+GLOBAL
+T}
+T{
+time_format
+T}:T{
+string
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+time_zone
+T}:T{
+string
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+concurrent_insert
+T}:T{
+boolean
+T}:T{
+GLOBAL
+T}
+T{
+timed_mutexes
+T}:T{
+boolean
+T}:T{
+GLOBAL
+T}
+T{
+timestamp
+T}:T{
+string
+T}:T{
+SESSION
+T}
+T{
+tmp_table_size
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+transaction_alloc_block_size
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+transaction_prealloc_size
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+tx_isolation
+T}:T{
+enumeration
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+unique_checks
+T}:T{
+boolean
+T}:T{
+SESSION
+T}
+T{
+updatable_views_with_limit
+T}:T{
+boolean
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+version_compile_os
+T}:T{
+string
+T}:T{
+GLOBAL
+T}
+T{
+wait_timeout
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+connect_timeout
+T}:T{
+numeric
+T}:T{
+GLOBAL
+T}
+T{
+date_format
+T}:T{
+string
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+automatic_sp_privileges
+T}:T{
+boolean
+T}:T{
+GLOBAL
+T}
+T{
+datetime_format
+T}:T{
+string
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+default_week_format
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+delay_key_write
+T}:T{
+enumeration
+T}:T{
+GLOBAL
+T}
+T{
+delayed_insert_limit
+T}:T{
+numeric
+T}:T{
+GLOBAL
+T}
+T{
+delayed_insert_timeout
+T}:T{
+numeric
+T}:T{
+GLOBAL
+T}
+T{
+delayed_queue_size
+T}:T{
+numeric
+T}:T{
+GLOBAL
+T}
+T{
+div_precision_increment
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+engine_condition_pushdown
+T}:T{
+boolean
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+expire_logs_days
+T}:T{
+numeric
+T}:T{
+GLOBAL
+T}
+T{
+flush
+T}:T{
+boolean
+T}:T{
+GLOBAL
+T}
+T{
+big_tables
+T}:T{
+boolean
+T}:T{
+GLOBAL
+T}
+T{
+flush_time
+T}:T{
+numeric
+T}:T{
+GLOBAL
+T}
+T{
+foreign_key_checks
+T}:T{
+boolean
+T}:T{
+SESSION
+T}
+T{
+ft_boolean_syntax
+T}:T{
+string
+T}:T{
+GLOBAL
+T}
+T{
+ft_max_word_len
+T}:T{
+numeric
+T}:T{
+GLOBAL
+T}
+T{
+ft_min_word_len
+T}:T{
+numeric
+T}:T{
+GLOBAL
+T}
+T{
+ft_query_expansion_limit
+T}:T{
+numeric
+T}:T{
+GLOBAL
+T}
+T{
+ft_stopword_file
+T}:T{
+filename
+T}:T{
+GLOBAL
+T}
+T{
+group_concat_max_len
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+identity
+T}:T{
+numeric
+T}:T{
+SESSION
+T}
+T{
+init_connect
+T}:T{
+string
+T}:T{
+GLOBAL
+T}
+T{
+binlog_cache_size
+T}:T{
+numeric
+T}:T{
+GLOBAL
+T}
+T{
+init_slave
+T}:T{
+string
+T}:T{
+GLOBAL
+T}
+T{
+innodb_autoextend_increment
+T}:T{
+numeric
+T}:T{
+GLOBAL
+T}
+T{
+innodb_checksums
+T}:T{
+boolean
+T}:T{
+GLOBAL
+T}
+T{
+innodb_commit_concurrency
+T}:T{
+numeric
+T}:T{
+GLOBAL
+T}
+T{
+innodb_concurrency_tickets
+T}:T{
+numeric
+T}:T{
+GLOBAL
+T}
+T{
+innodb_fast_shutdown
+T}:T{
+numeric
+T}:T{
+GLOBAL
+T}
+T{
+innodb_flush_log_at_trx_commit
+T}:T{
+numeric
+T}:T{
+GLOBAL
+T}
+T{
+innodb_max_dirty_pages_pct
+T}:T{
+numeric
+T}:T{
+GLOBAL
+T}
+T{
+innodb_max_purge_lag
+T}:T{
+numeric
+T}:T{
+GLOBAL
+T}
+T{
+innodb_support_xa
+T}:T{
+boolean
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+bulk_insert_buffer_size
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+innodb_sync_spin_loops
+T}:T{
+numeric
+T}:T{
+GLOBAL
+T}
+T{
+innodb_table_locks
+T}:T{
+boolean
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+innodb_thread_concurrency
+T}:T{
+numeric
+T}:T{
+GLOBAL
+T}
+T{
+innodb_thread_sleep_delay
+T}:T{
+numeric
+T}:T{
+GLOBAL
+T}
+T{
+insert_id
+T}:T{
+numeric
+T}:T{
+SESSION
+T}
+T{
+interactive_timeout
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+join_buffer_size
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+keep_files_on_create
+T}:T{
+boolean
+T}:T{
+GLOBAL
+T}
+T{
+key_buffer_size
+T}:T{
+numeric
+T}:T{
+GLOBAL
+T}
+T{
+key_cache_age_threshold
+T}:T{
+numeric
+T}:T{
+GLOBAL
+T}
+T{
+character_set_filesystem
+T}:T{
+string
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+key_cache_block_size
+T}:T{
+numeric
+T}:T{
+GLOBAL
+T}
+T{
+key_cache_division_limit
+T}:T{
+numeric
+T}:T{
+GLOBAL
+T}
+T{
+last_insert_id
+T}:T{
+numeric
+T}:T{
+SESSION
+T}
+T{
+lc_time_names
+T}:T{
+string
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+local_infile
+T}:T{
+boolean
+T}:T{
+GLOBAL
+T}
+T{
+log_bin
+T}:T{
+filename
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+log_bin_trust_function_creators
+T}:T{
+boolean
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+log_bin_trust_routine_creators
+T}:T{
+boolean
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+log_error
+T}:T{
+filename
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+log_queries_not_using_indexes
+T}:T{
+boolean
+T}:T{
+GLOBAL
+T}
+T{
+character_set_server
+T}:T{
+string
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+log_slow_queries
+T}:T{
+filename
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+log_warnings
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+long_query_time
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+low_priority_updates
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+max_allowed_packet
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+max_binlog_cache_size
+T}:T{
+numeric
+T}:T{
+GLOBAL
+T}
+T{
+max_binlog_size
+T}:T{
+numeric
+T}:T{
+GLOBAL
+T}
+T{
+max_connect_errors
+T}:T{
+numeric
+T}:T{
+GLOBAL
+T}
+T{
+max_connections
+T}:T{
+numeric
+T}:T{
+GLOBAL
+T}
+T{
+max_delayed_threads
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+character_set_client
+T}:T{
+string
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+max_error_count
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+max_heap_table_size
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+max_insert_delayed_threads
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+max_join_size
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+max_length_for_sort_data
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+max_prepared_stmt_count
+T}:T{
+numeric
+T}:T{
+GLOBAL
+T}
+T{
+max_relay_log_size
+T}:T{
+numeric
+T}:T{
+GLOBAL
+T}
+T{
+max_seeks_for_key
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+max_sort_length
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+max_sp_recursion_depth
+T}:T{
+numeric
+T}:T{
+GLOBAL
+T}
+T{
+character_set_connection
+T}:T{
+string
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+max_tmp_tables
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+max_user_connections
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+max_write_lock_count
+T}:T{
+numeric
+T}:T{
+GLOBAL
+T}
+T{
+multi_range_count
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+multi_read_range
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+myisam\-recover
+T}:T{
+enumeration
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+myisam_block_size
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+myisam_data_pointer_size
+T}:T{
+numeric
+T}:T{
+GLOBAL
+T}
+T{
+myisam_max_sort_file_size
+T}:T{
+numeric
+T}:T{
+GLOBAL
+T}
+T{
+myisam_repair_threads
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+.TE
+.sp
+.\" end of SS subsection "Dynamic System Variables"
+.SH "STATUS VARIABLES"
+.PP
+The server maintains many status variables that provide information about its operation. You can view these variables and their values by using the
+SHOW [GLOBAL] STATUS
+statement. The optional
+GLOBAL
+keyword aggregates the values over all connections.
+.sp
+.RS 3n
+.nf
+mysql> \fBSHOW GLOBAL STATUS;\fR
++\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-+
+| Variable_name | Value |
++\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-+
+| Aborted_clients | 0 |
+| Aborted_connects | 0 |
+| Bytes_received | 155372598 |
+| Bytes_sent | 1176560426 |
+...
+| Connections | 30023 |
+| Created_tmp_disk_tables | 0 |
+| Created_tmp_files | 3 |
+| Created_tmp_tables | 2 |
+...
+| Threads_created | 217 |
+| Threads_running | 88 |
+| Uptime | 1389872 |
++\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-+
+.fi
+.RE
+.PP
+The following table lists all available server status variables:
+.TS
+allbox tab(:);
+lB cB cB.
+T{
+\fBVariable Name\fR
+T}:T{
+\fBVariable Type\fR
+T}:T{
+\fBVariable Scope\fR
+T}
+.T&
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c
+l c c.
+T{
+Aborted_clients
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_alter_table
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_slave_stop
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_stmt_close
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_stmt_execute
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_stmt_fetch
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_stmt_prepare
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_stmt_reset
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_stmt_send_long_data
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_truncate
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_unlock_tables
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_update
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_analyze
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_update_multi
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_xa_commit
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_xa_end
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_xa_prepare
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_xa_recover
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_xa_rollback
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_xa_start
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Compression
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Connections
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Created_tmp_disk_tables
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_backup_table
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Created_tmp_files
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Created_tmp_tables
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Delayed_errors
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Delayed_insert_threads
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Delayed_writes
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Flush_commands
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Handler_commit
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Handler_delete
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Handler_discover
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Handler_prepare
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_begin
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Handler_read_first
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Handler_read_key
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Handler_read_next
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Handler_read_prev
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Handler_read_rnd
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Handler_read_rnd_next
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Handler_rollback
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Handler_savepoint
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Handler_savepoint_rollback
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Handler_update
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_call_procedure
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Handler_write
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Innodb_buffer_pool_pages_data
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Innodb_buffer_pool_pages_dirty
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Innodb_buffer_pool_pages_flushed
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Innodb_buffer_pool_pages_free
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Innodb_buffer_pool_pages_latched
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Innodb_buffer_pool_pages_misc
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Innodb_buffer_pool_pages_total
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Innodb_buffer_pool_read_ahead_rnd
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Innodb_buffer_pool_read_ahead_seq
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_change_db
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Innodb_buffer_pool_read_requests
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Innodb_buffer_pool_reads
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Innodb_buffer_pool_wait_free
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Innodb_buffer_pool_write_requests
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Innodb_data_fsyncs
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Innodb_data_pending_fsyncs
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Innodb_data_pending_reads
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Innodb_data_pending_writes
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Innodb_data_read
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Innodb_data_reads
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_change_master
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Innodb_data_writes
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Innodb_data_written
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Innodb_dblwr_pages_written
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Innodb_dblwr_writes
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Innodb_log_waits
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Innodb_log_write_requests
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Innodb_log_writes
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Innodb_os_log_fsyncs
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Innodb_os_log_pending_fsyncs
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Innodb_os_log_pending_writes
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_check
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Innodb_os_log_written
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Innodb_page_size
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Innodb_pages_created
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Innodb_pages_read
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Innodb_pages_written
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Innodb_row_lock_current_waits
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Innodb_row_lock_time
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Innodb_row_lock_time_avg
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Innodb_row_lock_time_max
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Innodb_row_lock_waits
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_checksum
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Innodb_rows_deleted
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Innodb_rows_inserted
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Innodb_rows_read
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Innodb_rows_updated
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Key_blocks_not_flushed
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Key_blocks_unused
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Key_blocks_used
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Key_read_requests
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Key_reads
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Key_write_requests
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_commit
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Key_writes
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Last_query_cost
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Max_used_connections
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Ndb_cluster_node_id
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Ndb_config_from_host
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Ndb_config_from_port
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Not_flushed_delayed_rows
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Open_files
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Open_streams
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Open_tables
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Aborted_connects
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_create_db
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Opened_tables
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+prepared_stmt_count
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Qcache_free_blocks
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Qcache_free_memory
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Qcache_hits
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Qcache_inserts
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Qcache_lowmem_prunes
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Qcache_not_cached
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Qcache_queries_in_cache
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Qcache_total_blocks
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_create_event
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Questions
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Relay_Log_Space
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Rpl_status
+T}:T{
+\
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Select_full_join
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Select_full_range_join
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Select_range
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Select_range_check
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Select_scan
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Slave_open_temp_tables
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Slave_retried_transactions
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_create_function
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Slave_running
+T}:T{
+boolean
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Slow_launch_threads
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Slow_queries
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Sort_merge_passes
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Sort_range
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Sort_rows
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Sort_scan
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Table_locks_immediate
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Table_locks_waited
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Tc_log_max_pages_used
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_create_index
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Tc_log_page_size
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Tc_log_page_waits
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Threads_cached
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Threads_connected
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Threads_created
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Threads_running
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Uptime
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Uptime_since_flush_status
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_create_table
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_create_user
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_dealloc_sql
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_delete
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_delete_multi
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_do
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Binlog_cache_disk_use
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_drop_db
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_drop_event
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_drop_function
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_drop_index
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_drop_table
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_drop_user
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_execute_sql
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_flush
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_grant
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_ha_close
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Binlog_cache_use
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_ha_open
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_ha_read
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_help
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_insert
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_insert_select
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_kill
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_load
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_lock_tables
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_optimize
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_preload_keys
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Bytes_received
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_prepare_sql
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_purge
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_purge_before_date
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_rename_table
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_repair
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_replace
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_replace_select
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_reset
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_restore_table
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_revoke
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Bytes_sent
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_revoke_all
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_rollback
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_savepoint
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_select
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_set_option
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_show_binlog_events
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_show_binlogs
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_show_charsets
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_show_collations
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_show_column_types
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_admin_commands
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_show_create_db
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_show_create_event
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_show_create_table
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_show_databases
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_show_engine_logs
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_show_engine_mutex
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_show_engine_status
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_show_errors
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_show_events
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_show_fields
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_alter_db
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_show_grants
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_show_innodb_status
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_show_keys
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_show_logs
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_show_master_status
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_show_ndb_status
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_show_new_master
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_show_open_tables
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_show_plugins
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_show_privileges
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_alter_event
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_show_processlist
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_show_slave_hosts
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_show_slave_status
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_show_status
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_show_storage_engines
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_show_tables
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_show_triggers
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_show_variables
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_show_warnings
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+T{
+Com_slave_start
+T}:T{
+numeric
+T}:T{
+GLOBAL | SESSION
+T}
+.TE
+.sp
+.sp
+.it 1 an-trap
+.nr an-no-space-flag 1
+.nr an-break-flag 1
+.br
+\fBNote\fR
+.PP
+Before MySQL 5.0.2,
+SHOW STATUS
+returned global status values. Because the default as of 5.0.2 is to return session values, this is incompatible with previous versions. To issue a
+SHOW STATUS
+statement that will retrieve global status values for all versions of MySQL, write it like this:
+.sp
+.RS 3n
+.nf
+SHOW /*!50002 GLOBAL */ STATUS;
+.fi
+.RE
+.PP
+Many status variables are reset to 0 by the
+FLUSH STATUS
+statement.
+.PP
+The status variables have the following meanings. Variables with no version indicated were already present prior to MySQL 5.0. For information regarding their implementation history, see
+MySQL 3.23, 4.0, 4.1 Reference Manual.
+.TP 3n
+\(bu
+Aborted_clients
+.sp
+The number of connections that were aborted because the client died without closing the connection properly. See
+Section\ 1.2.11, \(lqCommunication Errors and Aborted Connections\(rq.
+.TP 3n
+\(bu
+Aborted_connects
+.sp
+The number of failed attempts to connect to the MySQL server. See
+Section\ 1.2.11, \(lqCommunication Errors and Aborted Connections\(rq.
+.TP 3n
+\(bu
+Binlog_cache_disk_use
+.sp
+The number of transactions that used the temporary binary log cache but that exceeded the value of
+binlog_cache_size
+and used a temporary file to store statements from the transaction.
+.TP 3n
+\(bu
+Binlog_cache_use
+.sp
+The number of transactions that used the temporary binary log cache.
+.TP 3n
+\(bu
+Bytes_received
+.sp
+The number of bytes received from all clients.
+.TP 3n
+\(bu
+Bytes_sent
+.sp
+The number of bytes sent to all clients.
+.TP 3n
+\(bu
+Com_\fIxxx\fR
+.sp
+The
+Com_\fIxxx\fR
+statement counter variables indicate the number of times each
+\fIxxx\fR
+statement has been executed. There is one status variable for each type of statement. For example,
+Com_delete
+and
+Com_insert
+count
+DELETE
+and
+INSERT
+statements, respectively. However, if a query result is returned from query cache, the server increments the
+Qcache_hits
+status variable, not
+Com_select. See
+Section\ 5.4.4, \(lqQuery Cache Status and Maintenance\(rq.
+.sp
+All of the
+Com_stmt_\fIxxx\fR
+variables are increased even if a prepared statement argument is unknown or an error occurred during execution. In other words, their values correspond to the number of requests issued, not to the number of requests successfully completed.
+.sp
+The
+Com_stmt_\fIxxx\fR
+status variables were added in 5.0.8:
+.RS 3n
+.TP 3n
+\(bu
+Com_stmt_prepare
+.TP 3n
+\(bu
+Com_stmt_execute
+.TP 3n
+\(bu
+Com_stmt_fetch
+.TP 3n
+\(bu
+Com_stmt_send_long_data
+.TP 3n
+\(bu
+Com_stmt_reset
+.TP 3n
+\(bu
+Com_stmt_close
+.RE
+.IP "" 3n
+Those variables stand for prepared statement commands. Their names refer to the
+COM_\fIxxx\fR
+command set used in the network layer. In other words, their values increase whenever prepared statement API calls such as
+\fBmysql_stmt_prepare()\fR,
+\fBmysql_stmt_execute()\fR, and so forth are executed. However,
+Com_stmt_prepare,
+Com_stmt_execute
+and
+Com_stmt_close
+also increase for
+PREPARE,
+EXECUTE, or
+DEALLOCATE PREPARE, respectively. Additionally, the values of the older (available since MySQL 4.1.3) statement counter variables
+Com_prepare_sql,
+Com_execute_sql, and
+Com_dealloc_sql
+increase for the
+PREPARE,
+EXECUTE, and
+DEALLOCATE PREPARE
+statements.
+Com_stmt_fetch
+stands for the total number of network round\-trips issued when fetching from cursors.
+.TP 3n
+\(bu
+Compression
+.sp
+Whether the client connection uses compression in the client/server protocol. Added in MySQL 5.0.16.
+.TP 3n
+\(bu
+Connections
+.sp
+The number of connection attempts (successful or not) to the MySQL server.
+.TP 3n
+\(bu
+Created_tmp_disk_tables
+.sp
+The number of temporary tables on disk created automatically by the server while executing statements.
+.TP 3n
+\(bu
+Created_tmp_files
+.sp
+How many temporary files
+\fBmysqld\fR
+has created.
+.TP 3n
+\(bu
+Created_tmp_tables
+.sp
+The number of in\-memory temporary tables created automatically by the server while executing statements. If
+Created_tmp_disk_tables
+is large, you may want to increase the
+tmp_table_size
+value to cause temporary tables to be memory\-based instead of disk\-based.
+.TP 3n
+\(bu
+Delayed_errors
+.sp
+The number of rows written with
+INSERT DELAYED
+for which some error occurred (probably
+duplicate key).
+.TP 3n
+\(bu
+Delayed_insert_threads
+.sp
+The number of
+INSERT DELAYED
+handler threads in use.
+.TP 3n
+\(bu
+Delayed_writes
+.sp
+The number of
+INSERT DELAYED
+rows written.
+.TP 3n
+\(bu
+Flush_commands
+.sp
+The number of executed
+FLUSH
+statements.
+.TP 3n
+\(bu
+Handler_commit
+.sp
+The number of internal
+COMMIT
+statements.
+.TP 3n
+\(bu
+Handler_delete
+.sp
+The number of times that rows have been deleted from tables.
+.TP 3n
+\(bu
+Handler_discover
+.sp
+The MySQL server can ask the
+NDB Cluster
+storage engine if it knows about a table with a given name. This is called discovery.
+Handler_discover
+indicates the number of times that tables have been discovered via this mechanism.
+.TP 3n
+\(bu
+Handler_prepare
+.sp
+A counter for the prepare phase of two\-phase commit operations. Added in MySQL 5.0.3.
+.TP 3n
+\(bu
+Handler_read_first
+.sp
+The number of times the first entry was read from an index. If this value is high, it suggests that the server is doing a lot of full index scans; for example,
+SELECT col1 FROM foo, assuming that
+col1
+is indexed.
+.TP 3n
+\(bu
+Handler_read_key
+.sp
+The number of requests to read a row based on a key. If this value is high, it is a good indication that your tables are properly indexed for your queries.
+.TP 3n
+\(bu
+Handler_read_next
+.sp
+The number of requests to read the next row in key order. This value is incremented if you are querying an index column with a range constraint or if you are doing an index scan.
+.TP 3n
+\(bu
+Handler_read_prev
+.sp
+The number of requests to read the previous row in key order. This read method is mainly used to optimize
+ORDER BY ... DESC.
+.TP 3n
+\(bu
+Handler_read_rnd
+.sp
+The number of requests to read a row based on a fixed position. This value is high if you are doing a lot of queries that require sorting of the result. You probably have a lot of queries that require MySQL to scan entire tables or you have joins that don't use keys properly.
+.TP 3n
+\(bu
+Handler_read_rnd_next
+.sp
+The number of requests to read the next row in the data file. This value is high if you are doing a lot of table scans. Generally this suggests that your tables are not properly indexed or that your queries are not written to take advantage of the indexes you have.
+.TP 3n
+\(bu
+Handler_rollback
+.sp
+The number of requests for a storage engine to perform a rollback operation.
+.TP 3n
+\(bu
+Handler_savepoint
+.sp
+The number of requests for a storage engine to place a savepoint. Added in MySQL 5.0.3.
+.TP 3n
+\(bu
+Handler_savepoint_rollback
+.sp
+The number of requests for a storage engine to roll back to a savepoint. Added in MySQL 5.0.3.
+.TP 3n
+\(bu
+Handler_update
+.sp
+The number of requests to update a row in a table.
+.TP 3n
+\(bu
+Handler_write
+.sp
+The number of requests to insert a row in a table.
+.TP 3n
+\(bu
+Innodb_buffer_pool_pages_data
+.sp
+The number of pages containing data (dirty or clean). Added in MySQL 5.0.2.
+.TP 3n
+\(bu
+Innodb_buffer_pool_pages_dirty
+.sp
+The number of pages currently dirty. Added in MySQL 5.0.2.
+.TP 3n
+\(bu
+Innodb_buffer_pool_pages_flushed
+.sp
+The number of buffer pool page\-flush requests. Added in MySQL 5.0.2.
+.TP 3n
+\(bu
+Innodb_buffer_pool_pages_free
+.sp
+The number of free pages. Added in MySQL 5.0.2.
+.TP 3n
+\(bu
+Innodb_buffer_pool_pages_latched
+.sp
+The number of latched pages in
+InnoDB
+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.
+.TP 3n
+\(bu
+Innodb_buffer_pool_pages_misc
+.sp
+The number of pages that are busy because they have been allocated for administrative overhead such as row locks or the adaptive hash index. This value can also be calculated as
+Innodb_buffer_pool_pages_total
+\(en
+Innodb_buffer_pool_pages_free
+\(en
+Innodb_buffer_pool_pages_data. Added in MySQL 5.0.2.
+.TP 3n
+\(bu
+Innodb_buffer_pool_pages_total
+.sp
+The total size of buffer pool, in pages. Added in MySQL 5.0.2.
+.TP 3n
+\(bu
+Innodb_buffer_pool_read_ahead_rnd
+.sp
+The number of
+\(lqrandom\(rq
+read\-aheads initiated by
+InnoDB. This happens when a query scans a large portion of a table but in random order. Added in MySQL 5.0.2.
+.TP 3n
+\(bu
+Innodb_buffer_pool_read_ahead_seq
+.sp
+The number of sequential read\-aheads initiated by
+InnoDB. This happens when
+InnoDB
+does a sequential full table scan. Added in MySQL 5.0.2.
+.TP 3n
+\(bu
+Innodb_buffer_pool_read_requests
+.sp
+The number of logical read requests
+InnoDB
+has done. Added in MySQL 5.0.2.
+.TP 3n
+\(bu
+Innodb_buffer_pool_reads
+.sp
+The number of logical reads that
+InnoDB
+could not satisfy from the buffer pool and had to do a single\-page read. Added in MySQL 5.0.2.
+.TP 3n
+\(bu
+Innodb_buffer_pool_wait_free
+.sp
+Normally, writes to the
+InnoDB
+buffer pool happen in the background. However, if it is necessary to read or create a page and no clean pages are available, 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.
+.TP 3n
+\(bu
+Innodb_buffer_pool_write_requests
+.sp
+The number writes done to the
+InnoDB
+buffer pool. Added in MySQL 5.0.2.
+.TP 3n
+\(bu
+Innodb_data_fsyncs
+.sp
+The number of
+fsync()
+operations so far. Added in MySQL 5.0.2.
+.TP 3n
+\(bu
+Innodb_data_pending_fsyncs
+.sp
+The current number of pending
+fsync()
+operations. Added in MySQL 5.0.2.
+.TP 3n
+\(bu
+Innodb_data_pending_reads
+.sp
+The current number of pending reads. Added in MySQL 5.0.2.
+.TP 3n
+\(bu
+Innodb_data_pending_writes
+.sp
+The current number of pending writes. Added in MySQL 5.0.2.
+.TP 3n
+\(bu
+Innodb_data_read
+.sp
+The amount of data read so far, in bytes. Added in MySQL 5.0.2.
+.TP 3n
+\(bu
+Innodb_data_reads
+.sp
+The total number of data reads. Added in MySQL 5.0.2.
+.TP 3n
+\(bu
+Innodb_data_writes
+.sp
+The total number of data writes. Added in MySQL 5.0.2.
+.TP 3n
+\(bu
+Innodb_data_written
+.sp
+The amount of data written so far, in bytes. Added in MySQL 5.0.2.
+.TP 3n
+\(bu
+Innodb_dblwr_writes,
+Innodb_dblwr_pages_written
+.sp
+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
+Section\ 2.14.1, \(lqInnoDB Disk I/O\(rq.
+.TP 3n
+\(bu
+Innodb_log_waits
+.sp
+The number of times that the log buffer was too small and a wait was required for it to be flushed before continuing. Added in MySQL 5.0.2.
+.TP 3n
+\(bu
+Innodb_log_write_requests
+.sp
+The number of log write requests. Added in MySQL 5.0.2.
+.TP 3n
+\(bu
+Innodb_log_writes
+.sp
+The number of physical writes to the log file. Added in MySQL 5.0.2.
+.TP 3n
+\(bu
+Innodb_os_log_fsyncs
+.sp
+The number of
+fsync()
+writes done to the log file. Added in MySQL 5.0.2.
+.TP 3n
+\(bu
+Innodb_os_log_pending_fsyncs
+.sp
+The number of pending log file
+fsync()
+operations. Added in MySQL 5.0.2.
+.TP 3n
+\(bu
+Innodb_os_log_pending_writes
+.sp
+The number of pending log file writes. Added in MySQL 5.0.2.
+.TP 3n
+\(bu
+Innodb_os_log_written
+.sp
+The number of bytes written to the log file. Added in MySQL 5.0.2.
+.TP 3n
+\(bu
+Innodb_page_size
+.sp
+The compiled\-in
+InnoDB
+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.
+.TP 3n
+\(bu
+Innodb_pages_created
+.sp
+The number of pages created. Added in MySQL 5.0.2.
+.TP 3n
+\(bu
+Innodb_pages_read
+.sp
+The number of pages read. Added in MySQL 5.0.2.
+.TP 3n
+\(bu
+Innodb_pages_written
+.sp
+The number of pages written. Added in MySQL 5.0.2.
+.TP 3n
+\(bu
+Innodb_row_lock_current_waits
+.sp
+The number of row locks currently being waited for. Added in MySQL 5.0.3.
+.TP 3n
+\(bu
+Innodb_row_lock_time
+.sp
+The total time spent in acquiring row locks, in milliseconds. Added in MySQL 5.0.3.
+.TP 3n
+\(bu
+Innodb_row_lock_time_avg
+.sp
+The average time to acquire a row lock, in milliseconds. Added in MySQL 5.0.3.
+.TP 3n
+\(bu
+Innodb_row_lock_time_max
+.sp
+The maximum time to acquire a row lock, in milliseconds. Added in MySQL 5.0.3.
+.TP 3n
+\(bu
+Innodb_row_lock_waits
+.sp
+The number of times a row lock had to be waited for. Added in MySQL 5.0.3.
+.TP 3n
+\(bu
+Innodb_rows_deleted
+.sp
+The number of rows deleted from
+InnoDB
+tables. Added in MySQL 5.0.2.
+.TP 3n
+\(bu
+Innodb_rows_inserted
+.sp
+The number of rows inserted into
+InnoDB
+tables. Added in MySQL 5.0.2.
+.TP 3n
+\(bu
+Innodb_rows_read
+.sp
+The number of rows read from
+InnoDB
+tables. Added in MySQL 5.0.2.
+.TP 3n
+\(bu
+Innodb_rows_updated
+.sp
+The number of rows updated in
+InnoDB
+tables. Added in MySQL 5.0.2.
+.TP 3n
+\(bu
+Key_blocks_not_flushed
+.sp
+The number of key blocks in the key cache that have changed but have not yet been flushed to disk.
+.TP 3n
+\(bu
+Key_blocks_unused
+.sp
+The number of unused blocks in the key cache. You can use this value to determine how much of the key cache is in use; see the discussion of
+key_buffer_size
+in
+the section called \(lqSYSTEM VARIABLES\(rq.
+.TP 3n
+\(bu
+Key_blocks_used
+.sp
+The number of used blocks in the key cache. This value is a high\-water mark that indicates the maximum number of blocks that have ever been in use at one time.
+.TP 3n
+\(bu
+Key_read_requests
+.sp
+The number of requests to read a key block from the cache.
+.TP 3n
+\(bu
+Key_reads
+.sp
+The number of physical reads of a key block from disk. If
+Key_reads
+is large, then your
+key_buffer_size
+value is probably too small. The cache miss rate can be calculated as
+Key_reads/Key_read_requests.
+.TP 3n
+\(bu
+Key_write_requests
+.sp
+The number of requests to write a key block to the cache.
+.TP 3n
+\(bu
+Key_writes
+.sp
+The number of physical writes of a key block to disk.
+.TP 3n
+\(bu
+Last_query_cost
+.sp
+The total cost of the last compiled query as computed by the query optimizer. This is 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
+Last_query_cost
+was changed to session rather than global.
+.sp
+The
+Last_query_cost
+value can be computed accurately only for simple
+\(lqflat\(rq
+queries, not complex queries such as those with subqueries or
+UNION. For the latter, the value is set to 0.
+.sp
+Prior to MySQL 5.0.16, this variable was not updated for queries served from the query cache.
+.TP 3n
+\(bu
+Max_used_connections
+.sp
+The maximum number of connections that have been in use simultaneously since the server started.
+.TP 3n
+\(bu
+Ndb_cluster_node_id
+.sp
+If the server is acting as a MySQL Cluster node, then the value of this variable its node ID in the cluster.
+.sp
+If the server is not part of a MySQL Cluster, then the value of this variable is 0.
+.TP 3n
+\(bu
+Ndb_config_from_host
+.sp
+If the server is part of a MySQL Cluster, the value of this variable is the hostname or IP address of the Cluster management server from which it gets its configuration data.
+.sp
+If the server is not part of a MySQL Cluster, then the value of this variable is an empty string.
+.sp
+Prior to MySQL 5.0.23, this variable was named
+Ndb_connected_host.
+.TP 3n
+\(bu
+Ndb_config_from_port
+.sp
+If the server is part of a MySQL Cluster, the value of this variable is the number of the port through which it is connected to the Cluster management server from which it gets its configuration data.
+.sp
+If the server is not part of a MySQL Cluster, then the value of this variable is 0.
+.sp
+Prior to MySQL 5.0.23, this variable was named
+Ndb_connected_port.
+.TP 3n
+\(bu
+Ndb_number_of_data_nodes
+.sp
+If the server is part of a MySQL Cluster, the value of this variable is the number of data nodes in the cluster.
+.sp
+If the server is not part of a MySQL Cluster, then the value of this variable is 0.
+.sp
+Prior to MySQL 5.0.29, this variable was named
+Ndb_number_of_storage_nodes.
+.TP 3n
+\(bu
+Not_flushed_delayed_rows
+.sp
+The number of rows waiting to be written in
+INSERT DELAY
+queues.
+.TP 3n
+\(bu
+Open_files
+.sp
+The number of files that are open.
+.TP 3n
+\(bu
+Open_streams
+.sp
+The number of streams that are open (used mainly for logging).
+.TP 3n
+\(bu
+Open_tables
+.sp
+The number of tables that are open.
+.TP 3n
+\(bu
+Opened_tables
+.sp
+The number of tables that have been opened. If
+Opened_tables
+is big, your
+table_cache
+value is probably too small.
+.TP 3n
+\(bu
+Prepared_stmt_count
+.sp
+The current number of prepared statements. (The maximum number of statements is given by the
+max_prepared_stmt_count
+system variable.) This variable was added in MySQL 5.0.32.
+.TP 3n
+\(bu
+Qcache_free_blocks
+.sp
+The number of free memory blocks in the query cache.
+.TP 3n
+\(bu
+Qcache_free_memory
+.sp
+The amount of free memory for the query cache.
+.TP 3n
+\(bu
+Qcache_hits
+.sp
+The number of query cache hits.
+.TP 3n
+\(bu
+Qcache_inserts
+.sp
+The number of queries added to the query cache.
+.TP 3n
+\(bu
+Qcache_lowmem_prunes
+.sp
+The number of queries that were deleted from the query cache because of low memory.
+.TP 3n
+\(bu
+Qcache_not_cached
+.sp
+The number of non\-cached queries (not cacheable, or not cached due to the
+query_cache_type
+setting).
+.TP 3n
+\(bu
+Qcache_queries_in_cache
+.sp
+The number of queries registered in the query cache.
+.TP 3n
+\(bu
+Qcache_total_blocks
+.sp
+The total number of blocks in the query cache.
+.TP 3n
+\(bu
+Questions
+.sp
+The number of statements that clients have sent to the server.
+.TP 3n
+\(bu
+Rpl_status
+.sp
+The status of fail\-safe replication (not yet implemented).
+.TP 3n
+\(bu
+Select_full_join
+.sp
+The number of joins that perform table scans because they do not use indexes. If this value is not 0, you should carefully check the indexes of your tables.
+.TP 3n
+\(bu
+Select_full_range_join
+.sp
+The number of joins that used a range search on a reference table.
+.TP 3n
+\(bu
+Select_range
+.sp
+The number of joins that used ranges on the first table.
+This is normally not a critical issue even if the value is quite large.
+.TP 3n
+\(bu
+Select_range_check
+.sp
+The number of joins without keys that check for key usage after each row. If this is not 0, you should carefully check the indexes of your tables.
+.TP 3n
+\(bu
+Select_scan
+.sp
+The number of joins that did a full scan of the first table.
+.TP 3n
+\(bu
+Slave_open_temp_tables
+.sp
+The number of temporary tables that the slave SQL thread currently has open.
+.TP 3n
+\(bu
+Slave_running
+.sp
+This is
+ON
+if this server is a slave that is connected to a master.
+.TP 3n
+\(bu
+Slave_retried_transactions
+.sp
+The total number of times since startup that the replication slave SQL thread has retried transactions. This variable was added in version 5.0.4.
+.TP 3n
+\(bu
+Slow_launch_threads
+.sp
+The number of threads that have taken more than
+slow_launch_time
+seconds to create.
+.TP 3n
+\(bu
+Slow_queries
+.sp
+The number of queries that have taken more than
+long_query_time
+seconds. See
+Section\ 8.4, \(lqThe Slow Query Log\(rq.
+.TP 3n
+\(bu
+Sort_merge_passes
+.sp
+The number of merge passes that the sort algorithm has had to do. If this value is large, you should consider increasing the value of the
+sort_buffer_size
+system variable.
+.TP 3n
+\(bu
+Sort_range
+.sp
+The number of sorts that were done using ranges.
+.TP 3n
+\(bu
+Sort_rows
+.sp
+The number of sorted rows.
+.TP 3n
+\(bu
+Sort_scan
+.sp
+The number of sorts that were done by scanning the table.
+.TP 3n
+\(bu
+Ssl_\fIxxx\fR
+.sp
+Variables used for SSL connections.
+.TP 3n
+\(bu
+Table_locks_immediate
+.sp
+The number of times that a table lock was acquired immediately.
+.TP 3n
+\(bu
+Table_locks_waited
+.sp
+The number of times that a table lock could not be acquired immediately and a wait was needed. If this is high and you have performance problems, you should first optimize your queries, and then either split your table or tables or use replication.
+.TP 3n
+\(bu
+Tc_log_max_pages_used
+.sp
+For the memory\-mapped implementation of the log that is used by
+\fBmysqld\fR
+when it acts as the transaction coordinator for recovery of internal XA transactions, this variable indicates the largest number of pages used for the log since the server started. If the product of
+Tc_log_max_pages_used
+and
+Tc_log_page_size
+is always significantly less than the log size, the size is larger than necessary and can be reduced. (The size is set by the
+\fB\-\-log\-tc\-size\fR
+option. Currently, this variable is unused: It is unneeded for binary log\-based recovery, and the memory\-mapped recovery log method is not used unless the number of storage engines capable of two\-phase commit is greater than one. (InnoDB
+is the only applicable engine.) Added in MySQL 5.0.3.
+.TP 3n
+\(bu
+Tc_log_page_size
+.sp
+The page size used for the memory\-mapped implementation of the XA recovery log. The default value is determined using
+getpagesize(). Currently, this variable is unused for the same reasons as described for
+Tc_log_max_pages_used. Added in MySQL 5.0.3.
+.TP 3n
+\(bu
+Tc_log_page_waits
+.sp
+For the memory\-mapped implementation of the recovery log, this variable increments each time the server was not able to commit a transaction and had to wait for a free page in the log. If this value is large, you might want to increase the log size (with the
+\fB\-\-log\-tc\-size\fR
+option). For binary log\-based recovery, this variable increments each time the binary log cannot be closed because there are two\-phase commits in progress. (The close operation waits until all such transactions are finished.) Added in MySQL 5.0.3.
+.TP 3n
+\(bu
+Threads_cached
+.sp
+The number of threads in the thread cache.
+.TP 3n
+\(bu
+Threads_connected
+.sp
+The number of currently open connections.
+.TP 3n
+\(bu
+Threads_created
+.sp
+The number of threads created to handle connections. If
+Threads_created
+is big, you may want to increase the
+thread_cache_size
+value. The cache miss rate can be calculated as
+Threads_created/Connections.
+.TP 3n
+\(bu
+Threads_running
+.sp
+The number of threads that are not sleeping.
+.TP 3n
+\(bu
+Uptime
+.sp
+The number of seconds that the server has been up.
+.SH "SQL MODES"
+.PP
+The MySQL server can operate in different SQL modes, and can apply these modes differently for different clients. This capability enables each application to tailor the server's operating mode to its own requirements.
+.PP
+For answers to some questions that are often asked about server SQL modes in MySQL, see
+Section\ 3, \(lqMySQL 5.0 FAQ \(em Server SQL Mode\(rq.
+.PP
+Modes define what SQL syntax MySQL should support and what kind of data validation checks it should perform. This makes it easier to use MySQL in different environments and to use MySQL together with other database servers.
+.PP
+You can set the default SQL mode by starting
+\fBmysqld\fR
+with the
+\fB\-\-sql\-mode="\fR\fB\fImodes\fR\fR\fB"\fR
+option, or by using
+\fBsql\-mode="\fR\fB\fImodes\fR\fR\fB"\fR
+in
+\fImy.cnf\fR
+(Unix operating systems) or
+\fImy.ini\fR
+(Windows).
+\fImodes\fR
+is a list of different modes separated by comma (\(lq,\(rq) characters. The default value is empty (no modes set). The
+\fImodes\fR
+value also can be empty (\fB\-\-sql\-mode=""\fR
+on the command line, or
+\fBsql\-mode=""\fR
+in
+\fImy.cnf\fR
+on Unix systems or in
+\fImy.ini\fR
+on Windows) if you want to clear it explicitly.
+.PP
+You can change the SQL mode at runtime by using a
+SET [GLOBAL|SESSION] sql_mode='\fImodes\fR'
+statement to set the
+sql_mode
+system value. Setting the
+GLOBAL
+variable requires the
+SUPER
+privilege and affects the operation of all clients that connect from that time on. Setting the
+SESSION
+variable affects only the current client. Any client can change its own session
+sql_mode
+value at any time.
+.PP
+You can retrieve the current global or session
+sql_mode
+value with the following statements:
+.sp
+.RS 3n
+.nf
+SELECT @@global.sql_mode;
+SELECT @@session.sql_mode;
+.fi
+.RE
+.PP
+The most important
+sql_mode
+values are probably these:
+.TP 3n
+\(bu
+ANSI
+.sp
+This mode changes syntax and behavior to conform more closely to standard SQL.
+.TP 3n
+\(bu
+STRICT_TRANS_TABLES
+.sp
+If a value could not be inserted as given into a transactional table, abort the statement. For a 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)
+.TP 3n
+\(bu
+TRADITIONAL
+.sp
+Make MySQL behave like a
+\(lqtraditional\(rq
+SQL database system. A simple description of this mode is
+\(lqgive an error instead of a warning\(rq
+when inserting an incorrect value into a column.
+.sp
+.it 1 an-trap
+.nr an-no-space-flag 1
+.nr an-break-flag 1
+.br
+\fBNote\fR
+The
+INSERT/UPDATE
+aborts as soon as the error is noticed. This may not be what you want if you are using a non\-transactional storage engine, because data changes made prior to the error may not be rolled back, resulting in a
+\(lqpartially done\(rq
+update. (Added in MySQL 5.0.2)
+.sp
+.RE
+.PP
+When this manual refers to
+\(lqstrict mode,\(rq
+it means a mode where at least one of
+STRICT_TRANS_TABLES
+or
+STRICT_ALL_TABLES
+is enabled.
+.PP
+The following list describes all supported modes:
+.TP 3n
+\(bu
+ALLOW_INVALID_DATES
+.sp
+Don't do full checking of dates. Check only that the month is in the range from 1 to 12 and the day is in the range from 1 to 31. This is very convenient for Web applications where you obtain year, month, and day in three different fields and you want to store exactly what the user inserted (without date validation). This mode applies to
+DATE
+and
+DATETIME
+columns. It does not apply
+TIMESTAMP
+columns, which always require a valid date.
+.sp
+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, the server requires that month and day values be legal, and not merely in the range 1 to 12 and 1 to 31, respectively. With strict mode disabled, invalid dates such as
+\'2004\-04\-31'
+are converted to
+\'0000\-00\-00'
+and a warning is generated. With strict mode enabled, invalid dates generate an error. To allow such dates, enable
+ALLOW_INVALID_DATES.
+.TP 3n
+\(bu
+ANSI_QUOTES
+.sp
+Treat
+\(lq"\(rq
+as an identifier quote character (like the
+\(lq`\(rq
+quote character) and not as a string quote character. You can still use
+\(lq`\(rq
+to quote identifiers with this mode enabled. With
+ANSI_QUOTES
+enabled, you cannot use double quotes to quote literal strings, because it is interpreted as an identifier.
+.TP 3n
+\(bu
+ERROR_FOR_DIVISION_BY_ZERO
+.sp
+Produce an error in strict mode (otherwise a warning) when a division by zero (or
+MOD(X,0)) occurs during an
+INSERT
+or
+UPDATE. If this mode is not enabled, MySQL instead returns
+NULL
+for divisions by zero. For
+INSERT IGNORE
+or
+UPDATE IGNORE, MySQL generates a warning for divisions by zero, but the result of the operation is
+NULL. (Implemented in MySQL 5.0.2)
+.TP 3n
+\(bu
+HIGH_NOT_PRECEDENCE
+.sp
+From MySQL 5.0.2 on, the precedence of the
+NOT
+operator is such that expressions such as
+NOT a BETWEEN b AND c
+are parsed as
+NOT (a BETWEEN b AND c). Before MySQL 5.0.2, the expression is parsed as
+(NOT a) BETWEEN b AND c. The old higher\-precedence behavior can be obtained by enabling the
+HIGH_NOT_PRECEDENCE
+SQL mode. (Added in MySQL 5.0.2)
+.sp
+.RS 3n
+.nf
+mysql> \fBSET sql_mode = '';\fR
+mysql> \fBSELECT NOT 1 BETWEEN \-5 AND 5;\fR
+ \-> 0
+mysql> \fBSET sql_mode = 'HIGH_NOT_PRECEDENCE';\fR
+mysql> \fBSELECT NOT 1 BETWEEN \-5 AND 5;\fR
+ \-> 1
+.fi
+.RE
+.TP 3n
+\(bu
+IGNORE_SPACE
+.sp
+Allow spaces between a function name and the
+\(lq(\(rq
+character. This causes built\-in function names to be treated as reserved words. As a result, identifiers that are the same as function names must be quoted as described in
+Section\ 2, \(lqSchema Object Names\(rq. For example, because there is a
+\fBCOUNT()\fR
+function, the use of
+count
+as a table name in the following statement causes an error:
+.sp
+.RS 3n
+.nf
+mysql> \fBCREATE TABLE count (i INT);\fR
+ERROR 1064 (42000): You have an error in your SQL syntax
+.fi
+.RE
+The table name should be quoted:
+.sp
+.RS 3n
+.nf
+mysql> \fBCREATE TABLE `count` (i INT);\fR
+Query OK, 0 rows affected (0.00 sec)
+.fi
+.RE
+The
+IGNORE_SPACE
+SQL mode applies to built\-in functions, not to user\-defined functions or stored functions. It is always allowable to have spaces after a UDF or stored function name, regardless of whether
+IGNORE_SPACE
+is enabled.
+.sp
+For further discussion of
+IGNORE_SPACE, see
+Section\ 2.3, \(lqFunction Name Parsing and Resolution\(rq.
+.TP 3n
+\(bu
+NO_AUTO_CREATE_USER
+.sp
+Prevent the
+GRANT
+statement from automatically creating new users if it would otherwise do so, unless a non\-empty password also is specified. (Added in MySQL 5.0.2)
+.TP 3n
+\(bu
+NO_AUTO_VALUE_ON_ZERO
+.sp
+NO_AUTO_VALUE_ON_ZERO
+affects handling of
+AUTO_INCREMENT
+columns. Normally, you generate the next sequence number for the column by inserting either
+NULL
+or
+0
+into it.
+NO_AUTO_VALUE_ON_ZERO
+suppresses this behavior for
+0
+so that only
+NULL
+generates the next sequence number.
+.sp
+This mode can be useful if
+0
+has been stored in a table's
+AUTO_INCREMENT
+column. (Storing
+0
+is not a recommended practice, by the way.) For example, if you dump the table with
+\fBmysqldump\fR
+and then reload it, MySQL normally generates new sequence numbers when it encounters the
+0
+values, resulting in a table with contents different from the one that was dumped. Enabling
+NO_AUTO_VALUE_ON_ZERO
+before reloading the dump file solves this problem.
+\fBmysqldump\fR
+now automatically includes in its output a statement that enables
+NO_AUTO_VALUE_ON_ZERO, to avoid this problem.
+.TP 3n
+\(bu
+NO_BACKSLASH_ESCAPES
+.sp
+Disable the use of the backslash character (\(lq\\\(rq) as an escape character within strings. With this mode enabled, backslash becomes an ordinary character like any other. (Implemented in MySQL 5.0.1)
+.TP 3n
+\(bu
+NO_DIR_IN_CREATE
+.sp
+When creating a table, ignore all
+INDEX DIRECTORY
+and
+DATA DIRECTORY
+directives. This option is useful on slave replication servers.
+.TP 3n
+\(bu
+NO_ENGINE_SUBSTITUTION
+.sp
+Control automatic substitution of the default storage engine when a statement such as
+CREATE TABLE
+or
+ALTER TABLE
+specifies a storage engine that is disabled or not compiled in. (Implemented in MySQL 5.0.8)
+.sp
+With
+NO_ENGINE_SUBSTITUTION
+disabled, the default engine is used and a warning occurs if the desired engine is known but disabled or not compiled in. If the desired engine is invalid (not a known engine name), an error occurs and the table is not created or altered.
+.sp
+With
+NO_ENGINE_SUBSTITUTION
+enabled, an error occurs and the table is not created or altered if the desired engine is unavailable for any reason (whether disabled or invalid).
+.TP 3n
+\(bu
+NO_FIELD_OPTIONS
+.sp
+Do not print MySQL\-specific column options in the output of
+SHOW CREATE TABLE. This mode is used by
+\fBmysqldump\fR
+in portability mode.
+.TP 3n
+\(bu
+NO_KEY_OPTIONS
+.sp
+Do not print MySQL\-specific index options in the output of
+SHOW CREATE TABLE. This mode is used by
+\fBmysqldump\fR
+in portability mode.
+.TP 3n
+\(bu
+NO_TABLE_OPTIONS
+.sp
+Do not print MySQL\-specific table options (such as
+ENGINE) in the output of
+SHOW CREATE TABLE. This mode is used by
+\fBmysqldump\fR
+in portability mode.
+.TP 3n
+\(bu
+NO_UNSIGNED_SUBTRACTION
+.sp
+In integer subtraction operations, do not mark the result as
+UNSIGNED
+if one of the operands is unsigned. In other words,
+\fIthe result of a subtraction is always signed whenever this mode is in effect, even if one of the operands is unsigned\fR. For example, compare the type of column
+c2
+in table
+t1
+with that of column
+c2
+in table
+t2:
+.sp
+.RS 3n
+.nf
+mysql> \fBSET SQL_MODE='';\fR
+mysql> \fBCREATE TABLE test (c1 BIGINT UNSIGNED NOT NULL);\fR
+mysql> \fBCREATE TABLE t1 SELECT c1 \- 1 AS c2 FROM test;\fR
+mysql> \fBDESCRIBE t1;\fR
++\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-+\-\-\-\-\-+\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-+
+| Field | Type | Null | Key | Default | Extra |
++\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-+\-\-\-\-\-+\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-+
+| c2 | bigint(21) unsigned | | | 0 | |
++\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-+\-\-\-\-\-+\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-+
+mysql> \fBSET SQL_MODE='NO_UNSIGNED_SUBTRACTION';\fR
+mysql> \fBCREATE TABLE t2 SELECT c1 \- 1 AS c2 FROM test;\fR
+mysql> \fBDESCRIBE t2;\fR
++\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-+\-\-\-\-\-+\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-+
+| Field | Type | Null | Key | Default | Extra |
++\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-+\-\-\-\-\-+\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-+
+| c2 | bigint(21) | | | 0 | |
++\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-+\-\-\-\-\-+\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-+
+.fi
+.RE
+Note that this means that
+BIGINT UNSIGNED
+is not 100% usable in all contexts. See
+Section\ 9, \(lqCast Functions and Operators\(rq.
+.sp
+.RS 3n
+.nf
+mysql> \fBSET SQL_MODE = '';\fR
+mysql> \fBSELECT CAST(0 AS UNSIGNED) \- 1;\fR
++\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+
+| CAST(0 AS UNSIGNED) \- 1 |
++\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+
+| 18446744073709551615 |
++\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+
+mysql> \fBSET SQL_MODE = 'NO_UNSIGNED_SUBTRACTION';\fR
+mysql> \fBSELECT CAST(0 AS UNSIGNED) \- 1;\fR
++\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+
+| CAST(0 AS UNSIGNED) \- 1 |
++\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+
+| \-1 |
++\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+
+.fi
+.RE
+.TP 3n
+\(bu
+NO_ZERO_DATE
+.sp
+In strict mode, don't allow
+\'0000\-00\-00'
+as a valid date. You can still insert zero dates with the
+IGNORE
+option. When not in strict mode, the date is accepted but a warning is generated. (Added in MySQL 5.0.2)
+.TP 3n
+\(bu
+NO_ZERO_IN_DATE
+.sp
+In strict mode, don't accept dates where the month or day part is 0. If used with the
+IGNORE
+option, MySQL inserts a
+\'0000\-00\-00'
+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)
+.TP 3n
+\(bu
+ONLY_FULL_GROUP_BY
+.sp
+Do not allow queries for which the
+SELECT
+list refers to non\-aggregated columns that are not named in the
+GROUP BY
+clause. The following query is invalid with this mode enabled because
+address
+is not named in the
+GROUP BY
+clause:
+.sp
+.RS 3n
+.nf
+SELECT name, address, MAX(age) FROM t GROUP BY name;
+.fi
+.RE
+As of MySQL 5.0.23, this mode also restricts references to non\-aggregated columns in the
+HAVING
+clause that are not named in the
+GROUP BY
+clause.
+.TP 3n
+\(bu
+PIPES_AS_CONCAT
+.sp
+Treat
+||
+as a string concatenation operator (same as
+CONCAT()) rather than as a synonym for
+OR.
+.TP 3n
+\(bu
+REAL_AS_FLOAT
+.sp
+Treat
+REAL
+as a synonym for
+FLOAT. By default, MySQL treats
+REAL
+as a synonym for
+DOUBLE.
+.TP 3n
+\(bu
+STRICT_ALL_TABLES
+.sp
+Enable strict mode for all storage engines. Invalid data values are rejected. Additional detail follows. (Added in MySQL 5.0.2)
+.TP 3n
+\(bu
+STRICT_TRANS_TABLES
+.sp
+Enable strict mode for transactional storage engines, and when possible for non\-transactional storage engines. Additional details follow. (Implemented in MySQL 5.0.2)
+.sp
+.RE
+.PP
+Strict mode controls how MySQL handles input values that are invalid or missing. A value can be invalid for several reasons. For example, it might have the wrong data type for the column, or it might be out of range. A value is missing when a new row to be inserted does not contain a value for a non\-NULL
+column that has no explicit
+DEFAULT
+clause in its definition. (For a
+NULL
+column,
+NULL
+is inserted if the value is missing.)
+.PP
+For transactional tables, an error occurs for invalid or missing values in a statement when either of the
+STRICT_ALL_TABLES
+or
+STRICT_TRANS_TABLES
+modes are enabled. The statement is aborted and rolled back.
+.PP
+For non\-transactional tables, the behavior is the same for either mode, if the bad value occurs in the first row to be inserted or updated. The statement is aborted and the table remains unchanged. If the statement inserts or modifies multiple rows and the bad value occurs in the second or later row, the result depends on which strict option is enabled:
+.TP 3n
+\(bu
+For
+STRICT_ALL_TABLES, MySQL returns an error and ignores the rest of the rows. However, in this case, the earlier rows still have been inserted or updated. This means that you might get a partial update, which might not be what you want. To avoid this, it's best to use single\-row statements because these can be aborted without changing the table.
+.TP 3n
+\(bu
+For
+STRICT_TRANS_TABLES, MySQL converts an invalid value to the closest valid value for the column and insert the adjusted value. If a value is missing, MySQL inserts the implicit default value for the column data type. In either case, MySQL generates a warning rather than an error and continues processing the statement. Implicit defaults are described in
+Section\ 1.4, \(lqData Type Default Values\(rq.
+.sp
+.RE
+.PP
+Strict mode disallows invalid date values such as
+\'2004\-04\-31'. It does not disallow dates with zero parts such as
+\'2004\-04\-00'
+or
+\(lqzero\(rq
+dates. To disallow these as well, enable the
+NO_ZERO_IN_DATE
+and
+NO_ZERO_DATE
+SQL modes in addition to strict mode.
+.PP
+If you are not using strict mode (that is, neither
+STRICT_TRANS_TABLES
+nor
+STRICT_ALL_TABLES
+is enabled), MySQL inserts adjusted values for invalid or missing values and produces warnings. In strict mode, you can produce this behavior by using
+INSERT IGNORE
+or
+UPDATE IGNORE. See
+Section\ 5.4.28, \(lqSHOW WARNINGS Syntax\(rq.
+.PP
+The following special modes are provided as shorthand for combinations of mode values from the preceding list. All are available in MySQL 5.0 beginning with version 5.0.0, except for
+TRADITIONAL, which was implemented in MySQL 5.0.2.
+.PP
+The descriptions include all mode values that are available in the most recent version of MySQL. For older versions, a combination mode does not include individual mode values that are not available except in newer versions.
+.TP 3n
+\(bu
+ANSI
+.sp
+Equivalent to
+REAL_AS_FLOAT,
+PIPES_AS_CONCAT,
+ANSI_QUOTES,
+IGNORE_SPACE. Before MySQL 5.0.3,
+ANSI
+also includes
+ONLY_FULL_GROUP_BY.
+.sp
+As of MySQL 5.0.40,
+ANSI
+mode also causes the server to return an error for queries where a set function
+\fIS\fR
+with an outer reference
+\fIS\fR(\fIouter_ref\fR)
+cannot be aggregated in the outer query against which the outer reference has been resolved. This is such a query:
+.sp
+.RS 3n
+.nf
+SELECT * FROM t1 WHERE t1.a IN (SELECT MAX(t1.b) FROM t2 WHERE ...);
+.fi
+.RE
+Here,
+\fBMAX(t1.b)\fR
+cannot aggregated in the outer query because it appears in the
+WHERE
+clause of that query. Standard SQL requires an error in this situation. If
+ANSI
+mode is not enabled, the server treats
+\fIS\fR(\fIouter_ref\fR)
+in such queries the same way that it would interpret
+\fIS\fR(\fIconst\fR), as was always done prior to 5.0.40.
+.sp
+See
+Section\ 8.3, \(lqRunning MySQL in ANSI Mode\(rq.
+.TP 3n
+\(bu
+DB2
+.sp
+Equivalent to
+PIPES_AS_CONCAT,
+ANSI_QUOTES,
+IGNORE_SPACE,
+NO_KEY_OPTIONS,
+NO_TABLE_OPTIONS,
+NO_FIELD_OPTIONS.
+.TP 3n
+\(bu
+MAXDB
+.sp
+Equivalent to
+PIPES_AS_CONCAT,
+ANSI_QUOTES,
+IGNORE_SPACE,
+NO_KEY_OPTIONS,
+NO_TABLE_OPTIONS,
+NO_FIELD_OPTIONS,
+NO_AUTO_CREATE_USER.
+.TP 3n
+\(bu
+MSSQL
+.sp
+Equivalent to
+PIPES_AS_CONCAT,
+ANSI_QUOTES,
+IGNORE_SPACE,
+NO_KEY_OPTIONS,
+NO_TABLE_OPTIONS,
+NO_FIELD_OPTIONS.
+.TP 3n
+\(bu
+MYSQL323
+.sp
+Equivalent to
+NO_FIELD_OPTIONS,
+HIGH_NOT_PRECEDENCE.
+.TP 3n
+\(bu
+MYSQL40
+.sp
+Equivalent to
+NO_FIELD_OPTIONS,
+HIGH_NOT_PRECEDENCE.
+.TP 3n
+\(bu
+ORACLE
+.sp
+Equivalent to
+PIPES_AS_CONCAT,
+ANSI_QUOTES,
+IGNORE_SPACE,
+NO_KEY_OPTIONS,
+NO_TABLE_OPTIONS,
+NO_FIELD_OPTIONS,
+NO_AUTO_CREATE_USER.
+.TP 3n
+\(bu
+POSTGRESQL
+.sp
+Equivalent to
+PIPES_AS_CONCAT,
+ANSI_QUOTES,
+IGNORE_SPACE,
+NO_KEY_OPTIONS,
+NO_TABLE_OPTIONS,
+NO_FIELD_OPTIONS.
+.TP 3n
+\(bu
+TRADITIONAL
+.sp
+Equivalent to
+STRICT_TRANS_TABLES,
+STRICT_ALL_TABLES,
+NO_ZERO_IN_DATE,
+NO_ZERO_DATE,
+ERROR_FOR_DIVISION_BY_ZERO,
+NO_AUTO_CREATE_USER.
+.SH "THE SHUTDOWN PROCESS"
+.PP
+The server shutdown process takes place as follows:
+.TP 3n
+1.
+The shutdown process is initiated.
+.sp
+Server shutdown can be initiated several ways. For example, a user with the
+SHUTDOWN
+privilege can execute a
+\fBmysqladmin shutdown\fR
+command.
+\fBmysqladmin\fR
+can be used on any platform supported by MySQL. Other operating system\-specific shutdown initiation methods are possible as well: The server shuts down on Unix when it receives a
+SIGTERM
+signal. A server running as a service on Windows shuts down when the services manager tells it to.
+.TP 3n
+2.
+The server creates a shutdown thread if necessary.
+.sp
+Depending on how shutdown was initiated, the server might create a thread to handle the shutdown process. If shutdown was requested by a client, a shutdown thread is created. If shutdown is the result of receiving a
+SIGTERM
+signal, the signal thread might handle shutdown itself, or it might create a separate thread to do so. If the server tries to create a shutdown thread and cannot (for example, if memory is exhausted), it issues a diagnostic message that appears in the error log:
+.sp
+.RS 3n
+.nf
+Error: Can't create thread to kill server
+.fi
+.RE
+.TP 3n
+3.
+The server stops accepting new connections.
+.sp
+To prevent new activity from being initiated during shutdown, the server stops accepting new client connections. It does this by closing the network connections to which it normally listens for connections: the TCP/IP port, the Unix socket file, the Windows named pipe, and shared memory on Windows.
+.TP 3n
+4.
+The server terminates current activity.
+.sp
+For each thread that is associated with a client connection, the connection to the client is broken and the thread is marked as killed. Threads die when they notice that they are so marked. Threads for idle connections die quickly. Threads that currently are processing statements check their state periodically and take longer to die. For additional information about thread termination, see
+Section\ 5.5.3, \(lqKILL Syntax\(rq, in particular for the instructions about killed
+REPAIR TABLE
+or
+OPTIMIZE TABLE
+operations on
+MyISAM
+tables.
+.sp
+For threads that have an open transaction, the transaction is rolled back. Note that if a thread is updating a non\-transactional table, an operation such as a multiple\-row
+UPDATE
+or
+INSERT
+may leave the table partially updated, because the operation can terminate before completion.
+.sp
+If the server is a master replication server, threads associated with currently connected slaves are treated like other client threads. That is, each one is marked as killed and exits when it next checks its state.
+.sp
+If the server is a slave replication server, the I/O and SQL threads, if active, are stopped before client threads are marked as killed. The SQL thread is allowed to finish its current statement (to avoid causing replication problems), and then stops. If the SQL thread was in the middle of a transaction at this point, the transaction is rolled back.
+.TP 3n
+5.
+Storage engines are shut down or closed.
+.sp
+At this stage, the table cache is flushed and all open tables are closed.
+.sp
+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
+innodb_fast_shutdown
+is 2), writes the current LSN to the tablespace, and terminates its own internal threads.
+.TP 3n
+6.
+The server exits.
+.SH "SERVER\-SIDE HELP"
+.PP
+MySQL Server supports a
+HELP
+statement that returns online information from the MySQL Reference manual (see
+Section\ 3.2, \(lqHELP Syntax\(rq). The proper operation of this statement requires that the help tables in the
+mysql
+database be initialized with help topic information, which is done by processing the contents of the
+\fIfill_help_tables.sql\fR
+script.
+.PP
+For a MySQL binary distribution on Unix, help table setup occurs when you run
+\fBmysql_install_db\fR. For an RPM distribution on Linux or binary distribution on Windows, help table setup occurs as part of the MySQL installation process.
+.PP
+For a MySQL source distribution, you can find the
+\fIfill_help_tables.sql\fR
+file in the
+\fIscripts\fR
+directory. To load the file manually, make sure that you have initialized the
+mysql
+database by running
+\fBmysql_install_db\fR, and then process the file with the
+\fBmysql\fR
+client as follows:
+.sp
+.RS 3n
+.nf
+shell> \fBmysql \-u root mysql < fill_help_tables.sql\fR
+.fi
+.RE
+.PP
+If you are working with BitKeeper and a MySQL development source tree, the tree doesn't contain
+\fIfill_help_tables.sql\fR. You can download the proper file for your version of MySQL from
+\fI\%http://dev.mysql.com/doc/\fR. After downloading and uncompressing the file, process it with
+\fBmysql\fR
+as just described.
+.SH "COPYRIGHT"
+.PP
+Copyright 2007 MySQL AB
+.PP
+This documentation is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License.
+.PP
+This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
+.PP
+You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110\-1301 USA or see http://www.gnu.org/licenses/.
+.PP
+Please email
+<docs at mysql.com>
+for more information or if you are interested in doing a translation.
+.SH "REFERENCES"
+.TP 3
+1.\ MySQL Internals: Porting
+\%http://forge.mysql.com/wiki/MySQL_Internals_Porting
+.TP 3
+2.\ Auto\-Increment in Multiple\-Master Replication
+\%http://dev.mysql.com/doc/refman/5.0/en/replication\-auto\-increment.html
+.SH "SEE ALSO"
+For more information, please refer to the MySQL Reference Manual,
+which may already be installed locally and which is also available
+online at http://dev.mysql.com/doc/.
+.SH AUTHOR
+MySQL AB (http://www.mysql.com/).
Added: branches/sid-5.0/debian/manpages/mysqld_multi.1
===================================================================
--- branches/sid-5.0/debian/manpages/mysqld_multi.1 (rev 0)
+++ branches/sid-5.0/debian/manpages/mysqld_multi.1 2007-11-26 12:34:29 UTC (rev 1020)
@@ -0,0 +1,460 @@
+.\" Title: \fBmysqld_multi\fR
+.\" Author:
+.\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
+.\" Date: 11/25/2007
+.\" Manual: MySQL Database System
+.\" Source: MySQL 5.0
+.\"
+.TH "\fBMYSQLD_MULTI\fR" "1" "11/25/2007" "MySQL 5.0" "MySQL Database System"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
+.SH "NAME"
+mysqld_multi \- manage multiple MySQL servers
+.SH "SYNOPSIS"
+.HP 59
+\fBmysqld_multi [\fR\fB\fIoptions\fR\fR\fB] {start|stop|report} [\fR\fB\fIGNR\fR\fR\fB[,\fR\fB\fIGNR\fR\fR\fB] ...]\fR
+.SH "DESCRIPTION"
+.PP
+\fBmysqld_multi\fR
+is designed to manage several
+\fBmysqld\fR
+processes that listen for connections on different Unix socket files and TCP/IP ports. It can start or stop servers, or report their current status. The MySQL Instance Manager is an alternative means of managing multiple servers (see
+\fBmysqlmanager\fR(8)).
+.PP
+\fBmysqld_multi\fR
+searches for groups named
+[mysqld\fIN\fR]
+in
+\fImy.cnf\fR
+(or in the file named by the
+\fB\-\-config\-file\fR
+option).
+\fIN\fR
+can be any positive integer. This number is referred to in the following discussion as the option group number, or
+\fIGNR\fR. Group numbers distinguish option groups from one another and are used as arguments to
+\fBmysqld_multi\fR
+to specify which servers you want to start, stop, or obtain a status report for. Options listed in these groups are the same that you would use in the
+[mysqld]
+group used for starting
+\fBmysqld\fR. (See, for example,
+Section\ 4.16.2.2, \(lqStarting and Stopping MySQL Automatically\(rq.) However, when using multiple servers, it is necessary that each one use its own value for options such as the Unix socket file and TCP/IP port number. For more information on which options must be unique per server in a multiple\-server environment, see
+Section\ 9, \(lqRunning Multiple MySQL Servers on the Same Machine\(rq.
+.PP
+To invoke
+\fBmysqld_multi\fR, use the following syntax:
+.sp
+.RS 3n
+.nf
+shell> \fBmysqld_multi [\fR\fB\fIoptions\fR\fR\fB] {start|stop|report} [\fR\fB\fIGNR\fR\fR\fB[,\fR\fB\fIGNR\fR\fR\fB] ...]\fR
+.fi
+.RE
+.PP
+start,
+stop, and
+report
+indicate which operation to perform. You can perform the designated operation for a single server or multiple servers, depending on the
+\fIGNR\fR
+list that follows the option name. If there is no list,
+\fBmysqld_multi\fR
+performs the operation for all servers in the option file.
+.PP
+Each
+\fIGNR\fR
+value represents an option group number or range of group numbers. The value should be the number at the end of the group name in the option file. For example, the
+\fIGNR\fR
+for a group named
+[mysqld17]
+is
+17. To specify a range of numbers, separate the first and last numbers by a dash. The
+\fIGNR\fR
+value
+10\-13
+represents groups
+[mysqld10]
+through
+[mysqld13]. Multiple groups or group ranges can be specified on the command line, separated by commas. There must be no whitespace characters (spaces or tabs) in the
+\fIGNR\fR
+list; anything after a whitespace character is ignored.
+.PP
+This command starts a single server using option group
+[mysqld17]:
+.sp
+.RS 3n
+.nf
+shell> \fBmysqld_multi start 17\fR
+.fi
+.RE
+.PP
+This command stops several servers, using option groups
+[mysqld8]
+and
+[mysqld10]
+through
+[mysqld13]:
+.sp
+.RS 3n
+.nf
+shell> \fBmysqld_multi stop 8,10\-13\fR
+.fi
+.RE
+.PP
+For an example of how you might set up an option file, use this command:
+.sp
+.RS 3n
+.nf
+shell> \fBmysqld_multi \-\-example\fR
+.fi
+.RE
+.PP
+As of MySQL 5.0.42,
+\fBmysqld_multi\fR
+searches for option files as follows:
+.TP 3n
+\(bu
+With
+\fB\-\-no\-defaults\fR, no option files are read.
+.TP 3n
+\(bu
+With
+\fB\-\-defaults\-file=\fR\fB\fIfile_name\fR\fR, only the named file is read.
+.TP 3n
+\(bu
+Otherwise, option files in the standard list of locations are read, including any file named by the
+\fB\-\-defaults\-extra\-file=\fR\fB\fIfile_name\fR\fR
+option, if one is given. (If the option is given multiple times, the last value is used.)
+.sp
+.RE
+.PP
+Option files read are searched for
+[mysqld_multi]
+and
+[mysqld\fIN\fR]
+option groups.
+.PP
+Before MySQL 5.0.42, the preceding options are not recognized. Files in the standard locations are read, and any file named by the
+\fB\-\-config\-file=\fR\fB\fIfile_name\fR\fR
+option, if one is given. A file named by
+\fB\-\-config\-file\fR
+is read only for
+[mysqld\fIN\fR]
+option groups, not the
+[mysqld_multi]
+group.
+.PP
+\fBmysqld_multi\fR
+supports the following options:
+.TP 3n
+\(bu
+\fB\-\-help\fR
+.sp
+Display a help message and exit.
+.TP 3n
+\(bu
+\fB\-\-config\-file=\fR\fB\fIfile_name\fR\fR
+.sp
+As of MySQL 5.0.42, this option is deprecated. If given, it is treated the same way as
+\fB\-\-defaults\-extra\-file\fR, described earlier.
+.sp
+Before MySQL 5.0.42, this option specifies the name of an extra option file. It affects where
+\fBmysqld_multi\fR
+looks for
+[mysqld\fIN\fR]
+option groups. Without this option, all options are read from the usual
+\fImy.cnf\fR
+file. The option does not affect where
+\fBmysqld_multi\fR
+reads its own options, which are always taken from the
+[mysqld_multi]
+group in the usual
+\fImy.cnf\fR
+file.
+.TP 3n
+\(bu
+\fB\-\-example\fR
+.sp
+Display a sample option file.
+.TP 3n
+\(bu
+\fB\-\-log=\fR\fB\fIfile_name\fR\fR
+.sp
+Specify the name of the log file. If the file exists, log output is appended to it.
+.TP 3n
+\(bu
+\fB\-\-mysqladmin=\fR\fB\fIprog_name\fR\fR
+.sp
+The
+\fBmysqladmin\fR
+binary to be used to stop servers.
+.TP 3n
+\(bu
+\fB\-\-mysqld=\fR\fB\fIprog_name\fR\fR
+.sp
+The
+\fBmysqld\fR
+binary to be used. Note that you can specify
+\fBmysqld_safe\fR
+as the value for this option also. If you use
+\fBmysqld_safe\fR
+to start the server, you can include the
+mysqld
+or
+ledir
+options in the corresponding
+[mysqld\fIN\fR]
+option group. These options indicate the name of the server that
+\fBmysqld_safe\fR
+should start and the pathname of the directory where the server is located. (See the descriptions for these options in
+\fBmysqld_safe\fR(1).) Example:
+.sp
+.RS 3n
+.nf
+[mysqld38]
+mysqld = mysqld\-debug
+ledir = /opt/local/mysql/libexec
+.fi
+.RE
+.TP 3n
+\(bu
+\fB\-\-no\-log\fR
+.sp
+Print log information to
+stdout
+rather than to the log file. By default, output goes to the log file.
+.TP 3n
+\(bu
+\fB\-\-password=\fR\fB\fIpassword\fR\fR
+.sp
+The password of the MySQL account to use when invoking
+\fBmysqladmin\fR. Note that the password value is not optional for this option, unlike for other MySQL programs.
+.TP 3n
+\(bu
+\fB\-\-silent\fR
+.sp
+Silent mode; disable warnings.
+.TP 3n
+\(bu
+\fB\-\-tcp\-ip\fR
+.sp
+Connect to each MySQL server via the TCP/IP port instead of the Unix socket file. (If a socket file is missing, the server might still be running, but accessible only via the TCP/IP port.) By default, connections are made using the Unix socket file. This option affects
+stop
+and
+report
+operations.
+.TP 3n
+\(bu
+\fB\-\-user=\fR\fB\fIuser_name\fR\fR
+.sp
+The username of the MySQL account to use when invoking
+\fBmysqladmin\fR.
+.TP 3n
+\(bu
+\fB\-\-verbose\fR
+.sp
+Be more verbose.
+.TP 3n
+\(bu
+\fB\-\-version\fR
+.sp
+Display version information and exit.
+.sp
+.RE
+.PP
+Some notes about
+\fBmysqld_multi\fR:
+.TP 3n
+\(bu
+\fBMost important\fR: Before using
+\fBmysqld_multi\fR
+be sure that you understand the meanings of the options that are passed to the
+\fBmysqld\fR
+servers and
+\fIwhy\fR
+you would want to have separate
+\fBmysqld\fR
+processes. Beware of the dangers of using multiple
+\fBmysqld\fR
+servers with the same data directory. Use separate data directories, unless you
+\fIknow\fR
+what you are doing. Starting multiple servers with the same data directory does
+\fInot\fR
+give you extra performance in a threaded system. See
+Section\ 9, \(lqRunning Multiple MySQL Servers on the Same Machine\(rq.
+.TP 3n
+\(bu
+.sp
+.it 1 an-trap
+.nr an-no-space-flag 1
+.nr an-break-flag 1
+.br
+\fBImportant\fR
+Make sure that the data directory for each server is fully accessible to the Unix account that the specific
+\fBmysqld\fR
+process is started as.
+\fIDo not\fR
+use the Unix
+\fIroot\fR
+account for this, unless you
+\fIknow\fR
+what you are doing. See
+Section\ 4.5, \(lqHow to Run MySQL as a Normal User\(rq.
+.TP 3n
+\(bu
+Make sure that the MySQL account used for stopping the
+\fBmysqld\fR
+servers (with the
+\fBmysqladmin\fR
+program) has the same username and password for each server. Also, make sure that the account has the
+SHUTDOWN
+privilege. If the servers that you want to manage have different usernames or passwords for the administrative accounts, you might want to create an account on each server that has the same username and password. For example, you might set up a common
+multi_admin
+account by executing the following commands for each server:
+.sp
+.RS 3n
+.nf
+shell> \fBmysql \-u root \-S /tmp/mysql.sock \-p\fR
+Enter password:
+mysql> \fBGRANT SHUTDOWN ON *.*\fR
+ \-> \fBTO 'multi_admin'@'localhost' IDENTIFIED BY 'multipass';\fR
+.fi
+.RE
+See
+Section\ 5.2, \(lqHow the Privilege System Works\(rq. You have to do this for each
+\fBmysqld\fR
+server. Change the connection parameters appropriately when connecting to each one. Note that the hostname part of the account name must allow you to connect as
+multi_admin
+from the host where you want to run
+\fBmysqld_multi\fR.
+.TP 3n
+\(bu
+The Unix socket file and the TCP/IP port number must be different for every
+\fBmysqld\fR. (Alternatively, if the host has multiple network addresses, you can use
+\fB\-\-bind\-adress\fR
+to cause different servers to listen to different interfaces.)
+.TP 3n
+\(bu
+The
+\fB\-\-pid\-file\fR
+option is very important if you are using
+\fBmysqld_safe\fR
+to start
+\fBmysqld\fR
+(for example,
+\fB\-\-mysqld=mysqld_safe\fR) Every
+\fBmysqld\fR
+should have its own process ID file. The advantage of using
+\fBmysqld_safe\fR
+instead of
+\fBmysqld\fR
+is that
+\fBmysqld_safe\fR
+monitors its
+\fBmysqld\fR
+process and restarts it if the process terminates due to a signal sent using
+kill \-9
+or for other reasons, such as a segmentation fault. Please note that the
+\fBmysqld_safe\fR
+script might require that you start it from a certain place. This means that you might have to change location to a certain directory before running
+\fBmysqld_multi\fR. If you have problems starting, please see the
+\fBmysqld_safe\fR
+script. Check especially the lines:
+.sp
+.RS 3n
+.nf
+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
+MY_PWD=`pwd`
+# Check if we are starting this relative (for the binary release)
+if test \-d $MY_PWD/data/mysql \-a \-f ./share/mysql/english/errmsg.sys \-a \\
+ \-x ./bin/mysqld
+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
+.fi
+.RE
+The test performed by these lines should be successful, or you might encounter problems. See
+\fBmysqld_safe\fR(1).
+.TP 3n
+\(bu
+You might want to use the
+\fB\-\-user\fR
+option for
+\fBmysqld\fR, but to do this you need to run the
+\fBmysqld_multi\fR
+script as the Unix
+root
+user. Having the option in the option file doesn't matter; you just get a warning if you are not the superuser and the
+\fBmysqld\fR
+processes are started under your own Unix account.
+.sp
+.RE
+.PP
+The following example shows how you might set up an option file for use with
+\fBmysqld_multi\fR. The order in which the
+\fBmysqld\fR
+programs are started or stopped depends on the order in which they appear in the option file. Group numbers need not form an unbroken sequence. The first and fifth
+[mysqld\fIN\fR]
+groups were intentionally omitted from the example to illustrate that you can have
+\(lqgaps\(rq
+in the option file. This gives you more flexibility.
+.sp
+.RS 3n
+.nf
+# This file should probably be in your home dir (~/.my.cnf)
+# or /etc/my.cnf
+# Version 2.1 by Jani Tolonen
+[mysqld_multi]
+mysqld = /usr/local/bin/mysqld_safe
+mysqladmin = /usr/local/bin/mysqladmin
+user = multi_admin
+password = multipass
+[mysqld2]
+socket = /tmp/mysql.sock2
+port = 3307
+pid\-file = /usr/local/mysql/var2/hostname.pid2
+datadir = /usr/local/mysql/var2
+language = /usr/local/share/mysql/english
+user = john
+[mysqld3]
+socket = /tmp/mysql.sock3
+port = 3308
+pid\-file = /usr/local/mysql/var3/hostname.pid3
+datadir = /usr/local/mysql/var3
+language = /usr/local/share/mysql/swedish
+user = monty
+[mysqld4]
+socket = /tmp/mysql.sock4
+port = 3309
+pid\-file = /usr/local/mysql/var4/hostname.pid4
+datadir = /usr/local/mysql/var4
+language = /usr/local/share/mysql/estonia
+user = tonu
+[mysqld6]
+socket = /tmp/mysql.sock6
+port = 3311
+pid\-file = /usr/local/mysql/var6/hostname.pid6
+datadir = /usr/local/mysql/var6
+language = /usr/local/share/mysql/japanese
+user = jani
+.fi
+.RE
+.PP
+See
+Section\ 3.2, \(lqUsing Option Files\(rq.
+.SH "COPYRIGHT"
+.PP
+Copyright 2007 MySQL AB
+.PP
+This documentation is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License.
+.PP
+This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
+.PP
+You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110\-1301 USA or see http://www.gnu.org/licenses/.
+.PP
+Please email
+<docs at mysql.com>
+for more information or if you are interested in doing a translation.
+.SH "SEE ALSO"
+For more information, please refer to the MySQL Reference Manual,
+which may already be installed locally and which is also available
+online at http://dev.mysql.com/doc/.
+.SH AUTHOR
+MySQL AB (http://www.mysql.com/).
Added: branches/sid-5.0/debian/manpages/mysqld_safe.1
===================================================================
--- branches/sid-5.0/debian/manpages/mysqld_safe.1 (rev 0)
+++ branches/sid-5.0/debian/manpages/mysqld_safe.1 2007-11-26 12:34:29 UTC (rev 1020)
@@ -0,0 +1,446 @@
+.\" Title: \fBmysqld_safe\fR
+.\" Author:
+.\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
+.\" Date: 11/25/2007
+.\" Manual: MySQL Database System
+.\" Source: MySQL 5.0
+.\"
+.TH "\fBMYSQLD_SAFE\fR" "1" "11/25/2007" "MySQL 5.0" "MySQL Database System"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
+.SH "NAME"
+mysqld_safe \- MySQL server startup script
+.br
+safe_mysqld \- MySQL server startup script
+.SH "SYNOPSIS"
+.HP 20
+\fBmysqld_safe \fR\fB\fIoptions\fR\fR
+.SH "DESCRIPTION"
+.PP
+\fBmysqld_safe\fR
+is the recommended way to start a
+\fBmysqld\fR
+server on Unix and NetWare.
+\fBmysqld_safe\fR
+adds some safety features such as restarting the server when an error occurs and logging runtime information to an error log file. NetWare\-specific behaviors are listed later in this section.
+.sp
+.it 1 an-trap
+.nr an-no-space-flag 1
+.nr an-break-flag 1
+.br
+\fBNote\fR
+.PP
+To preserve backward compatibility with older versions of MySQL, MySQL binary distributions still include
+\fBsafe_mysqld\fR
+as a symbolic link to
+\fBmysqld_safe\fR. However, you should not rely on this because it is removed as of MySQL 5.1.
+.PP
+By default,
+\fBmysqld_safe\fR
+before MySQL 5.0.27 tries to start an executable named
+\fBmysqld\-max\fR
+if it exists, and
+\fBmysqld\fR
+otherwise. Be aware of the implications of this behavior:
+.TP 3n
+\(bu
+On Linux, the
+MySQL\-Max
+RPM relies on this
+\fBmysqld_safe\fR
+behavior. The RPM installs an executable named
+\fBmysqld\-max\fR, which causes
+\fBmysqld_safe\fR
+to automatically use that executable rather than
+\fBmysqld\fR
+from that point on.
+.TP 3n
+\(bu
+If you install a MySQL\-Max distribution that includes a server named
+\fBmysqld\-max\fR, and then upgrade later to a non\-Max version of MySQL,
+\fBmysqld_safe\fR
+will still attempt to run the old
+\fBmysqld\-max\fR
+server. If you perform such an upgrade, you should manually remove the old
+\fBmysqld\-max\fR
+server to ensure that
+\fBmysqld_safe\fR
+runs the new
+\fBmysqld\fR
+server.
+.sp
+.RE
+.PP
+To override the default behavior and specify explicitly the name of the server you want to run, specify a
+\fB\-\-mysqld\fR
+or
+\fB\-\-mysqld\-version\fR
+option to
+\fBmysqld_safe\fR. You can also use
+\fB\-\-ledir\fR
+to indicate the directory where
+\fBmysqld_safe\fR
+should look for the server.
+.PP
+Many of the options to
+\fBmysqld_safe\fR
+are the same as the options to
+\fBmysqld\fR. See
+the section called \(lqCOMMAND OPTIONS\(rq.
+.PP
+All options specified to
+\fBmysqld_safe\fR
+on the command line are passed to
+\fBmysqld\fR. If you want to use any options that are specific to
+\fBmysqld_safe\fR
+and that
+\fBmysqld\fR
+doesn't support, do not specify them on the command line. Instead, list them in the
+[mysqld_safe]
+group of an option file. See
+Section\ 3.2, \(lqUsing Option Files\(rq.
+.PP
+\fBmysqld_safe\fR
+reads all options from the
+[mysqld],
+[server], and
+[mysqld_safe]
+sections in option files. For example, if you specify a
+[mysqld]
+section like this,
+\fBmysqld_safe\fR
+will find and use the
+\fB\-\-log\-error\fR
+option:
+.sp
+.RS 3n
+.nf
+[mysqld]
+log\-error=error.log
+.fi
+.RE
+.PP
+For backward compatibility,
+\fBmysqld_safe\fR
+also reads
+[safe_mysqld]
+sections, although you should rename such sections to
+[mysqld_safe]
+in MySQL 5.0 installations.
+.PP
+\fBmysqld_safe\fR
+supports the following options:
+.TP 3n
+\(bu
+\fB\-\-help\fR
+.sp
+Display a help message and exit. (Added in MySQL 5.0.3)
+.TP 3n
+\(bu
+\fB\-\-autoclose\fR
+.sp
+(NetWare only) On NetWare,
+\fBmysqld_safe\fR
+provides a screen presence. When you unload (shut down) the
+\fBmysqld_safe\fR
+NLM, the screen does not by default go away. Instead, it prompts for user input:
+.sp
+.RS 3n
+.nf
+*<NLM has terminated; Press any key to close the screen>*
+.fi
+.RE
+If you want NetWare to close the screen automatically instead, use the
+\fB\-\-autoclose\fR
+option to
+\fBmysqld_safe\fR.
+.TP 3n
+\(bu
+\fB\-\-basedir=\fR\fB\fIpath\fR\fR
+.sp
+The path to the MySQL installation directory.
+.TP 3n
+\(bu
+\fB\-\-core\-file\-size=\fR\fB\fIsize\fR\fR
+.sp
+The size of the core file that
+\fBmysqld\fR
+should be able to create. The option value is passed to
+\fBulimit \-c\fR.
+.TP 3n
+\(bu
+\fB\-\-datadir=\fR\fB\fIpath\fR\fR
+.sp
+The path to the data directory.
+.TP 3n
+\(bu
+\fB\-\-defaults\-extra\-file=\fR\fB\fIpath\fR\fR
+.sp
+The name of an option file to be read in addition to the usual option files. This must be the first option on the command line if it is used. As of MySQL 5.0.6, if the file does not exist or is otherwise inaccessible, the server will exit with an error.
+.TP 3n
+\(bu
+\fB\-\-defaults\-file=\fR\fB\fIfile_name\fR\fR
+.sp
+The name of an option file to be read instead of the usual option files. This must be the first option on the command line if it is used.
+.TP 3n
+\(bu
+\fB\-\-ledir=\fR\fB\fIpath\fR\fR
+.sp
+If
+\fBmysqld_safe\fR
+cannot find the server, use this option to indicate the pathname to the directory where the server is located.
+.TP 3n
+\(bu
+\fB\-\-log\-error=\fR\fB\fIfile_name\fR\fR
+.sp
+Write the error log to the given file. See
+Section\ 8.1, \(lqThe Error Log\(rq.
+.TP 3n
+\(bu
+\fB\-\-mysqld=\fR\fB\fIprog_name\fR\fR
+.sp
+The name of the server program (in the
+ledir
+directory) that you want to start. This option is needed if you use the MySQL binary distribution but have the data directory outside of the binary distribution. If
+\fBmysqld_safe\fR
+cannot find the server, use the
+\fB\-\-ledir\fR
+option to indicate the pathname to the directory where the server is located.
+.TP 3n
+\(bu
+\fB\-\-mysqld\-version=\fR\fB\fIsuffix\fR\fR
+.sp
+This option is similar to the
+\fB\-\-mysqld\fR
+option, but you specify only the suffix for the server program name. The basename is assumed to be
+\fBmysqld\fR. For example, if you use
+\fB\-\-mysqld\-version=debug\fR,
+\fBmysqld_safe\fR
+starts the
+\fBmysqld\-debug\fR
+program in the
+ledir
+directory. If the argument to
+\fB\-\-mysqld\-version\fR
+is empty,
+\fBmysqld_safe\fR
+uses
+\fBmysqld\fR
+in the
+ledir
+directory.
+.TP 3n
+\(bu
+\fB\-\-nice=\fR\fB\fIpriority\fR\fR
+.sp
+Use the
+nice
+program to set the server's scheduling priority to the given value.
+.TP 3n
+\(bu
+\fB\-\-no\-defaults\fR
+.sp
+Do not read any option files. This must be the first option on the command line if it is used.
+.TP 3n
+\(bu
+\fB\-\-open\-files\-limit=\fR\fB\fIcount\fR\fR
+.sp
+The number of files that
+\fBmysqld\fR
+should be able to open. The option value is passed to
+\fBulimit \-n\fR. Note that you need to start
+\fBmysqld_safe\fR
+as
+root
+for this to work properly!
+.TP 3n
+\(bu
+\fB\-\-pid\-file=\fR\fB\fIfile_name\fR\fR
+.sp
+The pathname of the process ID file.
+.TP 3n
+\(bu
+\fB\-\-port=\fR\fB\fIport_num\fR\fR
+.sp
+The port number that the server should use when listening for TCP/IP connections. The port number must be 1024 or higher unless the server is started by the
+root
+system user.
+.TP 3n
+\(bu
+\fB\-\-skip\-kill\-mysqld\fR
+.sp
+Do not try to kill stray
+\fBmysqld\fR
+processes at startup. This option works only on Linux.
+.TP 3n
+\(bu
+\fB\-\-socket=\fR\fB\fIpath\fR\fR
+.sp
+The Unix socket file that the server should use when listening for local connections.
+.TP 3n
+\(bu
+\fB\-\-timezone=\fR\fB\fItimezone\fR\fR
+.sp
+Set the
+TZ
+time zone environment variable to the given option value. Consult your operating system documentation for legal time zone specification formats.
+.TP 3n
+\(bu
+\fB\-\-user={\fR\fB\fIuser_name\fR\fR\fB|\fR\fB\fIuser_id\fR\fR\fB}\fR
+.sp
+Run the
+\fBmysqld\fR
+server as the user having the name
+\fIuser_name\fR
+or the numeric user ID
+\fIuser_id\fR. (\(lqUser\(rq
+in this context refers to a system login account, not a MySQL user listed in the grant tables.)
+.sp
+.RE
+.PP
+If you execute
+\fBmysqld_safe\fR
+with the
+\fB\-\-defaults\-file\fR
+or
+\fB\-\-defaults\-extra\-option\fR
+option to name an option file, the option must be the first one given on the command line or the option file will not be used. For example, this command will not use the named option file:
+.sp
+.RS 3n
+.nf
+mysql> \fBmysqld_safe \-\-port=\fR\fB\fIport_num\fR\fR\fB \-\-defaults\-file=\fR\fB\fIfile_name\fR\fR
+.fi
+.RE
+.PP
+Instead, use the following command:
+.sp
+.RS 3n
+.nf
+mysql> \fBmysqld_safe \-\-defaults\-file=\fR\fB\fIfile_name\fR\fR\fB \-\-port=\fR\fB\fIport_num\fR\fR
+.fi
+.RE
+.PP
+The
+\fBmysqld_safe\fR
+script is written so that it normally can start a server that was installed from either a source or a binary distribution of MySQL, even though these types of distributions typically install the server in slightly different locations. (See
+Section\ 4.6, \(lqInstallation Layouts\(rq.)
+\fBmysqld_safe\fR
+expects one of the following conditions to be true:
+.TP 3n
+\(bu
+The server and databases can be found relative to the working directory (the directory from which
+\fBmysqld_safe\fR
+is invoked). For binary distributions,
+\fBmysqld_safe\fR
+looks under its working directory for
+\fIbin\fR
+and
+\fIdata\fR
+directories. For source distributions, it looks for
+\fIlibexec\fR
+and
+\fIvar\fR
+directories. This condition should be met if you execute
+\fBmysqld_safe\fR
+from your MySQL installation directory (for example,
+\fI/usr/local/mysql\fR
+for a binary distribution).
+.TP 3n
+\(bu
+If the server and databases cannot be found relative to the working directory,
+\fBmysqld_safe\fR
+attempts to locate them by absolute pathnames. Typical locations are
+\fI/usr/local/libexec\fR
+and
+\fI/usr/local/var\fR. The actual locations are determined from the values configured into the distribution at the time it was built. They should be correct if MySQL is installed in the location specified at configuration time.
+.sp
+.RE
+.PP
+Because
+\fBmysqld_safe\fR
+tries to find the server and databases relative to its own working directory, you can install a binary distribution of MySQL anywhere, as long as you run
+\fBmysqld_safe\fR
+from the MySQL installation directory:
+.sp
+.RS 3n
+.nf
+shell> \fBcd \fR\fB\fImysql_installation_directory\fR\fR
+shell> \fBbin/mysqld_safe &\fR
+.fi
+.RE
+.PP
+If
+\fBmysqld_safe\fR
+fails, even when invoked from the MySQL installation directory, you can specify the
+\fB\-\-ledir\fR
+and
+\fB\-\-datadir\fR
+options to indicate the directories in which the server and databases are located on your system.
+.PP
+Normally, you should not edit the
+\fBmysqld_safe\fR
+script. Instead, configure
+\fBmysqld_safe\fR
+by using command\-line options or options in the
+[mysqld_safe]
+section of a
+\fImy.cnf\fR
+option file. In rare cases, it might be necessary to edit
+\fBmysqld_safe\fR
+to get it to start the server properly. However, if you do this, your modified version of
+\fBmysqld_safe\fR
+might be overwritten if you upgrade MySQL in the future, so you should make a copy of your edited version that you can reinstall.
+.PP
+On NetWare,
+\fBmysqld_safe\fR
+is a NetWare Loadable Module (NLM) that is ported from the original Unix shell script. It starts the server as follows:
+.TP 3n
+1.
+Runs a number of system and option checks.
+.TP 3n
+2.
+Runs a check on
+MyISAM
+tables.
+.TP 3n
+3.
+Provides a screen presence for the MySQL server.
+.TP 3n
+4.
+Starts
+\fBmysqld\fR, monitors it, and restarts it if it terminates in error.
+.TP 3n
+5.
+Sends error messages from
+\fBmysqld\fR
+to the
+\fI\fIhost_name\fR\fR\fI.err\fR
+file in the data directory.
+.TP 3n
+6.
+Sends
+\fBmysqld_safe\fR
+screen output to the
+\fI\fIhost_name\fR\fR\fI.safe\fR
+file in the data directory.
+.SH "COPYRIGHT"
+.PP
+Copyright 2007 MySQL AB
+.PP
+This documentation is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License.
+.PP
+This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
+.PP
+You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110\-1301 USA or see http://www.gnu.org/licenses/.
+.PP
+Please email
+<docs at mysql.com>
+for more information or if you are interested in doing a translation.
+.SH "SEE ALSO"
+For more information, please refer to the MySQL Reference Manual,
+which may already be installed locally and which is also available
+online at http://dev.mysql.com/doc/.
+.SH AUTHOR
+MySQL AB (http://www.mysql.com/).
Added: branches/sid-5.0/debian/manpages/mysqldump.1
===================================================================
--- branches/sid-5.0/debian/manpages/mysqldump.1 (rev 0)
+++ branches/sid-5.0/debian/manpages/mysqldump.1 2007-11-26 12:34:29 UTC (rev 1020)
@@ -0,0 +1,1152 @@
+.\" Title: \fBmysqldump\fR
+.\" Author:
+.\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
+.\" Date: 11/25/2007
+.\" Manual: MySQL Database System
+.\" Source: MySQL 5.0
+.\"
+.TH "\fBMYSQLDUMP\fR" "1" "11/25/2007" "MySQL 5.0" "MySQL Database System"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
+.SH "NAME"
+mysqldump \- a database backup program
+.SH "SYNOPSIS"
+.HP 45
+\fBmysqldump [\fR\fB\fIoptions\fR\fR\fB] [\fR\fB\fIdb_name\fR\fR\fB [\fR\fB\fItbl_name\fR\fR\fB ...]]\fR
+.SH "DESCRIPTION"
+.PP
+The
+\fBmysqldump\fR
+client is a backup program originally written by Igor Romanenko. It can be used to dump a database or a collection of databases for backup or transfer to another SQL server (not necessarily a MySQL server). The dump typically contains SQL statements to create the table, populate it, or both. However,
+\fBmysqldump\fR
+can also be used to generate files in CSV, other delimited text, or XML format.
+.PP
+If you are doing a backup on the server and your tables all are
+MyISAM
+tables, consider using the
+\fBmysqlhotcopy\fR
+instead because it can accomplish faster backups and faster restores. See
+\fBmysqlhotcopy\fR(1).
+.PP
+There are three general ways to invoke
+\fBmysqldump\fR:
+.sp
+.RS 3n
+.nf
+shell> \fBmysqldump [\fR\fB\fIoptions\fR\fR\fB] \fR\fB\fIdb_name\fR\fR\fB [\fR\fB\fItables\fR\fR\fB]\fR
+shell> \fBmysqldump [\fR\fB\fIoptions\fR\fR\fB] \-\-databases \fR\fB\fIdb_name1\fR\fR\fB [\fR\fB\fIdb_name2\fR\fR\fB \fR\fB\fIdb_name3\fR\fR\fB...]\fR
+shell> \fBmysqldump [\fR\fB\fIoptions\fR\fR\fB] \-\-all\-databases\fR
+.fi
+.RE
+.PP
+If you do not name any tables following
+\fIdb_name\fR
+or if you use the
+\fB\-\-databases\fR
+or
+\fB\-\-all\-databases\fR
+option, entire databases are dumped.
+.PP
+To get a list of the options your version of
+\fBmysqldump\fR
+supports, execute
+\fBmysqldump \-\-help\fR.
+.PP
+Some
+\fBmysqldump\fR
+options are shorthand for groups of other options.
+\fB\-\-opt\fR
+and
+\fB\-\-compact\fR
+fall into this category. For example, use of
+\fB\-\-opt\fR
+is the same as specifying
+\fB\-\-add\-drop\-table \-\-add\-locks \-\-create\-options \-\-disable\-keys \-\-extended\-insert \-\-lock\-tables \-\-quick \-\-set\-charset\fR. Note that all of the options that
+\fB\-\-opt\fR
+stands for also are on by default because
+\fB\-\-opt\fR
+is on by default.
+.PP
+To reverse the effect of a group option, uses its
+\fB\-\-skip\-\fR\fB\fIxxx\fR\fR
+form (\fB\-\-skip\-opt\fR
+or
+\fB\-\-skip\-compact\fR). It is also possible to select only part of the effect of a group option by following it with options that enable or disable specific features. Here are some examples:
+.TP 3n
+\(bu
+To select the effect of
+\fB\-\-opt\fR
+except for some features, use the
+\fB\-\-skip\fR
+option for each feature. For example, to disable extended inserts and memory buffering, use
+\fB\-\-opt \-\-skip\-extended\-insert \-\-skip\-quick\fR. (As of MySQL 5.0,
+\fB\-\-skip\-extended\-insert \-\-skip\-quick\fR
+is sufficient because
+\fB\-\-opt\fR
+is on by default.)
+.TP 3n
+\(bu
+To reverse
+\fB\-\-opt\fR
+for all features except index disabling and table locking, use
+\fB\-\-skip\-opt \-\-disable\-keys \-\-lock\-tables\fR.
+.sp
+.RE
+.PP
+When you selectively enable or disable the effect of a group option, order is important because options are processed first to last. For example,
+\fB\-\-disable\-keys \-\-lock\-tables \-\-skip\-opt\fR
+would not have the intended effect; it is the same as
+\fB\-\-skip\-opt\fR
+by itself.
+.PP
+\fBmysqldump\fR
+can retrieve and dump table contents row by row, or it can retrieve the entire content from a table and buffer it in memory before dumping it. Buffering in memory can be a problem if you are dumping large tables. To dump tables row by row, use the
+\fB\-\-quick\fR
+option (or
+\fB\-\-opt\fR, which enables
+\fB\-\-quick\fR).
+\fB\-\-opt\fR
+(and hence
+\fB\-\-quick\fR) is enabled by default as of MySQL 5.0 to enable memory buffering, use
+\fB\-\-skip\-quick\fR.
+.PP
+If you are using a recent version of
+\fBmysqldump\fR
+to generate a dump to be reloaded into a very old MySQL server, you should not use the
+\fB\-\-opt\fR
+or
+\fB\-\-extended\-insert\fR
+option. Use
+\fB\-\-skip\-opt\fR
+instead.
+.PP
+Before MySQL 4.1.2, out\-of\-range numeric values such as
+\-inf
+and
+inf, as well as
+NaN
+(not\-a\-number) values are dumped by
+\fBmysqldump\fR
+as
+NULL. You can see this using the following sample table:
+.sp
+.RS 3n
+.nf
+mysql> \fBCREATE TABLE t (f DOUBLE);\fR
+mysql> \fBINSERT INTO t VALUES(1e+111111111111111111111);\fR
+mysql> \fBINSERT INTO t VALUES(\-1e111111111111111111111);\fR
+mysql> \fBSELECT f FROM t;\fR
++\-\-\-\-\-\-+
+| f |
++\-\-\-\-\-\-+
+| inf |
+| \-inf |
++\-\-\-\-\-\-+
+.fi
+.RE
+.PP
+For this table,
+\fBmysqldump\fR
+produces the following data output:
+.sp
+.RS 3n
+.nf
+\-\-
+\-\- Dumping data for table `t`
+\-\-
+INSERT INTO t VALUES (NULL);
+INSERT INTO t VALUES (NULL);
+.fi
+.RE
+.PP
+The significance of this behavior is that if you dump and restore the table, the new table has contents that differ from the original contents. This problem is fixed as of MySQL 4.1.2; you cannot insert
+inf
+in the table, so this
+\fBmysqldump\fR
+behavior is only relevant when you deal with old servers.
+.PP
+\fBmysqldump\fR
+supports the following options:
+.TP 3n
+\(bu
+\fB\-\-help\fR,
+\fB\-?\fR
+.sp
+Display a help message and exit.
+.TP 3n
+\(bu
+\fB\-\-add\-drop\-database\fR
+.sp
+Add a
+DROP DATABASE
+statement before each
+CREATE DATABASE
+statement.
+.TP 3n
+\(bu
+\fB\-\-add\-drop\-table\fR
+.sp
+Add a
+DROP TABLE
+statement before each
+CREATE TABLE
+statement.
+.TP 3n
+\(bu
+\fB\-\-add\-locks\fR
+.sp
+Surround each table dump with
+LOCK TABLES
+and
+UNLOCK TABLES
+statements. This results in faster inserts when the dump file is reloaded. See
+Section\ 2.17, \(lqSpeed of INSERT Statements\(rq.
+.TP 3n
+\(bu
+\fB\-\-all\-databases\fR,
+\fB\-A\fR
+.sp
+Dump all tables in all databases. This is the same as using the
+\fB\-\-databases\fR
+option and naming all the databases on the command line.
+.TP 3n
+\(bu
+\fB\-\-allow\-keywords\fR
+.sp
+Allow creation of column names that are keywords. This works by prefixing each column name with the table name.
+.TP 3n
+\(bu
+\fB\-\-character\-sets\-dir=\fR\fB\fIpath\fR\fR
+.sp
+The directory where character sets are installed. See
+Section\ 2, \(lqThe Character Set Used for Data and Sorting\(rq.
+.TP 3n
+\(bu
+\fB\-\-comments\fR,
+\fB\-i\fR
+.sp
+Write additional information in the dump file such as program version, server version, and host. This option is enabled by default. To suppress this additional information, use
+\fB\-\-skip\-comments\fR.
+.TP 3n
+\(bu
+\fB\-\-compact\fR
+.sp
+Produce less verbose output. This option enables the
+\fB\-\-skip\-add\-drop\-table\fR,
+\fB\-\-skip\-add\-locks\fR,
+\fB\-\-skip\-comments\fR,
+\fB\-\-skip\-disable\-keys\fR, and
+\fB\-\-skip\-set\-charset\fR
+options.
+.sp
+.it 1 an-trap
+.nr an-no-space-flag 1
+.nr an-break-flag 1
+.br
+\fBNote\fR
+Prior to release 5.0.48, this option did not create valid SQL if the database dump contained views. The recreation of views requires the creation and removal of temporary tables and this option suppressed the removal of those temporary tables. As a workaround, use
+\fB\-\-compress\fR
+with the
+\fB\-\-add\-drop\-table\fR
+option and then manually adjust the dump file.
+.TP 3n
+\(bu
+\fB\-\-compatible=\fR\fB\fIname\fR\fR
+.sp
+Produce output that is more compatible with other database systems or with older MySQL servers. The value of
+name
+can be
+ansi,
+mysql323,
+mysql40,
+postgresql,
+oracle,
+mssql,
+db2,
+maxdb,
+no_key_options,
+no_table_options, or
+no_field_options. To use several values, separate them by commas. These values have the same meaning as the corresponding options for setting the server SQL mode. See
+the section called \(lqSQL MODES\(rq.
+.sp
+This option does not guarantee compatibility with other servers. It only enables those SQL mode values that are currently available for making dump output more compatible. For example,
+\fB\-\-compatible=oracle\fR
+does not map data types to Oracle types or use Oracle comment syntax.
+.sp
+\fIThis option requires a server version of 4.1.0 or higher\fR. With older servers, it does nothing.
+.TP 3n
+\(bu
+\fB\-\-complete\-insert\fR,
+\fB\-c\fR
+.sp
+Use complete
+INSERT
+statements that include column names.
+.TP 3n
+\(bu
+\fB\-\-compress\fR,
+\fB\-C\fR
+.sp
+Compress all information sent between the client and the server if both support compression.
+.TP 3n
+\(bu
+\fB\-\-create\-options\fR
+.sp
+Include all MySQL\-specific table options in the
+CREATE TABLE
+statements.
+.TP 3n
+\(bu
+\fB\-\-databases\fR,
+\fB\-B\fR
+.sp
+Dump several databases. Normally,
+\fBmysqldump\fR
+treats the first name argument on the command line as a database name and following names as table names. With this option, it treats all name arguments as database names.
+CREATE DATABASE
+and
+USE
+statements are included in the output before each new database.
+.TP 3n
+\(bu
+\fB\-\-debug[=\fR\fB\fIdebug_options\fR\fR\fB]\fR,
+\fB\-# [\fR\fB\fIdebug_options\fR\fR\fB]\fR
+.sp
+Write a debugging log. The
+\fIdebug_options\fR
+string is often
+\'d:t:o,\fIfile_name\fR'. The default value is
+\'d:t:o,/tmp/mysqldump.trace'.
+.TP 3n
+\(bu
+\fB\-\-default\-character\-set=\fR\fB\fIcharset_name\fR\fR
+.sp
+Use
+\fIcharset_name\fR
+as the default character set. See
+Section\ 2, \(lqThe Character Set Used for Data and Sorting\(rq. If no character set is specified,
+\fBmysqldump\fR
+uses
+utf8, and earlier versions use
+latin1.
+.TP 3n
+\(bu
+\fB\-\-delayed\-insert\fR
+.sp
+Write
+INSERT DELAYED
+statements rather than
+INSERT
+statements.
+.TP 3n
+\(bu
+\fB\-\-delete\-master\-logs\fR
+.sp
+On a master replication server, delete the binary logs after performing the dump operation. This option automatically enables
+\fB\-\-master\-data\fR.
+.TP 3n
+\(bu
+\fB\-\-disable\-keys\fR,
+\fB\-K\fR
+.sp
+For each table, surround the
+INSERT
+statements with
+/*!40000 ALTER TABLE \fItbl_name\fR DISABLE KEYS */;
+and
+/*!40000 ALTER TABLE \fItbl_name\fR ENABLE KEYS */;
+statements. This makes loading the dump file faster because the indexes are created after all rows are inserted. This option is effective only for non\-unique indexes of
+MyISAM
+tables.
+.TP 3n
+\(bu
+\fB\-\-dump\-date\fR
+.sp
+\fBmysqldump\fR
+produces a
+\-\- Dump completed on \fIDATE\fR
+comment at the end of the dump if the
+\fB\-\-comments\fR
+option is given. However, the date causes dump files for identical data take at different times to appear to be different.
+\fB\-\-dump\-date\fR
+and
+\fB\-\-skip\-dump\-date\fR
+control whether the date is added to the comment. The default is
+\fB\-\-dump\-date\fR
+(include the date in the comment).
+\fB\-\-skip\-dump\-date\fR
+suppresses date printing. This option was added in MySQL 5.0.52.
+.TP 3n
+\(bu
+\fB\-\-extended\-insert\fR,
+\fB\-e\fR
+.sp
+Use multiple\-row
+INSERT
+syntax that include several
+VALUES
+lists. This results in a smaller dump file and speeds up inserts when the file is reloaded.
+.TP 3n
+\(bu
+\fB\-\-fields\-terminated\-by=...\fR,
+\fB\-\-fields\-enclosed\-by=...\fR,
+\fB\-\-fields\-optionally\-enclosed\-by=...\fR,
+\fB\-\-fields\-escaped\-by=...\fR
+.sp
+These options are used with the
+\fB\-T\fR
+option and have the same meaning as the corresponding clauses for
+LOAD DATA INFILE. See
+Section\ 2.5, \(lqLOAD DATA INFILE Syntax\(rq.
+.TP 3n
+\(bu
+\fB\-\-first\-slave\fR,
+\fB\-x\fR
+.sp
+Deprecated. Now renamed to
+\fB\-\-lock\-all\-tables\fR.
+.TP 3n
+\(bu
+\fB\-\-flush\-logs\fR,
+\fB\-F\fR
+.sp
+Flush the MySQL server log files before starting the dump. This option requires the
+RELOAD
+privilege. Note that if you use this option in combination with the
+\fB\-\-all\-databases\fR
+(or
+\fB\-A\fR) option, the logs are flushed
+\fIfor each database dumped\fR. The exception is when using
+\fB\-\-lock\-all\-tables\fR
+or
+\fB\-\-master\-data\fR: In this case, the logs are flushed only once, corresponding to the moment that all tables are locked. If you want your dump and the log flush to happen at exactly the same moment, you should use
+\fB\-\-flush\-logs\fR
+together with either
+\fB\-\-lock\-all\-tables\fR
+or
+\fB\-\-master\-data\fR.
+.TP 3n
+\(bu
+\fB\-\-flush\-privileges\fR
+.sp
+Emit a
+FLUSH PRIVILEGES
+statement after dumping the
+mysql
+database. This option should be used any time the dump contains the
+mysql
+database and any other database that depends on the data in the
+mysql
+database for proper restoration. This option was added in MySQL 5.0.26.
+.TP 3n
+\(bu
+\fB\-\-force\fR,
+\fB\-f\fR
+.sp
+Continue even if an SQL error occurs during a table dump.
+.sp
+One use for this option is to cause
+\fBmysqldump\fR
+to continue executing even when it encounters a view that has become invalid because the defintion refers to a table that has been dropped. Without
+\fB\-\-force\fR,
+\fBmysqldump\fR
+exits with an error message. With
+\fB\-\-force\fR,
+\fBmysqldump\fR
+prints the error message, but it also writes a SQL comment containing the view definition to the dump output and continues executing.
+.TP 3n
+\(bu
+\fB\-\-host=\fR\fB\fIhost_name\fR\fR,
+\fB\-h \fR\fB\fIhost_name\fR\fR
+.sp
+Dump data from the MySQL server on the given host. The default host is
+localhost.
+.TP 3n
+\(bu
+\fB\-\-hex\-blob\fR
+.sp
+Dump binary columns using hexadecimal notation (for example,
+\'abc'
+becomes
+0x616263). The affected data types are
+BINARY,
+VARBINARY, and
+BLOB. As of MySQL 5.0.13,
+BIT
+columns are affected as well.
+.TP 3n
+\(bu
+\fB\-\-ignore\-table=\fR\fB\fIdb_name.tbl_name\fR\fR
+.sp
+Do not dump the given table, which must be specified using both the database and table names. To ignore multiple tables, use this option multiple times.
+.TP 3n
+\(bu
+\fB\-\-insert\-ignore\fR
+.sp
+Write
+INSERT
+statements with the
+IGNORE
+option.
+.TP 3n
+\(bu
+\fB\-\-lines\-terminated\-by=...\fR
+.sp
+This option is used with the
+\fB\-T\fR
+option and has the same meaning as the corresponding clause for
+LOAD DATA INFILE. See
+Section\ 2.5, \(lqLOAD DATA INFILE Syntax\(rq.
+.TP 3n
+\(bu
+\fB\-\-lock\-all\-tables\fR,
+\fB\-x\fR
+.sp
+Lock all tables across all databases. This is achieved by acquiring a global read lock for the duration of the whole dump. This option automatically turns off
+\fB\-\-single\-transaction\fR
+and
+\fB\-\-lock\-tables\fR.
+.TP 3n
+\(bu
+\fB\-\-lock\-tables\fR,
+\fB\-l\fR
+.sp
+Lock all tables before dumping them. The tables are locked with
+READ LOCAL
+to allow concurrent inserts in the case of
+MyISAM
+tables. For transactional tables such as
+InnoDB
+and
+BDB,
+\fB\-\-single\-transaction\fR
+is a much better option, because it does not need to lock the tables at all.
+.sp
+Please note that when dumping multiple databases,
+\fB\-\-lock\-tables\fR
+locks tables for each database separately. Therefore, this option does not guarantee that the tables in the dump file are logically consistent between databases. Tables in different databases may be dumped in completely different states.
+.TP 3n
+\(bu
+\fB\-\-log\-error=\fR\fB\fIfile_name\fR\fR
+.sp
+Append warnings and errors to the named file. This option was added in MySQL 5.0.42.
+.TP 3n
+\(bu
+\fB\-\-master\-data[=\fR\fB\fIvalue\fR\fR\fB]\fR
+.sp
+Write the binary log filename and position to the output. This option requires the
+RELOAD
+privilege and the binary log must be enabled. If the option value is equal to 1, the position and filename are written to the dump output in the form of a
+CHANGE MASTER
+statement. If the dump is from a master server and you use it to set up a slave server, the
+CHANGE MASTER
+statement causes the slave to start from the correct position in the master's binary logs. If the option value is equal to 2, the
+CHANGE MASTER
+statement is written as an SQL comment. If the value is not specified, then the default value is 1.
+.sp
+The
+\fB\-\-master\-data\fR
+option automatically turns off
+\fB\-\-lock\-tables\fR. It also turns on
+\fB\-\-lock\-all\-tables\fR, unless
+\fB\-\-single\-transaction\fR
+also is specified (in which case, a global read lock is acquired only for a short time at the beginning of the dump. See also the description for
+\fB\-\-single\-transaction\fR. In all cases, any action on logs happens at the exact moment of the dump.
+.TP 3n
+\(bu
+\fB\-\-no\-autocommit\fR
+.sp
+Enclose the
+INSERT
+statements for each dumped table within
+SET AUTOCOMMIT=0
+and
+COMMIT
+statements.
+.TP 3n
+\(bu
+\fB\-\-no\-create\-db\fR,
+\fB\-n\fR
+.sp
+This option suppresses the
+CREATE DATABASE
+statements that are otherwise included in the output if the
+\fB\-\-databases\fR
+or
+\fB\-\-all\-databases\fR
+option is given.
+.TP 3n
+\(bu
+\fB\-\-no\-create\-info\fR,
+\fB\-t\fR
+.sp
+Do not write
+CREATE TABLE
+statements that re\-create each dumped table.
+.TP 3n
+\(bu
+\fB\-\-no\-data\fR,
+\fB\-d\fR
+.sp
+Do not write any table row information (that is, do not dump table contents). This is very useful if you want to dump only the
+CREATE TABLE
+statement for the table.
+.TP 3n
+\(bu
+\fB\-\-opt\fR
+.sp
+This option is shorthand; it is the same as specifying
+\fB\-\-add\-drop\-table \-\-add\-locks \-\-create\-options \-\-disable\-keys \-\-extended\-insert \-\-lock\-tables \-\-quick \-\-set\-charset\fR. It should give you a fast dump operation and produce a dump file that can be reloaded into a MySQL server quickly.
+.sp
+\fIThe \fR\fI\fB\-\-opt\fR\fR\fI option is enabled by default. Use \fR\fI\fB\-\-skip\-opt\fR\fR\fI to disable it.\fR
+See the discussion at the beginning of this section for information about selectively enabling or disabling certain of the options affected by
+\fB\-\-opt\fR.
+.TP 3n
+\(bu
+\fB\-\-order\-by\-primary\fR
+.sp
+Sorts each table's rows by its primary key, or by its first unique index, if such an index exists. This is useful when dumping a
+MyISAM
+table to be loaded into an
+InnoDB
+table, but will make the dump itself take considerably longer.
+.TP 3n
+\(bu
+\fB\-\-password[=\fR\fB\fIpassword\fR\fR\fB]\fR,
+\fB\-p[\fR\fB\fIpassword\fR\fR\fB]\fR
+.sp
+The password to use when connecting to the server. If you use the short option form (\fB\-p\fR), you
+\fIcannot\fR
+have a space between the option and the password. If you omit the
+\fIpassword\fR
+value following the
+\fB\-\-password\fR
+or
+\fB\-p\fR
+option on the command line, you are prompted for one.
+.sp
+Specifying a password on the command line should be considered insecure. See
+Section\ 6.6, \(lqKeeping Your Password Secure\(rq.
+.TP 3n
+\(bu
+\fB\-\-port=\fR\fB\fIport_num\fR\fR,
+\fB\-P \fR\fB\fIport_num\fR\fR
+.sp
+The TCP/IP port number to use for the connection.
+.TP 3n
+\(bu
+\fB\-\-protocol={TCP|SOCKET|PIPE|MEMORY}\fR
+.sp
+The connection protocol to use.
+.TP 3n
+\(bu
+\fB\-\-quick\fR,
+\fB\-q\fR
+.sp
+This option is useful for dumping large tables. It forces
+\fBmysqldump\fR
+to retrieve rows for a table from the server a row at a time rather than retrieving the entire row set and buffering it in memory before writing it out.
+.TP 3n
+\(bu
+\fB\-\-quote\-names\fR,
+\fB\-Q\fR
+.sp
+Quote database, table, and column names within
+\(lq`\(rq
+characters. If the
+ANSI_QUOTES
+SQL mode is enabled, names are quoted within
+\(lq"\(rq
+characters. This option is enabled by default. It can be disabled with
+\fB\-\-skip\-quote\-names\fR, but this option should be given after any option such as
+\fB\-\-compatible\fR
+that may enable
+\fB\-\-quote\-names\fR.
+.TP 3n
+\(bu
+\fB\-\-result\-file=\fR\fB\fIfile\fR\fR,
+\fB\-r \fR\fB\fIfile\fR\fR
+.sp
+Direct output to a given file. This option should be used on Windows to prevent newline
+\(lq\\n\(rq
+characters from being converted to
+\(lq\\r\\n\(rq
+carriage return/newline sequences. The result file is created and its contents overwritten, even if an error occurs while generating the dump. The previous contents are lost.
+.TP 3n
+\(bu
+\fB\-\-routines\fR,
+\fB\-R\fR
+.sp
+Dump stored routines (functions and procedures) from the dumped databases. Use of this option requires the
+SELECT
+privilege for the
+mysql.proc
+table. The output generated by using
+\fB\-\-routines\fR
+contains
+CREATE PROCEDURE
+and
+CREATE FUNCTION
+statements to re\-create the routines. However, these statements do not include attributes such as the routine creation and modification timestamps. This means that when the routines are reloaded, they will be created with the timestamps equal to the reload time.
+.sp
+If you require routines to be re\-created with their original timestamp attributes, do not use
+\fB\-\-routines\fR. Instead, dump and reload the contents of the
+mysql.proc
+table directly, using a MySQL account that has appropriate privileges for the
+mysql
+database.
+.sp
+This option was added in MySQL 5.0.13. Before that, stored routines are not dumped. Routine
+DEFINER
+values are not dumped until MySQL 5.0.20. This means that before 5.0.20, when routines are reloaded, they will be created with the definer set to the reloading user. If you require routines to be re\-created with their original definer, dump and load the contents of the
+mysql.proc
+table directly as described earlier.
+.TP 3n
+\(bu
+\fB\-\-set\-charset\fR
+.sp
+Add
+SET NAMES \fIdefault_character_set\fR
+to the output. This option is enabled by default. To suppress the
+SET NAMES
+statement, use
+\fB\-\-skip\-set\-charset\fR.
+.TP 3n
+\(bu
+\fB\-\-single\-transaction\fR
+.sp
+This option issues a
+BEGIN
+SQL statement before dumping data from the server. It is useful only with transactional tables such as
+InnoDB
+and
+BDB, because then it dumps the consistent state of the database at the time when
+BEGIN
+was issued without blocking any applications.
+.sp
+When using this option, you should keep in mind that only
+InnoDB
+tables are dumped in a consistent state. For example, any
+MyISAM
+or
+MEMORY
+tables dumped while using this option may still change state.
+.sp
+The
+\fB\-\-single\-transaction\fR
+option and the
+\fB\-\-lock\-tables\fR
+option are mutually exclusive, because
+LOCK TABLES
+causes any pending transactions to be committed implicitly.
+.sp
+While a
+\fB\-\-single\-transaction\fR
+dump is in process, to ensure a valid dump file (correct table contents and binary log position), no other connection should use the following statements:
+ALTER TABLE,
+DROP TABLE,
+RENAME TABLE,
+TRUNCATE TABLE. A consistent read is not isolated from those statements, so use of them on a table to be dumped can cause the
+SELECT
+performed by
+\fBmysqldump\fR
+to retrieve the table contents to obtain incorrect contents or fail.
+.sp
+This option is not supported for MySQL Cluster tables; the results cannot be guaranteed to be consistent due to the fact that the
+NDBCluster
+storage engine supports only the
+READ_COMMITTED
+transaction isolation level. You should always use
+NDB
+backup and restore instead.
+.sp
+To dump large tables, you should combine this option with
+\fB\-\-quick\fR.
+.TP 3n
+\(bu
+\fB\-\-skip\-comments\fR
+.sp
+See the description for the
+\fB\-\-comments\fR
+option.
+.TP 3n
+\(bu
+\fB\-\-skip\-opt\fR
+.sp
+See the description for the
+\fB\-\-opt\fR
+option.
+.TP 3n
+\(bu
+\fB\-\-socket=\fR\fB\fIpath\fR\fR,
+\fB\-S \fR\fB\fIpath\fR\fR
+.sp
+For connections to
+localhost, the Unix socket file to use, or, on Windows, the name of the named pipe to use.
+.TP 3n
+\(bu
+\fB\-\-ssl*\fR
+.sp
+Options that begin with
+\fB\-\-ssl\fR
+specify whether to connect to the server via SSL and indicate where to find SSL keys and certificates. See
+Section\ 6.7.3, \(lqSSL Command Options\(rq.
+.TP 3n
+\(bu
+\fB\-\-tab=\fR\fB\fIpath\fR\fR,
+\fB\-T \fR\fB\fIpath\fR\fR
+.sp
+Produce tab\-separated data files. For each dumped table,
+\fBmysqldump\fR
+creates a
+\fI\fItbl_name\fR\fR\fI.sql\fR
+file that contains the
+CREATE TABLE
+statement that creates the table, and a
+\fI\fItbl_name\fR\fR\fI.txt\fR
+file that contains its data. The option value is the directory in which to write the files.
+.sp
+By default, the
+\fI.txt\fR
+data files are formatted using tab characters between column values and a newline at the end of each line. The format can be specified explicitly using the
+\fB\-\-fields\-\fR\fB\fIxxx\fR\fR
+and
+\fB\-\-lines\-terminated\-by\fR
+options.
+.sp
+.it 1 an-trap
+.nr an-no-space-flag 1
+.nr an-break-flag 1
+.br
+\fBNote\fR
+This option should be used only when
+\fBmysqldump\fR
+is run on the same machine as the
+\fBmysqld\fR
+server. You must have the
+FILE
+privilege, and the server must have permission to write files in the directory that you specify.
+.TP 3n
+\(bu
+\fB\-\-tables\fR
+.sp
+Override the
+\fB\-\-databases\fR
+or
+\fB\-B\fR
+option.
+\fBmysqldump\fR
+regards all name arguments following the option as table names.
+.TP 3n
+\(bu
+\fB\-\-triggers\fR
+.sp
+Dump triggers for each dumped table. This option is enabled by default; disable it with
+\fB\-\-skip\-triggers\fR. This option was added in MySQL 5.0.11. Before that, triggers are not dumped.
+.TP 3n
+\(bu
+\fB\-\-tz\-utc\fR
+.sp
+Add
+SET TIME_ZONE='+00:00'
+to the dump file so that
+TIMESTAMP
+columns can be dumped and reloaded between servers in different time zones. Without this option,
+TIMESTAMP
+columns are dumped and reloaded in the time zones local to the source and destination servers, which can cause the values to change.
+\fB\-\-tz\-utc\fR
+also protects against changes due to daylight saving time.
+\fB\-\-tz\-utc\fR
+is enabled by default. To disable it, use
+\fB\-\-skip\-tz\-utc\fR. This option was added in MySQL 5.0.15.
+.TP 3n
+\(bu
+\fB\-\-user=\fR\fB\fIuser_name\fR\fR,
+\fB\-u \fR\fB\fIuser_name\fR\fR
+.sp
+The MySQL username to use when connecting to the server.
+.TP 3n
+\(bu
+\fB\-\-verbose\fR,
+\fB\-v\fR
+.sp
+Verbose mode. Print more information about what the program does.
+.TP 3n
+\(bu
+\fB\-\-version\fR,
+\fB\-V\fR
+.sp
+Display version information and exit.
+.TP 3n
+\(bu
+\fB\-\-where='\fR\fB\fIwhere_condition\fR\fR\fB'\fR,
+\fB\-w '\fR\fB\fIwhere_condition\fR\fR\fB'\fR
+.sp
+Dump only rows selected by the given
+WHERE
+condition. Quotes around the condition are mandatory if it contains spaces or other characters that are special to your command interpreter.
+.sp
+Examples:
+.sp
+.RS 3n
+.nf
+\-\-where="user='jimf'"
+\-w"userid>1"
+\-w"userid<1"
+.fi
+.RE
+.TP 3n
+\(bu
+\fB\-\-xml\fR,
+\fB\-X\fR
+.sp
+Write dump output as well\-formed XML.
+.sp
+\fBNULL\fR\fB, \fR\fB'NULL'\fR\fB, and Empty Values\fR: For some column named
+\fIcolumn_name\fR, the
+NULL
+value, an empty string, and the string value
+\'NULL'
+are distinguished from one another in the output generated by this option as follows:
+.TS
+allbox tab(:);
+l l
+l l
+l l
+l l.
+T{
+\fBValue\fR:
+T}:T{
+\fBXML Representation\fR:
+T}
+T{
+NULL (\fIunknown value\fR)
+T}:T{
+<field name="\fIcolumn_name\fR"
+ xsi:nil="true" />
+T}
+T{
+\'' (\fIempty string\fR)
+T}:T{
+<field
+ name="\fIcolumn_name\fR"></field>
+T}
+T{
+\'NULL' (\fIstring value\fR)
+T}:T{
+<field
+ name="\fIcolumn_name\fR">NULL</field>
+T}
+.TE
+.sp
+Beginning with MySQL 5.0.26, the output from the
+\fBmysql\fR
+client when run using the
+\fB\-\-xml\fR
+option also follows these rules. (See
+the section called \(lq\fBMYSQL\fR OPTIONS\(rq.)
+.sp
+Beginning with MySQL 5.0.40, XML output from
+\fBmysqldump\fR
+includes the XML namespace, as shown here:
+.sp
+.RS 3n
+.nf
+shell> \fBmysqldump \-\-xml \-u root world City\fR
+<?xml version="1.0"?>
+<mysqldump xmlns:xsi="http://www.w3.org/2001/XMLSchema\-instance">
+<database name="world">
+<table_structure name="City">
+<field Field="ID" Type="int(11)" Null="NO" Key="PRI" Extra="auto_increment" />
+<field Field="Name" Type="char(35)" Null="NO" Key="" Default="" Extra="" />
+<field Field="CountryCode" Type="char(3)" Null="NO" Key="" Default="" Extra="" />
+<field Field="District" Type="char(20)" Null="NO" Key="" Default="" Extra="" />
+<field Field="Population" Type="int(11)" Null="NO" Key="" Default="0" Extra="" />
+<key Table="City" Non_unique="0" Key_name="PRIMARY" Seq_in_index="1" Column_name="ID" Collation="A" Cardinality="4079"
+Null="" Index_type="BTREE" Comment="" />
+<options Name="City" Engine="MyISAM" Version="10" Row_format="Fixed" Rows="4079" Avg_row_length="67" Data_length="27329
+3" Max_data_length="18858823439613951" Index_length="43008" Data_free="0" Auto_increment="4080" Create_time="2007\-03\-31 01:47:01" Updat
+e_time="2007\-03\-31 01:47:02" Collation="latin1_swedish_ci" Create_options="" Comment="" />
+</table_structure>
+<table_data name="City">
+<row>
+<field name="ID">1</field>
+<field name="Name">Kabul</field>
+<field name="CountryCode">AFG</field>
+<field name="District">Kabol</field>
+<field name="Population">1780000</field>
+</row>
+\fI...\fR
+<row>
+<field name="ID">4079</field>
+<field name="Name">Rafah</field>
+<field name="CountryCode">PSE</field>
+<field name="District">Rafah</field>
+<field name="Population">92020</field>
+</row>
+</table_data>
+</database>
+</mysqldump>
+.fi
+.RE
+.sp
+.sp
+.RE
+.PP
+You can also set the following variables by using
+\fB\-\-\fR\fB\fIvar_name\fR\fR\fB=\fR\fB\fIvalue\fR\fR
+syntax:
+.TP 3n
+\(bu
+max_allowed_packet
+.sp
+The maximum size of the buffer for client/server communication. The maximum is 1GB.
+.TP 3n
+\(bu
+net_buffer_length
+.sp
+The initial size of the buffer for client/server communication. When creating multiple\-row\-insert statements (as with option
+\fB\-\-extended\-insert\fR
+or
+\fB\-\-opt\fR),
+\fBmysqldump\fR
+creates rows up to
+net_buffer_length
+length. If you increase this variable, you should also ensure that the
+net_buffer_length
+variable in the MySQL server is at least this large.
+.sp
+.RE
+.PP
+It is also possible to set variables by using
+\fB\-\-set\-variable=\fR\fB\fIvar_name\fR\fR\fB=\fR\fB\fIvalue\fR\fR
+or
+\fB\-O \fR\fB\fIvar_name\fR\fR\fB=\fR\fB\fIvalue\fR\fR
+syntax.
+\fIThis syntax is deprecated\fR.
+.PP
+The most common use of
+\fBmysqldump\fR
+is probably for making a backup of an entire database:
+.sp
+.RS 3n
+.nf
+shell> \fBmysqldump \fR\fB\fIdb_name\fR\fR\fB > \fR\fB\fIbackup\-file.sql\fR\fR
+.fi
+.RE
+.PP
+You can read the dump file back into the server like this:
+.sp
+.RS 3n
+.nf
+shell> \fBmysql \fR\fB\fIdb_name\fR\fR\fB < \fR\fB\fIbackup\-file.sql\fR\fR
+.fi
+.RE
+.PP
+Or like this:
+.sp
+.RS 3n
+.nf
+shell> \fBmysql \-e "source \fR\fB\fI/path\-to\-backup/backup\-file.sql\fR\fR\fB" \fR\fB\fIdb_name\fR\fR
+.fi
+.RE
+.PP
+\fBmysqldump\fR
+is also very useful for populating databases by copying data from one MySQL server to another:
+.sp
+.RS 3n
+.nf
+shell> \fBmysqldump \-\-opt \fR\fB\fIdb_name\fR\fR\fB | mysql \-\-host=\fR\fB\fIremote_host\fR\fR\fB \-C \fR\fB\fIdb_name\fR\fR
+.fi
+.RE
+.PP
+It is possible to dump several databases with one command:
+.sp
+.RS 3n
+.nf
+shell> \fBmysqldump \-\-databases \fR\fB\fIdb_name1\fR\fR\fB [\fR\fB\fIdb_name2\fR\fR\fB ...] > my_databases.sql\fR
+.fi
+.RE
+.PP
+To dump all databases, use the
+\fB\-\-all\-databases\fR
+option:
+.sp
+.RS 3n
+.nf
+shell> \fBmysqldump \-\-all\-databases > all_databases.sql\fR
+.fi
+.RE
+.PP
+For
+InnoDB
+tables,
+mysqldump
+provides a way of making an online backup:
+.sp
+.RS 3n
+.nf
+shell> \fBmysqldump \-\-all\-databases \-\-single\-transaction > all_databases.sql\fR
+.fi
+.RE
+.PP
+This backup just needs to acquire a global read lock on all tables (using
+FLUSH TABLES WITH READ LOCK) at the beginning of the dump. As soon as this lock has been acquired, the binary log coordinates are read and the lock is released. If and only if one long updating statement is running when the
+FLUSH
+statement is issued, the MySQL server may get stalled until that long statement finishes, and then the dump becomes lock\-free. If the update statements that the MySQL server receives are short (in terms of execution time), the initial lock period should not be noticeable, even with many updates.
+.PP
+For point\-in\-time recovery (also known as
+\(lqroll\-forward,\(rq
+when you need to restore an old backup and replay the changes that happened since that backup), it is often useful to rotate the binary log (see
+Section\ 8.3, \(lqThe Binary Log\(rq) or at least know the binary log coordinates to which the dump corresponds:
+.sp
+.RS 3n
+.nf
+shell> \fBmysqldump \-\-all\-databases \-\-master\-data=2 > all_databases.sql\fR
+.fi
+.RE
+.PP
+Or:
+.sp
+.RS 3n
+.nf
+shell> \fBmysqldump \-\-all\-databases \-\-flush\-logs \-\-master\-data=2\fR
+ \fB> all_databases.sql\fR
+.fi
+.RE
+.PP
+The
+\fB\-\-master\-data\fR
+and
+\fB\-\-single\-transaction\fR
+options can be used simultaneously, which provides a convenient way to make an online backup suitable for point\-in\-time recovery if tables are stored using the
+InnoDB
+storage engine.
+.PP
+For more information on making backups, see
+Section\ 7.1, \(lqDatabase Backups\(rq, and
+Section\ 7.2, \(lqExample Backup and Recovery Strategy\(rq.
+.PP
+If you encounter problems backing up views, please read the section that covers restrictions on views which describes a workaround for backing up views when this fails due to insufficient privileges. See
+Section\ 4, \(lqRestrictions on Views\(rq.
+.SH "COPYRIGHT"
+.PP
+Copyright 2007 MySQL AB
+.PP
+This documentation is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License.
+.PP
+This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
+.PP
+You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110\-1301 USA or see http://www.gnu.org/licenses/.
+.PP
+Please email
+<docs at mysql.com>
+for more information or if you are interested in doing a translation.
+.SH "SEE ALSO"
+For more information, please refer to the MySQL Reference Manual,
+which may already be installed locally and which is also available
+online at http://dev.mysql.com/doc/.
+.SH AUTHOR
+MySQL AB (http://www.mysql.com/).
Added: branches/sid-5.0/debian/manpages/mysqlhotcopy.1
===================================================================
--- branches/sid-5.0/debian/manpages/mysqlhotcopy.1 (rev 0)
+++ branches/sid-5.0/debian/manpages/mysqlhotcopy.1 2007-11-26 12:34:29 UTC (rev 1020)
@@ -0,0 +1,269 @@
+.\" Title: \fBmysqlhotcopy\fR
+.\" Author:
+.\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
+.\" Date: 11/25/2007
+.\" Manual: MySQL Database System
+.\" Source: MySQL 5.0
+.\"
+.TH "\fBMYSQLHOTCOPY\fR" "1" "11/25/2007" "MySQL 5.0" "MySQL Database System"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
+.SH "NAME"
+mysqlhotcopy \- a database backup program
+.SH "SYNOPSIS"
+.HP 23
+\fBmysqlhotcopy \fR\fB\fIarguments\fR\fR
+.SH "DESCRIPTION"
+.PP
+\fBmysqlhotcopy\fR
+is a Perl script that was originally written and contributed by Tim Bunce. It uses
+LOCK TABLES,
+FLUSH TABLES, and
+cp
+or
+scp
+to make a database backup quickly. It is the fastest way to make a backup of the database or single tables, but it can be run only on the same machine where the database directories are located.
+\fBmysqlhotcopy\fR
+works only for backing up
+MyISAM
+and
+ARCHIVE
+tables. It runs on Unix and NetWare.
+.sp
+.RS 3n
+.nf
+shell> \fBmysqlhotcopy \fR\fB\fIdb_name\fR\fR\fB [\fR\fB\fI/path/to/new_directory\fR\fR\fB]\fR
+.fi
+.RE
+.sp
+.RS 3n
+.nf
+shell> \fBmysqlhotcopy \fR\fB\fIdb_name_1\fR\fR\fB ... \fR\fB\fIdb_name_n\fR\fR\fB \fR\fB\fI/path/to/new_directory\fR\fR
+.fi
+.RE
+.PP
+Back up tables in the given database that match a regular expression:
+.sp
+.RS 3n
+.nf
+shell> \fBmysqlhotcopy \fR\fB\fIdb_name\fR\fR\fB./\fR\fB\fIregex\fR\fR\fB/\fR
+.fi
+.RE
+.PP
+The regular expression for the table name can be negated by prefixing it with a tilde (\(lq~\(rq):
+.sp
+.RS 3n
+.nf
+shell> \fBmysqlhotcopy \fR\fB\fIdb_name\fR\fR\fB./~\fR\fB\fIregex\fR\fR\fB/\fR
+.fi
+.RE
+.PP
+\fBmysqlhotcopy\fR
+supports the following options:
+.TP 3n
+\(bu
+\fB\-\-help\fR,
+\fB\-?\fR
+.sp
+Display a help message and exit.
+.TP 3n
+\(bu
+\fB\-\-addtodest\fR
+.sp
+Do not rename target directory (if it exists); merely add files to it.
+.TP 3n
+\(bu
+\fB\-\-allowold\fR
+.sp
+Do not abort if a target exists; rename it by adding an
+_old
+suffix.
+.TP 3n
+\(bu
+\fB\-\-checkpoint=\fR\fB\fIdb_name\fR\fR\fB.\fR\fB\fItbl_name\fR\fR
+.sp
+Insert checkpoint entries into the specified database
+\fIdb_name\fR
+and table
+\fItbl_name\fR.
+.TP 3n
+\(bu
+\fB\-\-chroot=\fR\fB\fIpath\fR\fR
+.sp
+Base directory of the
+\fBchroot\fR
+jail in which
+\fBmysqld\fR
+operates. The
+\fIpath\fR
+value should match that of the
+\fB\-\-chroot\fR
+option given to
+\fBmysqld\fR.
+.TP 3n
+\(bu
+\fB\-\-debug\fR
+.sp
+Enable debug output.
+.TP 3n
+\(bu
+\fB\-\-dryrun\fR,
+\fB\-n\fR
+.sp
+Report actions without performing them.
+.TP 3n
+\(bu
+\fB\-\-flushlog\fR
+.sp
+Flush logs after all tables are locked.
+.TP 3n
+\(bu
+\fB\-\-host=\fR\fB\fIhost_name\fR\fR,
+\fB\-h \fR\fB\fIhost_name\fR\fR
+.sp
+The hostname of the local host to use for making a TCP/IP connection to the local server. By default, the connection is made to
+localhost
+using a Unix socket file.
+.TP 3n
+\(bu
+\fB\-\-keepold\fR
+.sp
+Do not delete previous (renamed) target when done.
+.TP 3n
+\(bu
+\fB\-\-method=\fR\fB\fIcommand\fR\fR
+.sp
+The method for copying files (cp
+or
+scp).
+.TP 3n
+\(bu
+\fB\-\-noindices\fR
+.sp
+Do not include full index files in the backup. This makes the backup smaller and faster. The indexes for reloaded tables can be reconstructed later with
+\fBmyisamchk \-rq\fR.
+.TP 3n
+\(bu
+\fB\-\-password=\fR\fB\fIpassword\fR\fR,
+\fB\-p\fR\fB\fIpassword\fR\fR
+.sp
+The password to use when connecting to the server. Note that the password value is not optional for this option, unlike for other MySQL programs. You can use an option file to avoid giving the password on the command line.
+.sp
+Specifying a password on the command line should be considered insecure. See
+Section\ 6.6, \(lqKeeping Your Password Secure\(rq.
+.TP 3n
+\(bu
+\fB\-\-port=\fR\fB\fIport_num\fR\fR,
+\fB\-P \fR\fB\fIport_num\fR\fR
+.sp
+The TCP/IP port number to use when connecting to the local server.
+.TP 3n
+\(bu
+\fB\-\-quiet\fR,
+\fB\-q\fR
+.sp
+Be silent except for errors.
+.TP 3n
+\(bu
+\fB\-\-record_log_pos=\fR\fB\fIdb_name\fR\fR\fB.\fR\fB\fItbl_name\fR\fR
+.sp
+Record master and slave status in the specified database
+\fIdb_name\fR
+and table
+\fItbl_name\fR.
+.TP 3n
+\(bu
+\fB\-\-regexp=\fR\fB\fIexpr\fR\fR
+.sp
+Copy all databases with names that match the given regular expression.
+.TP 3n
+\(bu
+\fB\-\-resetmaster\fR
+.sp
+Reset the binary log after locking all the tables.
+.TP 3n
+\(bu
+\fB\-\-resetslave\fR
+.sp
+Reset the
+\fImaster.info\fR
+file after locking all the tables.
+.TP 3n
+\(bu
+\fB\-\-socket=\fR\fB\fIpath\fR\fR,
+\fB\-S \fR\fB\fIpath\fR\fR
+.sp
+The Unix socket file to use for the connection.
+.TP 3n
+\(bu
+\fB\-\-suffix=\fR\fB\fIstr\fR\fR
+.sp
+The suffix for names of copied databases.
+.TP 3n
+\(bu
+\fB\-\-tmpdir=\fR\fB\fIpath\fR\fR
+.sp
+The temporary directory. The default is
+\fI/tmp\fR.
+.TP 3n
+\(bu
+\fB\-\-user=\fR\fB\fIuser_name\fR\fR,
+\fB\-u \fR\fB\fIuser_name\fR\fR
+.sp
+The MySQL username to use when connecting to the server.
+.sp
+.RE
+.PP
+\fBmysqlhotcopy\fR
+reads the
+[client]
+and
+[mysqlhotcopy]
+option groups from option files.
+.PP
+To execute
+\fBmysqlhotcopy\fR, you must have access to the files for the tables that you are backing up, the
+SELECT
+privilege for those tables, the
+RELOAD
+privilege (to be able to execute
+FLUSH TABLES), and the
+LOCK TABLES
+privilege (to be able to lock the tables).
+.PP
+Use
+perldoc
+for additional
+\fBmysqlhotcopy\fR
+documentation, including information about the structure of the tables needed for the
+\fB\-\-checkpoint\fR
+and
+\fB\-\-record_log_pos\fR
+options:
+.sp
+.RS 3n
+.nf
+shell> \fBperldoc mysqlhotcopy\fR
+.fi
+.RE
+.SH "COPYRIGHT"
+.PP
+Copyright 2007 MySQL AB
+.PP
+This documentation is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License.
+.PP
+This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
+.PP
+You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110\-1301 USA or see http://www.gnu.org/licenses/.
+.PP
+Please email
+<docs at mysql.com>
+for more information or if you are interested in doing a translation.
+.SH "SEE ALSO"
+For more information, please refer to the MySQL Reference Manual,
+which may already be installed locally and which is also available
+online at http://dev.mysql.com/doc/.
+.SH AUTHOR
+MySQL AB (http://www.mysql.com/).
Added: branches/sid-5.0/debian/manpages/mysqlimport.1
===================================================================
--- branches/sid-5.0/debian/manpages/mysqlimport.1 (rev 0)
+++ branches/sid-5.0/debian/manpages/mysqlimport.1 2007-11-26 12:34:29 UTC (rev 1020)
@@ -0,0 +1,300 @@
+.\" Title: \fBmysqlimport\fR
+.\" Author:
+.\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
+.\" Date: 11/25/2007
+.\" Manual: MySQL Database System
+.\" Source: MySQL 5.0
+.\"
+.TH "\fBMYSQLIMPORT\fR" "1" "11/25/2007" "MySQL 5.0" "MySQL Database System"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
+.SH "NAME"
+mysqlimport \- a data import program
+.SH "SYNOPSIS"
+.HP 44
+\fBmysqlimport [\fR\fB\fIoptions\fR\fR\fB] \fR\fB\fIdb_name\fR\fR\fB \fR\fB\fItextfile1\fR\fR\fB ...\fR
+.SH "DESCRIPTION"
+.PP
+The
+\fBmysqlimport\fR
+client provides a command\-line interface to the
+LOAD DATA INFILE
+SQL statement. Most options to
+\fBmysqlimport\fR
+correspond directly to clauses of
+LOAD DATA INFILE
+syntax. See
+Section\ 2.5, \(lqLOAD DATA INFILE Syntax\(rq.
+.PP
+Invoke
+\fBmysqlimport\fR
+like this:
+.sp
+.RS 3n
+.nf
+shell> \fBmysqlimport [\fR\fB\fIoptions\fR\fR\fB] \fR\fB\fIdb_name\fR\fR\fB \fR\fB\fItextfile1\fR\fR\fB [\fR\fB\fItextfile2\fR\fR\fB ...]\fR
+.fi
+.RE
+.PP
+For each text file named on the command line,
+\fBmysqlimport\fR
+strips any extension from the filename and uses the result to determine the name of the table into which to import the file's contents. For example, files named
+\fIpatient.txt\fR,
+\fIpatient.text\fR, and
+\fIpatient\fR
+all would be imported into a table named
+patient.
+.PP
+\fBmysqlimport\fR
+supports the following options:
+.TP 3n
+\(bu
+\fB\-\-help\fR,
+\fB\-?\fR
+.sp
+Display a help message and exit.
+.TP 3n
+\(bu
+\fB\-\-character\-sets\-dir=\fR\fB\fIpath\fR\fR
+.sp
+The directory where character sets are installed. See
+Section\ 2, \(lqThe Character Set Used for Data and Sorting\(rq.
+.TP 3n
+\(bu
+\fB\-\-columns=\fR\fB\fIcolumn_list\fR\fR,
+\fB\-c \fR\fB\fIcolumn_list\fR\fR
+.sp
+This option takes a comma\-separated list of column names as its value. The order of the column names indicates how to match data file columns with table columns.
+.TP 3n
+\(bu
+\fB\-\-compress\fR,
+\fB\-C\fR
+.sp
+Compress all information sent between the client and the server if both support compression.
+.TP 3n
+\(bu
+\fB\-\-debug[=\fR\fB\fIdebug_options\fR\fR\fB]\fR,
+\fB\-# [\fR\fB\fIdebug_options\fR\fR\fB]\fR
+.sp
+Write a debugging log. The
+\fIdebug_options\fR
+string often is
+\'d:t:o,\fIfile_name\fR'.
+.TP 3n
+\(bu
+\fB\-\-default\-character\-set=\fR\fB\fIcharset_name\fR\fR
+.sp
+Use
+\fIcharset_name\fR
+as the default character set. See
+Section\ 2, \(lqThe Character Set Used for Data and Sorting\(rq.
+.TP 3n
+\(bu
+\fB\-\-delete\fR,
+\fB\-D\fR
+.sp
+Empty the table before importing the text file.
+.TP 3n
+\(bu
+\fB\-\-fields\-terminated\-by=...\fR,
+\fB\-\-fields\-enclosed\-by=...\fR,
+\fB\-\-fields\-optionally\-enclosed\-by=...\fR,
+\fB\-\-fields\-escaped\-by=...\fR
+.sp
+These options have the same meaning as the corresponding clauses for
+LOAD DATA INFILE. See
+Section\ 2.5, \(lqLOAD DATA INFILE Syntax\(rq.
+.TP 3n
+\(bu
+\fB\-\-force\fR,
+\fB\-f\fR
+.sp
+Ignore errors. For example, if a table for a text file does not exist, continue processing any remaining files. Without
+\fB\-\-force\fR,
+\fBmysqlimport\fR
+exits if a table does not exist.
+.TP 3n
+\(bu
+\fB\-\-host=\fR\fB\fIhost_name\fR\fR,
+\fB\-h \fR\fB\fIhost_name\fR\fR
+.sp
+Import data to the MySQL server on the given host. The default host is
+localhost.
+.TP 3n
+\(bu
+\fB\-\-ignore\fR,
+\fB\-i\fR
+.sp
+See the description for the
+\fB\-\-replace\fR
+option.
+.TP 3n
+\(bu
+\fB\-\-ignore\-lines=\fR\fB\fIN\fR\fR
+.sp
+Ignore the first
+\fIN\fR
+lines of the data file.
+.TP 3n
+\(bu
+\fB\-\-lines\-terminated\-by=...\fR
+.sp
+This option has the same meaning as the corresponding clause for
+LOAD DATA INFILE. For example, to import Windows files that have lines terminated with carriage return/linefeed pairs, use
+\fB\-\-lines\-terminated\-by="\\r\\n"\fR. (You might have to double the backslashes, depending on the escaping conventions of your command interpreter.) See
+Section\ 2.5, \(lqLOAD DATA INFILE Syntax\(rq.
+.TP 3n
+\(bu
+\fB\-\-local\fR,
+\fB\-L\fR
+.sp
+Read input files locally from the client host.
+.TP 3n
+\(bu
+\fB\-\-lock\-tables\fR,
+\fB\-l\fR
+.sp
+Lock
+\fIall\fR
+tables for writing before processing any text files. This ensures that all tables are synchronized on the server.
+.TP 3n
+\(bu
+\fB\-\-low\-priority\fR
+.sp
+Use
+LOW_PRIORITY
+when loading the table. This affects only storage engines that use only table\-level locking (MyISAM,
+MEMORY,
+MERGE).
+.TP 3n
+\(bu
+\fB\-\-password[=\fR\fB\fIpassword\fR\fR\fB]\fR,
+\fB\-p[\fR\fB\fIpassword\fR\fR\fB]\fR
+.sp
+The password to use when connecting to the server. If you use the short option form (\fB\-p\fR), you
+\fIcannot\fR
+have a space between the option and the password. If you omit the
+\fIpassword\fR
+value following the
+\fB\-\-password\fR
+or
+\fB\-p\fR
+option on the command line, you are prompted for one.
+.sp
+Specifying a password on the command line should be considered insecure. See
+Section\ 6.6, \(lqKeeping Your Password Secure\(rq.
+.TP 3n
+\(bu
+\fB\-\-port=\fR\fB\fIport_num\fR\fR,
+\fB\-P \fR\fB\fIport_num\fR\fR
+.sp
+The TCP/IP port number to use for the connection.
+.TP 3n
+\(bu
+\fB\-\-protocol={TCP|SOCKET|PIPE|MEMORY}\fR
+.sp
+The connection protocol to use.
+.TP 3n
+\(bu
+\fB\-\-replace\fR,
+\fB\-r\fR
+.sp
+The
+\fB\-\-replace\fR
+and
+\fB\-\-ignore\fR
+options control handling of input rows that duplicate existing rows on unique key values. If you specify
+\fB\-\-replace\fR, new rows replace existing rows that have the same unique key value. If you specify
+\fB\-\-ignore\fR, input rows that duplicate an existing row on a unique key value are skipped. If you do not specify either option, an error occurs when a duplicate key value is found, and the rest of the text file is ignored.
+.TP 3n
+\(bu
+\fB\-\-silent\fR,
+\fB\-s\fR
+.sp
+Silent mode. Produce output only when errors occur.
+.TP 3n
+\(bu
+\fB\-\-socket=\fR\fB\fIpath\fR\fR,
+\fB\-S \fR\fB\fIpath\fR\fR
+.sp
+For connections to
+localhost, the Unix socket file to use, or, on Windows, the name of the named pipe to use.
+.TP 3n
+\(bu
+\fB\-\-ssl*\fR
+.sp
+Options that begin with
+\fB\-\-ssl\fR
+specify whether to connect to the server via SSL and indicate where to find SSL keys and certificates. See
+Section\ 6.7.3, \(lqSSL Command Options\(rq.
+.TP 3n
+\(bu
+\fB\-\-user=\fR\fB\fIuser_name\fR\fR,
+\fB\-u \fR\fB\fIuser_name\fR\fR
+.sp
+The MySQL username to use when connecting to the server.
+.TP 3n
+\(bu
+\fB\-\-verbose\fR,
+\fB\-v\fR
+.sp
+Verbose mode. Print more information about what the program does.
+.TP 3n
+\(bu
+\fB\-\-version\fR,
+\fB\-V\fR
+.sp
+Display version information and exit.
+.sp
+.RE
+.PP
+Here is a sample session that demonstrates use of
+\fBmysqlimport\fR:
+.sp
+.RS 3n
+.nf
+shell> \fBmysql \-e 'CREATE TABLE imptest(id INT, n VARCHAR(30))' test\fR
+shell> \fBed\fR
+a
+100 Max Sydow
+101 Count Dracula
+.
+w imptest.txt
+32
+q
+shell> \fBod \-c imptest.txt\fR
+0000000 1 0 0 \\t M a x S y d o w \\n 1 0
+0000020 1 \\t C o u n t D r a c u l a \\n
+0000040
+shell> \fBmysqlimport \-\-local test imptest.txt\fR
+test.imptest: Records: 2 Deleted: 0 Skipped: 0 Warnings: 0
+shell> \fBmysql \-e 'SELECT * FROM imptest' test\fR
++\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+
+| id | n |
++\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+
+| 100 | Max Sydow |
+| 101 | Count Dracula |
++\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+
+.fi
+.RE
+.SH "COPYRIGHT"
+.PP
+Copyright 2007 MySQL AB
+.PP
+This documentation is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License.
+.PP
+This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
+.PP
+You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110\-1301 USA or see http://www.gnu.org/licenses/.
+.PP
+Please email
+<docs at mysql.com>
+for more information or if you are interested in doing a translation.
+.SH "SEE ALSO"
+For more information, please refer to the MySQL Reference Manual,
+which may already be installed locally and which is also available
+online at http://dev.mysql.com/doc/.
+.SH AUTHOR
+MySQL AB (http://www.mysql.com/).
Added: branches/sid-5.0/debian/manpages/mysqlmanager-pwgen.1
===================================================================
--- branches/sid-5.0/debian/manpages/mysqlmanager-pwgen.1 (rev 0)
+++ branches/sid-5.0/debian/manpages/mysqlmanager-pwgen.1 2007-11-26 12:34:29 UTC (rev 1020)
@@ -0,0 +1,39 @@
+.\" Title: \fBmysqlmanager\-pwgen\fR
+.\" Author:
+.\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
+.\" Date: 11/25/2007
+.\" Manual: MySQL Database System
+.\" Source: MySQL
+.\"
+.TH "\fBMYSQLMANAGER\-PWGE" "1" "11/25/2007" "MySQL" "MySQL Database System"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
+.SH "NAME"
+mysqlmanager\-pwgen \- internal test\-suite program
+.SH "SYNOPSIS"
+.HP 29
+\fBmysqlmanager\-pwgen [\fR\fB\fIoptions\fR\fR\fB]\fR
+.SH "DESCRIPTION"
+.PP
+This program was used internally for test purposes. As of MySQL 5.0, it is no longer used.
+.SH "COPYRIGHT"
+.PP
+Copyright 2007 MySQL AB
+.PP
+This documentation is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License.
+.PP
+This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
+.PP
+You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110\-1301 USA or see http://www.gnu.org/licenses/.
+.PP
+Please email
+<docs at mysql.com>
+for more information or if you are interested in doing a translation.
+.SH "SEE ALSO"
+For more information, please refer to the MySQL Reference Manual,
+which may already be installed locally and which is also available
+online at http://dev.mysql.com/doc/.
+.SH AUTHOR
+MySQL AB (http://www.mysql.com/).
Added: branches/sid-5.0/debian/manpages/mysqlmanager.8
===================================================================
--- branches/sid-5.0/debian/manpages/mysqlmanager.8 (rev 0)
+++ branches/sid-5.0/debian/manpages/mysqlmanager.8 2007-11-26 12:34:29 UTC (rev 1020)
@@ -0,0 +1,784 @@
+.\" Title: \fBmysqlmanager\fR
+.\" Author:
+.\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
+.\" Date: 11/25/2007
+.\" Manual: MySQL Database System
+.\" Source: MySQL 5.0
+.\"
+.TH "\fBMYSQLMANAGER\fR" "8" "11/25/2007" "MySQL 5.0" "MySQL Database System"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
+.SH "NAME"
+mysqlmanager \- the MySQL Instance Manager
+.SH "SYNOPSIS"
+.HP 23
+\fBmysqlmanager [\fR\fB\fIoptions\fR\fR\fB]\fR
+.SH "DESCRIPTION"
+.PP
+\fBmysqlmanager\fR
+is the MySQL Instance Manager (IM). This program monitors and manages MySQL Database Server instances. MySQL Instance Manager is available for Unix\-like operating systems, and also on Windows as of MySQL 5.0.13. It runs as a daemon that listens on a TCP/IP port. On Unix, it also listens on a Unix socket file.
+.PP
+MySQL Instance Manager is included in MySQL distributions from version 5.0.3, and can be used in place of the
+mysqld_safe
+script to start and stop one or more instances of MySQL Server. Because Instance Manager can manage multiple server instances, it can also be used in place of the
+\fBmysqld_multi\fR
+script. Instance Manager offers these capabilities:
+.TP 3n
+\(bu
+Instance Manager can start and stop instances, and report on the status of instances.
+.TP 3n
+\(bu
+Server instances can be treated as guarded or unguarded:
+.RS 3n
+.TP 3n
+\(bu
+When Instance Manager starts, it starts each guarded instance. If the instance crashes, Instance Manager detects this and restarts it. When Instance Manager stops, it stops the instance.
+.TP 3n
+\(bu
+A nonguarded instance is not started when Instance Manager starts or monitored by it. If the instance crashes after being started, Instance Manager does not restart it. When Instance Manager exits, it does not stop the instance if it is running.
+.RE
+.IP "" 3n
+Instances are guarded by default. An instance can be designated as nonguarded by including the
+\fBnonguarded\fR
+option in the configuration file.
+.TP 3n
+\(bu
+Instance Manager provides an interactive interface for configuring instances, so that the need to edit the configuration file manually is reduced or eliminated.
+.TP 3n
+\(bu
+Instance Manager provides remote instance management. That is, it runs on the host where you want to control MySQL Server instances, but you can connect to it from a remote host to perform instance\-management operations.
+.sp
+.RE
+.PP
+The following sections describe MySQL Instance Manager operation in more detail.
+.SH "MYSQL INSTANCE MANAGER COMMAND OPTIONS"
+.PP
+The MySQL Instance Manager supports a number of command options. For a brief listing, invoke
+\fBmysqlmanager\fR
+with the
+\fB\-\-help\fR
+option. Options may be given on the command line or in the Instance Manager configuration file. On Windows, the standard configuration file is
+\fImy.ini\fR
+in the directory where Instance Manager is installed. On Unix, the standard file is
+\fI/etc/my.cnf\fR. To specify a different configuration file, start Instance Manager with the
+\fB\-\-defaults\-file\fR
+option.
+.PP
+\fBmysqlmanager\fR
+supports the following options:
+.TP 3n
+\(bu
+\fB\-\-help\fR,
+\fB\-?\fR
+.sp
+Display a help message and exit.
+.TP 3n
+\(bu
+\fB\-\-angel\-pid\-file=\fR\fB\fIfile_name\fR\fR
+.sp
+The file in which the angel process records its process ID when
+\fBmysqlmanager\fR
+runs in daemon mode (that is, when the
+\fB\-\-run\-as\-service\fR
+option is given). The default filename is
+\fImysqlmanager.angel.pid\fR.
+.sp
+If the
+\fB\-\-angel\-pid\-file\fR
+option is not given, the default angel PID file has the same name as the PID file except that any PID file extension is replaced with an extension of
+\fI.angel.pid\fR. (For example,
+\fImysqlmanager.pid\fR
+becomes
+\fImysqlmanager.angel.pid\fR.)
+.sp
+This option was added in MySQL 5.0.23.
+.TP 3n
+\(bu
+\fB\-\-bind\-address=\fR\fB\fIIP\fR\fR
+.sp
+The IP address to bind to.
+.TP 3n
+\(bu
+\fB\-\-default\-mysqld\-path=\fR\fB\fIpath\fR\fR
+.sp
+The pathname of the MySQL Server binary. This pathname is used for all server instance sections in the configuration file for which no
+\fBmysqld\-path\fR
+option is present. The default value of this option is the compiled\-in pathname, which depends on how the MySQL distribution was configured. Example:
+\fB\-\-default\-mysqld\-path=/usr/sbin/mysqld\fR
+.TP 3n
+\(bu
+\fB\-\-defaults\-file=\fR\fB\fIfile_name\fR\fR
+.sp
+Read Instance Manager and MySQL Server settings from the given file. All configuration changes made by the Instance Manager will be written to this file. This must be the first option on the command line if it is used, and the file must exist.
+.sp
+If this option is not given, Instance Manager uses its standard configuration file. On Windows, the standard file is
+\fImy.ini\fR
+in the directory where Instance Manager is installed. On Unix, the standard file is
+\fI/etc/my.cnf\fR.
+.TP 3n
+\(bu
+\fB\-\-install\fR
+.sp
+On Windows, install Instance Manager as a Windows service. The service name is
+MySQL Manager. This option was added in MySQL 5.0.11.
+.TP 3n
+\(bu
+\fB\-\-log=\fR\fB\fIfile_name\fR\fR
+.sp
+The path to the Instance Manager log file. This option has no effect unless the
+\fB\-\-run\-as\-service\fR
+option is also given. If the filename specified for the option is a relative name, the log file is created under the directory from which Instance Manager is started. To ensure that the file is created in a specific directory, specify it as a full pathname.
+.sp
+If
+\fB\-\-run\-as\-service\fR
+is given without
+\fB\-\-log\fR, the log file is
+\fImysqlmanager.log\fR
+in the data directory.
+.sp
+If
+\fB\-\-run\-as\-service\fR
+is not given, log messages go to the standard output. To capture log output, you can redirect Instance Manager output to a file:
+.sp
+.RS 3n
+.nf
+mysqlmanager > im.log
+.fi
+.RE
+.TP 3n
+\(bu
+\fB\-\-monitoring\-interval=\fR\fB\fIseconds\fR\fR
+.sp
+The interval in seconds for monitoring server instances. The default value is 20 seconds. Instance Manager tries to connect to each monitored (guarded) instance using the non\-existing
+MySQL_Instance_Manager
+user account to check whether it is alive/not hanging. If the result of the connection attempt indicates that the instance is unavailable, Instance Manager performs several attempts to restart the instance.
+.sp
+Normally, the
+MySQL_Instance_Manager
+account does not exist, so the connection attempts by Instance Manager cause the monitored instance to produce messages in its general query log similar to the following:
+.sp
+.RS 3n
+.nf
+Access denied for user 'MySQL_Instance_M'@'localhost' (using password: YES)
+.fi
+.RE
+.sp
+.sp
+The
+nonguarded
+option in the appropriate server instance section disables monitoring for a particular instance. If the instance dies after being started, Instance Manager will not restart it. Instance Manager tries to connect to a nonguarded instance only when you request the instance's status (for example, with the
+SHOW INSTANCES
+status.
+.sp
+See
+the section called \(lqMYSQL SERVER INSTANCE STATUS MONITORING\(rq, for more information.
+.TP 3n
+\(bu
+\fB\-\-passwd\fR,
+\fB\-P\fR
+.sp
+Prepare an entry for the password file, print it to the standard output, and exit. You can redirect the output from Instance Manager to a file to save the entry in the file.
+.TP 3n
+\(bu
+\fB\-\-password\-file=\fR\fB\fIfile_name\fR\fR
+.sp
+The name of the file where the Instance Manager looks for users and passwords. On Windows, the default is
+\fImysqlmanager.passwd\fR
+in the directory where Instance Manager is installed. On Unix, the default file is
+\fI/etc/mysqlmanager.passwd\fR.
+.TP 3n
+\(bu
+\fB\-\-pid\-file=\fR\fB\fIfile_name\fR\fR
+.sp
+The process ID file to use. On Windows, the default file is
+\fImysqlmanager.pid\fR
+in the directory where Instance Manager is installed. On Unix, the default is
+\fImysqlmanager.pid\fR
+in the data directory.
+.TP 3n
+\(bu
+\fB\-\-port=\fR\fB\fIport_num\fR\fR
+.sp
+The port number to use when listening for TCP/IP connections from clients. The default port number (assigned by IANA) is 2273.
+.TP 3n
+\(bu
+\fB\-\-print\-defaults\fR
+.sp
+Print the current defaults and exit. This must be the first option on the command line if it is used.
+.TP 3n
+\(bu
+\fB\-\-remove\fR
+.sp
+On Windows, removes Instance Manager as a Windows service. This assumes that Instance Manager has been run with
+\fB\-\-install\fR
+previously. This option was added in MySQL 5.0.11.
+.TP 3n
+\(bu
+\fB\-\-run\-as\-service\fR
+.sp
+On Unix, daemonize and start an angel process. The angel process monitors Instance Manager and restarts it if it crashes. (The angel process itself is simple and unlikely to crash.)
+.TP 3n
+\(bu
+\fB\-\-socket=\fR\fB\fIpath\fR\fR
+.sp
+On Unix, the socket file to use for incoming connections. The default file is named
+\fI/tmp/mysqlmanager.sock\fR. This option has no meaning on Windows.
+.TP 3n
+\(bu
+\fB\-\-standalone\fR
+.sp
+This option is used on Windows to run Instance Manager in standalone mode. You should specify it when you start Instance Manager from the command line. This option was added in MySQL 5.0.13.
+.TP 3n
+\(bu
+\fB\-\-user=\fR\fB\fIuser_name\fR\fR
+.sp
+On Unix, the username of the system account to use for starting and running
+\fBmysqlmanager\fR. This option generates a warning and has no effect unless you start
+\fBmysqlmanager\fR
+as
+root
+(so that it can change its effective user ID), or as the named user. It is recommended that you configure
+\fBmysqlmanager\fR
+to run using the same account used to run the
+\fBmysqld\fR
+server. (\(lqUser\(rq
+in this context refers to a system login account, not a MySQL user listed in the grant tables.)
+.TP 3n
+\(bu
+\fB\-\-version\fR,
+\fB\-V\fR
+.sp
+Display version information and exit.
+.TP 3n
+\(bu
+\fB\-\-wait\-timeout=\fR\fB\fIN\fR\fR
+.sp
+The number of seconds to wait for activity on an incoming connection before closing it. The default is 28800 seconds (8 hours).
+.sp
+This option was added in MySQL 5.0.19. Before that, the timeout is 30 seconds and cannot be changed.
+.SH "MYSQL INSTANCE MANAGER CONFIGURATION FILES"
+.PP
+Instance Manager uses its standard configuration file unless it is started with a
+\fB\-\-defaults\-file\fR
+option that specifies a different file. On Windows, the standard file is
+\fImy.ini\fR
+in the directory where Instance Manager is installed. On Unix, the standard file is
+\fI/etc/my.cnf\fR. (Prior to MySQL 5.0.10, the MySQL Instance Manager read the same configuration files as the MySQL Server, including
+\fI/etc/my.cnf\fR,
+\fI~/.my.cnf\fR, and so forth.)
+.PP
+Instance Manager reads options for itself from the
+[manager]
+section of the configuration file, and options for server instances from
+[mysqld]
+or
+[mysqld\fIN\fR]
+sections. The
+[manager]
+section contains any of the options listed in
+the section called \(lqMYSQL INSTANCE MANAGER COMMAND OPTIONS\(rq, except for those specified as having to be given as the first option on the command line. Here is a sample
+[manager]
+section:
+.sp
+.RS 3n
+.nf
+# MySQL Instance Manager options section
+[manager]
+default\-mysqld\-path = /usr/local/mysql/libexec/mysqld
+socket=/tmp/manager.sock
+pid\-file=/tmp/manager.pid
+password\-file = /home/cps/.mysqlmanager.passwd
+monitoring\-interval = 2
+port = 1999
+bind\-address = 192.168.1.5
+.fi
+.RE
+.PP
+Each
+[mysqld]
+or
+[mysqld\fIN\fR]
+instance section specifies options given by Instance Manager to a server instance at startup. These are mainly common MySQL Server options (see
+the section called \(lqCOMMAND OPTIONS\(rq). In addition, a
+[mysqld\fIN\fR]
+section can contain the options in the following list, which are specific to Instance Manager. These options are interpreted by Instance Manager itself; it does not pass them to the server when it attempts to start that server.
+.sp
+.it 1 an-trap
+.nr an-no-space-flag 1
+.nr an-break-flag 1
+.br
+\fBWarning\fR
+.PP
+The Instance Manager\-specific options must not be used in a
+[mysqld]
+section. If a server is started without using Instance Manager, it will not recognize these options and will fail to start properly.
+.TP 3n
+\(bu
+mysqld\-path = \fIpath\fR
+.sp
+The pathname of the
+\fBmysqld\fR
+server binary to use for the server instance.
+.TP 3n
+\(bu
+nonguarded
+.sp
+This option disables Instance Manager monitoring functionality for the server instance. By default, an instance is guarded: At Instance Manager start time, it starts the instance. It also monitors the instance status and attempts to restart it if it fails. At Instance Manager exit time, it stops the instance. None of these things happen for nonguarded instances.
+.TP 3n
+\(bu
+shutdown\-delay = \fIseconds\fR
+.sp
+The number of seconds Instance Manager should wait for the server instance to shut down. The default value is 35 seconds. After the delay expires, Instance Manager assumes that the instance is hanging and attempts to terminate it. If you use
+InnoDB
+with large tables, you should increase this value.
+.sp
+.RE
+.PP
+Here are some sample instance sections:
+.sp
+.RS 3n
+.nf
+[mysqld1]
+mysqld\-path=/usr/local/mysql/libexec/mysqld
+socket=/tmp/mysql.sock
+port=3307
+server_id=1
+skip\-stack\-trace
+core\-file
+skip\-bdb
+log\-bin
+log\-error
+log=mylog
+log\-slow\-queries
+[mysqld2]
+nonguarded
+port=3308
+server_id=2
+mysqld\-path= /home/cps/mysql/trees/mysql\-5.0/sql/mysqld
+socket = /tmp/mysql.sock5
+pid\-file = /tmp/hostname.pid5
+datadir= /home/cps/mysql_data/data_dir1
+language=/home/cps/mysql/trees/mysql\-5.0/sql/share/english
+log\-bin
+log=/tmp/fordel.log
+.fi
+.RE
+.SH "STARTING THE MYSQL SERVER WITH MYSQL INSTANCE MANAGER"
+.PP
+This section discusses how Instance Manager starts server instances when it starts. However, before you start Instance Manager, you should set up a password file for it. Otherwise, you will not be able to connect to Instance Manager to control it after it starts. For details about creating Instance Manager accounts, see
+the section called \(lqINSTANCE MANAGER USER AND PASSWORD MANAGEMENT\(rq.
+.PP
+On Unix, the
+\fBmysqld\fR
+MySQL database server normally is started with the
+\fBmysql.server\fR
+script, which usually resides in the
+/etc/init.d/
+directory. In MySQL 5.0.3, this script invokes
+\fBmysqlmanager\fR
+(the MySQL Instance Manager binary) to start MySQL. (In prior versions of MySQL the
+\fBmysqld_safe\fR
+script is used for this purpose.) Starting from MySQL 5.0.4, the behavior of the startup script was changed again to incorporate both setup schemes. In version 5.0.4, the startup script uses the old scheme (invoking
+\fBmysqld_safe\fR) by default, but one can set the
+use_mysqld_safe
+variable in the script to
+0
+(zero) to use the MySQL Instance Manager to start a server.
+.PP
+Starting with MySQL 5.0.19, you can use Instance Manager if you modify the
+\fImy.cnf\fR
+configuration file by adding
+use\-manager
+to the
+[mysql.server]
+section:
+.sp
+.RS 3n
+.nf
+[mysql.server]
+use\-manager
+.fi
+.RE
+.PP
+When Instance Manager starts, it reads its configuration file if it exists to find server instance sections and prepare a list of instances. Instance sections have names of the form
+[mysqld]
+or
+[mysqld\fIN\fR], where
+\fIN\fR
+is an unsigned integer (for example,
+[mysqld1],
+[mysqld2], and so forth).
+.PP
+After preparing the list of instances, Instance Manager starts the guarded instances in the list. If there are no instances, Instance Manager creates an instance named
+mysqld
+and attempts to start it with default (compiled\-in) configuration values. This means that the Instance Manager cannot find the
+\fBmysqld\fR
+program if it is not installed in the default location. (Section\ 4.6, \(lqInstallation Layouts\(rq, describes default locations for components of MySQL distributions.) If you have installed the MySQL server in a non\-standard location, you should create the Instance Manager configuration file.
+.PP
+Instance Manager also stops all guarded server instances when it shuts down.
+.PP
+The allowable options for
+[mysqld\fIN\fR]
+server instance sections are described in
+the section called \(lqMYSQL INSTANCE MANAGER CONFIGURATION FILES\(rq. In these sections, you can use a special
+\fBmysqld\-path=\fR\fB\fIpath\-to\-mysqld\-binary\fR\fR
+option that is recognized only by Instance Manager. Use this option to let Instance Manager know where the
+\fBmysqld\fR
+binary resides. If there are multiple instances, it may also be necessary to set other options such as
+datadir
+and
+port, to ensure that each instance has a different data directory and TCP/IP port number.
+Section\ 9, \(lqRunning Multiple MySQL Servers on the Same Machine\(rq, discusses the configuration values that must differ for each instance when you run multiple instance on the same machine.
+.sp
+.it 1 an-trap
+.nr an-no-space-flag 1
+.nr an-break-flag 1
+.br
+\fBWarning\fR
+.PP
+The
+[mysqld]
+instance section, if it exists, must not contain any Instance Manager\-specific options.
+.PP
+The typical Unix startup/shutdown cycle for a MySQL server with the MySQL Instance Manager enabled is as follows:
+.TP 3n
+1.
+The
+\fB/etc/init.d/mysql\fR
+script starts MySQL Instance Manager.
+.TP 3n
+2.
+Instance Manager starts the guarded server instances and monitors them.
+.TP 3n
+3.
+If a server instance fails, Instance Manager restarts it.
+.TP 3n
+4.
+If Instance Manager is shut down (for example, with the
+\fB/etc/init.d/mysql stop\fR
+command), it shuts down all server instances.
+.SH "INSTANCE MANAGER USER AND PASSWORD MANAGEMENT"
+.PP
+The Instance Manager stores its user information in a password file. On Windows, the default is
+\fImysqlmanager.passwd\fR
+in the directory where Instance Manager is installed. On Unix, the default file is
+\fI/etc/mysqlmanager.passwd\fR. To specify a different location for the password file, use the
+\fB\-\-password\-file\fR
+option.
+.PP
+If the password file does not exist or contains no password entries, you cannot connect to the Instance Manager.
+.sp
+.it 1 an-trap
+.nr an-no-space-flag 1
+.nr an-break-flag 1
+.br
+\fBNote\fR
+.PP
+Any Instance Manager process that is running to monitor server instances does not notice changes to the password file. You must stop it and restart it after making password entry changes.
+.PP
+Entries in the password file have the following format, where the two fields are the account username and encrypted password, separated by a colon:
+.sp
+.RS 3n
+.nf
+petr:*35110DC9B4D8140F5DE667E28C72DD2597B5C848
+.fi
+.RE
+.PP
+Instance Manager password encryption is the same as that used by MySQL Server. It is a one\-way operation; no means are provided for decrypting encrypted passwords.
+.PP
+Instance Manager accounts differ somewhat from MySQL Server accounts:
+.TP 3n
+\(bu
+MySQL Server accounts are associated with a hostname, username, and password (see
+Section\ 6.1, \(lqMySQL Usernames and Passwords\(rq).
+.TP 3n
+\(bu
+Instance Manager accounts are associated with a username and password only.
+.sp
+.RE
+.PP
+This means that a client can connect to Instance Manager with a given username from any host. To limit connections so that clients can connect only from the local host, start Instance Manager with the
+\fB\-\-bind\-address=127.0.0.1\fR
+option so that it listens only to the local network interface. Remote clients will not be able to connect. Local clients can connect like this:
+.sp
+.RS 3n
+.nf
+shell> \fBmysql \-h 127.0.0.1 \-P 2273\fR
+.fi
+.RE
+.PP
+To generate a new entry, invoke Instance Manager with the
+\fB\-\-passwd\fR
+option and append the output to the
+\fI/etc/mysqlmanager.passwd\fR
+file. Here is an example:
+.sp
+.RS 3n
+.nf
+shell> \fBmysqlmanager \-\-passwd >> /etc/mysqlmanager.passwd\fR
+Creating record for new user.
+Enter user name: \fBmike\fR
+Enter password: \fBmikepass\fR
+Re\-type password: \fBmikepass\fR
+.fi
+.RE
+.PP
+At the prompts, enter the username and password for the new Instance Manager user. You must enter the password twice. It does not echo to the screen, so double entry guards against entering a different password than you intend (if the two passwords do not match, no entry is generated).
+.PP
+The preceding command causes the following line to be added to
+\fI/etc/mysqlmanager.passwd\fR:
+.sp
+.RS 3n
+.nf
+mike:*BBF1F551DD9DD96A01E66EC7DDC073911BAD17BA
+.fi
+.RE
+.SH "MYSQL SERVER INSTANCE STATUS MONITORING"
+.PP
+To monitor the status of each guarded server instance, the MySQL Instance Manager attempts to connect to the instance at regular intervals using the
+MySQL_Instance_Manager at localhost
+user account with a password of
+check_connection.
+.PP
+You are
+\fInot\fR
+required to create this account for MySQL Server; in fact, it is expected that it will not exist. Instance Manager can tell that a server is operational if the server accepts the connection attempt but refuses access for the account by returning a login error. However, these failed connection attempts are logged by the server to its general query log (see
+Section\ 8.2, \(lqThe General Query Log\(rq).
+.PP
+Instance Manager also attempts a connection to nonguarded server instances when you use the
+SHOW INSTANCES
+or
+SHOW INSTANCE STATUS
+command. This is the only status monitoring done for nonguarded instances.
+.PP
+Instance Manager knows if a server instance fails at startup because it receives a status from the attempt. For an instance that starts but later crashes, Instance Manager receives a signal because it is the parent process of the instance.
+.SH "CONNECTING TO MYSQL INSTANCE MANAGER"
+.PP
+After you set up a password file for the MySQL Instance Manager and Instance Manager is running, you can connect to it. The MySQL client\-server protocol is used to communicate with the Instance Manager. For example, you can connect to it using the standard
+\fBmysql\fR
+client program:
+.sp
+.RS 3n
+.nf
+shell> \fBmysql \-\-port=2273 \-\-host=im.example.org \-\-user=mysql \-\-password\fR
+.fi
+.RE
+.PP
+Instance Manager supports the version of the MySQL client\-server protocol used by the client tools and libraries distributed with MySQL 4.1 or later, so other programs that use the MySQL C API also can connect to it.
+.SH "MYSQL INSTANCE MANAGER COMMANDS"
+.PP
+After you connect to MySQL Instance Manager, you can issue commands. The following general principles apply to Instance Manager command execution:
+.TP 3n
+\(bu
+Commands that take an instance name fail if the name is not a valid instance name.
+.TP 3n
+\(bu
+Commands that take an instance name fail if the instance does not exist.
+.TP 3n
+\(bu
+Instance Manager maintains information about instance configuration in an internal (in\-memory) cache. Initially, this information comes from the configuration file if it exists, but some commands change the configuration of an instance. Commands that modify the configuration file fail if the file does not exist or is not accessible to Instance Manager.
+.TP 3n
+\(bu
+On Windows, the standard file is
+\fImy.ini\fR
+in the directory where Instance Manager is installed. On Unix, the standard configuration file is
+\fI/etc/my.cnf\fR. To specify a different configuration file, start Instance Manager with the
+\fB\-\-defaults\-file\fR
+option.
+.TP 3n
+\(bu
+If a
+[mysqld]
+instance section exists in the configuration file, it must not contain any Instance Manager\-specific options (see
+the section called \(lqMYSQL INSTANCE MANAGER CONFIGURATION FILES\(rq). Therefore, you must not add any of these options if you change the configuration for an instance named
+mysqld.
+.sp
+.RE
+.PP
+The following list describes the commands that Instance Manager accepts, with examples.
+.TP 3n
+\(bu
+START INSTANCE \fIinstance_name\fR
+.sp
+This command attempts to start an offline instance. The command is asynchronous; it does not wait for the instance to start.
+.sp
+.RS 3n
+.nf
+mysql> \fBSTART INSTANCE mysqld4;\fR
+Query OK, 0 rows affected (0,00 sec)
+.fi
+.RE
+.TP 3n
+\(bu
+STOP INSTANCE \fIinstance_name\fR
+.sp
+This command attempts to stop an instance. The command is synchronous; it waits for the instance to stop.
+.sp
+.RS 3n
+.nf
+mysql> \fBSTOP INSTANCE mysqld4;\fR
+Query OK, 0 rows affected (0,00 sec)
+.fi
+.RE
+.TP 3n
+\(bu
+SHOW INSTANCES
+.sp
+Shows the names and status of all loaded instances.
+.sp
+.RS 3n
+.nf
+mysql> \fBSHOW INSTANCES;\fR
++\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-+
+| instance_name | status |
++\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-+
+| mysqld3 | offline |
+| mysqld4 | online |
+| mysqld2 | offline |
++\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-+
+.fi
+.RE
+.TP 3n
+\(bu
+SHOW INSTANCE STATUS \fIinstance_name\fR
+.sp
+Shows status and version information for an instance.
+.sp
+.RS 3n
+.nf
+mysql> \fBSHOW INSTANCE STATUS mysqld3;\fR
++\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-+
+| instance_name | status | version |
++\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-+
+| mysqld3 | online | unknown |
++\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-+
+.fi
+.RE
+.TP 3n
+\(bu
+SHOW INSTANCE OPTIONS \fIinstance_name\fR
+.sp
+Shows the options used by an instance.
+.sp
+.RS 3n
+.nf
+mysql> \fBSHOW INSTANCE OPTIONS mysqld3;\fR
++\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+
+| option_name | value |
++\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+
+| instance_name | mysqld3 |
+| mysqld\-path | /home/cps/mysql/trees/mysql\-4.1/sql/mysqld |
+| port | 3309 |
+| socket | /tmp/mysql.sock3 |
+| pid\-file | hostname.pid3 |
+| datadir | /home/cps/mysql_data/data_dir1/ |
+| language | /home/cps/mysql/trees/mysql\-4.1/sql/share/english |
++\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+
+.fi
+.RE
+.TP 3n
+\(bu
+SHOW \fIinstance_name\fR LOG FILES
+.sp
+The command lists all log files used by the instance. The result set contains the path to the log file and the log file size. If no log file path is specified in the instance section of the configuration file (for example,
+log=/var/mysql.log), the Instance Manager tries to guess its placement. If Instance Manager is unable to guess the log file placement you should specify the log file location explicitly by using a log option in the appropriate instance section of the configuration file.
+.sp
+.RS 3n
+.nf
+mysql> \fBSHOW mysqld LOG FILES;\fR
++\-\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-+
+| Logfile | Path | Filesize |
++\-\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-+
+| ERROR LOG | /home/cps/var/mysql/owlet.err | 9186 |
+| GENERAL LOG | /home/cps/var/mysql/owlet.log | 471503 |
+| SLOW LOG | /home/cps/var/mysql/owlet\-slow.log | 4463 |
++\-\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-+
+.fi
+.RE
+Log options are described in
+the section called \(lqCOMMAND OPTIONS\(rq.
+.TP 3n
+\(bu
+SHOW \fIinstance_name\fR LOG {ERROR | SLOW | GENERAL} \fIsize\fR[,\fIoffset_from_end\fR]
+.sp
+This command retrieves a portion of the specified log file. Because most users are interested in the latest log messages, the
+\fIsize\fR
+parameter defines the number of bytes to retrieve from the end of the log. To retrieve data from the middle of the log file, specify the optional
+\fIoffset_from_end\fR
+parameter. The following example retrieves 21 bytes of data, starting 23 bytes before the end of the log file and ending 2 bytes before the end:
+.sp
+.RS 3n
+.nf
+mysql> \fBSHOW mysqld LOG GENERAL 21, 2;\fR
++\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+
+| Log |
++\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+
+| using password: YES |
++\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+
+.fi
+.RE
+.TP 3n
+\(bu
+SET \fIinstance_name\fR.\fIoption_name\fR[=\fIoption_value\fR]
+.sp
+This command edits the specified instance's configuration section to change or add instance options. The option is added to the section is it is not already present. Otherwise, the new setting replaces the existing one.
+.sp
+.RS 3n
+.nf
+mysql> \fBSET mysqld2.port=3322;\fR
+Query OK, 0 rows affected (0.00 sec)
+.fi
+.RE
+Changes made to the configuration file do not take effect until the MySQL server is restarted. In addition, these changes are not stored in the instance manager's local cache of instance settings until a
+FLUSH INSTANCES
+command is executed.
+.TP 3n
+\(bu
+UNSET \fIinstance_name\fR.\fIoption_name\fR
+.sp
+This command removes an option from an instance's configuration section.
+.sp
+.RS 3n
+.nf
+mysql> \fBUNSET mysqld2.port;\fR
+Query OK, 0 rows affected (0.00 sec)
+.fi
+.RE
+Changes made to the configuration file do not take effect until the MySQL server is restarted. In addition, these changes are not stored in the instance manager's local cache of instance settings until a
+FLUSH INSTANCES
+command is executed.
+.TP 3n
+\(bu
+FLUSH INSTANCES
+.sp
+This command forces Instance Manager reread the configuration file and to refresh internal structures. This command should be performed after editing the configuration file. The command does not restart instances.
+.sp
+.RS 3n
+.nf
+mysql> \fBFLUSH INSTANCES;\fR
+Query OK, 0 rows affected (0.04 sec)
+.fi
+.RE
+FLUSH INSTANCES
+is deprecated and will be removed in MySQL 5.2.
+.SH "COPYRIGHT"
+.PP
+Copyright 2007 MySQL AB
+.PP
+This documentation is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License.
+.PP
+This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
+.PP
+You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110\-1301 USA or see http://www.gnu.org/licenses/.
+.PP
+Please email
+<docs at mysql.com>
+for more information or if you are interested in doing a translation.
+.SH "SEE ALSO"
+For more information, please refer to the MySQL Reference Manual,
+which may already be installed locally and which is also available
+online at http://dev.mysql.com/doc/.
+.SH AUTHOR
+MySQL AB (http://www.mysql.com/).
Added: branches/sid-5.0/debian/manpages/mysqlmanagerc.1
===================================================================
--- branches/sid-5.0/debian/manpages/mysqlmanagerc.1 (rev 0)
+++ branches/sid-5.0/debian/manpages/mysqlmanagerc.1 2007-11-26 12:34:29 UTC (rev 1020)
@@ -0,0 +1,39 @@
+.\" Title: \fBmysqlmanagerc\fR
+.\" Author:
+.\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
+.\" Date: 11/25/2007
+.\" Manual: MySQL Database System
+.\" Source: MySQL
+.\"
+.TH "\fBMYSQLMANAGERC\fR" "1" "11/25/2007" "MySQL" "MySQL Database System"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
+.SH "NAME"
+mysqlmanagerc \- internal test\-suite program
+.SH "SYNOPSIS"
+.HP 24
+\fBmysqlmanagerc [\fR\fB\fIoptions\fR\fR\fB]\fR
+.SH "DESCRIPTION"
+.PP
+This program was used internally for test purposes. As of MySQL 5.0, it is no longer used.
+.SH "COPYRIGHT"
+.PP
+Copyright 2007 MySQL AB
+.PP
+This documentation is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License.
+.PP
+This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
+.PP
+You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110\-1301 USA or see http://www.gnu.org/licenses/.
+.PP
+Please email
+<docs at mysql.com>
+for more information or if you are interested in doing a translation.
+.SH "SEE ALSO"
+For more information, please refer to the MySQL Reference Manual,
+which may already be installed locally and which is also available
+online at http://dev.mysql.com/doc/.
+.SH AUTHOR
+MySQL AB (http://www.mysql.com/).
Added: branches/sid-5.0/debian/manpages/mysqlshow.1
===================================================================
--- branches/sid-5.0/debian/manpages/mysqlshow.1 (rev 0)
+++ branches/sid-5.0/debian/manpages/mysqlshow.1 2007-11-26 12:34:29 UTC (rev 1020)
@@ -0,0 +1,227 @@
+.\" Title: \fBmysqlshow\fR
+.\" Author:
+.\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
+.\" Date: 11/25/2007
+.\" Manual: MySQL Database System
+.\" Source: MySQL 5.0
+.\"
+.TH "\fBMYSQLSHOW\fR" "1" "11/25/2007" "MySQL 5.0" "MySQL Database System"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
+.SH "NAME"
+mysqlshow \- display database, table, and column information
+.SH "SYNOPSIS"
+.HP 52
+\fBmysqlshow [\fR\fB\fIoptions\fR\fR\fB] [\fR\fB\fIdb_name\fR\fR\fB [\fR\fB\fItbl_name\fR\fR\fB [\fR\fB\fIcol_name\fR\fR\fB]]]\fR
+.SH "DESCRIPTION"
+.PP
+The
+\fBmysqlshow\fR
+client can be used to quickly see which databases exist, their tables, or a table's columns or indexes.
+.PP
+\fBmysqlshow\fR
+provides a command\-line interface to several SQL
+SHOW
+statements. See
+Section\ 5.4, \(lqSHOW Syntax\(rq. The same information can be obtained by using those statements directly. For example, you can issue them from the
+\fBmysql\fR
+client program.
+.PP
+Invoke
+\fBmysqlshow\fR
+like this:
+.sp
+.RS 3n
+.nf
+shell> \fBmysqlshow [\fR\fB\fIoptions\fR\fR\fB] [\fR\fB\fIdb_name\fR\fR\fB [\fR\fB\fItbl_name\fR\fR\fB [\fR\fB\fIcol_name\fR\fR\fB]]]\fR
+.fi
+.RE
+.TP 3n
+\(bu
+If no database is given, a list of database names is shown.
+.TP 3n
+\(bu
+If no table is given, all matching tables in the database are shown.
+.TP 3n
+\(bu
+If no column is given, all matching columns and column types in the table are shown.
+.sp
+.RE
+.PP
+The output displays only the names of those databases, tables, or columns for which you have some privileges.
+.PP
+If the last argument contains shell or SQL wildcard characters (\(lq*\(rq,
+\(lq?\(rq,
+\(lq%\(rq, or
+\(lq_\(rq), only those names that are matched by the wildcard are shown. If a database name contains any underscores, those should be escaped with a backslash (some Unix shells require two) to get a list of the proper tables or columns.
+\(lq*\(rq
+and
+\(lq?\(rq
+characters are converted into SQL
+\(lq%\(rq
+and
+\(lq_\(rq
+wildcard characters. This might cause some confusion when you try to display the columns for a table with a
+\(lq_\(rq
+in the name, because in this case,
+\fBmysqlshow\fR
+shows you only the table names that match the pattern. This is easily fixed by adding an extra
+\(lq%\(rq
+last on the command line as a separate argument.
+.PP
+\fBmysqlshow\fR
+supports the following options:
+.TP 3n
+\(bu
+\fB\-\-help\fR,
+\fB\-?\fR
+.sp
+Display a help message and exit.
+.TP 3n
+\(bu
+\fB\-\-character\-sets\-dir=\fR\fB\fIpath\fR\fR
+.sp
+The directory where character sets are installed. See
+Section\ 2, \(lqThe Character Set Used for Data and Sorting\(rq.
+.TP 3n
+\(bu
+\fB\-\-compress\fR,
+\fB\-C\fR
+.sp
+Compress all information sent between the client and the server if both support compression.
+.TP 3n
+\(bu
+\fB\-\-count\fR
+.sp
+Show the number of rows per table. This can be slow for non\-MyISAM
+tables. This option was added in MySQL 5.0.6.
+.TP 3n
+\(bu
+\fB\-\-debug[=\fR\fB\fIdebug_options\fR\fR\fB]\fR,
+\fB\-# [\fR\fB\fIdebug_options\fR\fR\fB]\fR
+.sp
+Write a debugging log. The
+\fIdebug_options\fR
+string often is
+\'d:t:o,\fIfile_name\fR'.
+.TP 3n
+\(bu
+\fB\-\-default\-character\-set=\fR\fB\fIcharset_name\fR\fR
+.sp
+Use
+\fIcharset_name\fR
+as the default character set. See
+Section\ 2, \(lqThe Character Set Used for Data and Sorting\(rq.
+.TP 3n
+\(bu
+\fB\-\-host=\fR\fB\fIhost_name\fR\fR,
+\fB\-h \fR\fB\fIhost_name\fR\fR
+.sp
+Connect to the MySQL server on the given host.
+.TP 3n
+\(bu
+\fB\-\-keys\fR,
+\fB\-k\fR
+.sp
+Show table indexes.
+.TP 3n
+\(bu
+\fB\-\-password[=\fR\fB\fIpassword\fR\fR\fB]\fR,
+\fB\-p[\fR\fB\fIpassword\fR\fR\fB]\fR
+.sp
+The password to use when connecting to the server. If you use the short option form (\fB\-p\fR), you
+\fIcannot\fR
+have a space between the option and the password. If you omit the
+\fIpassword\fR
+value following the
+\fB\-\-password\fR
+or
+\fB\-p\fR
+option on the command line, you are prompted for one.
+.sp
+Specifying a password on the command line should be considered insecure. See
+Section\ 6.6, \(lqKeeping Your Password Secure\(rq.
+.sp
+Specifying a password on the command line should be considered insecure. See
+Section\ 6.6, \(lqKeeping Your Password Secure\(rq.
+.TP 3n
+\(bu
+\fB\-\-port=\fR\fB\fIport_num\fR\fR,
+\fB\-P \fR\fB\fIport_num\fR\fR
+.sp
+The TCP/IP port number to use for the connection.
+.TP 3n
+\(bu
+\fB\-\-protocol={TCP|SOCKET|PIPE|MEMORY}\fR
+.sp
+The connection protocol to use.
+.TP 3n
+\(bu
+\fB\-\-show\-table\-type\fR,
+\fB\-t\fR
+.sp
+Show a column indicating the table type, as in
+SHOW FULL TABLES. The type is
+BASE TABLE
+or
+VIEW. This option was added in MySQL 5.0.4.
+.TP 3n
+\(bu
+\fB\-\-socket=\fR\fB\fIpath\fR\fR,
+\fB\-S \fR\fB\fIpath\fR\fR
+.sp
+For connections to
+localhost, the Unix socket file to use, or, on Windows, the name of the named pipe to use.
+.TP 3n
+\(bu
+\fB\-\-ssl*\fR
+.sp
+Options that begin with
+\fB\-\-ssl\fR
+specify whether to connect to the server via SSL and indicate where to find SSL keys and certificates. See
+Section\ 6.7.3, \(lqSSL Command Options\(rq.
+.TP 3n
+\(bu
+\fB\-\-status\fR,
+\fB\-i\fR
+.sp
+Display extra information about each table.
+.TP 3n
+\(bu
+\fB\-\-user=\fR\fB\fIuser_name\fR\fR,
+\fB\-u \fR\fB\fIuser_name\fR\fR
+.sp
+The MySQL username to use when connecting to the server.
+.TP 3n
+\(bu
+\fB\-\-verbose\fR,
+\fB\-v\fR
+.sp
+Verbose mode. Print more information about what the program does. This option can be used multiple times to increase the amount of information.
+.TP 3n
+\(bu
+\fB\-\-version\fR,
+\fB\-V\fR
+.sp
+Display version information and exit.
+.SH "COPYRIGHT"
+.PP
+Copyright 2007 MySQL AB
+.PP
+This documentation is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License.
+.PP
+This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
+.PP
+You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110\-1301 USA or see http://www.gnu.org/licenses/.
+.PP
+Please email
+<docs at mysql.com>
+for more information or if you are interested in doing a translation.
+.SH "SEE ALSO"
+For more information, please refer to the MySQL Reference Manual,
+which may already be installed locally and which is also available
+online at http://dev.mysql.com/doc/.
+.SH AUTHOR
+MySQL AB (http://www.mysql.com/).
Added: branches/sid-5.0/debian/manpages/mysqltest.1
===================================================================
--- branches/sid-5.0/debian/manpages/mysqltest.1 (rev 0)
+++ branches/sid-5.0/debian/manpages/mysqltest.1 2007-11-26 12:34:29 UTC (rev 1020)
@@ -0,0 +1,383 @@
+.\" Title: \fBmysqltest\fR
+.\" Author:
+.\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
+.\" Date: 11/21/2007
+.\" Manual: MySQL Database System
+.\" Source: MySQL
+.\"
+.TH "\fBMYSQLTEST\fR" "1" "11/21/2007" "MySQL" "MySQL Database System"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
+.SH "NAME"
+mysqltest \- program to run test cases
+.br
+mysqltest_embedded \- program to run embedded test cases
+.SH "SYNOPSIS"
+.HP 30
+\fBmysqltest [\fR\fB\fIoptions\fR\fR\fB] [\fR\fB\fIdb_name\fR\fR\fB]\fR
+.HP 39
+\fBmysqltest_embedded [\fR\fB\fIoptions\fR\fR\fB] [\fR\fB\fIdb_name\fR\fR\fB]\fR
+.SH "DESCRIPTION"
+.PP
+The
+\fBmysqltest\fR
+program runs a test case against a MySQL server and optionally compares the output with a result file. This program reads input written in a special test language. Typically, you invoke
+\fBmysqltest\fR
+via
+\fBmysql\-test\-run.pl\fR
+rather than invoking it directly.
+.PP
+\fBmysqltest_embedded\fR
+is similar but is built with support for the
+libmysqld
+embedded server.
+.PP
+Features of
+\fBmysqltest\fR:
+.TP 3n
+\(bu
+Can send SQL statements to MySQL servers for execution
+.TP 3n
+\(bu
+Can execute external shell commands
+.TP 3n
+\(bu
+Can test whether the result from a SQL statement or shell command is as expected
+.TP 3n
+\(bu
+Can connect to one or more standalone
+\fBmysqld\fR
+servers and switch between connections
+.TP 3n
+\(bu
+Can connect to an embedded server (libmysqld), if MySQL is compiled with support for
+libmysqld. (In this case, the executable is named
+\fBmysqltest_embedded\fR
+rather than
+\fBmysqltest\fR.)
+.sp
+.RE
+.PP
+By default,
+\fBmysqltest\fR
+reads the test case on the standard input. To run
+\fBmysqltest\fR
+this way, you normally invoke it like this:
+.sp
+.RS 3n
+.nf
+shell> \fBmysqltest [\fR\fB\fIoptions\fR\fR\fB] [\fR\fB\fIdb_name\fR\fR\fB] < \fR\fB\fItest_file\fR\fR
+.fi
+.RE
+.PP
+You can also name the test case file with a
+\fB\-\-test\-file=\fR\fB\fIfile_name\fR\fR
+option.
+.PP
+\fBmysqltest\fR
+supports the following options:
+.TP 3n
+\(bu
+\fB\-\-help\fR,
+\fB\-?\fR
+.sp
+Display a help message and exit.
+.TP 3n
+\(bu
+\fB\-\-basedir=\fR\fB\fIdir_name\fR\fR,
+\fB\-b \fR\fB\fIdir_name\fR\fR
+.sp
+The base directory for tests.
+.TP 3n
+\(bu
+\fB\-\-big\-test\fR,
+\fB\-B\fR
+.sp
+Define the
+\fBmysqltest\fR
+variable
+$BIG_TEST
+as 1. This option was removed in MySQL 4.1.23, 5.0.30, and 5.1.13.
+.TP 3n
+\(bu
+\fB\-\-character\-sets\-dir=\fR\fB\fIpath\fR\fR
+.sp
+The directory where character sets are installed. This option was added in MySQL 4.1.23, 5.0.32, and 5.1.13.
+.TP 3n
+\(bu
+\fB\-\-compress\fR,
+\fB\-C\fR
+.sp
+Compress all information sent between the client and the server if both support compression.
+.TP 3n
+\(bu
+\fB\-\-cursor\-protocol\fR
+.sp
+Use cursors for prepared statements (implies
+\fB\-\-ps\-protocol\fR). This option was added in MySQL 5.0.19.
+.TP 3n
+\(bu
+\fB\-\-database=\fR\fB\fIdb_name\fR\fR,
+\fB\-D \fR\fB\fIdb_name\fR\fR
+.sp
+The default database to use.
+.TP 3n
+\(bu
+\fB\-\-debug[=\fR\fB\fIdebug_options\fR\fR\fB]\fR,
+\fB\-#[\fR\fB\fIdebug_options\fR\fR\fB]\fR
+.sp
+Write a debugging log if MySQL is built with debugging support. The default
+\fIdebug_options\fR
+value is
+\'d:t:S:i:O,/tmp/mysqltest.trace'.
+.TP 3n
+\(bu
+\fB\-\-debug\-check\fR
+.sp
+Print some debugging information when the program exits. This option was added in MySQL 5.1.21.
+.TP 3n
+\(bu
+\fB\-\-debug\-info\fR
+.sp
+Print debugging information and memory and CPU usage statistics when the program exits. This option was added in MySQL 5.1.14.
+.TP 3n
+\(bu
+\fB\-\-host=\fR\fB\fIhost_name\fR\fR,
+\fB\-h \fR\fB\fIhost_name\fR\fR
+.sp
+Connect to the MySQL server on the given host.
+.TP 3n
+\(bu
+\fB\-\-include=\fR\fB\fIfile_name\fR\fR,
+\fB\-i \fR\fB\fIfile_name\fR\fR
+.sp
+Include the contents of the given file before processing the contents of the test file. The included file should have the same format as other
+\fBmysqltest\fR
+test files. This option has the same effect as putting a
+\-\-source \fIfile_name\fR
+command as the first line of the test file. This option was added in MySQL 4.1.23, 5.0.30, and 5.1.7.
+.TP 3n
+\(bu
+\fB\-\-logdir=\fR\fB\fIdir_name\fR\fR
+.sp
+The directory to use for log files. This option was added in MySQL 5.1.14.
+.TP 3n
+\(bu
+\fB\-\-mark\-progress\fR
+.sp
+Write the line number and elapsed time to
+\fI\fItest_file\fR\fR\fI.progress\fR. This option was added in MySQL 4.1.23, 5.0.30, and 5.1.12.
+.TP 3n
+\(bu
+\fB\-\-max\-connect\-retries=\fR\fB\fInum\fR\fR
+.sp
+The maximum number of connection attempts when connecting to server. This option was added in MySQL 4.1.23, 5.0.23, and 5.1.11.
+.TP 3n
+\(bu
+\fB\-\-no\-defaults\fR
+.sp
+Do not read default options from any option files.
+.TP 3n
+\(bu
+\fB\-\-password[=\fR\fB\fIpassword\fR\fR\fB]\fR,
+\fB\-p[\fR\fB\fIpassword\fR\fR\fB]\fR
+.sp
+The password to use when connecting to the server. If you use the short option form (\fB\-p\fR), you
+\fIcannot\fR
+have a space between the option and the password. If you omit the
+\fIpassword\fR
+value following the
+\fB\-\-password\fR
+or
+\fB\-p\fR
+option on the command line, you are prompted for one.
+.TP 3n
+\(bu
+\fB\-\-port=\fR\fB\fIport_num\fR\fR,
+\fB\-P \fR\fB\fIport_num\fR\fR
+.sp
+The TCP/IP port number to use for the connection.
+.TP 3n
+\(bu
+\fB\-\-ps\-protocol\fR
+.sp
+Use the prepared\-statement protocol for communication.
+.TP 3n
+\(bu
+\fB\-\-quiet\fR
+.sp
+Suppress all normal output. This is a synonym for
+\fB\-\-silent\fR.
+.TP 3n
+\(bu
+\fB\-\-record\fR,
+\fB\-r\fR
+.sp
+Record the output that results from running the test file into the file named by the
+\fB\-\-result\-file\fR
+option, if that option is given.
+.TP 3n
+\(bu
+\fB\-\-result\-file=\fR\fB\fIfile_name\fR\fR,
+\fB\-R \fR\fB\fIfile_name\fR\fR
+.sp
+This option specifies the file for test case expected results.
+\fB\-\-result\-file\fR, together with
+\fB\-\-record\fR, determines how
+\fBmysqltest\fR
+treats the test actual and expected results for a test case:
+.RS 3n
+.TP 3n
+\(bu
+If the test produces no results,
+\fBmysqltest\fR
+exits with an error message to that effect.
+.TP 3n
+\(bu
+Otherwise, if
+\fB\-\-result\-file\fR
+is not given,
+\fBmysqltest\fR
+sends test results to the standard output.
+.TP 3n
+\(bu
+With
+\fB\-\-result\-file\fR
+but not
+\fB\-\-record\fR,
+\fBmysqltest\fR
+reads the expected results from the given file and compares them with the actual results. If the results do not match,
+\fBmysqltest\fR
+writes a
+\fI.reject\fR
+file in the same directory as the result file and exits with an error.
+.TP 3n
+\(bu
+With both
+\fB\-\-result\-file\fR
+and
+\fB\-\-record\fR,
+\fBmysqltest\fR
+updates the given file by writing the actual test results to it.
+.RE
+.TP 3n
+\(bu
+\fB\-\-server\-arg=\fR\fB\fIvalue\fR\fR,
+\fB\-A \fR\fB\fIvalue\fR\fR
+.sp
+Pass the argument as an argument to the embedded server. For example,
+\fB\-\-server\-arg=\-\-tmpdir=/tmp\fR
+or
+\fB\-\-server\-arg=\-\-core\fR. Up to 64 arguments can be given.
+.TP 3n
+\(bu
+\fB\-\-server\-file=\fR\fB\fIfile_name\fR\fR,
+\fB\-F \fR\fB\fIfile_name\fR\fR
+.sp
+Read arguments for the embedded server from the given file. The file should contain one argument per line.
+.TP 3n
+\(bu
+\fB\-\-silent\fR,
+\fB\-s\fR
+.sp
+Suppress all normal output.
+.TP 3n
+\(bu
+\fB\-\-skip\-safemalloc\fR
+.sp
+Do not use memory allocation checking.
+.TP 3n
+\(bu
+\fB\-\-sleep=\fR\fB\fInum\fR\fR,
+\fB\-T \fR\fB\fInum\fR\fR
+.sp
+Cause all
+sleep
+commands in the test case file to sleep
+\fInum\fR
+seconds. This option does not affect
+real_sleep
+commands.
+.sp
+As of MySQL 5.0.23, an option value of 0 can be used, which effectively disables
+sleep
+commands in the test case.
+.TP 3n
+\(bu
+\fB\-\-socket=\fR\fB\fIpath\fR\fR,
+\fB\-S \fR\fB\fIpath\fR\fR
+.sp
+The socket file to use when connecting to
+localhost
+(which is the default host).
+.TP 3n
+\(bu
+\fB\-\-sp\-protocol\fR
+.sp
+Execute DML statements within a stored procedure. For every DML statement,
+\fBmysqltest\fR
+creates and invokes a stored procedure that executes the statement rather than executing the statement directly. This option was added in MySQL 5.0.19.
+.TP 3n
+\(bu
+\fB\-\-test\-file=\fR\fB\fIfile_name\fR\fR,
+\fB\-x \fR\fB\fIfile_name\fR\fR
+.sp
+Read test input from this file. The default is to read from the standard input.
+.TP 3n
+\(bu
+\fB\-\-timer\-file=\fR\fB\fIfile_name\fR\fR,
+\fB\-m \fR\fB\fIfile_name\fR\fR
+.sp
+The file where the timing in microseconds is written.
+.TP 3n
+\(bu
+\fB\-\-tmpdir=\fR\fB\fIdir_name\fR\fR,
+\fB\-t \fR\fB\fIdir_name\fR\fR
+.sp
+The temporary directory where socket files are put.
+.TP 3n
+\(bu
+\fB\-\-user=\fR\fB\fIuser_name\fR\fR,
+\fB\-u \fR\fB\fIuser_name\fR\fR
+.sp
+The MySQL username to use when connecting to the server.
+.TP 3n
+\(bu
+\fB\-\-verbose\fR,
+\fB\-v\fR
+.sp
+Verbose mode. Print out more information what the program does.
+.TP 3n
+\(bu
+\fB\-\-version\fR,
+\fB\-V\fR
+.sp
+Display version information and exit.
+.TP 3n
+\(bu
+\fB\-\-view\-protocol\fR
+.sp
+Every
+SELECT
+statement is wrapped inside a view. This option was added in MySQL 5.0.19.
+.SH "COPYRIGHT"
+.PP
+Copyright 2007 MySQL AB
+.PP
+This documentation is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License.
+.PP
+This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
+.PP
+You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110\-1301 USA or see http://www.gnu.org/licenses/.
+.PP
+Please email
+<docs at mysql.com>
+for more information or if you are interested in doing a translation.
+.SH "SEE ALSO"
+For more information, please refer to the MySQL Reference Manual,
+which may already be installed locally and which is also available
+online at http://dev.mysql.com/doc/.
+.SH AUTHOR
+MySQL AB (http://www.mysql.com/).
Added: branches/sid-5.0/debian/manpages/mysqltest_embedded.1
===================================================================
--- branches/sid-5.0/debian/manpages/mysqltest_embedded.1 (rev 0)
+++ branches/sid-5.0/debian/manpages/mysqltest_embedded.1 2007-11-26 12:34:29 UTC (rev 1020)
@@ -0,0 +1 @@
+.so man1/mysqltest.1
Added: branches/sid-5.0/debian/manpages/ndb_config.1
===================================================================
--- branches/sid-5.0/debian/manpages/ndb_config.1 (rev 0)
+++ branches/sid-5.0/debian/manpages/ndb_config.1 2007-11-26 12:34:29 UTC (rev 1020)
@@ -0,0 +1,283 @@
+.\" Title: \fBndb_config\fR
+.\" Author:
+.\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
+.\" Date: 11/25/2007
+.\" Manual: MySQL Database System
+.\" Source: MySQL 5.0
+.\"
+.TH "\fBNDB_CONFIG\fR" "1" "11/25/2007" "MySQL 5.0" "MySQL Database System"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
+.SH "NAME"
+ndb_config \- extract NDB configuration information
+.SH "SYNOPSIS"
+.HP 19
+\fBndb_config \fR\fB\fIoptions\fR\fR
+.SH "DESCRIPTION"
+.PP
+This tool extracts configuration information for data nodes, SQL nodes, and API nodes from a cluster management node (and possibly its
+\fIconfig.ini\fR
+file).
+.PP
+\fBUsage\fR:
+.sp
+.RS 3n
+.nf
+ndb_config \fIoptions\fR
+.fi
+.RE
+.PP
+The
+\fIoptions\fR
+available for this utility differ somewhat from those used with the other utilities, and so are listed in their entirety in the next section, followed by some examples.
+.PP
+\fBOptions\fR:
+.TP 3n
+\(bu
+\fB\-\-usage\fR,
+\fB\-\-help\fR, or
+\fB\-?\fR
+.sp
+Causes
+\fBndb_config\fR
+to print a list of available options, and then exit.
+.TP 3n
+\(bu
+\fB\-\-version\fR,
+\fB\-V\fR
+.sp
+Causes
+\fBndb_config\fR
+to print a version information string, and then exit.
+.TP 3n
+\(bu
+\fB\-\-ndb\-connectstring=\fR\fB\fIconnect_string\fR\fR
+.sp
+Specifies the connectstring to use in connecting to the management server. The format for the connectstring is the same as described in
+Section\ 3.4.2, \(lqThe Cluster Connectstring\(rq, and defaults to
+localhost:1186.
+.sp
+.it 1 an-trap
+.nr an-no-space-flag 1
+.nr an-break-flag 1
+.br
+\fBNote\fR
+The use of
+\fB\-c\fR
+as a short version for this option is supported for
+\fBndb_config\fR
+beginning with MySQL 5.0.29.
+.TP 3n
+\(bu
+\fB\-\-config\-file=\fR\fB\fIpath\-to\-file\fR\fR
+.sp
+Gives the path to the management server's configuration file (\fIconfig.ini\fR). This may be a relative or absolute path. If the management node resides on a different host from the one on which
+\fBndb_config\fR
+is invoked, then an absolute path must be used.
+.TP 3n
+\(bu
+\fB\-\-query=\fR\fB\fIquery\-options\fR\fR,
+\fB\-q\fR
+\fIquery\-options\fR
+.sp
+This is a comma\-delimited list of
+query options
+\(em that is, a list of one or more node attributes to be returned. These include
+id
+(node ID), type (node type \(em that is,
+ndbd,
+mysqld, or
+ndb_mgmd), and any configuration parameters whose values are to be obtained.
+.sp
+For example,
+\fB\-\-query=id,type,indexmemory,datamemory\fR
+would return the node ID, node type,
+DataMemory, and
+IndexMemory
+for each node.
+.sp
+.it 1 an-trap
+.nr an-no-space-flag 1
+.nr an-break-flag 1
+.br
+\fBNote\fR
+If a given parameter is not applicable to a certain type of node, than an empty string is returned for the corresponding value. See the examples later in this section for more information.
+.TP 3n
+\(bu
+\fB\-\-host=\fR\fB\fIhostname\fR\fR
+.sp
+Specifies the hostname of the node for which configuration information is to be obtained.
+.TP 3n
+\(bu
+\fB\-\-id=\fR\fB\fInode_id\fR\fR,
+\fB\-\-nodeid=\fR\fB\fInode_id\fR\fR
+.sp
+Used to specify the node ID of the node for which configuration information is to be obtained.
+.TP 3n
+\(bu
+\fB\-\-nodes\fR
+.sp
+(Tells
+\fBndb_config\fR
+to print information from parameters defined in
+[ndbd]
+sections only. Currently, using this option has no affect, since these are the only values checked, but it may become possible in future to query parameters set in
+[tcp]
+and other sections of cluster configuration files.)
+.TP 3n
+\(bu
+\fB\-\-type=\fR\fB\fInode_type\fR\fR
+.sp
+Filters results so that only configuration values applying to nodes of the specified
+\fInode_type\fR
+(ndbd,
+mysqld, or
+ndb_mgmd) are returned.
+.TP 3n
+\(bu
+\fB\-\-fields=\fR\fB\fIdelimiter\fR\fR,
+\fB\-f\fR
+\fIdelimiter\fR
+.sp
+Specifies a
+\fIdelimiter\fR
+string used to separate the fields in the result. The default is
+\(lq,\(rq
+(the comma character).
+.sp
+.it 1 an-trap
+.nr an-no-space-flag 1
+.nr an-break-flag 1
+.br
+\fBNote\fR
+If the
+\fIdelimiter\fR
+contains spaces or escapes (such as
+\\n
+for the linefeed character), then it must be quoted.
+.TP 3n
+\(bu
+\fB\-\-rows=\fR\fB\fIseparator\fR\fR,
+\fB\-r\fR
+\fIseparator\fR
+.sp
+Specifies a
+\fIseparator\fR
+string used to separate the rows in the result. The default is a space character.
+.sp
+.it 1 an-trap
+.nr an-no-space-flag 1
+.nr an-break-flag 1
+.br
+\fBNote\fR
+If the
+\fIseparator\fR
+contains spaces or escapes (such as
+\\n
+for the linefeed character), then it must be quoted.
+.sp
+.RE
+.PP
+\fBExamples\fR:
+.TP 3n
+1.
+To obtain the node ID and type of each node in the cluster:
+.sp
+.RS 3n
+.nf
+shell> \fB./ndb_config \-\-query=id,type \-\-fields=':' \-\-rows='\\n'\fR
+1:ndbd
+2:ndbd
+3:ndbd
+4:ndbd
+5:ndb_mgmd
+6:mysqld
+7:mysqld
+8:mysqld
+9:mysqld
+.fi
+.RE
+In this example, we used the
+\fB\-\-fields\fR
+options to separate the ID and type of each node with a colon character (:), and the
+\fB\-\-rows\fR
+options to place the values for each node on a new line in the output.
+.TP 3n
+2.
+To produce a connectstring that can be used by data, SQL, and API nodes to connect to the management server:
+.sp
+.RS 3n
+.nf
+shell> \fB./ndb_config \-\-config\-file=usr/local/mysql/cluster\-data/config.ini \-\-query=hostname,portnumber \-\-fields=: \-\-rows=, \-\-type=ndb_mgmd\fR
+192.168.0.179:1186
+.fi
+.RE
+.TP 3n
+3.
+This invocation of
+\fBndb_config\fR
+checks only data nodes (using the
+\fB\-\-type\fR
+option), and shows the values for each node's ID and hostname, and its
+DataMemory,
+IndexMemory, and
+DataDir
+parameters:
+.sp
+.RS 3n
+.nf
+shell> \fB./ndb_config \-\-type=ndbd \-\-query=id,host,datamemory,indexmemory,datadir \-f ' : ' \-r '\\n'\fR
+1 : 192.168.0.193 : 83886080 : 18874368 : /usr/local/mysql/cluster\-data
+2 : 192.168.0.112 : 83886080 : 18874368 : /usr/local/mysql/cluster\-data
+3 : 192.168.0.176 : 83886080 : 18874368 : /usr/local/mysql/cluster\-data
+4 : 192.168.0.119 : 83886080 : 18874368 : /usr/local/mysql/cluster\-data
+.fi
+.RE
+In this example, we used the short options
+\fB\-f\fR
+and
+\fB\-r\fR
+for setting the field delimiter and row separator, respectively.
+.TP 3n
+4.
+To exclude results from any host except one in particular, use the
+\fB\-\-host\fR
+option:
+.sp
+.RS 3n
+.nf
+shell> \fB./ndb_config \-\-host=192.168.0.176 \-f : \-r '\\n' \-q id,type\fR
+3:ndbd
+5:ndb_mgmd
+.fi
+.RE
+In this example, we also used the short form
+\fB\-q\fR
+to determine the attributes to be queried.
+.sp
+Similarly, you can limit results to a node with a specific ID using the
+\fB\-\-id\fR
+or
+\fB\-\-nodeid\fR
+option.
+.SH "COPYRIGHT"
+.PP
+Copyright 2007 MySQL AB
+.PP
+This documentation is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License.
+.PP
+This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
+.PP
+You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110\-1301 USA or see http://www.gnu.org/licenses/.
+.PP
+Please email
+<docs at mysql.com>
+for more information or if you are interested in doing a translation.
+.SH "SEE ALSO"
+For more information, please refer to the MySQL Reference Manual,
+which may already be installed locally and which is also available
+online at http://dev.mysql.com/doc/.
+.SH AUTHOR
+MySQL AB (http://www.mysql.com/).
Added: branches/sid-5.0/debian/manpages/ndb_cpcd.1
===================================================================
--- branches/sid-5.0/debian/manpages/ndb_cpcd.1 (rev 0)
+++ branches/sid-5.0/debian/manpages/ndb_cpcd.1 2007-11-26 12:34:29 UTC (rev 1020)
@@ -0,0 +1,50 @@
+.\" Title: \fBndb_cpcd\fR
+.\" Author:
+.\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
+.\" Date: 11/25/2007
+.\" Manual: MySQL Database System
+.\" Source: MySQL 5.0
+.\"
+.TH "\fBNDB_CPCD\fR" "1" "11/25/2007" "MySQL 5.0" "MySQL Database System"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
+.SH "NAME"
+ndb_cpcd \- automate testing of NDB (development use only)
+.SH "SYNOPSIS"
+.HP 17
+\fBndb_cpcd \fR\fB\fIoptions\fR\fR
+.SH "DESCRIPTION"
+.PP
+This utility is found in the
+\fIlibexec\fR
+directory. It is part of an internal automated test framework used in testing and bedugging MySQL Cluster. Because it can control processes on remote systems, it is not advisable to use
+\fBndb_cpcd\fR
+in a production cluster.
+.PP
+Because some users may be interested in employing the Cluster testing framework for their own development or testing purposes, we intend to make details of this application's usage available in the near future as part of the MySQL Internals Manual.
+.PP
+The source files for
+\fBndb_cpcd\fR
+may be found in the directory
+\fIstorage/ndb/src/cw/cpcd\fR, in the MySQL 5.0 source tree.
+.SH "COPYRIGHT"
+.PP
+Copyright 2007 MySQL AB
+.PP
+This documentation is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License.
+.PP
+This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
+.PP
+You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110\-1301 USA or see http://www.gnu.org/licenses/.
+.PP
+Please email
+<docs at mysql.com>
+for more information or if you are interested in doing a translation.
+.SH "SEE ALSO"
+For more information, please refer to the MySQL Reference Manual,
+which may already be installed locally and which is also available
+online at http://dev.mysql.com/doc/.
+.SH AUTHOR
+MySQL AB (http://www.mysql.com/).
Added: branches/sid-5.0/debian/manpages/ndb_delete_all.1
===================================================================
--- branches/sid-5.0/debian/manpages/ndb_delete_all.1 (rev 0)
+++ branches/sid-5.0/debian/manpages/ndb_delete_all.1 2007-11-26 12:34:29 UTC (rev 1020)
@@ -0,0 +1,75 @@
+.\" Title: \fBndb_delete_all\fR
+.\" Author:
+.\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
+.\" Date: 11/25/2007
+.\" Manual: MySQL Database System
+.\" Source: MySQL 5.0
+.\"
+.TH "\fBNDB_DELETE_ALL\fR" "1" "11/25/2007" "MySQL 5.0" "MySQL Database System"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
+.SH "NAME"
+ndb_delete_all \- delete all rows from NDB table
+.SH "SYNOPSIS"
+.HP 23
+\fBndb_delete_all \fR\fB\fIoptions\fR\fR
+.SH "DESCRIPTION"
+.PP
+\fBndb_delete_all\fR
+deletes all rows from the given
+NDB
+table. In some cases, this can be much faster than
+DELETE
+or even
+TRUNCATE.
+.PP
+\fBUsage\fR:
+.sp
+.RS 3n
+.nf
+ndb_delete_all \-c \fIconnect_string\fR \fItbl_name\fR \-d \fIdb_name\fR
+.fi
+.RE
+.PP
+This deletes all rows from the table named
+\fItbl_name\fR
+in the database named
+\fIdb_name\fR. It is exactly equivalent to executing
+TRUNCATE \fIdb_name\fR.\fItbl_name\fR
+in MySQL.
+.PP
+\fBAdditional Options\fR:
+.TP 3n
+\(bu
+\fB\-\-transactional\fR,
+\fB\-t\fR
+.sp
+Use of this option causes the delete operation to be performed as a single transaction.
+.sp
+.it 1 an-trap
+.nr an-no-space-flag 1
+.nr an-break-flag 1
+.br
+\fBWarning\fR
+With very large tables, using this option may cause the number of operations available to the cluster to be exceeded.
+.SH "COPYRIGHT"
+.PP
+Copyright 2007 MySQL AB
+.PP
+This documentation is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License.
+.PP
+This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
+.PP
+You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110\-1301 USA or see http://www.gnu.org/licenses/.
+.PP
+Please email
+<docs at mysql.com>
+for more information or if you are interested in doing a translation.
+.SH "SEE ALSO"
+For more information, please refer to the MySQL Reference Manual,
+which may already be installed locally and which is also available
+online at http://dev.mysql.com/doc/.
+.SH AUTHOR
+MySQL AB (http://www.mysql.com/).
Added: branches/sid-5.0/debian/manpages/ndb_desc.1
===================================================================
--- branches/sid-5.0/debian/manpages/ndb_desc.1 (rev 0)
+++ branches/sid-5.0/debian/manpages/ndb_desc.1 2007-11-26 12:34:29 UTC (rev 1020)
@@ -0,0 +1,118 @@
+.\" Title: \fBndb_desc\fR
+.\" Author:
+.\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
+.\" Date: 11/25/2007
+.\" Manual: MySQL Database System
+.\" Source: MySQL 5.0
+.\"
+.TH "\fBNDB_DESC\fR" "1" "11/25/2007" "MySQL 5.0" "MySQL Database System"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
+.SH "NAME"
+ndb_desc \- describe NDB tables
+.SH "SYNOPSIS"
+.HP 17
+\fBndb_desc \fR\fB\fIoptions\fR\fR
+.SH "DESCRIPTION"
+.PP
+\fBndb_desc\fR
+provides a detailed description of one or more
+NDB
+tables.
+.PP
+\fBUsage\fR:
+.sp
+.RS 3n
+.nf
+ndb_desc \-c \fIconnect_string\fR \fItbl_name\fR \-d \fIdb_name\fR
+.fi
+.RE
+.PP
+\fBSample Output\fR:
+.PP
+MySQL table creation and population statements:
+.sp
+.RS 3n
+.nf
+USE test;
+CREATE TABLE fish (
+ id INT(11) NOT NULL AUTO_INCREMENT,
+ name VARCHAR(20),
+ PRIMARY KEY pk (id),
+ UNIQUE KEY uk (name)
+) ENGINE=NDBCLUSTER;
+INSERT INTO fish VALUES
+ ('','guppy'), ('','tuna'), ('','shark'),
+ ('','manta ray'), ('','grouper'), ('','puffer');
+.fi
+.RE
+.PP
+Output from
+\fBndb_desc\fR:
+.sp
+.RS 3n
+.nf
+shell> \fB./ndb_desc \-c localhost fish \-d test \-p\fR
+\-\- fish \-\-
+Version: 16777221
+Fragment type: 5
+K Value: 6
+Min load factor: 78
+Max load factor: 80
+Temporary table: no
+Number of attributes: 2
+Number of primary keys: 1
+Length of frm data: 268
+Row Checksum: 1
+Row GCI: 1
+TableStatus: Retrieved
+\-\- Attributes \-\-
+id Int PRIMARY KEY DISTRIBUTION KEY AT=FIXED ST=MEMORY
+name Varchar(20;latin1_swedish_ci) NULL AT=SHORT_VAR ST=MEMORY
+\-\- Indexes \-\-
+PRIMARY KEY(id) \- UniqueHashIndex
+uk(name) \- OrderedIndex
+PRIMARY(id) \- OrderedIndex
+uk$unique(name) \- UniqueHashIndex
+\-\- Per partition info \-\-
+Partition Row count Commit count Frag fixed memory Frag varsized memory
+2 2 2 65536 327680
+1 2 2 65536 327680
+3 2 2 65536 327680
+NDBT_ProgramExit: 0 \- OK
+.fi
+.RE
+.PP
+\fBAdditional Options\fR:
+.TP 3n
+\(bu
+\fB\-\-extra\-partition\-info\fR,
+\fB\-p\fR
+.sp
+Prints additional information about the table's partitions.
+.TP 3n
+\(bu
+Information about multiple tables can be obtained in a single invocation of
+\fBndb_desc\fR
+by using their names, separated by spaces. All of the tables must be in the same database.
+.SH "COPYRIGHT"
+.PP
+Copyright 2007 MySQL AB
+.PP
+This documentation is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License.
+.PP
+This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
+.PP
+You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110\-1301 USA or see http://www.gnu.org/licenses/.
+.PP
+Please email
+<docs at mysql.com>
+for more information or if you are interested in doing a translation.
+.SH "SEE ALSO"
+For more information, please refer to the MySQL Reference Manual,
+which may already be installed locally and which is also available
+online at http://dev.mysql.com/doc/.
+.SH AUTHOR
+MySQL AB (http://www.mysql.com/).
Added: branches/sid-5.0/debian/manpages/ndb_drop_index.1
===================================================================
--- branches/sid-5.0/debian/manpages/ndb_drop_index.1 (rev 0)
+++ branches/sid-5.0/debian/manpages/ndb_drop_index.1 2007-11-26 12:34:29 UTC (rev 1020)
@@ -0,0 +1,106 @@
+.\" Title: \fBndb_drop_index\fR
+.\" Author:
+.\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
+.\" Date: 11/25/2007
+.\" Manual: MySQL Database System
+.\" Source: MySQL 5.0
+.\"
+.TH "\fBNDB_DROP_INDEX\fR" "1" "11/25/2007" "MySQL 5.0" "MySQL Database System"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
+.SH "NAME"
+ndb_drop_index \- drop index from NDB table
+.SH "SYNOPSIS"
+.HP 23
+\fBndb_drop_index \fR\fB\fIoptions\fR\fR
+.SH "DESCRIPTION"
+.PP
+\fBndb_drop_index\fR
+drops the specified index from an
+NDB
+table.
+\fIIt is recommended that you use this utility only as an example for writing NDB API applications\fR
+\(em see the Warning later in this section for details.
+.PP
+\fBUsage\fR:
+.sp
+.RS 3n
+.nf
+ndb_drop_index \-c \fIconnect_string\fR \fItable_name\fR \fIindex\fR \-d \fIdb_name\fR
+.fi
+.RE
+.PP
+The statement shown above drops the index named
+\fIindex\fR
+from the
+\fItable\fR
+in the
+\fIdatabase\fR.
+.PP
+\fBAdditional Options\fR: None that are specific to this application.
+.sp
+.it 1 an-trap
+.nr an-no-space-flag 1
+.nr an-break-flag 1
+.br
+\fBWarning\fR
+.PP
+\fIOperations performed on Cluster table indexes using the NDB API are not visible to MySQL and make the table unusable by a MySQL server\fR. If you use this program to drop an index, then try to access the table from an SQL node, an error results, as shown here:
+.sp
+.RS 3n
+.nf
+shell> \fB./ndb_drop_index \-c localhost dogs ix \-d ctest1\fR
+Dropping index dogs/idx...OK
+NDBT_ProgramExit: 0 \- OK
+shell> \fB./mysql \-u jon \-p ctest1\fR
+Enter password: *******
+Reading table information for completion of table and column names
+You can turn off this feature to get a quicker startup with \-A
+Welcome to the MySQL monitor. Commands end with ; or \\g.
+Your MySQL connection id is 7 to server version: 5.1.12\-beta\-20060817
+Type 'help;' or '\\h' for help. Type '\\c' to clear the buffer.
+mysql> SHOW TABLES;
++\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+
+| Tables_in_ctest1 |
++\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+
+| a |
+| bt1 |
+| bt2 |
+| dogs |
+| employees |
+| fish |
++\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+
+6 rows in set (0.00 sec)
+mysql> SELECT * FROM dogs;
+ERROR 1296 (HY000): Got error 4243 'Index not found' from NDBCLUSTER
+.fi
+.RE
+.PP
+In such a case, your
+\fIonly\fR
+option for making the table available to MySQL again is to drop the table and re\-create it. You can use either the SQL statementDROP TABLE
+or the
+\fBndb_drop_table\fR
+utility (see
+\fBndb_drop_table\fR(1)) to drop the table.
+.SH "COPYRIGHT"
+.PP
+Copyright 2007 MySQL AB
+.PP
+This documentation is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License.
+.PP
+This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
+.PP
+You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110\-1301 USA or see http://www.gnu.org/licenses/.
+.PP
+Please email
+<docs at mysql.com>
+for more information or if you are interested in doing a translation.
+.SH "SEE ALSO"
+For more information, please refer to the MySQL Reference Manual,
+which may already be installed locally and which is also available
+online at http://dev.mysql.com/doc/.
+.SH AUTHOR
+MySQL AB (http://www.mysql.com/).
Added: branches/sid-5.0/debian/manpages/ndb_drop_table.1
===================================================================
--- branches/sid-5.0/debian/manpages/ndb_drop_table.1 (rev 0)
+++ branches/sid-5.0/debian/manpages/ndb_drop_table.1 2007-11-26 12:34:29 UTC (rev 1020)
@@ -0,0 +1,57 @@
+.\" Title: \fBndb_drop_table\fR
+.\" Author:
+.\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
+.\" Date: 11/25/2007
+.\" Manual: MySQL Database System
+.\" Source: MySQL 5.0
+.\"
+.TH "\fBNDB_DROP_TABLE\fR" "1" "11/25/2007" "MySQL 5.0" "MySQL Database System"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
+.SH "NAME"
+ndb_drop_table \- drop NDB table
+.SH "SYNOPSIS"
+.HP 23
+\fBndb_drop_table \fR\fB\fIoptions\fR\fR
+.SH "DESCRIPTION"
+.PP
+\fBndb_drop_table\fR
+drops the specified
+NDB
+table. (If you try to use this on a table created with a storage engine other than NDB, it fails with the error
+723: No such table exists.) This operation is extremely fast \(em in some cases, it can be an order of magnitude faster than using
+DROP TABLE
+on an
+NDB
+table from MySQL.
+.PP
+\fBUsage\fR:
+.sp
+.RS 3n
+.nf
+ndb_drop_table \-c \fIconnect_string\fR \fItbl_name\fR \-d \fIdb_name\fR
+.fi
+.RE
+.PP
+\fBAdditional Options\fR: None.
+.SH "COPYRIGHT"
+.PP
+Copyright 2007 MySQL AB
+.PP
+This documentation is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License.
+.PP
+This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
+.PP
+You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110\-1301 USA or see http://www.gnu.org/licenses/.
+.PP
+Please email
+<docs at mysql.com>
+for more information or if you are interested in doing a translation.
+.SH "SEE ALSO"
+For more information, please refer to the MySQL Reference Manual,
+which may already be installed locally and which is also available
+online at http://dev.mysql.com/doc/.
+.SH AUTHOR
+MySQL AB (http://www.mysql.com/).
Added: branches/sid-5.0/debian/manpages/ndb_error_reporter.1
===================================================================
--- branches/sid-5.0/debian/manpages/ndb_error_reporter.1 (rev 0)
+++ branches/sid-5.0/debian/manpages/ndb_error_reporter.1 2007-11-26 12:34:29 UTC (rev 1020)
@@ -0,0 +1,60 @@
+.\" Title: \fBndb_error_reporter\fR
+.\" Author:
+.\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
+.\" Date: 11/25/2007
+.\" Manual: MySQL Database System
+.\" Source: MySQL 5.0
+.\"
+.TH "\fBNDB_ERROR_REPORTE" "1" "11/25/2007" "MySQL 5.0" "MySQL Database System"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
+.SH "NAME"
+ndb_error_reporter \- NDB error\-reporting utility
+.SH "SYNOPSIS"
+.HP 27
+\fBndb_error_reporter \fR\fB\fIoptions\fR\fR
+.SH "DESCRIPTION"
+.PP
+\fBndb_error_reporter\fR
+creates an archive from data node and management node log files that can be used to help diagnose bugs or other problems with a cluster.
+\fIIt is highly recommended that you make use of this utility when filing reports of bugs in MySQL Cluster\fR.
+.PP
+\fBUsage\fR:
+.sp
+.RS 3n
+.nf
+ndb_error_reporter \fIpath/to/config\-file\fR [\fIusername\fR] [\-\-fs]
+.fi
+.RE
+.PP
+This utility is intended for use on a management node host, and requires the path to the management host configuration file (\fIconfig.ini\fR). Optionally, you can supply the name of a user that is able to access the cluster's data nodes via SSH, in order to copy the data node log files. ndb_error_reporter then includes all of these files in archive that is created in the same directory in which it is run. The archive is named
+\fIndb_error_report_\fR\fI\fIYYYYMMDDHHMMSS\fR\fR\fI.tar.bz2\fR, where
+\fIYYYYMMDDHHMMSS\fR
+is a datetime string.
+.PP
+If the
+\fB\-\-fs\fR
+is used, then the data node filesystems are also copied to the management host and included in the archive that is produced by this script. As data node filesystems can be extremely large even after being compressed, we ask that you please do
+\fInot\fR
+send archives created using this option to MySQL AB unless you are specifically requested to do so.
+.SH "COPYRIGHT"
+.PP
+Copyright 2007 MySQL AB
+.PP
+This documentation is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License.
+.PP
+This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
+.PP
+You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110\-1301 USA or see http://www.gnu.org/licenses/.
+.PP
+Please email
+<docs at mysql.com>
+for more information or if you are interested in doing a translation.
+.SH "SEE ALSO"
+For more information, please refer to the MySQL Reference Manual,
+which may already be installed locally and which is also available
+online at http://dev.mysql.com/doc/.
+.SH AUTHOR
+MySQL AB (http://www.mysql.com/).
Added: branches/sid-5.0/debian/manpages/ndb_mgm.1
===================================================================
--- branches/sid-5.0/debian/manpages/ndb_mgm.1 (rev 0)
+++ branches/sid-5.0/debian/manpages/ndb_mgm.1 2007-11-26 12:34:29 UTC (rev 1020)
@@ -0,0 +1,68 @@
+.\" Title: \fBndb_mgm\fR
+.\" Author:
+.\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
+.\" Date: 11/25/2007
+.\" Manual: MySQL Database System
+.\" Source: MySQL 5.0
+.\"
+.TH "\fBNDB_MGM\fR" "1" "11/25/2007" "MySQL 5.0" "MySQL Database System"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
+.SH "NAME"
+ndb_mgm \- the management client process
+.SH "SYNOPSIS"
+.HP 16
+\fBndb_mgm \fR\fB\fIoptions\fR\fR
+.SH "DESCRIPTION"
+.PP
+The
+\fBndb_mgm\fR
+management client process is actually not needed to run the cluster. Its value lies in providing a set of commands for checking the cluster's status, starting backups, and performing other administrative functions. The management client accesses the management server using a C API. Advanced users can also employ this API for programming dedicated management processes to perform tasks similar to those performed by
+\fBndb_mgm\fR.
+.PP
+To start the management client, it is necessary to supply the hostname and port number of the management server:
+.sp
+.RS 3n
+.nf
+shell> \fBndb_mgm [\fR\fB\fIhost_name\fR\fR\fB [\fR\fB\fIport_num\fR\fR\fB]]\fR
+.fi
+.RE
+.PP
+For example:
+.sp
+.RS 3n
+.nf
+shell> \fBndb_mgm ndb_mgmd.mysql.com 1186\fR
+.fi
+.RE
+.PP
+The default hostname and port number are
+localhost
+and 1186, respectively.
+.PP
+Additional information about using
+\fBndb_mgm\fR
+can be found in
+Section\ 5.2.4, \(lqCommand Options for \fBndb_mgm\fR\(rq, and
+Section\ 6.2, \(lqCommands in the MySQL Cluster Management Client\(rq.
+.SH "COPYRIGHT"
+.PP
+Copyright 2007 MySQL AB
+.PP
+This documentation is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License.
+.PP
+This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
+.PP
+You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110\-1301 USA or see http://www.gnu.org/licenses/.
+.PP
+Please email
+<docs at mysql.com>
+for more information or if you are interested in doing a translation.
+.SH "SEE ALSO"
+For more information, please refer to the MySQL Reference Manual,
+which may already be installed locally and which is also available
+online at http://dev.mysql.com/doc/.
+.SH AUTHOR
+MySQL AB (http://www.mysql.com/).
Added: branches/sid-5.0/debian/manpages/ndb_mgmd.1
===================================================================
--- branches/sid-5.0/debian/manpages/ndb_mgmd.1 (rev 0)
+++ branches/sid-5.0/debian/manpages/ndb_mgmd.1 2007-11-26 12:34:29 UTC (rev 1020)
@@ -0,0 +1,84 @@
+.\" Title: \fBndb_mgmd\fR
+.\" Author:
+.\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
+.\" Date: 11/25/2007
+.\" Manual: MySQL Database System
+.\" Source: MySQL 5.0
+.\"
+.TH "\fBNDB_MGMD\fR" "1" "11/25/2007" "MySQL 5.0" "MySQL Database System"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
+.SH "NAME"
+ndb_mgmd \- the management server process
+.SH "SYNOPSIS"
+.HP 17
+\fBndb_mgmd \fR\fB\fIoptions\fR\fR
+.SH "DESCRIPTION"
+.PP
+The management server is the process that reads the cluster configuration file and distributes this information to all nodes in the cluster that request it. It also maintains a log of cluster activities. Management clients can connect to the management server and check the cluster's status.
+.PP
+It is not strictly necessary to specify a connectstring when starting the management server. However, if you are using more than one management server, a connectstring should be provided and each node in the cluster should specify its node ID explicitly.
+.PP
+See
+Section\ 3.4.2, \(lqThe Cluster Connectstring\(rq, for information about using connectstrings.
+Section\ 5.2, \(lqCommand Options for MySQL Cluster Processes\(rq, describes other options for
+\fBndb_mgmd\fR.
+.PP
+The following files are created or used by
+\fBndb_mgmd\fR
+in its starting directory, and are placed in the
+DataDir
+as specified in the
+\fIconfig.ini\fR
+configuration file. In the list that follows,
+\fInode_id\fR
+is the unique node identifier.
+.TP 3n
+\(bu
+\fIconfig.ini\fR
+is the configuration file for the cluster as a whole. This file is created by the user and read by the management server.
+Section\ 3, \(lqMySQL Cluster Configuration\(rq, discusses how to set up this file.
+.TP 3n
+\(bu
+\fIndb_\fR\fI\fInode_id\fR\fR\fI_cluster.log\fR
+is the cluster events log file. Examples of such events include checkpoint startup and completion, node startup events, node failures, and levels of memory usage. A complete listing of cluster events with descriptions may be found in
+Section\ 6, \(lqManagement of MySQL Cluster\(rq.
+.sp
+When the size of the cluster log reaches one million bytes, the file is renamed to
+\fIndb_\fR\fI\fInode_id\fR\fR\fI_cluster.log.\fR\fI\fIseq_id\fR\fR, where
+\fIseq_id\fR
+is the sequence number of the cluster log file. (For example: If files with the sequence numbers 1, 2, and 3 already exist, the next log file is named using the number
+4.)
+.TP 3n
+\(bu
+\fIndb_\fR\fI\fInode_id\fR\fR\fI_out.log\fR
+is the file used for
+stdout
+and
+stderr
+when running the management server as a daemon.
+.TP 3n
+\(bu
+\fIndb_\fR\fI\fInode_id\fR\fR\fI.pid\fR
+is the process ID file used when running the management server as a daemon.
+.SH "COPYRIGHT"
+.PP
+Copyright 2007 MySQL AB
+.PP
+This documentation is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License.
+.PP
+This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
+.PP
+You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110\-1301 USA or see http://www.gnu.org/licenses/.
+.PP
+Please email
+<docs at mysql.com>
+for more information or if you are interested in doing a translation.
+.SH "SEE ALSO"
+For more information, please refer to the MySQL Reference Manual,
+which may already be installed locally and which is also available
+online at http://dev.mysql.com/doc/.
+.SH AUTHOR
+MySQL AB (http://www.mysql.com/).
Added: branches/sid-5.0/debian/manpages/ndb_print_backup_file.1
===================================================================
--- branches/sid-5.0/debian/manpages/ndb_print_backup_file.1 (rev 0)
+++ branches/sid-5.0/debian/manpages/ndb_print_backup_file.1 2007-11-26 12:34:29 UTC (rev 1020)
@@ -0,0 +1,70 @@
+.\" Title: \fBndb_print_backup_file\fR
+.\" Author:
+.\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
+.\" Date: 11/25/2007
+.\" Manual: MySQL Database System
+.\" Source: MySQL 5.0
+.\"
+.TH "\fBNDB_PRINT_BACKUP_" "1" "11/25/2007" "MySQL 5.0" "MySQL Database System"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
+.SH "NAME"
+ndb_print_backup_file \- print NDB backup file contents
+.SH "SYNOPSIS"
+.HP 32
+\fBndb_print_backup_file \fR\fB\fIfile_name\fR\fR
+.SH "DESCRIPTION"
+.PP
+\fBndb_print_backup_file\fR
+obtains diagnostic information from a cluster backup file.
+.PP
+\fBUsage\fR:
+.sp
+.RS 3n
+.nf
+ndb_print_backup_file \fIfile_name\fR
+.fi
+.RE
+.PP
+\fIfile_name\fR
+is the name of a cluster backup file. This can be any of the files (\fI.Data\fR,
+\fI.ctl\fR, or
+\fI.log\fR
+file) found in a cluster backup directory. These files are found in the data node's backup directory under the subdirectory
+\fIBACKUP\-\fR\fI\fI#\fR\fR, where
+\fI#\fR
+is the sequence number for the backup. For more information about cluster backup files and their contents, see
+Section\ 7.1, \(lqCluster Backup Concepts\(rq.
+.PP
+Like
+\fBndb_print_schema_file\fR
+and
+\fBndb_print_sys_file\fR
+(and unlike most of the other
+NDB
+utilities that are intended to be run on a management server host or to connect to a management server)
+\fBndb_print_backup_file\fR
+must be run on a cluster data node, since it accesses the data node filesystem directly. Because it does not make use of the management server, this utility can be used when the management server is not running, and even when the cluster has been completely shut down.
+.PP
+\fBAdditional Options\fR: None.
+.SH "COPYRIGHT"
+.PP
+Copyright 2007 MySQL AB
+.PP
+This documentation is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License.
+.PP
+This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
+.PP
+You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110\-1301 USA or see http://www.gnu.org/licenses/.
+.PP
+Please email
+<docs at mysql.com>
+for more information or if you are interested in doing a translation.
+.SH "SEE ALSO"
+For more information, please refer to the MySQL Reference Manual,
+which may already be installed locally and which is also available
+online at http://dev.mysql.com/doc/.
+.SH AUTHOR
+MySQL AB (http://www.mysql.com/).
Added: branches/sid-5.0/debian/manpages/ndb_print_schema_file.1
===================================================================
--- branches/sid-5.0/debian/manpages/ndb_print_schema_file.1 (rev 0)
+++ branches/sid-5.0/debian/manpages/ndb_print_schema_file.1 2007-11-26 12:34:29 UTC (rev 1020)
@@ -0,0 +1,63 @@
+.\" Title: \fBndb_print_schema_file\fR
+.\" Author:
+.\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
+.\" Date: 11/25/2007
+.\" Manual: MySQL Database System
+.\" Source: MySQL 5.0
+.\"
+.TH "\fBNDB_PRINT_SCHEMA_" "1" "11/25/2007" "MySQL 5.0" "MySQL Database System"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
+.SH "NAME"
+ndb_print_schema_file \- print NDB schema file contents
+.SH "SYNOPSIS"
+.HP 32
+\fBndb_print_schema_file \fR\fB\fIfile_name\fR\fR
+.SH "DESCRIPTION"
+.PP
+\fBndb_print_schema_file\fR
+obtains diagnostic information from a cluster schema file.
+.PP
+\fBUsage\fR:
+.sp
+.RS 3n
+.nf
+ndb_print_schema_file \fIfile_name\fR
+.fi
+.RE
+.PP
+\fIfile_name\fR
+is the name of a cluster schema file.
+.PP
+Like
+\fBndb_print_backup_file\fR
+and
+\fBndb_print_sys_file\fR
+(and unlike most of the other
+NDB
+utilities that are intended to be run on a management server host or to connect to a management server)
+\fBndb_schema_backup_file\fR
+must be run on a cluster data node, since it accesses the data node filesystem directly. Because it does not make use of the management server, this utility can be used when the management server is not running, and even when the cluster has been completely shut down.
+.PP
+\fBAdditional Options\fR: None.
+.SH "COPYRIGHT"
+.PP
+Copyright 2007 MySQL AB
+.PP
+This documentation is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License.
+.PP
+This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
+.PP
+You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110\-1301 USA or see http://www.gnu.org/licenses/.
+.PP
+Please email
+<docs at mysql.com>
+for more information or if you are interested in doing a translation.
+.SH "SEE ALSO"
+For more information, please refer to the MySQL Reference Manual,
+which may already be installed locally and which is also available
+online at http://dev.mysql.com/doc/.
+.SH AUTHOR
+MySQL AB (http://www.mysql.com/).
Added: branches/sid-5.0/debian/manpages/ndb_print_sys_file.1
===================================================================
--- branches/sid-5.0/debian/manpages/ndb_print_sys_file.1 (rev 0)
+++ branches/sid-5.0/debian/manpages/ndb_print_sys_file.1 2007-11-26 12:34:29 UTC (rev 1020)
@@ -0,0 +1,66 @@
+.\" Title: \fBndb_print_sys_file\fR
+.\" Author:
+.\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
+.\" Date: 11/25/2007
+.\" Manual: MySQL Database System
+.\" Source: MySQL 5.0
+.\"
+.TH "\fBNDB_PRINT_SYS_FIL" "1" "11/25/2007" "MySQL 5.0" "MySQL Database System"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
+.SH "NAME"
+ndb_print_sys_file \- print NDB system file contents
+.SH "SYNOPSIS"
+.HP 29
+\fBndb_print_sys_file \fR\fB\fIfile_name\fR\fR
+.SH "DESCRIPTION"
+.PP
+\fBndb_print_sys_file\fR
+obtains diagnostic information from a cluster system file.
+.PP
+\fBUsage\fR:
+.sp
+.RS 3n
+.nf
+ndb_print_sys_file \fIfile_name\fR
+.fi
+.RE
+.PP
+\fIfile_name\fR
+is the name of a cluster system file (sysfile). Cluster system files are located in a data node's data directory (DataDir); the path under this directory to system files matches the pattern
+\fIndb_\fR\fI\fI#\fR\fR\fI_fs/D\fR\fI\fI#\fR\fR\fI/DBDIH/P\fR\fI\fI#\fR\fR\fI.sysfile\fR. In each case, the
+\fI#\fR
+represents a number (not necessarily the same number).
+.PP
+Like
+\fBndb_print_backup_file\fR
+and
+\fBndb_print_schema_file\fR
+(and unlike most of the other
+NDB
+utilities that are intended to be run on a management server host or to connect to a management server)
+\fBndb_print_backup_file\fR
+must be run on a cluster data node, since it accesses the data node filesystem directly. Because it does not make use of the management server, this utility can be used when the management server is not running, and even when the cluster has been completely shut down.
+.PP
+\fBAdditional Options\fR: None.
+.SH "COPYRIGHT"
+.PP
+Copyright 2007 MySQL AB
+.PP
+This documentation is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License.
+.PP
+This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
+.PP
+You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110\-1301 USA or see http://www.gnu.org/licenses/.
+.PP
+Please email
+<docs at mysql.com>
+for more information or if you are interested in doing a translation.
+.SH "SEE ALSO"
+For more information, please refer to the MySQL Reference Manual,
+which may already be installed locally and which is also available
+online at http://dev.mysql.com/doc/.
+.SH AUTHOR
+MySQL AB (http://www.mysql.com/).
Added: branches/sid-5.0/debian/manpages/ndb_restore.1
===================================================================
--- branches/sid-5.0/debian/manpages/ndb_restore.1 (rev 0)
+++ branches/sid-5.0/debian/manpages/ndb_restore.1 2007-11-26 12:34:29 UTC (rev 1020)
@@ -0,0 +1,443 @@
+.\" Title: \fBndb_restore\fR
+.\" Author:
+.\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
+.\" Date: 11/25/2007
+.\" Manual: MySQL Database System
+.\" Source: MySQL 5.0
+.\"
+.TH "\fBNDB_RESTORE\fR" "1" "11/25/2007" "MySQL 5.0" "MySQL Database System"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
+.SH "NAME"
+ndb_restore \- restore a Cluster backup
+.SH "SYNOPSIS"
+.HP 20
+\fBndb_restore \fR\fB\fIoptions\fR\fR
+.SH "DESCRIPTION"
+.PP
+The cluster restoration program is implemented as a separate command\-line utility
+\fBndb_restore\fR, which can normally be found in the MySQL
+\fIbin\fR
+directory. This program reads the files created as a result of the backup and inserts the stored information into the database.
+.PP
+\fBndb_restore\fR
+must be executed once for each of the backup files that were created by the
+START BACKUP
+command used to create the backup (see
+Section\ 7.2, \(lqUsing The Management Client to Create a Backup\(rq). This is equal to the number of data nodes in the cluster at the time that the backup was created.
+.sp
+.it 1 an-trap
+.nr an-no-space-flag 1
+.nr an-break-flag 1
+.br
+\fBNote\fR
+.PP
+Before using
+\fBndb_restore\fR, it is recommended that the cluster be running in single user mode, unless you are restoring multiple data nodes in parallel. See
+Section\ 6.4, \(lqSingle User Mode\(rq, for more information about single user mode.
+.PP
+Typical options for this utility are shown here:
+.sp
+.RS 3n
+.nf
+ndb_restore [\-c \fIconnectstring\fR] \-n \fInode_id\fR [\-m] \-b \fIbackup_id\fR \-r [backup_path=]\fI/path/to/backup/files\fR
+.fi
+.RE
+.PP
+The
+\fB\-c\fR
+option is used to specify a connectstring which tells
+ndb_restore
+where to locate the cluster management server. (See
+Section\ 3.4.2, \(lqThe Cluster Connectstring\(rq, for information on connectstrings.) If this option is not used, then
+\fBndb_restore\fR
+attempts to connect to a management server on
+localhost:1186. This utility acts as a cluster API node, and so requires a free connection
+\(lqslot\(rq
+to connect to the cluster management server. This means that there must be at least one
+[api]
+or
+[mysqld]
+section that can be used by it in the cluster
+\fIconfig.ini\fR
+file. It is a good idea to keep at least one empty
+[api]
+or
+[mysqld]
+section in
+\fIconfig.ini\fR
+that is not being used for a MySQL server or other application for this reason (see
+Section\ 3.4.6, \(lqDefining SQL and Other API Nodes\(rq).
+.PP
+You can verify that
+\fBndb_restore\fR
+is connected to the cluster by using the
+\fBSHOW\fR
+command in the
+\fBndb_mgm\fR
+management client. You can also accomplish this from a system shell, as shown here:
+.sp
+.RS 3n
+.nf
+shell> \fBndb_mgm \-e "SHOW"\fR
+.fi
+.RE
+.PP
+\fB\-n\fR
+is used to specify the node ID of the data node on which the backups were taken.
+.PP
+The first time you run the
+\fBndb_restore\fR
+restoration program, you also need to restore the metadata. In other words, you must re\-create the database tables \(em this can be done by running it with the
+\fB\-m\fR
+option. Note that the cluster should have an empty database when starting to restore a backup. (In other words, you should start
+\fBndbd\fR
+with
+\fB\-\-initial\fR
+prior to performing the restore.)
+.PP
+The
+\fB\-b\fR
+option is used to specify the ID or sequence number of the backup, and is the same number shown by the management client in the
+Backup \fIbackup_id\fR completed
+message displayed upon completion of a backup. (See
+Section\ 7.2, \(lqUsing The Management Client to Create a Backup\(rq.)
+.PP
+The path to the backup directory is required, and must include the subdirectory corresponding to the ID backup of the backup to be restored. For example, if the data node's
+DataDir
+is
+\fI/var/lib/mysql\-cluster\fR, then the backup directory is
+\fI/var/lib/mysql\-cluster/BACKUP\fR, and the backup files for the backup with the ID 3 can be found in
+\fI/var/lib/mysql\-cluster/BACKUP/BACKUP\-3\fR. The path may be absolute or relative to the directory in which the
+\fBndb_restore\fR
+executable is located, and may be optionally prefixed with
+\fBbackup_path=\fR.
+.sp
+.it 1 an-trap
+.nr an-no-space-flag 1
+.nr an-break-flag 1
+.br
+\fBImportant\fR
+.PP
+When restoring cluster backups, you must be sure to restore all data nodes from backups having the same backup ID. Using files from different backups will at best result in restoring the cluster to an inconsistent state, and may fail altogether.
+.PP
+It is possible to restore a backup to a database with a different configuration than it was created from. For example, suppose that a backup with backup ID
+12, created in a cluster with two database nodes having the node IDs
+2
+and
+3, is to be restored to a cluster with four nodes. Then
+\fBndb_restore\fR
+must be run twice \(em once for each database node in the cluster where the backup was taken. However,
+\fBndb_restore\fR
+cannot always restore backups made from a cluster running one version of MySQL to a cluster running a different MySQL version. See
+Section\ 4.2, \(lqCluster Upgrade and Downgrade Compatibility\(rq, for more information.
+.sp
+.it 1 an-trap
+.nr an-no-space-flag 1
+.nr an-break-flag 1
+.br
+\fBNote\fR
+.PP
+For more rapid restoration, the data may be restored in parallel, provided that there is a sufficient number of cluster connections available. That is, when restoring to multiple nodes in parallel, you must have an
+[api]
+or
+[mysqld]
+section in the cluster
+\fIconfig.ini\fR
+file available for each concurrent
+\fBndb_restore\fR
+process. However, the data files must always be applied before the logs.
+.PP
+Most of the options available for this program are shown in the following table:
+.TS
+allbox tab(:);
+l l l l
+l l l l
+l l l l
+l l l l
+l l l l
+l l l l
+l l l l
+l l l l
+l l l l
+l l l l
+l l l l
+l l l l
+l l l l
+l l l l
+l l l l
+l l l l
+l l l l
+l l l l
+l l l l
+l l l l
+l l l l.
+T{
+\fBLong Form\fR
+T}:T{
+\fBShort Form\fR
+T}:T{
+\fBDescription\fR
+T}:T{
+\fBDefault Value\fR
+T}
+T{
+\fB\-\-ndb\-nodeid\fR
+T}:T{
+\fINone\fR
+T}:T{
+Specify a node ID for the \fBndb_restore\fR process
+T}:T{
+0
+T}
+T{
+\fB\-\-ndb\-optimized\-node\-selection\fR
+T}:T{
+\fINone\fR
+T}:T{
+Optimize selection of nodes for transactions
+T}:T{
+TRUE
+T}
+T{
+\fB\-\-ndb\-shm\fR
+T}:T{
+\fINone\fR
+T}:T{
+Use shared memory connections when available
+T}:T{
+FALSE
+T}
+T{
+\fB\-\-nodeid\fR
+T}:T{
+\fB\-n\fR
+T}:T{
+Use backup files from node with the specified ID
+T}:T{
+0
+T}
+T{
+\fB\-\-parallelism\fR
+T}:T{
+\fB\-p\fR
+T}:T{
+Set from 1 to 1024 parallel transactions to be used during the
+ restoration process
+T}:T{
+128
+T}
+T{
+\fB\-\-print\fR
+T}:T{
+\fINone\fR
+T}:T{
+Print metadata, data, and log to stdout
+T}:T{
+FALSE
+T}
+T{
+\fB\-\-print_data\fR
+T}:T{
+\fINone\fR
+T}:T{
+Print data to stdout
+T}:T{
+FALSE
+T}
+T{
+\fB\-\-print_log\fR
+T}:T{
+\fINone\fR
+T}:T{
+Print log to stdout
+T}:T{
+FALSE
+T}
+T{
+\fB\-\-print_meta\fR
+T}:T{
+\fINone\fR
+T}:T{
+Print metadata to stdout
+T}:T{
+FALSE
+T}
+T{
+\fB\-\-restore_data\fR
+T}:T{
+\fB\-r\fR
+T}:T{
+Restore data and logs
+T}:T{
+FALSE
+T}
+T{
+\fB\-\-backup\-id\fR
+T}:T{
+\fB\-b\fR
+T}:T{
+Backup sequence ID
+T}:T{
+0
+T}
+T{
+\fB\-\-restore_meta\fR
+T}:T{
+\fB\-m\fR
+T}:T{
+Restore table metadata
+T}:T{
+FALSE
+T}
+T{
+\fB\-\-version\fR
+T}:T{
+\fB\-V\fR
+T}:T{
+Output version information and exit
+T}:T{
+[N/A]
+T}
+T{
+\fB\-\-backup_path\fR
+T}:T{
+\fINone\fR
+T}:T{
+Path to backup files
+T}:T{
+\fI./\fR
+T}
+T{
+\fB\-\-character\-sets\-dir\fR
+T}:T{
+\fINone\fR
+T}:T{
+Specify the directory where character set information can be found
+T}:T{
+\fINone\fR
+T}
+T{
+\fB\-\-connect\fR, \fB\-\-connectstring\fR, or
+ \fB\-\-ndb\-connectstring\fR
+T}:T{
+\fB\-c\fR or \fB\-C\fR
+T}:T{
+Set the connectstring in
+ [nodeid=\fInode_id;][host=]\fR\fIhost\fR[:\fIport\fR]
+ format
+T}:T{
+localhost:1186
+T}
+T{
+\fB\-\-core\-file\fR
+T}:T{
+\fINone\fR
+T}:T{
+Write a core file in the event of an error
+T}:T{
+TRUE
+T}
+T{
+\fB\-\-debug\fR
+T}:T{
+\fB\-#\fR
+T}:T{
+Output debug log
+T}:T{
+d:t:O,\fI/tmp/ndb_restore.trace\fR
+T}
+T{
+\fB\-\-help\fR or \fB\-\-usage\fR
+T}:T{
+\fB\-?\fR
+T}:T{
+Display help message with available options and current values, then
+ exit
+T}:T{
+[N/A]
+T}
+T{
+\fB\-\-ndb\-mgmd\-host\fR
+T}:T{
+\fINone\fR
+T}:T{
+Set the host and port in
+ \fIhost\fR[:\fIport\fR]
+ format for the management server to connect to; this
+ is the same as \fB\-\-connect\fR,
+ \fB\-\-connectstring\fR, or
+ \fB\-\-ndb\-connectstring\fR, but without a
+ way to specify the nodeid
+T}:T{
+\fINone\fR
+T}
+.TE
+.sp
+.PP
+Beginning with MySQL 5.0.40, several additional options are available for use with the
+\fB\-\-print_data\fR
+option in generating data dumps, either to
+stdout, or to a file. These are similar to some of the options used with
+\fBmysqldump\fR, and are shown in the following table:
+.TS allbox tab(:); l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l. T{ \fBLong Form\fR T}:T{ \fBShort Form\fR T}:T{ \fBDescription\fR T}:T{ \fBDefault Value\fR T} T{ \fB\-\-tab\fR T}:T{ \fB\-T\fR T}:T{ Creates dumpfiles, one per table, each named \fI\fItbl_name\fR\fR\fI.txt\fR. Takes as its argument the path to the directory where the files should be saved (required; use . for the current directory). T}:T{ \fINone\fR T} T{ \fB\-\-fields\-enclosed\-by\fR T}:T{ \fINone\fR T}:T{ String used to enclose all column values T}:T{ \fINone\fR T} T{ \fB\-\-fields\-optionally\-enclosed\-by\fR T}:T{ \fINone\fR T}:T{ String used to enclose column values containing character data (such as CHAR, VARCHAR, BINARY, TEXT, or ENUM) T}:T{ \fINone\fR T} T{ \fB\-\-fields\-terminated\-by\fR T}:T{ \fINone\fR T}:T{ String used to separate column values T}:T{ \\t (tab character) T} T{ \fB\-\-hex\fR T}:T{ \fINone\fR T}:T{ Use hex format for binary values T}:T{ [N/A] T} T{ \fB\-\-lines\-terminated\-by\fR T}:T{ \fINone\fR T}:T{ String used to terminate each line T}:T{ \\n (linefeed character) T} T{ \fB\-\-append\fR T}:T{ \fINone\fR T}:T{ When used with \fB\-\-tab\fR, causes the data to be appended to existing files of the same name T}:T{ [N/A] T} .TE .sp
+.sp
+.it 1 an-trap
+.nr an-no-space-flag 1
+.nr an-break-flag 1
+.br
+\fBNote\fR
+.PP
+If a table has no explicit primary key, then the output generated when using the
+\fB\-\-print\fR
+includes the table's hidden primary key.
+.PP
+Beginning with MySQL 5.0.40, it is possible to restore selected databases, or to restore selected tables from a given database using the syntax shown here:
+.sp
+.RS 3n
+.nf
+ndb_restore \fIother_options\fR \fIdb_name_1\fR [\fIdb_name_2\fR[, \fIdb_name_3\fR][, ...] | \fItbl_name_1\fR[, \fItbl_name_2\fR][, ...]]
+.fi
+.RE
+.sp
+In other words, you can specify either of the following to be restored:
+.TP 3n
+\(bu
+All tables from one or more databases
+.TP 3n
+\(bu
+One or more tables from a single database
+.sp
+.RE
+.sp
+.it 1 an-trap
+.nr an-no-space-flag 1
+.nr an-break-flag 1
+.br
+\fBNote\fR
+.PP
+\fBndb_restore\fR
+reports both temporary and permanent errors. In the case of temporary errors, it may able to recover from them. Beginning with MySQL 5.0.29, it reports
+Restore successful, but encountered temporary error, please look at configuration
+in such cases.
+.SH "COPYRIGHT"
+.PP
+Copyright 2007 MySQL AB
+.PP
+This documentation is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License.
+.PP
+This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
+.PP
+You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110\-1301 USA or see http://www.gnu.org/licenses/.
+.PP
+Please email
+<docs at mysql.com>
+for more information or if you are interested in doing a translation.
+.SH "SEE ALSO"
+For more information, please refer to the MySQL Reference Manual,
+which may already be installed locally and which is also available
+online at http://dev.mysql.com/doc/.
+.SH AUTHOR
+MySQL AB (http://www.mysql.com/).
Added: branches/sid-5.0/debian/manpages/ndb_select_all.1
===================================================================
--- branches/sid-5.0/debian/manpages/ndb_select_all.1 (rev 0)
+++ branches/sid-5.0/debian/manpages/ndb_select_all.1 2007-11-26 12:34:29 UTC (rev 1020)
@@ -0,0 +1,216 @@
+.\" Title: \fBndb_select_all\fR
+.\" Author:
+.\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
+.\" Date: 11/25/2007
+.\" Manual: MySQL Database System
+.\" Source: MySQL 5.0
+.\"
+.TH "\fBNDB_SELECT_ALL\fR" "1" "11/25/2007" "MySQL 5.0" "MySQL Database System"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
+.SH "NAME"
+ndb_select_all \- print rows from NDB table
+.SH "SYNOPSIS"
+.HP 67
+\fBndb_select_all \-c \fR\fB\fIconnect_string\fR\fR\fB \fR\fB\fItbl_name\fR\fR\fB \-d \fR\fB\fIdb_name\fR\fR\fB [> \fR\fB\fIfile_name\fR\fR\fB]\fR
+.SH "DESCRIPTION"
+.PP
+\fBndb_select_all\fR
+prints all rows from an
+NDB
+table to
+stdout.
+.PP
+\fBUsage\fR:
+.sp
+.RS 3n
+.nf
+ndb_select_all \-c \fIconnect_string\fR \fItbl_name\fR \-d \fIdb_name\fR [> \fIfile_name\fR]
+.fi
+.RE
+.PP
+\fBAdditional Options\fR:
+.TP 3n
+\(bu
+\fB\-\-lock=\fR\fB\fIlock_type\fR\fR,
+\fB\-l \fR\fB\fIlock_type\fR\fR
+.sp
+Employs a lock when reading the table. Possible values for
+\fIlock_type\fR
+are:
+.RS 3n
+.TP 3n
+\(bu
+0: Read lock
+.TP 3n
+\(bu
+1: Read lock with hold
+.TP 3n
+\(bu
+2: Exclusive read lock
+.RE
+.IP "" 3n
+There is no default value for this option.
+.TP 3n
+\(bu
+\fB\-\-order=\fR\fB\fIindex_name\fR\fR,
+\fB\-o \fR\fB\fIindex_name\fR\fR
+.sp
+Orders the output according to the index named
+\fIindex_name\fR. Note that this is the name of an index, not of a column, and that the index must have been explicitly named when created.
+.TP 3n
+\(bu
+\fB\-\-descending\fR,
+\fB\-z\fR
+.sp
+Sorts the output in descending order. This option can be used only in conjunction with the
+\fB\-o\fR
+(\fB\-\-order\fR) option.
+.TP 3n
+\(bu
+\fB\-\-header=FALSE\fR
+.sp
+Excludes column headers from the output.
+.TP 3n
+\(bu
+\fB\-\-useHexFormat\fR
+\fB\-x\fR
+.sp
+Causes all numeric values to be displayed in hexadecimal format. This does not affect the output of numerals contained in strings or datetime values.
+.TP 3n
+\(bu
+\fB\-\-delimiter=\fR\fB\fIcharacter\fR\fR,
+\fB\-D \fR\fB\fIcharacter\fR\fR
+.sp
+Causes the
+\fIcharacter\fR
+to be used as a column delimiter. Only table data columns are separated by this delimiter.
+.sp
+The default delimiter is the tab character.
+.TP 3n
+\(bu
+\fB\-\-rowid\fR
+.sp
+Adds a
+ROWID
+column providing information about the fragments in which rows are stored.
+.TP 3n
+\(bu
+\fB\-\-gci\fR
+.sp
+Adds a column to the output showing the global checkpoint at which each row was last updated. See
+Section\ 12, \(lqMySQL Cluster Glossary\(rq, and
+Section\ 6.3.2, \(lqLog Events\(rq, for more information about checkpoints.
+.TP 3n
+\(bu
+\fB\-\-tupscan\fR,
+\fB\-t\fR
+.sp
+Scan the table in the order of the tuples.
+.TP 3n
+\(bu
+\fB\-\-nodata\fR
+.sp
+Causes any table data to be omitted.
+.sp
+.RE
+.PP
+\fBSample Output\fR:
+.PP
+Output from a MySQL
+SELECT
+statement:
+.sp
+.RS 3n
+.nf
+mysql> \fBSELECT * FROM ctest1.fish;\fR
++\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-+
+| id | name |
++\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-+
+| 3 | shark |
+| 6 | puffer |
+| 2 | tuna |
+| 4 | manta ray |
+| 5 | grouper |
+| 1 | guppy |
++\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-+
+6 rows in set (0.04 sec)
+.fi
+.RE
+.PP
+Output from the equivalent invocation of
+\fBndb_select_all\fR:
+.sp
+.RS 3n
+.nf
+shell> \fB./ndb_select_all \-c localhost fish \-d ctest1\fR
+id name
+3 [shark]
+6 [puffer]
+2 [tuna]
+4 [manta ray]
+5 [grouper]
+1 [guppy]
+6 rows returned
+NDBT_ProgramExit: 0 \- OK
+.fi
+.RE
+.PP
+Note that all string values are enclosed by square brackets (\(lq[...]\(rq) in the output of
+\fBndb_select_all\fR. For a further example, consider the table created and populated as shown here:
+.sp
+.RS 3n
+.nf
+CREATE TABLE dogs (
+ id INT(11) NOT NULL AUTO_INCREMENT,
+ name VARCHAR(25) NOT NULL,
+ breed VARCHAR(50) NOT NULL,
+ PRIMARY KEY pk (id),
+ KEY ix (name)
+)
+ENGINE=NDB;
+INSERT INTO dogs VALUES
+ ('', 'Lassie', 'collie'),
+ ('', 'Scooby\-Doo', 'Great Dane'),
+ ('', 'Rin\-Tin\-Tin', 'German Shepherd'),
+ ('', 'Rosscoe', 'Mutt');
+.fi
+.RE
+.PP
+This demonstrates the use of several additional
+\fBndb_select_all\fR
+options:
+.sp
+.RS 3n
+.nf
+shell> \fB./ndb_select_all \-d ctest1 dogs \-o ix \-z \-\-gci\fR
+GCI id name breed
+834461 2 [Scooby\-Doo] [Great Dane]
+834878 4 [Rosscoe] [Mutt]
+834463 3 [Rin\-Tin\-Tin] [German Shepherd]
+835657 1 [Lassie] [Collie]
+4 rows returned
+NDBT_ProgramExit: 0 \- OK
+.fi
+.RE
+.SH "COPYRIGHT"
+.PP
+Copyright 2007 MySQL AB
+.PP
+This documentation is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License.
+.PP
+This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
+.PP
+You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110\-1301 USA or see http://www.gnu.org/licenses/.
+.PP
+Please email
+<docs at mysql.com>
+for more information or if you are interested in doing a translation.
+.SH "SEE ALSO"
+For more information, please refer to the MySQL Reference Manual,
+which may already be installed locally and which is also available
+online at http://dev.mysql.com/doc/.
+.SH AUTHOR
+MySQL AB (http://www.mysql.com/).
Added: branches/sid-5.0/debian/manpages/ndb_select_count.1
===================================================================
--- branches/sid-5.0/debian/manpages/ndb_select_count.1 (rev 0)
+++ branches/sid-5.0/debian/manpages/ndb_select_count.1 2007-11-26 12:34:29 UTC (rev 1020)
@@ -0,0 +1,65 @@
+.\" Title: \fBndb_select_count\fR
+.\" Author:
+.\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
+.\" Date: 11/25/2007
+.\" Manual: MySQL Database System
+.\" Source: MySQL 5.0
+.\"
+.TH "\fBNDB_SELECT_COUNT\\" "1" "11/25/2007" "MySQL 5.0" "MySQL Database System"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
+.SH "NAME"
+ndb_select_count \- print row counts for NDB tables
+.SH "SYNOPSIS"
+.HP 76
+\fBndb_select_count [\-c \fR\fB\fIconnect_string\fR\fR\fB] \-d\fR\fB\fIdb_name\fR\fR\fB \fR\fB\fItbl_name\fR\fR\fB[, \fR\fB\fItbl_name2\fR\fR\fB[, ...]]\fR
+.SH "DESCRIPTION"
+.PP
+\fBndb_select_count\fR
+prints the number of rows in one or more
+NDB
+tables. With a single table, the result is equivalent to that obtained by using the MySQL statement
+SELECT COUNT(*) FROM \fItbl_name\fR.
+.PP
+\fBUsage\fR:
+.sp
+.RS 3n
+.nf
+ndb_select_count [\-c \fIconnect_string\fR] \-d\fIdb_name\fR \fItbl_name\fR[, \fItbl_name2\fR[, ...]]
+.fi
+.RE
+.PP
+\fBAdditional Options\fR: None that are specific to this application. However, you can obtain row counts from multiple tables in the same database by listing the table names separated by spaces when invoking this command, as shown under
+\fBSample Output\fR.
+.PP
+\fBSample Output\fR:
+.sp
+.RS 3n
+.nf
+shell> \fB./ndb_select_count \-c localhost \-d ctest1 fish dogs\fR
+6 records in table fish
+4 records in table dogs
+NDBT_ProgramExit: 0 \- OK
+.fi
+.RE
+.SH "COPYRIGHT"
+.PP
+Copyright 2007 MySQL AB
+.PP
+This documentation is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License.
+.PP
+This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
+.PP
+You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110\-1301 USA or see http://www.gnu.org/licenses/.
+.PP
+Please email
+<docs at mysql.com>
+for more information or if you are interested in doing a translation.
+.SH "SEE ALSO"
+For more information, please refer to the MySQL Reference Manual,
+which may already be installed locally and which is also available
+online at http://dev.mysql.com/doc/.
+.SH AUTHOR
+MySQL AB (http://www.mysql.com/).
Added: branches/sid-5.0/debian/manpages/ndb_show_tables.1
===================================================================
--- branches/sid-5.0/debian/manpages/ndb_show_tables.1 (rev 0)
+++ branches/sid-5.0/debian/manpages/ndb_show_tables.1 2007-11-26 12:34:29 UTC (rev 1020)
@@ -0,0 +1,113 @@
+.\" Title: \fBndb_show_tables\fR
+.\" Author:
+.\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
+.\" Date: 11/25/2007
+.\" Manual: MySQL Database System
+.\" Source: MySQL 5.0
+.\"
+.TH "\fBNDB_SHOW_TABLES\\F" "1" "11/25/2007" "MySQL 5.0" "MySQL Database System"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
+.SH "NAME"
+ndb_show_tables \- display list of NDB tables
+.SH "SYNOPSIS"
+.HP 26
+\fBndb_show_tables [\fR\fB\fIoptions\fR\fR\fB]\fR
+.SH "DESCRIPTION"
+.PP
+\fBndb_show_tables\fR
+displays a list of all
+NDB
+database objects in the cluster. By default, this includes not only both user\-created tables and
+NDB
+system tables, but
+NDB\-specific indexes, and internal triggers, as well.
+.PP
+\fBUsage\fR:
+.sp
+.RS 3n
+.nf
+ndb_show_tables [\-c \fIconnect_string\fR]
+.fi
+.RE
+.PP
+\fBAdditional Options\fR:
+.TP 3n
+\(bu
+\fB\-\-loops\fR,
+\fB\-l\fR
+.sp
+Specifies the number of times the utility should execute. This is 1 when this option is not specified, but if you do use the option, you must supply an integer argument for it.
+.TP 3n
+\(bu
+\fB\-\-parsable\fR,
+\fB\-p\fR
+.sp
+Using this option causes the output to be in a format suitable for use with
+LOAD DATA INFILE.
+.TP 3n
+\(bu
+\fB\-\-type\fR,
+\fB\-t\fR
+.sp
+Can be used to restrict the output to one type of object, specified by an integer type code as shown here:
+.RS 3n
+.TP 3n
+\(bu
+\fB1\fR: System table
+.TP 3n
+\(bu
+\fB2\fR: User\-created table
+.TP 3n
+\(bu
+\fB3\fR: Unique hash index
+.RE
+.IP "" 3n
+Any other value causes all
+NDB
+database objects to be listed (the default).
+.TP 3n
+\(bu
+\fB\-\-unqualified\fR,
+\fB\-u\fR
+.sp
+If specified, this causes unqualified object names to be displayed.
+.sp
+.RE
+.sp
+.it 1 an-trap
+.nr an-no-space-flag 1
+.nr an-break-flag 1
+.br
+\fBNote\fR
+.PP
+Only user\-created Cluster tables may be accessed from MySQL; system tables such as
+SYSTAB_0
+are not visible to
+\fBmysqld\fR. However, you can examine the contents of system tables using
+NDB
+API applications such as
+\fBndb_select_all\fR
+(see
+\fBndb_select_all\fR(1)).
+.SH "COPYRIGHT"
+.PP
+Copyright 2007 MySQL AB
+.PP
+This documentation is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License.
+.PP
+This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
+.PP
+You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110\-1301 USA or see http://www.gnu.org/licenses/.
+.PP
+Please email
+<docs at mysql.com>
+for more information or if you are interested in doing a translation.
+.SH "SEE ALSO"
+For more information, please refer to the MySQL Reference Manual,
+which may already be installed locally and which is also available
+online at http://dev.mysql.com/doc/.
+.SH AUTHOR
+MySQL AB (http://www.mysql.com/).
Added: branches/sid-5.0/debian/manpages/ndb_size.pl.1
===================================================================
--- branches/sid-5.0/debian/manpages/ndb_size.pl.1 (rev 0)
+++ branches/sid-5.0/debian/manpages/ndb_size.pl.1 2007-11-26 12:34:29 UTC (rev 1020)
@@ -0,0 +1,126 @@
+.\" Title: \fBndb_size.pl\fR
+.\" Author:
+.\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
+.\" Date: 11/25/2007
+.\" Manual: MySQL Database System
+.\" Source: MySQL 5.0
+.\"
+.TH "\fBNDB_SIZE.PL\fR" "1" "11/25/2007" "MySQL 5.0" "MySQL Database System"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
+.SH "NAME"
+ndb_size.pl \- NDBCluster Size Requirement Estimator
+.SH "SYNOPSIS"
+.HP 22
+\fBndb_size.pl \fR\fB\fIarguments\fR\fR
+.SH "DESCRIPTION"
+.PP
+This is a Perl script that can be used to estimate the amount of space that would be required by a MySQL database if it were converted to use the
+NDBCluster
+storage engine. Unlike the other utilities discussed in this section, it does not require access to a MySQL Cluster (in fact, there is no reason for it to do so). However, it does need to access the MySQL server on which the database to be tested resides.
+.PP
+\fBRequirements\fR:
+.TP 3n
+\(bu
+A running MySQL server. The server instance does not have to provide support for MySQL Cluster.
+.TP 3n
+\(bu
+A working installation of Perl.
+.TP 3n
+\(bu
+The
+DBI
+and
+HTML::Template
+modules, both of which can be obtained from CPAN if they are not already part of your Perl installation. (Many Linux and other operating system distributions provide their own packages for one or both of these libraries.)
+.TP 3n
+\(bu
+The
+\fIndb_size.tmpl\fR
+template file, which you should be able to find in the
+\fIshare/mysql\fR
+directory of your MySQL installation. This file should be copied or moved into the same directory as
+\fIndb_size.pl\fR
+\(em if it is not there already \(em before running the script.
+.TP 3n
+\(bu
+A MySQL user account having the necessary privileges. If you do not wish to use an existing account, then creating one using
+GRANT USAGE ON \fIdb_name\fR.*
+\(em where
+\fIdb_name\fR
+is the name of the database to be examined \(em is sufficient for this purpose.
+.sp
+.RE
+.PP
+\fIndb_size.pl\fR
+and
+\fIndb_size.tmpl\fR
+can also be found in the MySQL sources in
+\fIstorage/ndb/tools\fR. If these files are not present in your MySQL installation, you can obtain them from the
+[1]\&\fIMySQLForge project page\fR.
+.PP
+\fBUsage\fR:
+.sp
+.RS 3n
+.nf
+perl ndb_size.pl \fIdb_name\fR \fIhostname\fR \fIusername\fR \fIpassword\fR > \fIfile_name\fR.html
+.fi
+.RE
+.PP
+The command shown connects to the MySQL server at
+\fIhostname\fR
+using the account of the user
+\fIusername\fR
+having the password
+\fIpassword\fR, analyses all of the tables in database
+\fIdb_name\fR, and generates a report in HTML format which is directed to the file
+\fI\fIfile_name\fR\fR\fI.html\fR. (Without the redirection, the output is sent to
+stdout.) This figure shows partial sample output as viewed in a Web browser:
+.PP
+The output from this script includes:
+.TP 3n
+\(bu
+Minimum values for the
+DataMemory,
+IndexMemory,
+MaxNoOfTables,
+MaxNoOfAttributes,
+MaxNoOfOrderedIndexes,
+MaxNoOfUniqueHashIndexes, and
+MaxNoOfTriggers
+configuration parameters required to accommodate the tables analysed.
+.TP 3n
+\(bu
+Memory requirements for all of the tables, attributes, ordered indexes, and unique hash indexes defined in the database.
+.TP 3n
+\(bu
+The
+IndexMemory
+and
+DataMemory
+required per table and table row.
+.SH "COPYRIGHT"
+.PP
+Copyright 2007 MySQL AB
+.PP
+This documentation is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License.
+.PP
+This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
+.PP
+You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110\-1301 USA or see http://www.gnu.org/licenses/.
+.PP
+Please email
+<docs at mysql.com>
+for more information or if you are interested in doing a translation.
+.SH "REFERENCES"
+.TP 3
+1.\ MySQLForge project page
+\%http://forge.mysql.com/projects/view.php?id=88
+.SH "SEE ALSO"
+For more information, please refer to the MySQL Reference Manual,
+which may already be installed locally and which is also available
+online at http://dev.mysql.com/doc/.
+.SH AUTHOR
+MySQL AB (http://www.mysql.com/).
Added: branches/sid-5.0/debian/manpages/ndb_waiter.1
===================================================================
--- branches/sid-5.0/debian/manpages/ndb_waiter.1 (rev 0)
+++ branches/sid-5.0/debian/manpages/ndb_waiter.1 2007-11-26 12:34:29 UTC (rev 1020)
@@ -0,0 +1,189 @@
+.\" Title: \fBndb_waiter\fR
+.\" Author:
+.\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
+.\" Date: 11/25/2007
+.\" Manual: MySQL Database System
+.\" Source: MySQL 5.0
+.\"
+.TH "\fBNDB_WAITER\fR" "1" "11/25/2007" "MySQL 5.0" "MySQL Database System"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
+.SH "NAME"
+ndb_waiter \- wait for cluster to reach a given status
+.SH "SYNOPSIS"
+.HP 19
+\fBndb_waiter \fR\fB\fIoptions\fR\fR
+.SH "DESCRIPTION"
+.PP
+\fBndb_waiter\fR
+repeatedly (each 100 milliseconds) prints out the status of all cluster data nodes until either the cluster reaches a given status or the
+\fB\-\-timeout\fR
+limit is exceeded, then exits. By default, it waits for the cluster to achieve
+STARTED
+status, in which all nodes have started and connected to the cluster. This can be overridden using the
+\fB\-\-no\-contact\fR
+and
+\fB\-\-not\-started\fR
+options (see
+Additional Options).
+.PP
+The node states reported by this utility are as follows:
+.TP 3n
+\(bu
+NO_CONTACT: The node cannot be contacted.
+.TP 3n
+\(bu
+UNKNOWN: The node can be contacted, but its status is not yet known. Usually, this means that the node has received a
+START
+or
+RESTART
+command from the management server, but has not yet acted on it.
+.TP 3n
+\(bu
+NOT_STARTED: The node has stopped, but remains in contact with the cluster. This is seen when restarting the node using the management client's
+RESTART
+command.
+.TP 3n
+\(bu
+STARTING: The node's
+\fBndbd\fR
+process has started, but the node has not yet joined the cluster.
+.TP 3n
+\(bu
+STARTED: The node is operational, and has joined the cluster.
+.TP 3n
+\(bu
+SHUTTING_DOWN: The node is shutting down.
+.TP 3n
+\(bu
+SINGLE USER MODE: This is shown for all cluster data nodes when the cluster is in single user mode.
+.sp
+.RE
+.PP
+\fBUsage\fR:
+.sp
+.RS 3n
+.nf
+ndb_waiter [\-c \fIconnect_string\fR]
+.fi
+.RE
+.PP
+\fBAdditional Options\fR:
+.TP 3n
+\(bu
+\fB\-\-no\-contact\fR,
+\fB\-n\fR
+.sp
+Instead of waiting for the
+STARTED
+state,
+\fBndb_waiter\fR
+continues running until the cluster reaches
+NO_CONTACT
+status before exiting.
+.TP 3n
+\(bu
+\fB\-\-not\-started\fR
+.sp
+Instead of waiting for the
+STARTED
+state,
+\fBndb_waiter\fR
+continues running until the cluster reaches
+NOT_STARTED
+status before exiting.
+.TP 3n
+\(bu
+\fB\-\-timeout=\fR\fB\fIseconds\fR\fR,
+\fB\-t \fR\fB\fIseconds\fR\fR
+.sp
+Time to wait. The program exits if the desired state is not achieved within this number of seconds. The default is 120 seconds (1200 reporting cycles).
+.sp
+.RE
+.PP
+\fBSample Output\fR. Shown here is the output from
+\fBndb_waiter\fR
+when run against a 4\-node cluster in which two nodes have been shut down and then started again manually. Duplicate reports (indicated by
+\(lq...\(rq) are omitted.
+.sp
+.RS 3n
+.nf
+shell> \fB./ndb_waiter \-c localhost\fR
+Connecting to mgmsrv at (localhost)
+State node 1 STARTED
+State node 2 NO_CONTACT
+State node 3 STARTED
+State node 4 NO_CONTACT
+Waiting for cluster enter state STARTED
+...
+State node 1 STARTED
+State node 2 UNKNOWN
+State node 3 STARTED
+State node 4 NO_CONTACT
+Waiting for cluster enter state STARTED
+...
+State node 1 STARTED
+State node 2 STARTING
+State node 3 STARTED
+State node 4 NO_CONTACT
+Waiting for cluster enter state STARTED
+...
+State node 1 STARTED
+State node 2 STARTING
+State node 3 STARTED
+State node 4 UNKNOWN
+Waiting for cluster enter state STARTED
+...
+State node 1 STARTED
+State node 2 STARTING
+State node 3 STARTED
+State node 4 STARTING
+Waiting for cluster enter state STARTED
+...
+State node 1 STARTED
+State node 2 STARTED
+State node 3 STARTED
+State node 4 STARTING
+Waiting for cluster enter state STARTED
+...
+State node 1 STARTED
+State node 2 STARTED
+State node 3 STARTED
+State node 4 STARTED
+Waiting for cluster enter state STARTED
+NDBT_ProgramExit: 0 \- OK
+.fi
+.RE
+.sp
+.it 1 an-trap
+.nr an-no-space-flag 1
+.nr an-break-flag 1
+.br
+\fBNote\fR
+.PP
+If no connectstring is specified, then
+\fBndb_waiter\fR
+tries to connect to a management on
+localhost, and reports
+Connecting to mgmsrv at (null).
+.SH "COPYRIGHT"
+.PP
+Copyright 2007 MySQL AB
+.PP
+This documentation is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License.
+.PP
+This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
+.PP
+You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110\-1301 USA or see http://www.gnu.org/licenses/.
+.PP
+Please email
+<docs at mysql.com>
+for more information or if you are interested in doing a translation.
+.SH "SEE ALSO"
+For more information, please refer to the MySQL Reference Manual,
+which may already be installed locally and which is also available
+online at http://dev.mysql.com/doc/.
+.SH AUTHOR
+MySQL AB (http://www.mysql.com/).
Added: branches/sid-5.0/debian/manpages/ndbd.1
===================================================================
--- branches/sid-5.0/debian/manpages/ndbd.1 (rev 0)
+++ branches/sid-5.0/debian/manpages/ndbd.1 2007-11-26 12:34:29 UTC (rev 1020)
@@ -0,0 +1,178 @@
+.\" Title: \fBndbd\fR
+.\" Author:
+.\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
+.\" Date: 11/25/2007
+.\" Manual: MySQL Database System
+.\" Source: MySQL 5.0
+.\"
+.TH "\fBNDBD\fR" "1" "11/25/2007" "MySQL 5.0" "MySQL Database System"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
+.SH "NAME"
+ndbd \- the storage engine node process
+.SH "SYNOPSIS"
+.HP 13
+\fBndbd \fR\fB\fIoptions\fR\fR
+.SH "DESCRIPTION"
+.PP
+\fBndbd\fR
+is the process that is used to handle all the data in tables using the NDB Cluster storage engine. This is the process that empowers a data node to accomplish distributed transaction handling, node recovery, checkpointing to disk, online backup, and related tasks.
+.PP
+In a MySQL Cluster, a set of
+\fBndbd\fR
+processes cooperate in handling data. These processes can execute on the same computer (host) or on different computers. The correspondences between data nodes and Cluster hosts is completely configurable.
+.PP
+\fBndbd\fR
+generates a set of log files which are placed in the directory specified by
+DataDir
+in the
+\fIconfig.ini\fR
+configuration file.
+.PP
+These log files are listed below.
+\fInode_id\fR
+is the node's unique identifier. Note that
+\fInode_id\fR
+represents the node's unique identifier. For example,
+\fIndb_2_error.log\fR
+is the error log generated by the data node whose node ID is
+2.
+.TP 3n
+\(bu
+\fIndb_\fR\fI\fInode_id\fR\fR\fI_error.log\fR
+is a file containing records of all crashes which the referenced
+\fBndbd\fR
+process has encountered. Each record in this file contains a brief error string and a reference to a trace file for this crash. A typical entry in this file might appear as shown here:
+.sp
+.RS 3n
+.nf
+Date/Time: Saturday 30 July 2004 \- 00:20:01
+Type of error: error
+Message: Internal program error (failed ndbrequire)
+Fault ID: 2341
+Problem data: DbtupFixAlloc.cpp
+Object of reference: DBTUP (Line: 173)
+ProgramName: NDB Kernel
+ProcessID: 14909
+TraceFile: ndb_2_trace.log.2
+***EOM***
+.fi
+.RE
+Listings of possible
+\fBndbd\fR
+exit codes and messages generated when a data node process shuts down prematurely can be found in
+[1]\&\fIndbd Error Messages\fR.
+.sp
+.it 1 an-trap
+.nr an-no-space-flag 1
+.nr an-break-flag 1
+.br
+\fBImportant\fR
+\fIThe last entry in the error log file is not necessarily the newest one\fR
+(nor is it likely to be). Entries in the error log are
+\fInot\fR
+listed in chronological order; rather, they correspond to the order of the trace files as determined in the
+\fIndb_\fR\fI\fInode_id\fR\fR\fI_trace.log.next\fR
+file (see below). Error log entries are thus overwritten in a cyclical and not sequential fashion.
+.TP 3n
+\(bu
+\fIndb_\fR\fI\fInode_id\fR\fR\fI_trace.log.\fR\fI\fItrace_id\fR\fR
+is a trace file describing exactly what happened just before the error occurred. This information is useful for analysis by the MySQL Cluster development team.
+.sp
+It is possible to configure the number of these trace files that will be created before old files are overwritten.
+\fItrace_id\fR
+is a number which is incremented for each successive trace file.
+.TP 3n
+\(bu
+\fIndb_\fR\fI\fInode_id\fR\fR\fI_trace.log.next\fR
+is the file that keeps track of the next trace file number to be assigned.
+.TP 3n
+\(bu
+\fIndb_\fR\fI\fInode_id\fR\fR\fI_out.log\fR
+is a file containing any data output by the
+\fBndbd\fR
+process. This file is created only if
+\fBndbd\fR
+is started as a daemon, which is the default behavior.
+.TP 3n
+\(bu
+\fIndb_\fR\fI\fInode_id\fR\fR\fI.pid\fR
+is a file containing the process ID of the
+\fBndbd\fR
+process when started as a daemon. It also functions as a lock file to avoid the starting of nodes with the same identifier.
+.TP 3n
+\(bu
+\fIndb_\fR\fI\fInode_id\fR\fR\fI_signal.log\fR
+is a file used only in debug versions of
+\fBndbd\fR, where it is possible to trace all incoming, outgoing, and internal messages with their data in the
+\fBndbd\fR
+process.
+.sp
+.RE
+.PP
+It is recommended not to use a directory mounted through NFS because in some environments this can cause problems whereby the lock on the
+\fI.pid\fR
+file remains in effect even after the process has terminated.
+.PP
+To start
+\fBndbd\fR, it may also be necessary to specify the hostname of the management server and the port on which it is listening. Optionally, one may also specify the node ID that the process is to use.
+.sp
+.RS 3n
+.nf
+shell> \fBndbd \-\-connect\-string="nodeid=2;host=ndb_mgmd.mysql.com:1186"\fR
+.fi
+.RE
+.PP
+See
+Section\ 3.4.2, \(lqThe Cluster Connectstring\(rq, for additional information about this issue.
+Section\ 5.2, \(lqCommand Options for MySQL Cluster Processes\(rq, describes other options for
+\fBndbd\fR.
+.PP
+When
+\fBndbd\fR
+starts, it actually initiates two processes. The first of these is called the
+\(lqangel process\(rq; its only job is to discover when the execution process has been completed, and then to restart the
+\fBndbd\fR
+process if it is configured to do so. Thus, if you attempt to kill
+\fBndbd\fR
+via the Unix
+\fBkill\fR
+command, it is necessary to kill both processes, beginning with the angel process. The preferred method of terminating an
+\fBndbd\fR
+process is to use the management client and stop the process from there.
+.PP
+The execution process uses one thread for reading, writing, and scanning data, as well as all other activities. This thread is implemented asynchronously so that it can easily handle thousands of concurrent activites. In addition, a watch\-dog thread supervises the execution thread to make sure that it does not hang in an endless loop. A pool of threads handles file I/O, with each thread able to handle one open file. Threads can also be used for transporter connections by the transporters in the
+\fBndbd\fR
+process. In a multi\-processor system performing a large number of operations (including updates), the
+\fBndbd\fR
+process can consume up to 2 CPUs if permitted to do so.
+.PP
+For a machine with many CPUs it is possible to use several
+\fBndbd\fR
+processes which belong to different node groups; however, such a configuration is still considered experimental and is not supported for MySQL 5.0 in a production setting. See
+Section\ 10, \(lqKnown Limitations of MySQL Cluster\(rq.
+.SH "COPYRIGHT"
+.PP
+Copyright 2007 MySQL AB
+.PP
+This documentation is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License.
+.PP
+This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
+.PP
+You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110\-1301 USA or see http://www.gnu.org/licenses/.
+.PP
+Please email
+<docs at mysql.com>
+for more information or if you are interested in doing a translation.
+.SH "REFERENCES"
+.TP 3
+1.\ ndbd Error Messages
+\%http://dev.mysql.com/doc/ndbapi/en/ndbd\-error\-messages.html
+.SH "SEE ALSO"
+For more information, please refer to the MySQL Reference Manual,
+which may already be installed locally and which is also available
+online at http://dev.mysql.com/doc/.
+.SH AUTHOR
+MySQL AB (http://www.mysql.com/).
Added: branches/sid-5.0/debian/manpages/perror.1
===================================================================
--- branches/sid-5.0/debian/manpages/perror.1 (rev 0)
+++ branches/sid-5.0/debian/manpages/perror.1 2007-11-26 12:34:29 UTC (rev 1020)
@@ -0,0 +1,121 @@
+.\" Title: \fBperror\fR
+.\" Author:
+.\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
+.\" Date: 11/25/2007
+.\" Manual: MySQL Database System
+.\" Source: MySQL 5.0
+.\"
+.TH "\fBPERROR\fR" "1" "11/25/2007" "MySQL 5.0" "MySQL Database System"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
+.SH "NAME"
+perror \- explain error codes
+.SH "SYNOPSIS"
+.HP 31
+\fBperror [\fR\fB\fIoptions\fR\fR\fB] \fR\fB\fIerrorcode\fR\fR\fB ...\fR
+.SH "DESCRIPTION"
+.PP
+For most system errors, MySQL displays, in addition to an internal text message, the system error code in one of the following styles:
+.sp
+.RS 3n
+.nf
+message ... (errno: #)
+message ... (Errcode: #)
+.fi
+.RE
+.PP
+You can find out what the error code means by examining the documentation for your system or by using the
+\fBperror\fR
+utility.
+.PP
+\fBperror\fR
+prints a description for a system error code or for a storage engine (table handler) error code.
+.PP
+Invoke
+\fBperror\fR
+like this:
+.sp
+.RS 3n
+.nf
+shell> \fBperror [\fR\fB\fIoptions\fR\fR\fB] \fR\fB\fIerrorcode\fR\fR\fB ...\fR
+.fi
+.RE
+.PP
+Example:
+.sp
+.RS 3n
+.nf
+shell> \fBperror 13 64\fR
+OS error code 13: Permission denied
+OS error code 64: Machine is not on the network
+.fi
+.RE
+.PP
+To obtain the error message for a MySQL Cluster error code, invoke
+\fBperror\fR
+with the
+\fB\-\-ndb\fR
+option:
+.sp
+.RS 3n
+.nf
+shell> \fBperror \-\-ndb \fR\fB\fIerrorcode\fR\fR
+.fi
+.RE
+.PP
+Note that the meaning of system error messages may be dependent on your operating system. A given error code may mean different things on different operating systems.
+.PP
+\fBperror\fR
+supports the following options:
+.TP 3n
+\(bu
+\fB\-\-help\fR,
+\fB\-\-info\fR,
+\fB\-I\fR,
+\fB\-?\fR
+.sp
+Display a help message and exit.
+.TP 3n
+\(bu
+\fB\-\-ndb\fR
+.sp
+Print the error message for a MySQL Cluster error code.
+.TP 3n
+\(bu
+\fB\-\-silent\fR,
+\fB\-s\fR
+.sp
+Silent mode. Print only the error message.
+.TP 3n
+\(bu
+\fB\-\-verbose\fR,
+\fB\-v\fR
+.sp
+Verbose mode. Print error code and message. This is the default behavior.
+.TP 3n
+\(bu
+\fB\-\-version\fR,
+\fB\-V\fR
+.sp
+Display version information and exit.
+.SH "COPYRIGHT"
+.PP
+Copyright 2007 MySQL AB
+.PP
+This documentation is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License.
+.PP
+This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
+.PP
+You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110\-1301 USA or see http://www.gnu.org/licenses/.
+.PP
+Please email
+<docs at mysql.com>
+for more information or if you are interested in doing a translation.
+.SH "SEE ALSO"
+For more information, please refer to the MySQL Reference Manual,
+which may already be installed locally and which is also available
+online at http://dev.mysql.com/doc/.
+.SH AUTHOR
+MySQL AB (http://www.mysql.com/).
Added: branches/sid-5.0/debian/manpages/replace.1
===================================================================
--- branches/sid-5.0/debian/manpages/replace.1 (rev 0)
+++ branches/sid-5.0/debian/manpages/replace.1 2007-11-26 12:34:29 UTC (rev 1020)
@@ -0,0 +1,123 @@
+.\" Title: \fBreplace\fR
+.\" Author:
+.\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
+.\" Date: 11/25/2007
+.\" Manual: MySQL Database System
+.\" Source: MySQL 5.0
+.\"
+.TH "\fBREPLACE\fR" "1" "11/25/2007" "MySQL 5.0" "MySQL Database System"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
+.SH "NAME"
+replace \- a string\-replacement utility
+.SH "SYNOPSIS"
+.HP 18
+\fBreplace \fR\fB\fIarguments\fR\fR
+.SH "DESCRIPTION"
+.PP
+The
+\fBreplace\fR
+utility program changes strings in place in files or on the standard input.
+.PP
+Invoke
+\fBreplace\fR
+in one of the following ways:
+.sp
+.RS 3n
+.nf
+shell> \fBreplace \fR\fB\fIfrom\fR\fR\fB \fR\fB\fIto\fR\fR\fB [\fR\fB\fIfrom\fR\fR\fB \fR\fB\fIto\fR\fR\fB] ... \-\- \fR\fB\fIfile\fR\fR\fB [\fR\fB\fIfile\fR\fR\fB] ...\fR
+shell> \fBreplace \fR\fB\fIfrom\fR\fR\fB \fR\fB\fIto\fR\fR\fB [\fR\fB\fIfrom\fR\fR\fB \fR\fB\fIto\fR\fR\fB] ... < \fR\fB\fIfile\fR\fR
+.fi
+.RE
+.PP
+\fIfrom\fR
+represents a string to look for and
+\fIto\fR
+represents its replacement. There can be one or more pairs of strings.
+.PP
+Use the
+\fB\-\-\fR
+option to indicate where the string\-replacement list ends and the filenames begin. In this case, any file named on the command line is modified in place, so you may want to make a copy of the original before converting it.
+\fIreplace\fR
+prints a message indicating which of the input files it actually modifies.
+.PP
+If the
+\fB\-\-\fR
+option is not given,
+\fBreplace\fR
+reads the standard input and writes to the standard output.
+.PP
+\fBreplace\fR
+uses a finite state machine to match longer strings first. It can be used to swap strings. For example, the following command swaps
+a
+and
+b
+in the given files,
+\fIfile1\fR
+and
+\fIfile2\fR:
+.sp
+.RS 3n
+.nf
+shell> \fBreplace a b b a \-\- file1 file2 ...\fR
+.fi
+.RE
+.PP
+The
+\fBreplace\fR
+program is used by
+\fBmsql2mysql\fR. See
+\fBmsql2mysql\fR(1).
+.PP
+\fBreplace\fR
+supports the following options:
+.TP 3n
+\(bu
+\fB\-?\fR,
+\fB\-I\fR
+.sp
+Display a help message and exit.
+.TP 3n
+\(bu
+\fB\-# \fR\fB\fIdebug_options\fR\fR
+.sp
+Write a debugging log. The
+\fIdebug_options\fR
+string often is
+\'d:t:o,\fIfile_name\fR'.
+.TP 3n
+\(bu
+\fB\-s\fR
+.sp
+Silent mode. Print less information what the program does.
+.TP 3n
+\(bu
+\fB\-v\fR
+.sp
+Verbose mode. Print more information about what the program does.
+.TP 3n
+\(bu
+\fB\-V\fR
+.sp
+Display version information and exit.
+.SH "COPYRIGHT"
+.PP
+Copyright 2007 MySQL AB
+.PP
+This documentation is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License.
+.PP
+This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
+.PP
+You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110\-1301 USA or see http://www.gnu.org/licenses/.
+.PP
+Please email
+<docs at mysql.com>
+for more information or if you are interested in doing a translation.
+.SH "SEE ALSO"
+For more information, please refer to the MySQL Reference Manual,
+which may already be installed locally and which is also available
+online at http://dev.mysql.com/doc/.
+.SH AUTHOR
+MySQL AB (http://www.mysql.com/).
Added: branches/sid-5.0/debian/manpages/resolve_stack_dump.1
===================================================================
--- branches/sid-5.0/debian/manpages/resolve_stack_dump.1 (rev 0)
+++ branches/sid-5.0/debian/manpages/resolve_stack_dump.1 2007-11-26 12:34:29 UTC (rev 1020)
@@ -0,0 +1,82 @@
+.\" Title: \fBresolve_stack_dump\fR
+.\" Author:
+.\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
+.\" Date: 11/25/2007
+.\" Manual: MySQL Database System
+.\" Source: MySQL 5.0
+.\"
+.TH "\fBRESOLVE_STACK_DUM" "1" "11/25/2007" "MySQL 5.0" "MySQL Database System"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
+.SH "NAME"
+resolve_stack_dump \- resolve numeric stack trace dump to symbols
+.SH "SYNOPSIS"
+.HP 62
+\fBresolve_stack_dump [\fR\fB\fIoptions\fR\fR\fB] \fR\fB\fIsymbols_file\fR\fR\fB [\fR\fB\fInumeric_dump_file\fR\fR\fB]\fR
+.SH "DESCRIPTION"
+.PP
+\fBresolve_stack_dump\fR
+resolves a numeric stack dump to symbols.
+.PP
+Invoke
+\fBresolve_stack_dump\fR
+like this:
+.sp
+.RS 3n
+.nf
+shell> \fBresolve_stack_dump [\fR\fB\fIoptions\fR\fR\fB] \fR\fB\fIsymbols_file\fR\fR\fB [\fR\fB\fInumeric_dump_file\fR\fR\fB]\fR
+.fi
+.RE
+.PP
+The symbols file should include the output from the
+\fBnm \-\-numeric\-sort mysqld\fR
+command. The numeric dump file should contain a numeric stack track from
+\fBmysqld\fR. If no numeric dump file is named on the command line, the stack trace is read from the standard input.
+.PP
+\fBresolve_stack_dump\fR
+understands the options described in the following list.
+.TP 3n
+\(bu
+\fB\-\-help\fR,
+\fB\-h\fR
+.sp
+Display a help message and exit.
+.TP 3n
+\(bu
+\fB\-\-numeric\-dump\-file=\fR\fB\fIfile_name\fR\fR,
+\fB\-n \fR\fB\fIfile_name\fR\fR
+.sp
+Read the stack trace from the given file.
+.TP 3n
+\(bu
+\fB\-\-symbols\-file=\fR\fB\fIfile_name\fR\fR,
+\fB\-s \fR\fB\fIfile_name\fR\fR
+.sp
+Use the given symbols file.
+.TP 3n
+\(bu
+\fB\-\-version\fR,
+\fB\-V\fR
+.sp
+Display version information and exit.
+.SH "COPYRIGHT"
+.PP
+Copyright 2007 MySQL AB
+.PP
+This documentation is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License.
+.PP
+This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
+.PP
+You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110\-1301 USA or see http://www.gnu.org/licenses/.
+.PP
+Please email
+<docs at mysql.com>
+for more information or if you are interested in doing a translation.
+.SH "SEE ALSO"
+For more information, please refer to the MySQL Reference Manual,
+which may already be installed locally and which is also available
+online at http://dev.mysql.com/doc/.
+.SH AUTHOR
+MySQL AB (http://www.mysql.com/).
Added: branches/sid-5.0/debian/manpages/resolveip.1
===================================================================
--- branches/sid-5.0/debian/manpages/resolveip.1 (rev 0)
+++ branches/sid-5.0/debian/manpages/resolveip.1 2007-11-26 12:34:29 UTC (rev 1020)
@@ -0,0 +1,74 @@
+.\" Title: \fBresolveip\fR
+.\" Author:
+.\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
+.\" Date: 11/25/2007
+.\" Manual: MySQL Database System
+.\" Source: MySQL 5.0
+.\"
+.TH "\fBRESOLVEIP\fR" "1" "11/25/2007" "MySQL 5.0" "MySQL Database System"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
+.SH "NAME"
+resolveip \- resolve hostname to IP address or vice versa
+.SH "SYNOPSIS"
+.HP 44
+\fBresolveip [\fR\fB\fIoptions\fR\fR\fB] {\fR\fB\fIhost_name\fR\fR\fB|\fR\fB\fIip\-addr\fR\fR\fB} ...\fR
+.SH "DESCRIPTION"
+.PP
+The
+\fBresolveip\fR
+utility resolves hostnames to IP addresses and vice versa.
+.PP
+Invoke
+\fBresolveip\fR
+like this:
+.sp
+.RS 3n
+.nf
+shell> \fBresolveip [\fR\fB\fIoptions\fR\fR\fB] {\fR\fB\fIhost_name\fR\fR\fB|\fR\fB\fIip\-addr\fR\fR\fB} ...\fR
+.fi
+.RE
+.PP
+\fBresolveip\fR
+understands the options described in the following list.
+.TP 3n
+\(bu
+\fB\-\-help\fR,
+\fB\-info\fR,
+\fB\-?\fR,
+\fB\-I\fR
+.sp
+Display a help message and exit.
+.TP 3n
+\(bu
+\fB\-\-silent\fR,
+\fB\-s\fR
+.sp
+Silent mode. Produce less output.
+.TP 3n
+\(bu
+\fB\-\-version\fR,
+\fB\-V\fR
+.sp
+Display version information and exit.
+.SH "COPYRIGHT"
+.PP
+Copyright 2007 MySQL AB
+.PP
+This documentation is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License.
+.PP
+This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
+.PP
+You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110\-1301 USA or see http://www.gnu.org/licenses/.
+.PP
+Please email
+<docs at mysql.com>
+for more information or if you are interested in doing a translation.
+.SH "SEE ALSO"
+For more information, please refer to the MySQL Reference Manual,
+which may already be installed locally and which is also available
+online at http://dev.mysql.com/doc/.
+.SH AUTHOR
+MySQL AB (http://www.mysql.com/).
Added: branches/sid-5.0/debian/manpages/safe_mysqld.1
===================================================================
--- branches/sid-5.0/debian/manpages/safe_mysqld.1 (rev 0)
+++ branches/sid-5.0/debian/manpages/safe_mysqld.1 2007-11-26 12:34:29 UTC (rev 1020)
@@ -0,0 +1 @@
+.so man1/mysqld_safe.1
More information about the Pkg-mysql-commits
mailing list