This is manual.info, produced by makeinfo version 4.8 from manual.texi. START-INFO-DIR-ENTRY * mysql: (mysql). MySQL documentation. END-INFO-DIR-ENTRY  File: manual.info, Node: Top, Next: introduction, Prev: (dir), Up: (dir) This is the Reference Manual for the MySQL Database System, version 5.0, through release 5.0.46. It is not intended for use with older versions of the MySQL software due to the many functional and other differences between MySQL 5.0 and previous versions. If you are using a version 4.1 release of the MySQL software, please refer to the `MySQL 3.23, 4.0, 4.1 Reference Manual' (http://dev.mysql.com/doc/refman/4.1/en/), which covers the 3.23, 4.0, and 4.1 series of MySQL software releases. Differences between minor versions of MySQL 5.0 are noted in the present text with reference to release numbers (5.0.X). * Menu: * introduction:: General Information * installing:: Installing and Upgrading MySQL * tutorial:: Tutorial * using-mysql-programs:: Using MySQL Programs * database-administration:: Database Administration * replication:: Replication * optimization:: Optimization * client-utility-programs:: Client and Utility Programs * language-structure:: Language Structure * charset:: Character Set Support * data-types:: Data Types * functions:: Functions and Operators * sql-syntax:: SQL Statement Syntax * storage-engines:: Storage Engines * mysql-cluster:: MySQL Cluster * spatial-extensions:: Spatial Extensions * stored-procedures:: Stored Procedures and Functions * triggers:: Triggers * views:: Views * information-schema:: The `INFORMATION_SCHEMA' Database * precision-math:: Precision Math * apis:: APIs and Libraries * connectors:: Connectors * extending-mysql:: Extending MySQL * faqs:: MySQL 5.0 Frequently Asked Questions * error-handling:: Errors, Error Codes, and Common Problems * releasenotes-es:: MySQL Enterprise Release Notes * releasenotes-cs:: MySQL Community Server Enhancements and Release Notes * news:: MySQL Change History * restrictions:: Limits and Restrictions * credits:: Credits  File: manual.info, Node: introduction, Next: installing, Prev: Top, Up: Top 1 General Information ********************* * Menu: * manual-info:: About This Manual * manual-conventions:: Conventions Used in This Manual * what-is-mysql-ab:: Overview of MySQL AB * what-is:: Overview of the MySQL Database Management System * maxdb:: Overview of the MaxDB Database Management System * roadmap:: MySQL Development Roadmap * information-sources:: MySQL Information Sources * bug-reports:: How to Report Bugs or Problems * compatibility:: MySQL Standards Compliance The MySQL(R) software delivers a very fast, multi-threaded, multi-user, and robust SQL (Structured Query Language) database server. MySQL Server is intended for mission-critical, heavy-load production systems as well as for embedding into mass-deployed software. MySQL is a registered trademark of MySQL AB. The MySQL software is Dual Licensed. Users can choose to use the MySQL software as an Open Source product under the terms of the GNU General Public License (`http://www.fsf.org/licenses/') or can purchase a standard commercial license from MySQL AB. See `http://www.mysql.com/company/legal/licensing/' for more information on our licensing policies. The following list describes some sections of particular interest in this manual: * For a discussion about the capabilities of the MySQL Database Server, see *Note features::. * For future plans, see *Note roadmap::. * For installation instructions, see *Note installing::. For information about upgrading MySQL, see *Note upgrade::. * For a tutorial introduction to the MySQL Database Server, see *Note tutorial::. * For information about configuring and administering MySQL Server, see *Note database-administration::. * For information about setting up replication servers, see *Note replication::. * For answers to a number of questions that are often asked concerning the MySQL Database Server and its capabilities, see *Note faqs::. * For a list of currently known bugs and misfeatures, see *Note bugs::. * For a list of all the contributors to this project, see *Note credits::. * For a history of new features and bugfixes, see *Note news::. * For tips on porting the MySQL Database Software to new architectures or operating systems, see MySQL Internals: Porting (http://forge.mysql.com/wiki/MySQL_Internals_Porting). * For benchmarking information, see the `sql-bench' benchmarking directory in your MySQL distribution. *Important*: To report errors (often called `bugs'), please use the instructions at *Note bug-reports::. If you have found a sensitive security bug in MySQL Server, please let us know immediately by sending an email message to .  File: manual.info, Node: manual-info, Next: manual-conventions, Prev: introduction, Up: introduction 1.1 About This Manual ===================== This is the Reference Manual for the MySQL Database System, version 5.0, through release 5.0.46. It is not intended for use with older versions of the MySQL software due to the many functional and other differences between MySQL 5.0 and previous versions. If you are using a version 4.1 release of the MySQL software, please refer to the `MySQL 3.23, 4.0, 4.1 Reference Manual' (http://dev.mysql.com/doc/refman/4.1/en/), which covers the 3.23, 4.0, and 4.1 series of MySQL software releases. Differences between minor versions of MySQL 5.0 are noted in the present text with reference to release numbers (5.0.X). Because this manual serves as a reference, it does not provide general instruction on SQL or relational database concepts. It also does not teach you how to use your operating system or command-line interpreter. The MySQL Database Software is under constant development, and the Reference Manual is updated frequently as well. The most recent version of the manual is available online in searchable form at `http://dev.mysql.com/doc/'. Other formats also are available there, including HTML, PDF, and Windows CHM versions. The Reference Manual source files are written in DocBook XML format. The HTML version and other formats are produced automatically, primarily using the DocBook XSL stylesheets. For information about DocBook, see `http://docbook.org/' The DocBook XML sources of this manual are available from `http://dev.mysql.com/tech-resources/sources.html'. You can check out a copy of the documentation repository with this command: svn checkout http://svn.mysql.com/svnpublic/mysqldoc/ If you have questions about using MySQL, you can ask them using our mailing lists or forums. See *Note mailing-lists::, and *Note forums::. If you have suggestions concerning additions or corrections to the manual itself, please send them to the documentation team at . This manual was originally written by David Axmark and Michael `Monty' Widenius. It is maintained by the MySQL Documentation Team, consisting of Paul DuBois, Stefan Hinz, Jon Stephens, Martin MC Brown, and Peter Lavin. For the many other contributors, see *Note credits::. The copyright to this manual is owned by the Swedish company MySQL AB. MySQL(R) and the MySQL logo are registered trademarks of MySQL AB. Other trademarks and registered trademarks referred to in this manual are the property of their respective owners, and are used for identification purposes only.  File: manual.info, Node: manual-conventions, Next: what-is-mysql-ab, Prev: manual-info, Up: introduction 1.2 Conventions Used in This Manual =================================== This manual uses certain typographical conventions: * `Text in this style' is used for SQL statements; database, table, and column names; program listings and source code; and environment variables. Example: `To reload the grant tables, use the `FLUSH PRIVILEGES' statement.' * Text in this style indicates input that you type in examples. * `Text in this style' indicates the names of executable programs and scripts, examples being `mysql' (the MySQL command line client program) and `mysqld' (the MySQL server executable). * TEXT IN THIS STYLE is used for variable input for which you should substitute a value of your own choosing. * Filenames and directory names are written like this: `The global `my.cnf' file is located in the `/etc' directory.' * Character sequences are written like this: `To specify a wildcard, use the ``%'' character.' * _Text in this style_ is used for emphasis. * *Text in this style* is used in table headings and to convey especially strong emphasis. When commands are shown that are meant to be executed from within a particular program, the prompt shown preceding the command indicates which command to use. For example, `shell>' indicates a command that you execute from your login shell, and `mysql>' indicates a statement that you execute from the `mysql' client program: shell> type a shell command here mysql> type a mysql statement here The `shell' is your command interpreter. On Unix, this is typically a program such as `sh', `csh', or `bash'. On Windows, the equivalent program is `command.com' or `cmd.exe', typically run in a console window. When you enter a command or statement shown in an example, do not type the prompt shown in the example. Database, table, and column names must often be substituted into statements. To indicate that such substitution is necessary, this manual uses DB_NAME, TBL_NAME, and COL_NAME. For example, you might see a statement like this: mysql> SELECT COL_NAME FROM DB_NAME.TBL_NAME; This means that if you were to enter a similar statement, you would supply your own database, table, and column names, perhaps like this: mysql> SELECT author_name FROM biblio_db.author_list; SQL keywords are not case sensitive and may be written in any lettercase. This manual uses uppercase. In syntax descriptions, square brackets (``['' and ``]'') indicate optional words or clauses. For example, in the following statement, `IF EXISTS' is optional: DROP TABLE [IF EXISTS] TBL_NAME When a syntax element consists of a number of alternatives, the alternatives are separated by vertical bars (``|''). When one member from a set of choices _may_ be chosen, the alternatives are listed within square brackets (``['' and ``]''): TRIM([[BOTH | LEADING | TRAILING] [REMSTR] FROM] STR) When one member from a set of choices _must_ be chosen, the alternatives are listed within braces (``{'' and ``}''): {DESCRIBE | DESC} TBL_NAME [COL_NAME | WILD] An ellipsis (`...') indicates the omission of a section of a statement, typically to provide a shorter version of more complex syntax. For example, `INSERT ... SELECT' is shorthand for the form of `INSERT' statement that is followed by a `SELECT' statement. An ellipsis can also indicate that the preceding syntax element of a statement may be repeated. In the following example, multiple RESET_OPTION values may be given, with each of those after the first preceded by commas: RESET RESET_OPTION [,RESET_OPTION] ... Commands for setting shell variables are shown using Bourne shell syntax. For example, the sequence to set the `CC' environment variable and run the `configure' command looks like this in Bourne shell syntax: shell> CC=gcc ./configure If you are using `csh' or `tcsh', you must issue commands somewhat differently: shell> setenv CC gcc shell> ./configure  File: manual.info, Node: what-is-mysql-ab, Next: what-is, Prev: manual-conventions, Up: introduction 1.3 Overview of MySQL AB ======================== MySQL AB is the company of the MySQL founders and main developers. MySQL AB was originally established in Sweden by David Axmark, Allan Larsson, and Michael `Monty' Widenius. We are dedicated to developing the MySQL database software and promoting it to new users. MySQL AB owns the copyright to the MySQL source code, the MySQL logo and (registered) trademark, and this manual. See *Note what-is::. The MySQL core values show our dedication to MySQL and Open Source. These core values direct how MySQL AB works with the MySQL server software: * To be the best and the most widely used database in the world * To be available and affordable by all * To be easy to use * To be continuously improved while remaining fast and safe * To be fun to use and improve * To be free from bugs These are the core values of the company MySQL AB and its employees: * We subscribe to the Open Source philosophy and support the Open Source community * We aim to be good citizens * We prefer partners that share our values and mindset * We answer email and provide support * We are a virtual company, networking with others * We work against software patents The MySQL Web site (`http://www.mysql.com/') provides the latest information about MySQL and MySQL AB. By the way, the `AB' part of the company name is the acronym for the Swedish `aktiebolag,' or `stock company.' It translates to `MySQL, Inc.' In fact, MySQL, Inc. and MySQL GmbH are examples of MySQL AB subsidiaries. They are located in the United States and Germany, respectively.  File: manual.info, Node: what-is, Next: maxdb, Prev: what-is-mysql-ab, Up: introduction 1.4 Overview of the MySQL Database Management System ==================================================== * Menu: * what-is-mysql:: What is MySQL? * history:: History of MySQL * features:: The Main Features of MySQL  File: manual.info, Node: what-is-mysql, Next: history, Prev: what-is, Up: what-is 1.4.1 What is MySQL? -------------------- MySQL, the most popular Open Source SQL database management system, is developed, distributed, and supported by MySQL AB. MySQL AB is a commercial company, founded by the MySQL developers. It is a second generation Open Source company that unites Open Source values and methodology with a successful business model. The MySQL Web site (`http://www.mysql.com/') provides the latest information about MySQL software and MySQL AB. * MySQL is a database management system. A database is a structured collection of data. It may be anything from a simple shopping list to a picture gallery or the vast amounts of information in a corporate network. To add, access, and process data stored in a computer database, you need a database management system such as MySQL Server. Since computers are very good at handling large amounts of data, database management systems play a central role in computing, as standalone utilities, or as parts of other applications. * MySQL is a relational database management system. A relational database stores data in separate tables rather than putting all the data in one big storeroom. This adds speed and flexibility. The SQL part of `MySQL' stands for `Structured Query Language.' SQL is the most common standardized language used to access databases and is defined by the ANSI/ISO SQL Standard. The SQL standard has been evolving since 1986 and several versions exist. In this manual, `SQL-92' refers to the standard released in 1992, `SQL:1999' refers to the standard released in 1999, and `SQL:2003' refers to the current version of the standard. We use the phrase `the SQL standard' to mean the current version of the SQL Standard at any time. * MySQL software is Open Source. Open Source means that it is possible for anyone to use and modify the software. Anybody can download the MySQL software from the Internet and use it without paying anything. If you wish, you may study the source code and change it to suit your needs. The MySQL software uses the GPL (GNU General Public License), `http://www.fsf.org/licenses/', to define what you may and may not do with the software in different situations. If you feel uncomfortable with the GPL or need to embed MySQL code into a commercial application, you can buy a commercially licensed version from us. See the MySQL Licensing Overview for more information (`http://www.mysql.com/company/legal/licensing/'). * The MySQL Database Server is very fast, reliable, and easy to use. If that is what you are looking for, you should give it a try. MySQL Server also has a practical set of features developed in close cooperation with our users. You can find a performance comparison of MySQL Server with other database managers on our benchmark page. See *Note mysql-benchmarks::. MySQL Server was originally developed to handle large databases much faster than existing solutions and has been successfully used in highly demanding production environments for several years. Although under constant development, MySQL Server today offers a rich and useful set of functions. Its connectivity, speed, and security make MySQL Server highly suited for accessing databases on the Internet. * MySQL Server works in client/server or embedded systems. The MySQL Database Software is a client/server system that consists of a multi-threaded SQL server that supports different backends, several different client programs and libraries, administrative tools, and a wide range of application programming interfaces (APIs). We also provide MySQL Server as an embedded multi-threaded library that you can link into your application to get a smaller, faster, easier-to-manage standalone product. * A large amount of contributed MySQL software is available. It is very likely that your favorite application or language supports the MySQL Database Server. The official way to pronounce `MySQL' is `My Ess Que Ell' (not `my sequel'), but we don't mind if you pronounce it as `my sequel' or in some other localized way.  File: manual.info, Node: history, Next: features, Prev: what-is-mysql, Up: what-is 1.4.2 History of MySQL ---------------------- We started out with the intention of using the `mSQL' database system to connect to our tables using our own fast low-level (ISAM) routines. However, after some testing, we came to the conclusion that `mSQL' was not fast enough or flexible enough for our needs. This resulted in a new SQL interface to our database but with almost the same API interface as `mSQL'. This API was designed to allow third-party code that was written for use with `mSQL' to be ported easily for use with MySQL. The derivation of the name MySQL is not clear. Our base directory and a large number of our libraries and tools have had the prefix `my' for well over 10 years. However, co-founder Monty Widenius's daughter is also named My. Which of the two gave its name to MySQL is still a mystery, even for us. The name of the MySQL Dolphin (our logo) is `Sakila,' which was chosen by the founders of MySQL AB from a huge list of names suggested by users in our `Name the Dolphin' contest. The winning name was submitted by Ambrose Twebaze, an Open Source software developer from Swaziland, Africa. According to Ambrose, the feminine name Sakila has its roots in SiSwati, the local language of Swaziland. Sakila is also the name of a town in Arusha, Tanzania, near Ambrose's country of origin, Uganda.  File: manual.info, Node: features, Prev: history, Up: what-is 1.4.3 The Main Features of MySQL -------------------------------- This section describes some of the important characteristics of the MySQL Database Software. See also *Note roadmap::, for more information about current and upcoming features. In most respects, it applies to all versions of MySQL. For information about features as they are introduced into MySQL on a series-specific basis, see `In a Nutshell' section of the appropriate Manual: * MySQL 4.0 and 4.1: MySQL 4.0 in a Nutshell (http://dev.mysql.com/doc/refman/4.1/en/mysql-4-0-nutshell.html), and MySQL 4.1 in a Nutshell (http://dev.mysql.com/doc/refman/4.1/en/mysql-4-1-nutshell.html) * MySQL 5.0: *Note mysql-5-0-nutshell:: * MySQL 5.1: What's New in MySQL 5.1 (http://dev.mysql.com/doc/refman/5.1/en/mysql-5-1-nutshell.html) Internals and Portability: * Written in C and C++. * Tested with a broad range of different compilers. * Works on many different platforms. See *Note which-os::. * Uses GNU Automake, Autoconf, and Libtool for portability. * The MySQL Server design is multi-layered with independent modules. * Fully multi-threaded using kernel threads. It can easily use multiple CPUs if they are available. * Provides transactional and non-transactional storage engines. * Uses very fast B-tree disk tables (`MyISAM') with index compression. * Relatively easy to add other storage engines. This is useful if you want to provide an SQL interface for an in-house database. * A very fast thread-based memory allocation system. * Very fast joins using an optimized one-sweep multi-join. * In-memory hash tables, which are used as temporary tables. * SQL functions are implemented using a highly optimized class library and should be as fast as possible. Usually there is no memory allocation at all after query initialization. * The MySQL code is tested with Purify (a commercial memory leakage detector) as well as with Valgrind, a GPL tool (`http://developer.kde.org/~sewardj/'). * The server is available as a separate program for use in a client/server networked environment. It is also available as a library that can be embedded (linked) into standalone applications. Such applications can be used in isolation or in environments where no network is available. Data Types: * Many data types: signed/unsigned integers 1, 2, 3, 4, and 8 bytes long, `FLOAT', `DOUBLE', `CHAR', `VARCHAR', `TEXT', `BLOB', `DATE', `TIME', `DATETIME', `TIMESTAMP', `YEAR', `SET', `ENUM', and OpenGIS spatial types. See *Note data-types::. * Fixed-length and variable-length records. Statements and Functions: * Full operator and function support in the `SELECT' list and `WHERE' clause of queries. For example: mysql> SELECT CONCAT(first_name, ' ', last_name) -> FROM citizen -> WHERE income/dependents > 10000 AND age > 30; * Full support for SQL `GROUP BY' and `ORDER BY' clauses. Support for group functions (`COUNT()', `COUNT(DISTINCT ...)', `AVG()', `STD()', `SUM()', `MAX()', `MIN()', and `GROUP_CONCAT()'). * Support for `LEFT OUTER JOIN' and `RIGHT OUTER JOIN' with both standard SQL and ODBC syntax. * Support for aliases on tables and columns as required by standard SQL. * `DELETE', `INSERT', `REPLACE', and `UPDATE' return the number of rows that were changed (affected). It is possible to return the number of rows matched instead by setting a flag when connecting to the server. * The MySQL-specific `SHOW' statement can be used to retrieve information about databases, storage engines, tables, and indexes. MySQL 5.0 adds support for the `INFORMATION_SCHEMA' database, implemented according to standard SQL. * The `EXPLAIN' statement can be used to determine how the optimizer resolves a query. * Function names do not clash with table or column names. For example, `ABS' is a valid column name. The only restriction is that for a function call, no spaces are allowed between the function name and the ``('' that follows it. See *Note reserved-words::. * You can refer to tables from different databases in the same statement. Security: * A privilege and password system that is very flexible and secure, and that allows host-based verification. * Passwords are secure because all password traffic is encrypted when you connect to a server. Scalability and Limits: * Handles large databases. We use MySQL Server with databases that contain 50 million records. We also know of users who use MySQL Server with 60,000 tables and about 5,000,000,000 rows. * Up to 64 indexes per table are allowed (32 before MySQL 4.1.2). Each index may consist of 1 to 16 columns or parts of columns. The maximum index width is 1000 bytes (767 for `InnoDB'); before MySQL 4.1.2, the limit is 500 bytes. An index may use a prefix of a column for `CHAR', `VARCHAR', `BLOB', or `TEXT' column types. Connectivity: * Clients can connect to MySQL Server using several protocols: * Clients can connect using TCP/IP sockets on any platform. * On Windows systems in the NT family (NT, 2000, XP, 2003, or Vista), clients can connect using named pipes if the server is started with the `--enable-named-pipe' option. In MySQL 4.1 and higher, Windows servers also support shared-memory connections if started with the `--shared-memory' option. Clients can connect through shared memory by using the `--protocol=memory' option. * On Unix systems, clients can connect using Unix domain socket files. * MySQL client programs can be written in many languages. A client library written in C is available for clients written in C or C++, or for any language that provides C bindings. * APIs for C, C++, Eiffel, Java, Perl, PHP, Python, Ruby, and Tcl are available, allowing MySQL clients to be written in many languages. See *Note apis::. * The Connector/ODBC (MyODBC) interface provides MySQL support for client programs that use ODBC (Open Database Connectivity) connections. For example, you can use MS Access to connect to your MySQL server. Clients can be run on Windows or Unix. MyODBC source is available. All ODBC 2.5 functions are supported, as are many others. See *Note connectors::. * The Connector/J interface provides MySQL support for Java client programs that use JDBC connections. Clients can be run on Windows or Unix. Connector/J source is available. See *Note connectors::. * MySQL Connector/NET enables developers to easily create .NET applications that require secure, high-performance data connectivity with MySQL. It implements the required ADO.NET interfaces and integrates into ADO.NET aware tools. Developers can build applications using their choice of .NET languages. MySQL Connector/NET is a fully managed ADO.NET driver written in 100% pure C#. See *Note connectors::. Localization: * The server can provide error messages to clients in many languages. See *Note languages::. * Full support for several different character sets, including `latin1' (cp1252), `german', `big5', `ujis', and more. For example, the Scandinavian characters ``aa'', ``a"'' and ``o"'' are allowed in table and column names. Unicode support is available as of MySQL 4.1. * All data is saved in the chosen character set. * Sorting and comparisons are done according to the chosen character set and collation (using `latin1' and Swedish collation by default). It is possible to change this when the MySQL server is started. To see an example of very advanced sorting, look at the Czech sorting code. MySQL Server supports many different character sets that can be specified at compile time and runtime. * As of MySQL 4.1, the server time zone can be changed dynamically, and individual clients can specify their own time zone. *Note time-zone-support::. MySQL Enterprise For assistance in getting optimal performance from your MySQL server subscribe to MySQL Enterprise. For more information see `http://www.mysql.com/products/enterprise/'. Clients and Tools: * MySQL AB provides several client and utility programs. These include both command-line programs such as `mysqldump' and `mysqladmin', and graphical programs such as MySQL Administrator and MySQL Query Browser. * MySQL Server has built-in support for SQL statements to check, optimize, and repair tables. These statements are available from the command line through the `mysqlcheck' client. MySQL also includes `myisamchk', a very fast command-line utility for performing these operations on `MyISAM' tables. See *Note client-utility-programs::. * MySQL programs can be invoked with the `--help' or `-?' option to obtain online assistance.  File: manual.info, Node: maxdb, Next: roadmap, Prev: what-is, Up: introduction 1.5 Overview of the MaxDB Database Management System ==================================================== * Menu: * maxdb-overview:: What is MaxDB? * maxdb-history:: History of MaxDB * maxdb-features:: Features of MaxDB * maxdb-licensing:: Licensing and Support * maxdb-mysql-differences:: Feature Differences Between MaxDB and MySQL * maxdb-mysql-interoperability:: Interoperability Features Between MaxDB and MySQL * maxdb-links:: MaxDB-Related Links MaxDB is a heavy-duty enterprise database. The database management system is SAP-certified. MaxDB is the new name of a database management system formerly called SAP DB. In 2003 SAP AG and MySQL AB joined a partnership and re-branded the database system to MaxDB. The development of MaxDB has continued since then as it was done before--through the SAP developer team. MySQL AB cooperates closely with the MaxDB team at SAP around delivering improvements to the MaxDB product. Joint efforts include development of new native drivers to enable more efficient usage of MaxDB in the Open Source community, and improvement of documentation to expand the MaxDB user base. Interoperability features between MySQL and MaxDB database also are seen as important. For example, the new MaxDB Synchronization Manager supports data synchronization from MaxDB to MySQL. The MaxDB database management system does not share a common code-base with the MySQL database management system. The MaxDB and MySQL database management systems are independent products provided by MySQL AB. MySQL AB offers a complete portfolio of Professional Services for MaxDB.  File: manual.info, Node: maxdb-overview, Next: maxdb-history, Prev: maxdb, Up: maxdb 1.5.1 What is MaxDB? -------------------- MaxDB is an ANSI SQL-92 (entry level) compliant relational database management system (RDBMS) from SAP AG, that is delivered by MySQL AB as well. MaxDB fulfills the needs for enterprise usage: safety, scalability, high concurrency, and performance. It runs on all major operating systems. Over the years it has proven able to run SAP R/3 and terabytes of data in 24x7 operation. The database development started in 1977 as a research project at the Technical University of Berlin. In the early 1980s it became a database product that subsequently was owned by Nixdorf, Siemens Nixdorf, Software AG, and today by SAP AG. Along the way, it has been named VDN, Reflex, Supra 2, DDB/4, Entire SQL-DB-Server, and ADABAS D. In 1997, SAP took over the software from Software AG and renamed it to SAP DB. Since October 2000, SAP DB sources additionally were released as Open Source under the GNU General Public License (see GNU General Public License (http://dev.mysql.com/doc/refman/5.0/en/gpl-license.html)). In 2003, SAP AG and MySQL AB formed a partnership and re-branded the database system to MaxDB.  File: manual.info, Node: maxdb-history, Next: maxdb-features, Prev: maxdb-overview, Up: maxdb 1.5.2 History of MaxDB ---------------------- The history of MaxDB goes back to SAP DB, SAP AG's DBMS. That is, MaxDB is a re-branded and enhanced version of SAP DB. For many years, MaxDB has been used for small, medium, and large installations of the mySAP Business Suite and other demanding SQL applications requiring an enterprise-class DBMS with regard to the number of users, the transactional workload, and the size of the database. SAP DB was meant to provide an alternative to third-party database systems such as Oracle, Microsoft SQL Server, and DB2 by IBM. In October 2000, SAP AG released SAP DB under the GNU GPL license (see GNU General Public License (http://dev.mysql.com/doc/refman/5.0/en/gpl-license.html)), thus making it Open Source software. Today, MaxDB is used in about 3,500 SAP customer installations worldwide. Moreover, the majority of all DBMS installations on Unix and Linux within SAP's IT department rely on MaxDB. MaxDB is tuned toward heavy-duty online transaction processing (OLTP) with several thousand users and database sizes ranging from several hundred GB to multiple TB. In 2003, SAP and MySQL concluded a partnership and development cooperation agreement. As a result, SAP's database system SAP DB has been delivered under the name of MaxDB by MySQL since the release of version 7.5 (November 2003). Version 7.5 of MaxDB is a direct advancement of the SAP DB 7.4 code base. Therefore, the MaxDB software version 7.5 can be used as a direct upgrade of previous SAP DB versions starting 7.2.04 and higher. The former SAP DB development team at SAP AG is responsible, now as before, for developing and supporting MaxDB. MySQL AB cooperates closely with the MaxDB team at SAP around delivering improvements to the MaxDB product, see *Note maxdb::. Both SAP AG and MySQL AB handle the sale and distribution of MaxDB. The advancement of MaxDB and the MySQL Server leverages synergies that benefit both product lines. MaxDB is subjected to SAP AG's complete quality assurance process before it is shipped with SAP solutions or provided as a download from the MySQL site.  File: manual.info, Node: maxdb-features, Next: maxdb-licensing, Prev: maxdb-history, Up: maxdb 1.5.3 Features of MaxDB ----------------------- MaxDB is a heavy-duty, SAP-certified Open Source database for OLTP and OLAP usage which offers high reliability, availability, scalability, and a very comprehensive feature set. It is targeted for large mySAP Business Suite environments and other applications that require maximum enterprise-level database functionality and complements the MySQL database server. MaxDB operates as a client/server product. It was developed to meet the needs of installations in OLTP and Data Warehouse/OLAP/Decision Support scenarios and offers these benefits: * *Easy configuration and administration:* GUI-based Installation Manager and Database Manager as single administration tools for DBMS operations * *Around-the-clock operation, no planned downtimes, no permanent attendance required:* Automatic space management, no need for reorganizations * *Sophisticated backup and restore capabilities:* Online and incremental backups, recovery wizard to guide you through the recovery scenario * *Supports large number of users, database sizes in the terabytes, and demanding workloads:* Proven reliability, performance, and scalability * *High availability:* Cluster support, standby configuration, hot standby configuration  File: manual.info, Node: maxdb-licensing, Next: maxdb-mysql-differences, Prev: maxdb-features, Up: maxdb 1.5.4 Licensing and Support --------------------------- MaxDB can be used under the same licenses available for the other products distributed by MySQL AB. Thus, MaxDB is available under the GNU General Public License, and a commercial license. For more information on licensing, see `http://www.mysql.com/company/legal/licensing/'. MySQL AB offers MaxDB technical support to non-SAP customers. MaxDB support is available on various levels (Basic, Silver, and Gold), which expand from unlimited email/web-support to 24x7 phone support for business critical systems. MySQL AB also offers Licenses and Support for MaxDB when used with SAP Applications, like SAP NetWeaver and mySAP Business Suite. For more information on licenses and support for your needs, please contact MySQL AB. (See `http://www.mysql.com/company/contact/'.) Consulting and training services are available. MySQL gives classes on MaxDB at regular intervals. See `http://www.mysql.com/training/' for a list of classes.  File: manual.info, Node: maxdb-mysql-differences, Next: maxdb-mysql-interoperability, Prev: maxdb-licensing, Up: maxdb 1.5.5 Feature Differences Between MaxDB and MySQL ------------------------------------------------- MaxDB is MySQL AB's SAP-certified database. The MaxDB database server complements the MySQL AB product portfolio. Some MaxDB features are not available on the MySQL database management server and vice versa. The following list summarizes the main differences between MaxDB and MySQL; it is not complete. * MaxDB runs as a client/server system. MySQL can run as a client/server system or as an embedded system. * MaxDB might not run on all platforms supported by MySQL. * MaxDB uses a proprietary network protocol for client/server communication. MySQL uses either TCP/IP (with or without SSL encryption), sockets (under Unix-like systems), or named pipes or shared memory (under Windows NT-family systems). * MaxDB supports stored procedures and functions. MySQL 5.0 and up also supports stored procedures and functions. MaxDB supports programming of triggers through an SQL extension. MySQL 5.0 supports triggers. MaxDB contains a debugger for stored procedure languages, can cascade nested triggers, and supports multiple triggers per action and row. * MaxDB is distributed with user interfaces that are text-based, graphical, or Web-based. MySQL is distributed with text-based user interfaces only; graphical user interfaces such as MySQL Query Browser or MySQL Administrator are shipped separately from the main distributions. Web-based user interfaces for MySQL are offered by third parties. * MaxDB supports a number of programming interfaces that also are supported by MySQL. For developing with MaxDB, the MaxDB ODBC Driver, SQL Database Connectivity (SQLDBC), JDBC Driver, Perl and Python modules and a MaxDB PHP extension, which provides access to MySQL MaxDB databases using PHP, are available. Third Party Programming Interfaces: Support for OLE DB, ADO, DAO, RDO and .NET through ODBC. MaxDB supports embedded SQL with C/C++. * MaxDB includes administrative features that MySQL does not have: job scheduling by time (included in MySQL as of 5.1), event, and alert, and sending messages to a database administrator on alert thresholds. (MySQL has scheduling support starting with version 5.1.6.)  File: manual.info, Node: maxdb-mysql-interoperability, Next: maxdb-links, Prev: maxdb-mysql-differences, Up: maxdb 1.5.6 Interoperability Features Between MaxDB and MySQL ------------------------------------------------------- MaxDB and MySQL are independent database management servers. The interoperation of the systems is possible in a way that the systems can exchange their data. To exchange data between MaxDB and MySQL, you can use the import and export tools of the systems or the MaxDB Synchronization Manager. The import and export tools can be used to transfer data in an infrequent, manual fashion. The MaxDB Synchronization Manager offers faster, automatic data transfer capabilities. The MaxDB Loader can be used to export data and object definitions. The Loader can export data using MaxDB internal, binary formats and text formats (CSV). Data exported from MaxDB in text formats can be imported into MySQL using the `mysqlimport' client program. To export MySQL data, you can use either `mysqldump' to create `INSERT' statements or `SELECT ... INTO OUTFILE' to create a text file (CSV). Use the MaxDB Loader to import the data files generated by MySQL. Object definitions can be exchanged between the systems using MaxDB Loader and the MySQL tool `mysqldump'. As the SQL dialects of both systems differ slightly and MaxDB has features currently not supported by MySQL like SQL constraints, we recommend to hand-tune the definition files. The `mysqldump' tool offers an option `--compatible=maxdb' to produce output that is compatible with MaxDB to make porting easier. The MaxDB Synchronization Manager is available as part of MaxDB 7.6. The Synchronization Manager supports creation of asynchronous replication scenarios between several MaxDB instances. However, interoperability features also are planned, so that the Synchronization Manager supports replication to and from a MySQL server.  File: manual.info, Node: maxdb-links, Prev: maxdb-mysql-interoperability, Up: maxdb 1.5.7 MaxDB-Related Links ------------------------- The main page for MaxDB information is `http://www.mysql.com/products/maxdb', which provides details about the features of the MaxDB database management systems and has pointers to available documentation. The MySQL Reference Manual does not contain any MaxDB documentation other than the introduction given in this section. MaxDB has its own documentation, which is called the MaxDB library and is available at `http://dev.mysql.com/doc/maxdb/index.html'. MySQL AB runs a community mailing list on MaxDB; see `http://lists.mysql.com/maxdb'. The list shows a vivid community discussion. Many of the core developers contribute to it. Product announcements are sent to the list. A Web forum on MaxDB is available at `http://forums.mysql.com/'. The forum focuses on MaxDB questions not related to SAP applications.  File: manual.info, Node: roadmap, Next: information-sources, Prev: maxdb, Up: introduction 1.6 MySQL Development Roadmap ============================= * Menu: * mysql-5-0-nutshell:: What's New in MySQL 5.0 This section describes the general MySQL development roadmap, including major features implemented in or planned for various MySQL releases. The following sections provide information for each release series. The current production release series is MySQL 5.0, which was declared stable for production use as of MySQL 5.0.15, released in October 2005. The previous production release series was MySQL 4.1, which was declared stable for production use as of MySQL 4.1.7, released in October 2004. `Production status' means that future 5.0 and 4.1 development is limited only to bugfixes. For the older MySQL 4.0 and 3.23 series, only critical bugfixes are made. Active MySQL development currently is taking place in the MySQL 5.0 and 5.1 release series, and new features are being added only to the latter. Before upgrading from one release series to the next, please see the notes in *Note upgrade::. The most requested features and the versions in which they were implemented or are scheduled for implementation are summarized in the following table: *Feature* *MySQL Series* Unions 4.0 Subqueries 4.1 R-trees 4.1 (for the `MyISAM' storage engine) Stored procedures 5.0 Views 5.0 Cursors 5.0 XA transactions 5.0 Triggers 5.0 and 5.1 Event scheduler 5.1 Partitioning 5.1 Pluggable storage 5.1 engine API Plugin API 5.1 Row-based replication 5.1 Server log tables 5.1 Foreign keys 5.2 (implemented in 3.23 for `InnoDB')  File: manual.info, Node: mysql-5-0-nutshell, Prev: roadmap, Up: roadmap 1.6.1 What's New in MySQL 5.0 ----------------------------- The following features are implemented in MySQL 5.0. * *`BIT' Data Type*: Can be used to store numbers in binary notation. See *Note numeric-type-overview::. * *Cursors*: Elementary support for server-side cursors. For information about using cursors within stored routines, see *Note cursors::. For information about using cursors from within the C API, see *Note mysql-stmt-attr-set::. * *Information Schema*: The introduction of the `INFORMATION_SCHEMA' database in MySQL 5.0 provided a standards-compliant means for accessing the MySQL Server's metadata; that is, data about the databases (schemas) on the server and the objects which they contain. See *Note information-schema::. * *Instance Manager*: Can be used to start and stop the MySQL Server, even from a remote host. See *Note instance-manager::. * *Precision Math*: MySQL 5.0 introduced stricter criteria for acceptance or rejection of data, and implemented a new library for fixed-point arithmetic. These contributed to a much higher degree of accuracy for mathematical operations and greater control over invalid values. See *Note precision-math::. * *Storage Engines*: Storage engines added in MySQL 5.0 include `ARCHIVE' and `FEDERATED'. See *Note archive-storage-engine::, and *Note federated-storage-engine::. * *Stored Routines*: Support for named stored procedures and stored functions was implemented in MySQL 5.0. See *Note stored-procedures::. * *Strict Mode and Standard Error Handling*: MySQL 5.0 added a strict mode where by it follows standard SQL in a number of ways in which it did not previously. Support for standard SQLSTATE error messages was also implemented. See *Note server-sql-mode::. * *Triggers*: MySQL 5.0 added limited support for triggers. See *Note triggers::, and *Note ansi-diff-triggers::. * *`VARCHAR' Data Type*: The maximum effective length of a `VARCHAR' column was increased to 65,535 bytes, and stripping of trailing whitespace was eliminated. (The actual maximum length of a `VARCHAR' is determined by the maximum row size and the character set you use. The maximum _effective_ column length is subject to a row size of 65,532 bytes.) See *Note string-types::. * *Views*: MySQL 5.0 added support for named, updatable views. See *Note views::, and *Note ansi-diff-views::. * *XA Transactions*: See *Note xa::. MySQL Enterprise For assistance in maximizing your usage of the many new features of MySQL, subscribe to MySQL Enterprise. For more information see `http://www.mysql.com/products/enterprise/advisors.html'. * *Performance enhancements*: A number of improvements were made in MySQL 5.0 to improve the speed of certain types of queries and in the handling of certain types. These include: * MySQL 5.0 introduces a new `greedy' optimizer which can greatly reduce the time required to arrive at a query execution plan. This is particularly noticeable where several tables are to be joined and no good join keys can otherwise be found. Without the greedy optimizer, the complexity of the search for an execution plan is calculated as `N!', where N is the number of tables to be joined. The greedy optimizer reduces this to `N!/(D-1)!', where D is the depth of the search. Although the greedy optimizer does not guarantee the best possible of all execution plans (this is currently being worked on), it can reduce the time spent arriving at an execution plan for a join involving a great many tables -- 30, 40, or more -- by a factor of as much as 1,000. This should eliminate most if not all situations where users thought that the optimizer had hung when trying to perform joins across many tables. * Use of the _Index Merge_ method to obtain better optimization of `AND' and `OR' relations over different keys. (Previously, these were optimized only where both relations in the `WHERE' clause involved the same key.) This also applies to other one-to-one comparison operators (`>', `<', and so on), including `=' and the `IN' operator. This means that MySQL can use multiple indexes in retrieving results for conditions such as `WHERE key1 > 4 OR key2 < 7' and even combinations of conditions such as `WHERE (key1 > 4 OR key2 < 7) AND (key3 >= 10 OR key4 = 1)'. See *Note index-merge-optimization::. * A new equality detector finds and optimizes `hidden' equalities in joins. For example, a `WHERE' clause such as t1.c1=t2.c2 AND t2.c2=t3.c3 AND t1.c1 < 5 implies these other conditions t1.c1=t3.c3 AND t2.c2 < 5 AND t3.c3 < 5 These optimizations can be applied with any combination of `AND' and `OR' operators. See *Note nested-joins::, and *Note outer-join-simplification::. * Optimization of `NOT IN' and `NOT BETWEEN' relations, reducing or eliminating table scans for queries making use of them by mean of range analysis. The performance of MySQL with regard to these relations now matches its performance with regard to `IN' and `BETWEEN'. * The `VARCHAR' data type as implemented in MySQL 5.0 is more efficient than in previous versions, due to the elimination of the old (and nonstandard) removal of trailing spaces during retrieval. * The addition of a true `BIT' column type; this type is much more efficient for storage and retrieval of Boolean values than the workarounds required in MySQL in versions previous to 5.0. * *Performance Improvements in the `InnoDB' Storage Engine*: * New compact storage format which can save up to 20% of the disk space required in previous MySQL/`InnoDB' versions. * Faster recovery from a failed or aborted `ALTER TABLE'. * Faster implementation of `TRUNCATE'. (See *Note innodb::.) * *Performance Improvements in the `NDBCluster' Storage Engine*: * Faster handling of queries that use `IN' and `BETWEEN'. * *Condition pushdown*: In cases involving the comparison of an unindexed column with a constant, this condition is `pushed down' to the cluster where it is evaluated in all partitions simultaneously, eliminating the need to send non-matching records over the network. This can make such queries 10 to 100 times faster than in MySQL 4.1 Cluster. See *Note explain::, for more information. (See *Note mysql-cluster::.) For those wishing to take a look at the bleeding edge of MySQL development, we make our BitKeeper repository for MySQL publicly available. See *Note installing-source-tree::.  File: manual.info, Node: information-sources, Next: bug-reports, Prev: roadmap, Up: introduction 1.7 MySQL Information Sources ============================= * Menu: * mailing-lists:: MySQL Mailing Lists * forums:: MySQL Community Support at the MySQL Forums * irc:: MySQL Community Support on Internet Relay Chat (IRC) * mysql-enterprise-information:: MySQL Enterprise This section lists sources of additional information that you may find helpful, such as the MySQL mailing lists and user forums, and Internet Relay Chat.  File: manual.info, Node: mailing-lists, Next: forums, Prev: information-sources, Up: information-sources 1.7.1 MySQL Mailing Lists ------------------------- * Menu: * mailing-list-use:: Guidelines for Using the Mailing Lists This section introduces the MySQL mailing lists and provides guidelines as to how the lists should be used. When you subscribe to a mailing list, you receive all postings to the list as email messages. You can also send your own questions and answers to the list. To subscribe to or unsubscribe from any of the mailing lists described in this section, visit `http://lists.mysql.com/'. For most of them, you can select the regular version of the list where you get individual messages, or a digest version where you get one large message per day. Please _do not_ send messages about subscribing or unsubscribing to any of the mailing lists, because such messages are distributed automatically to thousands of other users. Your local site may have many subscribers to a MySQL mailing list. If so, the site may have a local mailing list, so that messages sent from `lists.mysql.com' to your site are propagated to the local list. In such cases, please contact your system administrator to be added to or dropped from the local MySQL list. If you wish to have traffic for a mailing list go to a separate mailbox in your mail program, set up a filter based on the message headers. You can use either the `List-ID:' or `Delivered-To:' headers to identify list messages. The MySQL mailing lists are as follows: * `announce' This list is for announcements of new versions of MySQL and related programs. This is a low-volume list to which all MySQL users should subscribe. * `mysql' This is the main list for general MySQL discussion. Please note that some topics are better discussed on the more-specialized lists. If you post to the wrong list, you may not get an answer. * `bugs' This list is for people who want to stay informed about issues reported since the last release of MySQL or who want to be actively involved in the process of bug hunting and fixing. See *Note bug-reports::. * `internals' This list is for people who work on the MySQL code. This is also the forum for discussions on MySQL development and for posting patches. * `mysqldoc' This list is for people who work on the MySQL documentation: people from MySQL AB, translators, and other community members. * `benchmarks' This list is for anyone interested in performance issues. Discussions concentrate on database performance (not limited to MySQL), but also include broader categories such as performance of the kernel, filesystem, disk system, and so on. * `packagers' This list is for discussions on packaging and distributing MySQL. This is the forum used by distribution maintainers to exchange ideas on packaging MySQL and on ensuring that MySQL looks and feels as similar as possible on all supported platforms and operating systems. * `java' This list is for discussions about the MySQL server and Java. It is mostly used to discuss JDBC drivers such as MySQL Connector/J. * `win32' This list is for all topics concerning the MySQL software on Microsoft operating systems, such as Windows 9x, Me, NT, 2000, XP, and 2003. * `myodbc' This list is for all topics concerning connecting to the MySQL server with ODBC. * `gui-tools' This list is for all topics concerning MySQL graphical user interface tools such as `MySQL Administrator' and `MySQL Query Browser'. * `cluster' This list is for discussion of MySQL Cluster. * `dotnet' This list is for discussion of the MySQL server and the .NET platform. It is mostly related to MySQL Connector/Net. * `plusplus' This list is for all topics concerning programming with the C++ API for MySQL. * `perl' This list is for all topics concerning Perl support for MySQL with `DBD::mysql'. If you're unable to get an answer to your questions from a MySQL mailing list or forum, one option is to purchase support from MySQL AB. This puts you in direct contact with MySQL developers. The following table shows some MySQL mailing lists in languages other than English. These lists are not operated by MySQL AB. * `' A French mailing list. * `' A Korean mailing list. To subscribe, email `subscribe mysql your@email.address' to this list. * `' A German mailing list. To subscribe, email `subscribe mysql-de your@email.address' to this list. You can find information about this mailing list at `http://www.4t2.com/mysql/'. * `' A Portuguese mailing list. To subscribe, email `subscribe mysql-br your@email.address' to this list. * `' A Spanish mailing list. To subscribe, email `subscribe mysql your@email.address' to this list.  File: manual.info, Node: mailing-list-use, Prev: mailing-lists, Up: mailing-lists 1.7.1.1 Guidelines for Using the Mailing Lists .............................................. Please don't post mail messages from your browser with HTML mode turned on. Many users don't read mail with a browser. When you answer a question sent to a mailing list, if you consider your answer to have broad interest, you may want to post it to the list instead of replying directly to the individual who asked. Try to make your answer general enough that people other than the original poster may benefit from it. When you post to the list, please make sure that your answer is not a duplication of a previous answer. Try to summarize the essential part of the question in your reply. Don't feel obliged to quote the entire original message. When answers are sent to you individually and not to the mailing list, it is considered good etiquette to summarize the answers and send the summary to the mailing list so that others may have the benefit of responses you received that helped you solve your problem.  File: manual.info, Node: forums, Next: irc, Prev: mailing-lists, Up: information-sources 1.7.2 MySQL Community Support at the MySQL Forums ------------------------------------------------- The forums at `http://forums.mysql.com' are an important community resource. Many forums are available, grouped into these general categories: * Migration * MySQL Usage * MySQL Connectors * Programming Languages * Tools * 3rd-Party Applications * Storage Engines * MySQL Technology * SQL Standards * Business  File: manual.info, Node: irc, Next: mysql-enterprise-information, Prev: forums, Up: information-sources 1.7.3 MySQL Community Support on Internet Relay Chat (IRC) ---------------------------------------------------------- In addition to the various MySQL mailing lists and forums, you can find experienced community people on Internet Relay Chat (IRC). These are the best networks/channels currently known to us: *freenode* (see `http://www.freenode.net/' for servers) * `#mysql' is primarily for MySQL questions, but other database and general SQL questions are welcome. Questions about PHP, Perl, or C in combination with MySQL are also common. If you are looking for IRC client software to connect to an IRC network, take a look at `xChat' (`http://www.xchat.org/'). X-Chat (GPL licensed) is available for Unix as well as for Windows platforms (a free Windows build of X-Chat is available at `http://www.silverex.org/download/').  File: manual.info, Node: mysql-enterprise-information, Prev: irc, Up: information-sources 1.7.4 MySQL Enterprise ---------------------- MySQL AB offers technical support in the form of MySQL Enterprise. For organizations that rely on the MySQL DBMS for business-critical production applications, MySQL Enterprise is a commercial subscription offering which includes: * MySQL Enterprise Server * MySQL Network Monitoring and Advisory Services * Monthly Rapid Updates and Quarterly Service Packs * MySQL Knowledge Base * 24x7 Technical and Consultative Support MySQL Enterprise is available in multiple tiers, giving you the flexibility to choose the level of service that best matches your needs. For more information see MySQL Enterprise (http://www.mysql.com/products/enterprise/).  File: manual.info, Node: bug-reports, Next: compatibility, Prev: information-sources, Up: introduction 1.8 How to Report Bugs or Problems ================================== Before posting a bug report about a problem, please try to verify that it is a bug and that it has not been reported already: * Start by searching the MySQL online manual at `http://dev.mysql.com/doc/'. We try to keep the manual up to date by updating it frequently with solutions to newly found problems. The change history (`http://dev.mysql.com/doc/mysql/en/news.html') can be particularly useful since it is quite possible that a newer version contains a solution to your problem. * If you get a parse error for a SQL statement, please check your syntax closely. If you can't find something wrong with it, it's extremely likely that your current version of MySQL Server doesn't support the syntax you are using. If you are using the current version and the manual doesn't cover the syntax that you are using, MySQL Server doesn't support your statement. In this case, your options are to implement the syntax yourself or email and ask for an offer to implement it. If the manual covers the syntax you are using, but you have an older version of MySQL Server, you should check the MySQL change history to see when the syntax was implemented. In this case, you have the option of upgrading to a newer version of MySQL Server. * For solutions to some common problems, see *Note problems::. * Search the bugs database at `http://bugs.mysql.com/' to see whether the bug has been reported and fixed. * Search the MySQL mailing list archives at `http://lists.mysql.com/'. See *Note mailing-lists::. * You can also use `http://www.mysql.com/search/' to search all the Web pages (including the manual) that are located at the MySQL AB Web site. If you can't find an answer in the manual, the bugs database, or the mailing list archives, check with your local MySQL expert. If you still can't find an answer to your question, please use the following guidelines for reporting the bug. The normal way to report bugs is to visit `http://bugs.mysql.com/', which is the address for our bugs database. This database is public and can be browsed and searched by anyone. If you log in to the system, you can enter new reports. If you have no Web access, you can generate a bug report by using the `mysqlbug' script described at the end of this section. Bugs posted in the bugs database at `http://bugs.mysql.com/' that are corrected for a given release are noted in the change history. If you have found a sensitive security bug in MySQL, you can send email to . To discuss problems with other users, you can use one of the MySQL mailing lists. *Note mailing-lists::. Writing a good bug report takes patience, but doing it right the first time saves time both for us and for yourself. A good bug report, containing a full test case for the bug, makes it very likely that we will fix the bug in the next release. This section helps you write your report correctly so that you don't waste your time doing things that may not help us much or at all. Please read this section carefully and make sure that all the information described here is included in your report. Preferably, you should test the problem using the latest production or development version of MySQL Server before posting. Anyone should be able to repeat the bug by just using `mysql test < script_file' on your test case or by running the shell or Perl script that you include in the bug report. Any bug that we are able to repeat has a high chance of being fixed in the next MySQL release. It is most helpful when a good description of the problem is included in the bug report. That is, give a good example of everything you did that led to the problem and describe, in exact detail, the problem itself. The best reports are those that include a full example showing how to reproduce the bug or problem. See MySQL Internals: Porting (http://forge.mysql.com/wiki/MySQL_Internals_Porting). Remember that it is possible for us to respond to a report containing too much information, but not to one containing too little. People often omit facts because they think they know the cause of a problem and assume that some details don't matter. A good principle to follow is that if you are in doubt about stating something, state it. It is faster and less troublesome to write a couple more lines in your report than to wait longer for the answer if we must ask you to provide information that was missing from the initial report. The most common errors made in bug reports are (a) not including the version number of the MySQL distribution that you use, and (b) not fully describing the platform on which the MySQL server is installed (including the platform type and version number). These are highly relevant pieces of information, and in 99 cases out of 100, the bug report is useless without them. Very often we get questions like, `Why doesn't this work for me?' Then we find that the feature requested wasn't implemented in that MySQL version, or that a bug described in a report has been fixed in newer MySQL versions. Errors often are platform-dependent. In such cases, it is next to impossible for us to fix anything without knowing the operating system and the version number of the platform. If you compiled MySQL from source, remember also to provide information about your compiler if it is related to the problem. Often people find bugs in compilers and think the problem is MySQL-related. Most compilers are under development all the time and become better version by version. To determine whether your problem depends on your compiler, we need to know what compiler you used. Note that every compiling problem should be regarded as a bug and reported accordingly. If a program produces an error message, it is very important to include the message in your report. If we try to search for something from the archives, it is better that the error message reported exactly matches the one that the program produces. (Even the lettercase should be observed.) It is best to copy and paste the entire error message into your report. You should never try to reproduce the message from memory. If you have a problem with Connector/ODBC (MyODBC), please try to generate a trace file and send it with your report. See the MyODBC section of *Note connectors::. If your report includes long query output lines from test cases that you run with the `mysql' command-line tool, you can make the output more readable by using the `--vertical' option or the `\G' statement terminator. The `EXPLAIN SELECT' example later in this section demonstrates the use of `\G'. Please include the following information in your report: * The version number of the MySQL distribution you are using (for example, MySQL 5.0.19). You can find out which version you are running by executing `mysqladmin version'. The `mysqladmin' program can be found in the `bin' directory under your MySQL installation directory. * The manufacturer and model of the machine on which you experience the problem. * The operating system name and version. If you work with Windows, you can usually get the name and version number by double-clicking your My Computer icon and pulling down the `Help/About Windows' menu. For most Unix-like operating systems, you can get this information by executing the command `uname -a'. * Sometimes the amount of memory (real and virtual) is relevant. If in doubt, include these values. * If you are using a source distribution of the MySQL software, include the name and version number of the compiler that you used. If you have a binary distribution, include the distribution name. * If the problem occurs during compilation, include the exact error messages and also a few lines of context around the offending code in the file where the error occurs. * If `mysqld' died, you should also report the statement that crashed `mysqld'. You can usually get this information by running `mysqld' with query logging enabled, and then looking in the log after `mysqld' crashes. See MySQL Internals: Porting (http://forge.mysql.com/wiki/MySQL_Internals_Porting). * If a database table is related to the problem, include the output from the `SHOW CREATE TABLE DB_NAME.TBL_NAME' statement in the bug report. This is a very easy way to get the definition of any table in a database. The information helps us create a situation matching the one that you have experienced. * The SQL mode in effect when the problem occurred can be significant, so please report the value of the `sql_mode' system variable. For stored procedure, stored function, and trigger objects, the relevant `sql_mode' value is the one in effect when the object was created. For a stored procedure or function, the `SHOW CREATE PROCEDURE' or `SHOW CREATE FUNCTION' statement shows the relevant SQL mode, or you can query `INFORMATION_SCHEMA' for the information: SELECT ROUTINE_SCHEMA, ROUTINE_NAME, SQL_MODE FROM INFORMATION_SCHEMA.ROUTINES; For triggers, you can use this statement: SELECT EVENT_OBJECT_SCHEMA, EVENT_OBJECT_TABLE, TRIGGER_NAME, SQL_MODE FROM INFORMATION_SCHEMA.TRIGGERS; * For performance-related bugs or problems with `SELECT' statements, you should always include the output of `EXPLAIN SELECT ...', and at least the number of rows that the `SELECT' statement produces. You should also include the output from `SHOW CREATE TABLE TBL_NAME' for each table that is involved. The more information you provide about your situation, the more likely it is that someone can help you. The following is an example of a very good bug report. The statements are run using the `mysql' command-line tool. Note the use of the `\G' statement terminator for statements that would otherwise provide very long output lines that are difficult to read. mysql> SHOW VARIABLES; mysql> SHOW COLUMNS FROM ...\G mysql> EXPLAIN SELECT ...\G mysql> FLUSH STATUS; mysql> SELECT ...; mysql> SHOW STATUS; * If a bug or problem occurs while running `mysqld', try to provide an input script that reproduces the anomaly. This script should include any necessary source files. The more closely the script can reproduce your situation, the better. If you can make a reproducible test case, you should upload it to be attached to the bug report. If you can't provide a script, you should at least include the output from `mysqladmin variables extended-status processlist' in your report to provide some information on how your system is performing. * If you can't produce a test case with only a few rows, or if the test table is too big to be included in the bug report (more than 10 rows), you should dump your tables using `mysqldump' and create a `README' file that describes your problem. Create a compressed archive of your files using `tar' and `gzip' or `zip', and use FTP to transfer the archive to `ftp://ftp.mysql.com/pub/mysql/upload/'. Then enter the problem into our bugs database at `http://bugs.mysql.com/'. * If you believe that the MySQL server produces a strange result from a statement, include not only the result, but also your opinion of what the result should be, and an explanation describing the basis for your opinion. * When you provide an example of the problem, it's better to use the table names, variable names, and so forth that exist in your actual situation than to come up with new names. The problem could be related to the name of a table or variable. These cases are rare, perhaps, but it is better to be safe than sorry. After all, it should be easier for you to provide an example that uses your actual situation, and it is by all means better for us. If you have data that you don't want to be visible to others in the bug report, you can use FTP to transfer it to `ftp://ftp.mysql.com/pub/mysql/upload/'. If the information is really top secret and you don't want to show it even to us, go ahead and provide an example using other names, but please regard this as the last choice. * Include all the options given to the relevant programs, if possible. For example, indicate the options that you use when you start the `mysqld' server, as well as the options that you use to run any MySQL client programs. The options to programs such as `mysqld' and `mysql', and to the `configure' script, are often key to resolving problems and are very relevant. It is never a bad idea to include them. If your problem involves a program written in a language such as Perl or PHP, please include the language processor's version number, as well as the version for any modules that the program uses. For example, if you have a Perl script that uses the `DBI' and `DBD::mysql' modules, include the version numbers for Perl, `DBI', and `DBD::mysql'. * If your question is related to the privilege system, please include the output of `mysqlaccess', the output of `mysqladmin reload', and all the error messages you get when trying to connect. When you test your privileges, you should first run `mysqlaccess'. After this, execute `mysqladmin reload version' and try to connect with the program that gives you trouble. `mysqlaccess' can be found in the `bin' directory under your MySQL installation directory. * If you have a patch for a bug, do include it. But don't assume that the patch is all we need, or that we can use it, if you don't provide some necessary information such as test cases showing the bug that your patch fixes. We might find problems with your patch or we might not understand it at all. If so, we can't use it. If we can't verify the exact purpose of the patch, we won't use it. Test cases help us here. Show that the patch handles all the situations that may occur. If we find a borderline case (even a rare one) where the patch won't work, it may be useless. * Guesses about what the bug is, why it occurs, or what it depends on are usually wrong. Even the MySQL team can't guess such things without first using a debugger to determine the real cause of a bug. * Indicate in your bug report that you have checked the reference manual and mail archive so that others know you have tried to solve the problem yourself. * If the problem is that your data appears corrupt or you get errors when you access a particular table, you should first check your tables and then try to repair them with `CHECK TABLE' and `REPAIR TABLE' or with `myisamchk'. See *Note database-administration::. If you are running Windows, please verify the value of `lower_case_table_names' using the `SHOW VARIABLES LIKE 'lower_case_table_names'' command. This variable affects how the server handles lettercase of database and table names. Its effect for a given value should be as described in *Note identifier-case-sensitivity::. * If you often get corrupted tables, you should try to find out when and why this happens. In this case, the error log in the MySQL data directory may contain some information about what happened. (This is the file with the `.err' suffix in the name.) See *Note error-log::. Please include any relevant information from this file in your bug report. Normally `mysqld' should _never_ crash a table if nothing killed it in the middle of an update. If you can find the cause of `mysqld' dying, it's much easier for us to provide you with a fix for the problem. See *Note what-is-crashing::. * If possible, download and install the most recent version of MySQL Server and check whether it solves your problem. All versions of the MySQL software are thoroughly tested and should work without problems. We believe in making everything as backward-compatible as possible, and you should be able to switch MySQL versions without difficulty. See *Note which-version::. If you have no Web access and cannot report a bug by visiting `http://bugs.mysql.com/', you can use the `mysqlbug' script to generate a bug report (or a report about any problem). `mysqlbug' helps you generate a report by determining much of the following information automatically, but if something important is missing, please include it with your message. `mysqlbug' can be found in the `scripts' directory (source distribution) and in the `bin' directory under your MySQL installation directory (binary distribution).  File: manual.info, Node: compatibility, Prev: bug-reports, Up: introduction 1.9 MySQL Standards Compliance ============================== * Menu: * standards:: What Standards MySQL Follows * sql-mode:: Selecting SQL Modes * ansi-mode:: Running MySQL in ANSI Mode * extensions-to-ansi:: MySQL Extensions to Standard SQL * differences-from-ansi:: MySQL Differences from Standard SQL * constraints:: How MySQL Deals with Constraints This section describes how MySQL relates to the ANSI/ISO SQL standards. MySQL Server has many extensions to the SQL standard, and here you can find out what they are and how to use them. You can also find information about functionality missing from MySQL Server, and how to work around some of the differences. The SQL standard has been evolving since 1986 and several versions exist. In this manual, `SQL-92' refers to the standard released in 1992, `SQL:1999' refers to the standard released in 1999, and `SQL:2003' refers to the current version of the standard. We use the phrase `the SQL standard' or `standard SQL' to mean the current version of the SQL Standard at any time. One of our main goals with the product is to continue to work toward compliance with the SQL standard, but without sacrificing speed or reliability. We are not afraid to add extensions to SQL or support for non-SQL features if this greatly increases the usability of MySQL Server for a large segment of our user base. The `HANDLER' interface is an example of this strategy. See *Note handler::. We continue to support transactional and non-transactional databases to satisfy both mission-critical 24/7 usage and heavy Web or logging usage. MySQL Server was originally designed to work with medium-sized databases (10-100 million rows, or about 100MB per table) on small computer systems. Today MySQL Server handles terabyte-sized databases, but the code can also be compiled in a reduced version suitable for hand-held and embedded devices. The compact design of the MySQL server makes development in both directions possible without any conflicts in the source tree. Currently, we are not targeting real-time support, although MySQL replication capabilities offer significant functionality. MySQL supports high-availability database clustering using the `NDBCluster' storage engine. See *Note mysql-cluster::. XML support is to be implemented in a future version of the database server.  File: manual.info, Node: standards, Next: sql-mode, Prev: compatibility, Up: compatibility 1.9.1 What Standards MySQL Follows ---------------------------------- Our aim is to support the full ANSI/ISO SQL standard, but without making concessions to speed and quality of the code. ODBC levels 0-3.51.  File: manual.info, Node: sql-mode, Next: ansi-mode, Prev: standards, Up: compatibility 1.9.2 Selecting SQL Modes ------------------------- The MySQL server can operate in different SQL modes, and can apply these modes differentially for different clients. This capability enables each application to tailor the server's operating mode to its own requirements. SQL modes control aspects of server operation such as 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. You can set the default SQL mode by starting `mysqld' with the `--sql-mode="MODE_VALUE"' option. You can also change the mode at runtime by setting the `sql_mode' system variable with a `SET [SESSION|GLOBAL] sql_mode='MODE_VALUE'' statement. For more information on setting the SQL mode, see *Note server-sql-mode::.  File: manual.info, Node: ansi-mode, Next: extensions-to-ansi, Prev: sql-mode, Up: compatibility 1.9.3 Running MySQL in ANSI Mode -------------------------------- You can tell `mysqld' to run in ANSI mode with the `--ansi' startup option. Running the server in ANSI mode is the same as starting it with the following options: --transaction-isolation=SERIALIZABLE --sql-mode=ANSI You can achieve the same effect at runtime by executing these two statements: SET GLOBAL TRANSACTION ISOLATION LEVEL SERIALIZABLE; SET GLOBAL sql_mode = 'ANSI'; You can see that setting the `sql_mode' system variable to `'ANSI'' enables all SQL mode options that are relevant for ANSI mode as follows: mysql> SET GLOBAL sql_mode='ANSI'; mysql> SELECT @@global.sql_mode; -> 'REAL_AS_FLOAT,PIPES_AS_CONCAT,ANSI_QUOTES,IGNORE_SPACE,ANSI' Note that running the server in ANSI mode with `--ansi' is not quite the same as setting the SQL mode to `'ANSI''. The `--ansi' option affects the SQL mode and also sets the transaction isolation level. Setting the SQL mode to `'ANSI'' has no effect on the isolation level. See *Note server-options::, and *Note sql-mode::.  File: manual.info, Node: extensions-to-ansi, Next: differences-from-ansi, Prev: ansi-mode, Up: compatibility 1.9.4 MySQL Extensions to Standard SQL -------------------------------------- MySQL Server supports some extensions that you probably won't find in other SQL DBMSs. Be warned that if you use them, your code won't be portable to other SQL servers. In some cases, you can write code that includes MySQL extensions, but is still portable, by using comments of the following form: /*! MYSQL-SPECIFIC CODE */ In this case, MySQL Server parses and executes the code within the comment as it would any other SQL statement, but other SQL servers will ignore the extensions. For example, MySQL Server recognizes the `STRAIGHT_JOIN' keyword in the following statement, but other servers will not: SELECT /*! STRAIGHT_JOIN */ col1 FROM table1,table2 WHERE ... If you add a version number after the ``!'' character, the syntax within the comment is executed only if the MySQL version is greater than or equal to the specified version number. The `TEMPORARY' keyword in the following comment is executed only by servers from MySQL 3.23.02 or higher: CREATE /*!32302 TEMPORARY */ TABLE t (a INT); The following descriptions list MySQL extensions, organized by category. * Organization of data on disk MySQL Server maps each database to a directory under the MySQL data directory, and maps tables within a database to filenames in the database directory. This has a few implications: * Database and table names are case sensitive in MySQL Server on operating systems that have case-sensitive filenames (such as most Unix systems). See *Note identifier-case-sensitivity::. * You can use standard system commands to back up, rename, move, delete, and copy tables that are managed by the `MyISAM' storage engine. For example, it is possible to rename a `MyISAM' table by renaming the `.MYD', `.MYI', and `.frm' files to which the table corresponds. (Nevertheless, it is preferable to use `RENAME TABLE' or `ALTER TABLE ... RENAME' and let the server rename the files.) Database and table names cannot contain pathname separator characters (``/'', ``\''). * General language syntax * By default, strings can be enclosed by either ``"'' or ``''', not just by ``'''. (If the `ANSI_QUOTES' SQL mode is enabled, strings can be enclosed only by ``''' and the server interprets strings enclosed by ``"'' as identifiers.) * ``\'' is the escape character in strings. * In SQL statements, you can access tables from different databases with the DB_NAME.TBL_NAME syntax. Some SQL servers provide the same functionality but call this `User space'. MySQL Server doesn't support tablespaces such as used in statements like this: `CREATE TABLE ralph.my_table ... IN my_tablespace'. * SQL statement syntax * The `ANALYZE TABLE', `CHECK TABLE', `OPTIMIZE TABLE', and `REPAIR TABLE' statements. * The `CREATE DATABASE', `DROP DATABASE', and `ALTER DATABASE' statements. See *Note create-database::, *Note drop-database::, and *Note alter-database::. * The `DO' statement. * `EXPLAIN SELECT' to obtain a description of how tables are processed by the query optimizer. * The `FLUSH' and `RESET' statements. * The `SET' statement. See *Note set-option::. * The `SHOW' statement. See *Note show::. As of MySQL 5.0, the information produced by many of the MySQL-specific `SHOW' statements can be obtained in more standard fashion by using `SELECT' to query `INFORMATION_SCHEMA'. See *Note information-schema::. * Use of `LOAD DATA INFILE'. In many cases, this syntax is compatible with Oracle's `LOAD DATA INFILE'. See *Note load-data::. * Use of `RENAME TABLE'. See *Note rename-table::. * Use of `REPLACE' instead of `DELETE' plus `INSERT'. See *Note replace::. * Use of `CHANGE COL_NAME', `DROP COL_NAME', or `DROP INDEX', `IGNORE' or `RENAME' in `ALTER TABLE' statements. Use of multiple `ADD', `ALTER', `DROP', or `CHANGE' clauses in an `ALTER TABLE' statement. See *Note alter-table::. * Use of index names, indexes on a prefix of a column, and use of `INDEX' or `KEY' in `CREATE TABLE' statements. See *Note create-table::. * Use of `TEMPORARY' or `IF NOT EXISTS' with `CREATE TABLE'. * Use of `IF EXISTS' with `DROP TABLE' and `DROP DATABASE'. * The capability of dropping multiple tables with a single `DROP TABLE' statement. * The `ORDER BY' and `LIMIT' clauses of the `UPDATE' and `DELETE' statements. * `INSERT INTO TBL_NAME SET COL_NAME = ...' syntax. * The `DELAYED' clause of the `INSERT' and `REPLACE' statements. * The `LOW_PRIORITY' clause of the `INSERT', `REPLACE', `DELETE', and `UPDATE' statements. * Use of `INTO OUTFILE' or `INTO DUMPFILE' in `SELECT' statements. See *Note select::. * Options such as `STRAIGHT_JOIN' or `SQL_SMALL_RESULT' in `SELECT' statements. * You don't need to name all selected columns in the `GROUP BY' clause. This gives better performance for some very specific, but quite normal queries. See *Note group-by-functions-and-modifiers::. * You can specify `ASC' and `DESC' with `GROUP BY', not just with `ORDER BY'. * The ability to set variables in a statement with the `:=' assignment operator: mysql> SELECT @a:=SUM(total),@b:=COUNT(*),@a/@b AS avg -> FROM test_table; mysql> SELECT @t1:=(@t2:=1)+@t3:=4,@t1,@t2,@t3; * Data types * The `MEDIUMINT', `SET', and `ENUM' data types, and the various `BLOB' and `TEXT' data types. * The `AUTO_INCREMENT', `BINARY', `NULL', `UNSIGNED', and `ZEROFILL' data type attributes. * Functions and operators * To make it easier for users who migrate from other SQL environments, MySQL Server supports aliases for many functions. For example, all string functions support both standard SQL syntax and ODBC syntax. * MySQL Server understands the `||' and `&&' operators to mean logical OR and AND, as in the C programming language. In MySQL Server, `||' and `OR' are synonyms, as are `&&' and `AND'. Because of this nice syntax, MySQL Server doesn't support the standard SQL `||' operator for string concatenation; use `CONCAT()' instead. Because `CONCAT()' takes any number of arguments, it's easy to convert use of the `||' operator to MySQL Server. * Use of `COUNT(DISTINCT VALUE_LIST)' where VALUE_LIST has more than one element. * String comparisons are case-insensitive by default, with sort ordering determined by the collation of the current character set, which is `latin1' (cp1252 West European) by default. If you don't like this, you should declare your columns with the `BINARY' attribute or use the `BINARY' cast, which causes comparisons to be done using the underlying character code values rather then a lexical ordering. * The `%' operator is a synonym for `MOD()'. That is, `N % M' is equivalent to `MOD(N,M)'. `%' is supported for C programmers and for compatibility with PostgreSQL. * The `=', `<>', `<=',`<', `>=',`>', `<<', `>>', `<=>', `AND', `OR', or `LIKE' operators may be used in expressions in the output column list (to the left of the `FROM') in `SELECT' statements. For example: mysql> SELECT col1=1 AND col2=2 FROM my_table; * The `LAST_INSERT_ID()' function returns the most recent `AUTO_INCREMENT' value. See *Note information-functions::. * `LIKE' is allowed on numeric values. * The `REGEXP' and `NOT REGEXP' extended regular expression operators. * `CONCAT()' or `CHAR()' with one argument or more than two arguments. (In MySQL Server, these functions can take a variable number of arguments.) * The `BIT_COUNT()', `CASE', `ELT()', `FROM_DAYS()', `FORMAT()', `IF()', `PASSWORD()', `ENCRYPT()', `MD5()', `ENCODE()', `DECODE()', `PERIOD_ADD()', `PERIOD_DIFF()', `TO_DAYS()', and `WEEKDAY()' functions. * Use of `TRIM()' to trim substrings. Standard SQL supports removal of single characters only. * The `GROUP BY' functions `STD()', `BIT_OR()', `BIT_AND()', `BIT_XOR()', and `GROUP_CONCAT()'. See *Note group-by-functions-and-modifiers::. For a prioritized list indicating when new extensions are added to MySQL Server, you should consult the online MySQL development roadmap at `http://dev.mysql.com/doc/mysql/en/roadmap.html'.  File: manual.info, Node: differences-from-ansi, Next: constraints, Prev: extensions-to-ansi, Up: compatibility 1.9.5 MySQL Differences from Standard SQL ----------------------------------------- * Menu: * ansi-diff-subqueries:: Subquery Support * ansi-diff-select-into-table:: `SELECT INTO TABLE' * ansi-diff-transactions:: Transactions and Atomic Operations * ansi-diff-triggers:: Stored Routines and Triggers * ansi-diff-foreign-keys:: Foreign Keys * ansi-diff-views:: Views * ansi-diff-comments:: '`--'' as the Start of a Comment We try to make MySQL Server follow the ANSI SQL standard and the ODBC SQL standard, but MySQL Server performs operations differently in some cases: * For `VARCHAR' columns, trailing spaces are removed when the value is stored. (This is fixed in MySQL 5.0.3). See *Note bugs::. * In some cases, `CHAR' columns are silently converted to `VARCHAR' columns when you define a table or alter its structure. (This no longer occurs as of MySQL 5.0.3). See *Note silent-column-changes::. * There are several differences between the MySQL and standard SQL privilege systems. For example, in MySQL, privileges for a table are not automatically revoked when you delete a table. You must explicitly issue a `REVOKE' statement to revoke privileges for a table. For more information, see *Note revoke::. * The `CAST()' function does not support cast to `REAL' or `BIGINT'. See *Note cast-functions::. * Standard SQL requires that a `HAVING' clause in a `SELECT' statement be able to refer to columns in the `GROUP BY' clause. This cannot be done before MySQL 5.0.2.  File: manual.info, Node: ansi-diff-subqueries, Next: ansi-diff-select-into-table, Prev: differences-from-ansi, Up: differences-from-ansi 1.9.5.1 Subquery Support ........................ MySQL 4.1 and up supports subqueries and derived tables. A `subquery' is a `SELECT' statement nested within another statement. A `derived table' (an unnamed view) is a subquery in the `FROM' clause of another statement. See *Note subqueries::. For MySQL versions older than 4.1, most subqueries can be rewritten using joins or other methods. See *Note rewriting-subqueries::, for examples that show how to do this.  File: manual.info, Node: ansi-diff-select-into-table, Next: ansi-diff-transactions, Prev: ansi-diff-subqueries, Up: differences-from-ansi 1.9.5.2 `SELECT INTO TABLE' ........................... MySQL Server doesn't support the `SELECT ... INTO TABLE' Sybase SQL extension. Instead, MySQL Server supports the `INSERT INTO ... SELECT' standard SQL syntax, which is basically the same thing. See *Note insert-select::. For example: INSERT INTO tbl_temp2 (fld_id) SELECT tbl_temp1.fld_order_id FROM tbl_temp1 WHERE tbl_temp1.fld_order_id > 100; Alternatively, you can use `SELECT ... INTO OUTFILE' or `CREATE TABLE ... SELECT'. As of MySQL 5.0, you can use `SELECT ... INTO' with user-defined variables. The same syntax can also be used inside stored routines using cursors and local variables. See *Note select-into-statement::.  File: manual.info, Node: ansi-diff-transactions, Next: ansi-diff-triggers, Prev: ansi-diff-select-into-table, Up: differences-from-ansi 1.9.5.3 Transactions and Atomic Operations .......................................... MySQL Server (version 3.23-max and all versions 4.0 and above) supports transactions with the `InnoDB' and `BDB' transactional storage engines. `InnoDB' provides _full_ `ACID' compliance. See *Note storage-engines::. For information about `InnoDB' differences from standard SQL with regard to treatment of transaction errors, see *Note innodb-error-handling::. The other non-transactional storage engines in MySQL Server (such as `MyISAM') follow a different paradigm for data integrity called `atomic operations.' In transactional terms, `MyISAM' tables effectively always operate in `AUTOCOMMIT=1' mode. Atomic operations often offer comparable integrity with higher performance. Because MySQL Server supports both paradigms, you can decide whether your applications are best served by the speed of atomic operations or the use of transactional features. This choice can be made on a per-table basis. MySQL Enterprise For expert advice on choosing and tuning storage engines, subscribe to the MySQL Network Monitoring and Advisory Service. For more information see `http://www.mysql.com/products/enterprise/advisors.html'. As noted, the trade-off for transactional versus non-transactional storage engines lies mostly in performance. Transactional tables have significantly higher memory and disk space requirements, and more CPU overhead. On the other hand, transactional storage engines such as `InnoDB' also offer many significant features. MySQL Server's modular design allows the concurrent use of different storage engines to suit different requirements and deliver optimum performance in all situations. But how do you use the features of MySQL Server to maintain rigorous integrity even with the non-transactional `MyISAM' tables, and how do these features compare with the transactional storage engines? * If your applications are written in a way that is dependent on being able to call `ROLLBACK' rather than `COMMIT' in critical situations, transactions are more convenient. Transactions also ensure that unfinished updates or corrupting activities are not committed to the database; the server is given the opportunity to do an automatic rollback and your database is saved. If you use non-transactional tables, MySQL Server in almost all cases allows you to resolve potential problems by including simple checks before updates and by running simple scripts that check the databases for inconsistencies and automatically repair or warn if such an inconsistency occurs. Note that just by using the MySQL log or even adding one extra log, you can normally fix tables perfectly with no data integrity loss. * More often than not, critical transactional updates can be rewritten to be atomic. Generally speaking, all integrity problems that transactions solve can be done with `LOCK TABLES' or atomic updates, ensuring that there are no automatic aborts from the server, which is a common problem with transactional database systems. * To be safe with MySQL Server, regardless of whether you use transactional tables, you only need to have backups and have binary logging turned on. When that is true, you can recover from any situation that you could with any other transactional database system. It is always good to have backups, regardless of which database system you use. The transactional paradigm has its benefits and its drawbacks. Many users and application developers depend on the ease with which they can code around problems where an abort appears to be necessary, or is necessary. However, even if you are new to the atomic operations paradigm, or more familiar with transactions, do consider the speed benefit that non-transactional tables can offer on the order of three to five times the speed of the fastest and most optimally tuned transactional tables. In situations where integrity is of highest importance, MySQL Server offers transaction-level reliability and integrity even for non-transactional tables. If you lock tables with `LOCK TABLES', all updates stall until integrity checks are made. If you obtain a `READ LOCAL' lock (as opposed to a write lock) for a table that allows concurrent inserts at the end of the table, reads are allowed, as are inserts by other clients. The newly inserted records are not be seen by the client that has the read lock until it releases the lock. With `INSERT DELAYED', you can write inserts that go into a local queue until the locks are released, without having the client wait for the insert to complete. See *Note concurrent-inserts::, and *Note insert-delayed::. `Atomic,' in the sense that we mean it, is nothing magical. It only means that you can be sure that while each specific update is running, no other user can interfere with it, and there can never be an automatic rollback (which can happen with transactional tables if you are not very careful). MySQL Server also guarantees that there are no dirty reads. Following are some techniques for working with non-transactional tables: * Loops that need transactions normally can be coded with the help of `LOCK TABLES', and you don't need cursors to update records on the fly. * To avoid using `ROLLBACK', you can employ the following strategy: 1. Use `LOCK TABLES' to lock all the tables you want to access. 2. Test the conditions that must be true before performing the update. 3. Update if the conditions are satisfied. 4. Use `UNLOCK TABLES' to release your locks. This is usually a much faster method than using transactions with possible rollbacks, although not always. The only situation this solution doesn't handle is when someone kills the threads in the middle of an update. In that case, all locks are released but some of the updates may not have been executed. * You can also use functions to update records in a single operation. You can get a very efficient application by using the following techniques: * Modify columns relative to their current value. * Update only those columns that actually have changed. For example, when we are updating customer information, we update only the customer data that has changed and test only that none of the changed data, or data that depends on the changed data, has changed compared to the original row. The test for changed data is done with the `WHERE' clause in the `UPDATE' statement. If the record wasn't updated, we give the client a message: `Some of the data you have changed has been changed by another user.' Then we show the old row versus the new row in a window so that the user can decide which version of the customer record to use. This gives us something that is similar to column locking but is actually even better because we only update some of the columns, using values that are relative to their current values. This means that typical `UPDATE' statements look something like these: UPDATE tablename SET pay_back=pay_back+125; UPDATE customer SET customer_date='current_date', address='new address', phone='new phone', money_owed_to_us=money_owed_to_us-125 WHERE customer_id=id AND address='old address' AND phone='old phone'; This is very efficient and works even if another client has changed the values in the `pay_back' or `money_owed_to_us' columns. * In many cases, users have wanted `LOCK TABLES' or `ROLLBACK' for the purpose of managing unique identifiers. This can be handled much more efficiently without locking or rolling back by using an `AUTO_INCREMENT' column and either the `LAST_INSERT_ID()' SQL function or the `mysql_insert_id()' C API function. See *Note information-functions::, and *Note mysql-insert-id::. You can generally code around the need for row-level locking. Some situations really do need it, and `InnoDB' tables support row-level locking. Otherwise, with `MyISAM' tables, you can use a flag column in the table and do something like the following: UPDATE TBL_NAME SET row_flag=1 WHERE id=ID; MySQL returns `1' for the number of affected rows if the row was found and `row_flag' wasn't `1' in the original row. You can think of this as though MySQL Server changed the preceding statement to: UPDATE TBL_NAME SET row_flag=1 WHERE id=ID AND row_flag <> 1;  File: manual.info, Node: ansi-diff-triggers, Next: ansi-diff-foreign-keys, Prev: ansi-diff-transactions, Up: differences-from-ansi 1.9.5.4 Stored Routines and Triggers .................................... Stored procedures and functions are implemented beginning with MySQL 5.0. See *Note stored-procedures::. Basic trigger functionality is implemented beginning with MySQL 5.0.2, with further development planned for MySQL 5.1. See *Note triggers::.  File: manual.info, Node: ansi-diff-foreign-keys, Next: ansi-diff-views, Prev: ansi-diff-triggers, Up: differences-from-ansi 1.9.5.5 Foreign Keys .................... In MySQL Server 3.23.44 and up, the `InnoDB' storage engine supports checking of foreign key constraints, including `CASCADE', `ON DELETE', and `ON UPDATE'. See *Note innodb-foreign-key-constraints::. For storage engines other than `InnoDB', MySQL Server parses the `FOREIGN KEY' syntax in `CREATE TABLE' statements, but does not use or store it. In the future, the implementation will be extended to store this information in the table specification file so that it may be retrieved by `mysqldump' and ODBC. At a later stage, foreign key constraints will be implemented for `MyISAM' tables as well. Foreign key enforcement offers several benefits to database developers: * Assuming proper design of the relationships, foreign key constraints make it more difficult for a programmer to introduce an inconsistency into the database. * Centralized checking of constraints by the database server makes it unnecessary to perform these checks on the application side. This eliminates the possibility that different applications may not all check the constraints in the same way. * Using cascading updates and deletes can simplify the application code. * Properly designed foreign key rules aid in documenting relationships between tables. Do keep in mind that these benefits come at the cost of additional overhead for the database server to perform the necessary checks. Additional checking by the server affects performance, which for some applications may be sufficiently undesirable as to be avoided if possible. (Some major commercial applications have coded the foreign key logic at the application level for this reason.) MySQL gives database developers the choice of which approach to use. If you don't need foreign keys and want to avoid the overhead associated with enforcing referential integrity, you can choose another storage engine instead, such as `MyISAM'. (For example, the `MyISAM' storage engine offers very fast performance for applications that perform only `INSERT' and `SELECT' operations. In this case, the table has no holes in the middle and the inserts can be performed concurrently with retrievals. See *Note concurrent-inserts::.) If you choose not to take advantage of referential integrity checks, keep the following considerations in mind: * In the absence of server-side foreign key relationship checking, the application itself must handle relationship issues. For example, it must take care to insert rows into tables in the proper order, and to avoid creating orphaned child records. It must also be able to recover from errors that occur in the middle of multiple-record insert operations. * If `ON DELETE' is the only referential integrity capability an application needs, you can achieve a similar effect as of MySQL Server 4.0 by using multiple-table `DELETE' statements to delete rows from many tables with a single statement. See *Note delete::. * A workaround for the lack of `ON DELETE' is to add the appropriate `DELETE' statements to your application when you delete records from a table that has a foreign key. In practice, this is often as quick as using foreign keys and is more portable. Be aware that the use of foreign keys can sometimes lead to problems: * Foreign key support addresses many referential integrity issues, but it is still necessary to design key relationships carefully to avoid circular rules or incorrect combinations of cascading deletes. * It is not uncommon for a DBA to create a topology of relationships that makes it difficult to restore individual tables from a backup. (MySQL alleviates this difficulty by allowing you to temporarily disable foreign key checks when reloading a table that depends on other tables. See *Note innodb-foreign-key-constraints::. As of MySQL 4.1.1, `mysqldump' generates dump files that take advantage of this capability automatically when they are reloaded.) Note that foreign keys in SQL are used to check and enforce referential integrity, not to join tables. If you want to get results from multiple tables from a `SELECT' statement, you do this by performing a join between them: SELECT * FROM t1 INNER JOIN t2 ON t1.id = t2.id; See *Note join::, and *Note example-foreign-keys::. The `FOREIGN KEY' syntax without `ON DELETE ...' is often used by ODBC applications to produce automatic `WHERE' clauses.  File: manual.info, Node: ansi-diff-views, Next: ansi-diff-comments, Prev: ansi-diff-foreign-keys, Up: differences-from-ansi 1.9.5.6 Views ............. Views (including updatable views) are implemented beginning with MySQL Server 5.0.1. See *Note views::. Views are useful for allowing users to access a set of relations (tables) as if it were a single table, and limiting their access to just that. Views can also be used to restrict access to rows (a subset of a particular table). For access control to columns, you can also use the sophisticated privilege system in MySQL Server. See *Note privilege-system::. In designing an implementation of views, our ambitious goal, as much as is possible within the confines of SQL, has been full compliance with `Codd's Rule #6' for relational database systems: `All views that are theoretically updatable, should in practice also be updatable.'  File: manual.info, Node: ansi-diff-comments, Prev: ansi-diff-views, Up: differences-from-ansi 1.9.5.7 '`--'' as the Start of a Comment ........................................ Standard SQL uses the C syntax `/* this is a comment */' for comments, and MySQL Server supports this syntax as well. MySQL also support extensions to this syntax that allow MySQL-specific SQL to be embedded in the comment, as described in *Note comments::. Standard SQL uses ``--'' as a start-comment sequence. MySQL Server uses ``#'' as the start comment character. MySQL Server 3.23.3 and up also supports a variant of the ``--'' comment style. That is, the ``--'' start-comment sequence must be followed by a space (or by a control character such as a newline). The space is required to prevent problems with automatically generated SQL queries that use constructs such as the following, where we automatically insert the value of the payment for `payment': UPDATE account SET credit=credit-payment Consider about what happens if `payment' has a negative value such as `-1': UPDATE account SET credit=credit--1 `credit--1' is a legal expression in SQL, but ``--'' is interpreted as the start of a comment, part of the expression is discarded. The result is a statement that has a completely different meaning than intended: UPDATE account SET credit=credit The statement produces no change in value at all. This illustrates that allowing comments to start with ``--'' can have serious consequences. Using our implementation requires a space following the ``--'' in order for it to be recognized as a start-comment sequence in MySQL Server 3.23.3 and newer. Therefore, `credit--1' is safe to use. Another safe feature is that the `mysql' command-line client ignores lines that start with ``--''. The following information is relevant only if you are running a MySQL version earlier than 3.23.3: If you have an SQL script in a text file that contains ``--'' comments, you should use the `replace' utility as follows to convert the comments to use ``#'' characters before executing the script: shell> replace " --" " #" < text-file-with-funny-comments.sql \ | mysql DB_NAME That is safer than executing the script in the usual way: shell> mysql DB_NAME < text-file-with-funny-comments.sql You can also edit the script file `in place' to change the ``--'' comments to ``#'' comments: shell> replace " --" " #" -- text-file-with-funny-comments.sql Change them back with this command: shell> replace " #" " --" -- text-file-with-funny-comments.sql See *Note replace-utility::.  File: manual.info, Node: constraints, Prev: differences-from-ansi, Up: compatibility 1.9.6 How MySQL Deals with Constraints -------------------------------------- * Menu: * constraint-primary-key:: `PRIMARY KEY' and `UNIQUE' Index Constraints * constraint-invalid-data:: Constraints on Invalid Data * constraint-enum:: `ENUM' and `SET' Constraints MySQL allows you to work both with transactional tables that allow rollback and with non-transactional tables that do not. Because of this, constraint handling is a bit different in MySQL than in other DBMSs. We must handle the case when you have inserted or updated a lot of rows in a non-transactional table for which changes cannot be rolled back when an error occurs. The basic philosophy is that MySQL Server tries to produce an error for anything that it can detect while parsing a statement to be executed, and tries to recover from any errors that occur while executing the statement. We do this in most cases, but not yet for all. The options MySQL has when an error occurs are to stop the statement in the middle or to recover as well as possible from the problem and continue. By default, the server follows the latter course. This means, for example, that the server may coerce illegal values to the closest legal values. Beginning with MySQL 5.0.2, several SQL mode options are available to provide greater control over handling of bad data values and whether to continue statement execution or abort when errors occur. Using these options, you can configure MySQL Server to act in a more traditional fashion that is like other DBMSs that reject improper input. The SQL mode can be set globally at server startup to affect all clients. Individual clients can set the SQL mode at runtime, which enables each client to select the behavior most appropriate for its requirements. See *Note server-sql-mode::. MySQL Enterprise To be alerted when there is no form of server-enforced data integrity, subscribe to the MySQL Network Monitoring and Advisory Service. For more information see `http://www.mysql.com/products/enterprise/advisors.html'. The following sections describe how MySQL Server handles different types of constraints.  File: manual.info, Node: constraint-primary-key, Next: constraint-invalid-data, Prev: constraints, Up: constraints 1.9.6.1 `PRIMARY KEY' and `UNIQUE' Index Constraints .................................................... Normally, an error occurs when you try to `INSERT' or `UPDATE' a row that causes a primary key, unique key, or foreign key violation. If you are using a transactional storage engine such as `InnoDB', MySQL automatically rolls back the statement. If you are using a non-transactional storage engine, MySQL stops processing the statement at the row for which the error occurred and leaves any remaining rows unprocessed. If you want to ignore such key violations, MySQL supports an `IGNORE' keyword for `INSERT' and `UPDATE'. In this case, MySQL ignores any key violations and continues processing with the next row. See *Note insert::, and *Note update::. You can get information about the number of rows actually inserted or updated with the `mysql_info()' C API function. You can also use the `SHOW WARNINGS' statement. See *Note mysql-info::, and *Note show-warnings::. Currently, only `InnoDB' tables support foreign keys. See *Note innodb-foreign-key-constraints::. Foreign key support in `MyISAM' tables is scheduled for implementation in MySQL 5.2. See *Note roadmap::.  File: manual.info, Node: constraint-invalid-data, Next: constraint-enum, Prev: constraint-primary-key, Up: constraints 1.9.6.2 Constraints on Invalid Data ................................... Before MySQL 5.0.2, MySQL is forgiving of illegal or improper data values and coerces them to legal values for data entry. In MySQL 5.0.2 and up, that remains the default behavior, but you can change the server SQL mode to select more traditional treatment of bad values such that the server rejects them and aborts the statement in which they occur. *Note server-sql-mode::. This section describes the default (forgiving) behavior of MySQL, as well as the strict SQL mode and how it differs. If you are not using strict mode, then whenever you insert an `incorrect' value into a column, such as a `NULL' into a `NOT NULL' column or a too-large numeric value into a numeric column, MySQL sets the column to the `best possible value' instead of producing an error: The following rules describe in more detail how this works: * If you try to store an out of range value into a numeric column, MySQL Server instead stores zero, the smallest possible value, or the largest possible value, whichever is closest to the invalid value. * For strings, MySQL stores either the empty string or as much of the string as can be stored in the column. * If you try to store a string that doesn't start with a number into a numeric column, MySQL Server stores 0. * Invalid values for `ENUM' and `SET' columns ae handled as described in *Note constraint-enum::. * MySQL allows you to store certain incorrect date values into `DATE' and `DATETIME' columns (such as `'2000-02-31'' or `'2000-02-00''). The idea is that it's not the job of the SQL server to validate dates. If MySQL can store a date value and retrieve exactly the same value, MySQL stores it as given. If the date is totally wrong (outside the server's ability to store it), the special `zero' date value `'0000-00-00'' is stored in the column instead. * If you try to store `NULL' into a column that doesn't take `NULL' values, an error occurs for single-row `INSERT' statements. For multiple-row `INSERT' statements or for `INSERT INTO ... SELECT' statements, MySQL Server stores the implicit default value for the column data type. In general, this is `0' for numeric types, the empty string (`''') for string types, and the `zero' value for date and time types. Implicit default values are discussed in *Note data-type-defaults::. * If an `INSERT' statement specifies no value for a column, MySQL inserts its default value if the column definition includes an explicit `DEFAULT' clause. If the definition has no such `DEFAULT' clause, MySQL inserts the implicit default value for the column data type. The reason for using the preceding rules in non-strict mode is that we can't check these conditions until the statement has begun executing. We can't just roll back if we encounter a problem after updating a few rows, because the storage engine may not support rollback. The option of terminating the statement is not that good; in this case, the update would be `half done,' which is probably the worst possible scenario. In this case, it's better to `do the best you can' and then continue as if nothing happened. In MySQL 5.0.2 and up, you can select stricter treatment of input values by using the `STRICT_TRANS_TABLES' or `STRICT_ALL_TABLES' SQL modes: SET sql_mode = 'STRICT_TRANS_TABLES'; SET sql_mode = 'STRICT_ALL_TABLES'; `STRICT_TRANS_TABLES' enables strict mode for transactional storage engines, and also to some extent for non-transactional engines. It works like this: * For transactional storage engines, bad data values occurring anywhere in a statement cause the statement to abort and roll back. * For non-transactional storage engines, a statement aborts if the error occurs in the first row to be inserted or updated. (When the error occurs in the first row, the statement can be aborted to leave the table unchanged, just as for a transactional table.) Errors in rows after the first do not abort the statement, because the table has already been changed by the first row. Instead, bad data values are adjusted and result in warnings rather than errors. In other words, with `STRICT_TRANS_TABLES', a wrong value causes MySQL to roll back all updates done so far, if that can be done without changing the table. But once the table has been changed, further errors result in adjustments and warnings. For even stricter checking, enable `STRICT_ALL_TABLES'. This is the same as `STRICT_TRANS_TABLES' except that for non-transactional storage engines, errors abort the statement even for bad data in rows following the first row. This means that if an error occurs partway through a multiple-row insert or update for a non-transactional table, a partial update results. Earlier rows are inserted or updated, but those from the point of the error on are not. To avoid this for non-transactional tables, either use single-row statements or else use `STRICT_TRANS_TABLES' if conversion warnings rather than errors are acceptable. To avoid problems in the first place, do not use MySQL to check column content. It is safest (and often faster) to let the application ensure that it passes only legal values to the database. With either of the strict mode options, you can cause errors to be treated as warnings by using `INSERT IGNORE' or `UPDATE IGNORE' rather than `INSERT' or `UPDATE' without `IGNORE'.  File: manual.info, Node: constraint-enum, Prev: constraint-invalid-data, Up: constraints 1.9.6.3 `ENUM' and `SET' Constraints .................................... `ENUM' and `SET' columns provide an efficient way to define columns that can contain only a given set of values. See *Note enum::, and *Note set::. However, before MySQL 5.0.2, `ENUM' and `SET' columns do not provide true constraints on entry of invalid data: * `ENUM' columns always have a default value. If you specify no default value, then it is `NULL' for columns that can have `NULL', otherwise it is the first enumeration value in the column definition. * If you insert an incorrect value into an `ENUM' column or if you force a value into an `ENUM' column with `IGNORE', it is set to the reserved enumeration value of `0', which is displayed as an empty string in string context. * If you insert an incorrect value into a `SET' column, the incorrect value is ignored. For example, if the column can contain the values `'a'', `'b'', and `'c'', an attempt to assign `'a,x,b,y'' results in a value of `'a,b''. As of MySQL 5.0.2, you can configure the server to use strict SQL mode. See *Note server-sql-mode::. With strict mode enabled, the definition of a `ENUM' or `SET' column does act as a constraint on values entered into the column. An error occurs for values that do not satisfy these conditions: * An `ENUM' value must be one of those listed in the column definition, or the internal numeric equivalent thereof. The value cannot be the error value (that is, 0 or the empty string). For a column defined as `ENUM('a','b','c')', values such as `''', `'d'', or `'ax'' are illegal and are rejected. * A `SET' value must be the empty string or a value consisting only of the values listed in the column definition separated by commas. For a column defined as `SET('a','b','c')', values such as `'d'' or `'a,b,c,d'' are illegal and are rejected. Errors for invalid values can be suppressed in strict mode if you use `INSERT IGNORE' or `UPDATE IGNORE'. In this case, a warning is generated rather than an error. For `ENUM', the value is inserted as the error member (`0'). For `SET', the value is inserted as given except that any invalid substrings are deleted. For example, `'a,x,b,y'' results in a value of `'a,b''.  File: manual.info, Node: installing, Next: tutorial, Prev: introduction, Up: Top 2 Installing and Upgrading MySQL ******************************** * Menu: * installation-overview:: MySQL Installation Overview * installation-version:: Determining your current MySQL version * installing-es:: Installing MySQL Enterprise * installing-cs:: Installing MySQL Community Server  File: manual.info, Node: installation-overview, Next: installation-version, Prev: installing, Up: installing 2.1 MySQL Installation Overview =============================== This chapter describes how to obtain and install MySQL. You can choose to install MySQL Enterprise or MySQL Community Server: * MySQL Enterprise is MySQL AB's commercial offering for modern enterprise businesses. It includes MySQL Enterprise Server and the services provided by MySQL Network. To install MySQL Enterprise, see *Note installing-es::. * MySQL Community Server is for users who are comfortable configuring and administering MySQL by themselves. To install MySQL Community Server, see *Note installing-cs::. If you plan to upgrade an existing version of MySQL to a newer version rather than install MySQL for the first time, see *Note upgrade::, for information about upgrade procedures and about issues that you should consider before upgrading. If you are interested in migrating to MySQL from another database system, you may wish to read *Note faqs-migration::, which contains answers to some common questions concerning migration issues.  File: manual.info, Node: installation-version, Next: installing-es, Prev: installation-overview, Up: installing 2.2 Determining your current MySQL version ========================================== To determine the version and release of your currently installed MySQL installation, there are a number of options. * Using a command client (`mysql'), the server version of the MySQL server that you are connected to will be shown once you are connected. The server version information will include `community' or `enterprise' accordingly. For example, here is the output from a MySQL Community Server edition installed on Linux: Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 6 Server version: 5.0.27-standard MySQL Community Edition - Standard (GPL) Type 'help;' or '\h' for help. Type '\c' to clear the buffer. mysql> Below is the output from MySQL Enterprise Server on Windows: Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 2 Server version: 5.0.28-enterprise-gpl-nt MySQL Enterprise Server (GPL) Type 'help;' or '\h' for help. Type '\c' to clear the buffer. mysql> * You may also determine the version information using the version variables. Both the version and version_comment variables contain version information for the server you are connected to. Use the `SHOW VARIABLES' statement to obtain the information you want. For example: mysql> show variables like "%version%"; +-------------------------+------------------------------------------+ | Variable_name | Value | +-------------------------+------------------------------------------+ | protocol_version | 10 | | version | 5.0.27-standard | | version_comment | MySQL Community Edition - Standard (GPL) | | version_compile_machine | i686 | | version_compile_os | pc-linux-gnu | +-------------------------+------------------------------------------+ 5 rows in set (0.04 sec) mysql> * The `STATUS' command will display the version and version comment information. For example: mysql> status; -------------- ./client/mysql Ver 14.12 Distrib 5.0.29, for pc-linux-gnu (i686) using readline 5.0 Connection id: 8 Current database: Current user: mc@localhost SSL: Not in use Current pager: /usr/bin/less Using outfile: '' Using delimiter: ; Server version: 5.0.27-standard MySQL Community Edition - Standard (GPL) Protocol version: 10 Connection: Localhost via UNIX socket Server characterset: latin1 Db characterset: latin1 Client characterset: latin1 Conn. characterset: latin1 UNIX socket: /tmp/mysql.sock Uptime: 1 day 3 hours 58 min 43 sec Threads: 2 Questions: 17 Slow queries: 0 Opens: 11 Flush tables: 1 Open tables: 6 Queries per second avg: 0.000 -------------- * MySQL Administrator will show the server version within the `Server Information' tab. Only the value of the `version' information is shown.  File: manual.info, Node: installing-es, Next: installing-cs, Prev: installation-version, Up: installing 2.3 Installing MySQL Enterprise =============================== * Menu: * installing-es-overview:: Overview of MySQL Enterprise Installation * installing-es-disttypes:: Enterprise Server Distribution Types * installing-es-installer:: Installing the Enterprise MySQL Server * installing-es-upgrade:: Upgrading MySQL Enterprise Server * installing-es-uninstall:: Uninstalling MySQL Enterprise This section does not apply to MySQL Community Server users. This section contains information about the components, installation and initial configuration requirements for installing MySQL Enterprise.  File: manual.info, Node: installing-es-overview, Next: installing-es-disttypes, Prev: installing-es, Up: installing-es 2.3.1 Overview of MySQL Enterprise Installation ----------------------------------------------- This section does not apply to MySQL Community Server users. To obtain MySQL Enterprise, visit `http://www.mysql.com/products/enterprise/'. The platforms that are officially supported for MySQL Enterprise are listed at `http://www.mysql.com/support/supportedplatforms.html'. To install MySQL Enterprise, you should install the main distribution plus the latest available service pack or hot-fix. You only need to install the latest service pack or hot-fix - this will include all updates since the previous main distribution release. For platforms that do not have a MySQL Enterprise Server installer, use the Community Server instructions (see *Note installing-cs::).  File: manual.info, Node: installing-es-disttypes, Next: installing-es-installer, Prev: installing-es-overview, Up: installing-es 2.3.2 Enterprise Server Distribution Types ------------------------------------------ This section does not apply to MySQL Community Server users. Enterprise Server releases will be created for the following packages from the MySQL 5.0 tree: * `mysql-enterprise': Released under a commercial license and includes the following storage engines: `MyISAM', `MEMORY', `MERGE', `InnoDB', `ARCHIVE', `BLACKHOLE', `EXAMPLE', `FEDERATED'. * `mysql-enterprise-gpl': Same as `mysql-enterprise', but released under the GPL. * `mysql-cluster': `mysql-enterprise' plus MySQL Cluster (`NDB'). * `mysql-classic': Released under a commercial license, does not include `InnoDB'. * `mysql-community': Same as `mysql-enterprise-gpl', but available for the community, and released every 6 months. To satisfy different user requirements, we provide several servers. `mysqld' is an optimized server that is a smaller, faster binary. `mysqld-debug' is compiled with debugging support but is otherwise configured identically to the non-debug server. Each of these servers is compiled from the same source distribution, though with different configuration options. All native MySQL clients can connect to servers from either MySQL version.  File: manual.info, Node: installing-es-installer, Next: installing-es-upgrade, Prev: installing-es-disttypes, Up: installing-es 2.3.3 Installing the Enterprise MySQL Server -------------------------------------------- * Menu: * installing-es-installer-windows:: Using the Enterprise MySQL Installer for Windows * mysql-config-wizard:: MySQL Server Configuration Wizard This section does not apply to MySQL Community Server users. Installers for MySQL Enterprise are available for the Windows and Mac OS X. For other platforms, you will need to use the TAR, Zip or native package format (RPM, Solaris PKG) pafiles to perform the installation.  File: manual.info, Node: installing-es-installer-windows, Next: mysql-config-wizard, Prev: installing-es-installer, Up: installing-es-installer 2.3.3.1 Using the Enterprise MySQL Installer for Windows ........................................................ This section does not apply to MySQL Community Server users. The Enterprise MySQL Server installer installs the MySQL server and the MySQL Server Configuration Wizard, and enables you to run the configuration wizard to set up and configure your server before use. To start the installation process: 1. Download the `mysql-enterpriseVERSION-win32.zip' file and extract the `Setup.exe' file. You should double-click on this file to start the installation process. 2. The opening screen provides an overview of what the installer will achieve. Click `Next' to continue. MySQL Enterprise Installer Main Screen (Windows) 3. Choose your installation type. The *Typical* installation installs the main server and associated components, but does not include the developer libraries. The *Complete* installation installs everything. The *Custom* installation enables you to select which components are installed. Choose your installation and click `Next' to continue. MySQL Enterprise Installer Setup type (Windows) 4. If you have selected the custom installation, you need to choose which components are installed. Click `Next' to continute. MySQL Enterprise Installer Custom Installation (Windows) 5. The installation choices you have made will be summarized for you. If you have made a mistake, you can click `Back' to choose an alternate installation type. If you are ready to continue, choose `Install'. MySQL Enterprise Installer Installation Summary (Windows) 6. You can optionally set up your a connection to your MySQL.com account by entering your login details, or you can create a new account, or you can skip the MySQL.com signup. MySQL Enterprise Installer MySQL.com Registration (Windows) 7. The installation should proceed, installing the components you have selected. Once the installation has completed, you will get the opportunity to start the MySQL Instance Configuration Wizard. Untick the box if you do not want to run the wizard at this time. Click `Finish' to complete the installation. If you have opted to run the wizard, then it will be started once the installer has completed. MySQL Enterprise Installer Completed (Windows) If you selected to run the MySQL Configuration Wizard, see *Note mysql-config-wizard::.  File: manual.info, Node: mysql-config-wizard, Prev: installing-es-installer-windows, Up: installing-es-installer 2.3.3.2 MySQL Server Configuration Wizard ......................................... * Menu: * mysql-config-wizard-starting:: Starting the MySQL Server Configuration Wizard * mysql-config-wizard-maintenance:: Choosing a Maintenance Option * mysql-config-wizard-configuration-type:: Choosing a Configuration Type * mysql-config-wizard-server-type:: The Server Type Dialog * mysql-config-wizard-database-usage:: The Database Usage Dialog * mysql-config-wizard-tablespace:: The InnoDB Tablespace Dialog * mysql-config-wizard-connections:: The Concurrent Connections Dialog * mysql-config-wizard-networking:: The Networking and Strict Mode Options Dialog * mysql-config-wizard-character-set:: The Character Set Dialog * mysql-config-wizard-service:: The Service Options Dialog * mysql-config-wizard-security:: The Security Options Dialog * mysql-config-wizard-confirmation:: The Confirmation Dialog The MySQL Server Configuration Wizard helps automate the process of configuring your server. It creates a custom MySQL configuration file (`my.ini' or `my.cnf') by asking you a series of questions and then applying your responses to a template to generate the configuration file that is tuned to your installation. The MySQL Server Configuration Wizard is included with the MySQL 5.0 server. For Community Server users, the MySQL Server Configuration Wizard is available only for Windows. For Enterprise Server users, the MySQL Server Configuration Wizard is included as part of the standard Enterprise Installer. The MySQL Server Configuration Wizard is to a large extent the result of feedback that MySQL AB has received from many users over a period of several years. However, if you find that it lacks some feature important to you, please report it in our bugs database using the instructions given in *Note bug-reports::.  File: manual.info, Node: mysql-config-wizard-starting, Next: mysql-config-wizard-maintenance, Prev: mysql-config-wizard, Up: mysql-config-wizard 2.3.3.3 Starting the MySQL Server Configuration Wizard ...................................................... * Menu: * mysql-config-wizard-starting-windows:: The MySQL Server Configuration Wizard on Windows * mysql-config-wizard-starting-linux:: Starting the MySQL Server Configuration Wizard on Linux The MySQL Server Configuration Wizard is normally started as part of the installation process. You should only need to run the MySQL Server Configuration Wizard again when you need to change the configuration parameters of your server. MySQL Server Configuration Wizard  File: manual.info, Node: mysql-config-wizard-starting-windows, Next: mysql-config-wizard-starting-linux, Prev: mysql-config-wizard-starting, Up: mysql-config-wizard-starting 2.3.3.4 The MySQL Server Configuration Wizard on Windows ........................................................ You can launch the MySQL Configuration Wizard by clicking the `MySQL Server Instance Config Wizard' entry in the `MySQL' section of the Windows `Start' menu. Alternatively, you can navigate to the `bin' directory of your MySQL installation and launch the `MySQLInstanceConfig.exe' file directly. The MySQL Server Configuration Wizard places the `my.ini' file in the installation directory for the MySQL server. This helps associate configuration files with particular server instances. To ensure that the MySQL server knows where to look for the `my.ini' file, an argument similar to this is passed to the MySQL server as part of the service installation: --defaults-file="C:\PROGRAM FILES\MYSQL\MYSQL SERVER 5.0\my.ini" Here, C:\PROGRAM FILES\MYSQL\MYSQL SERVER 5.0 is replaced with the installation path to the MySQL Server. The `--defaults-file' option instructs the MySQL server to read the specified file for configuration options when it starts. Apart from making changes to the `my.ini' file by running the MySQL Server Configuration Wizard again, you can modify it by opening it with a text editor and making any necessary changes. You can also modify the server configuration with the MySQL Administrator (http://www.mysql.com/products/administrator/) utility. For more information about server configuration, see *Note server-options::. MySQL clients and utilities such as the `mysql' and `mysqldump' command-line clients are not able to locate the `my.ini' file located in the server installation directory. To configure the client and utility applications, create a new `my.ini' file in the Windows installation directory (for example, `C:\WINDOWS'). Under Windows Server 2003, Windows Server 2000 and Windows XP, MySQL Server Configuration Wizard will configure MySQL to work as a Windows service. To start and stop MySQL you use the `Services' application that is supplied as part of the Windows Administrator Tools.  File: manual.info, Node: mysql-config-wizard-starting-linux, Prev: mysql-config-wizard-starting-windows, Up: mysql-config-wizard-starting 2.3.3.5 Starting the MySQL Server Configuration Wizard on Linux ............................................................... This section does not apply to MySQL Community Server users. To start the MySQL Configuration Wizard on Linux, you must run the `mysqlsetup' command. You must be running an X Windows System server for the MySQL Server Configuration Wizard. To display the MySQL Server Configuration Wizard interface on a different machine, set the value of the `DISPLAY' variable on the command line: shell> DISPLAY=REMOTE:0.0 mysqlsetup The MySQL Server Configuration Wizard places the `my.cnf' file in the `/etc' directory. This configuration file is automatically used when `mysqld' is started. The standard MySQL server initialization script, typically located within `/etc/init.d/mysql', will also use this file automatically. Apart from making changes to the `my.ini' file by running the MySQL Server Configuration Wizard again, you can modify it by opening it with a text editor and making any necessary changes. You can also modify the server configuration with the MySQL Administrator (http://www.mysql.com/products/administrator/) utility. For more information about server configuration, see *Note server-options::.  File: manual.info, Node: mysql-config-wizard-maintenance, Next: mysql-config-wizard-configuration-type, Prev: mysql-config-wizard-starting, Up: mysql-config-wizard 2.3.3.6 Choosing a Maintenance Option ..................................... If the MySQL Server Configuration Wizard detects an existing configuration file, you have the option of either reconfiguring your existing server, or removing the server instance by deleting the configuration file and stopping and removing the MySQL service. To reconfigure an existing server, choose the `Re-configure Instance' option and click the `Next' button. Any existing configuration file is not overwritten, but renamed (within the same directory) using a timestamp (Windows) or sequential number (Linux). To remove the existing server instance, choose the `Remove Instance' option and click the `Next' button. If you choose the `Remove Instance' option, you advance to a confirmation window. Click the `Execute' button. The MySQL Server Configuration Wizard stops and removes the MySQL service, and then deletes the configuration file. The server installation and its `data' folder are not removed. If you choose the `Re-configure Instance' option, you advance to the `Configuration Type' dialog where you can choose the type of installation that you wish to configure.  File: manual.info, Node: mysql-config-wizard-configuration-type, Next: mysql-config-wizard-server-type, Prev: mysql-config-wizard-maintenance, Up: mysql-config-wizard 2.3.3.7 Choosing a Configuration Type ..................................... When you start the MySQL Server Configuration Wizard for a new MySQL installation, or choose the `Re-configure Instance' option for an existing installation, you advance to the `Configuration Type' dialog. MySQL Server Configuration Wizard: Configuration Type There are two configuration types available: `Detailed Configuration' and `Standard Configuration'. The `Standard Configuration' option is intended for new users who want to get started with MySQL quickly without having to make many decisions about server configuration. The `Detailed Configuration' option is intended for advanced users who want more fine-grained control over server configuration. If you are new to MySQL and need a server configured as a single-user developer machine, the `Standard Configuration' should suit your needs. Choosing the `Standard Configuration' option causes the MySQL Configuration Wizard to set all configuration options automatically with the exception of `Service Options' and `Security Options'. The `Standard Configuration' sets options that may be incompatible with systems where there are existing MySQL installations. If you have an existing MySQL installation on your system in addition to the installation you wish to configure, the `Detailed Configuration' option is recommended. To complete the `Standard Configuration', please refer to the sections on `Service Options' and `Security Options' in *Note mysql-config-wizard-service::, and *Note mysql-config-wizard-security::, respectively.  File: manual.info, Node: mysql-config-wizard-server-type, Next: mysql-config-wizard-database-usage, Prev: mysql-config-wizard-configuration-type, Up: mysql-config-wizard 2.3.3.8 The Server Type Dialog .............................. There are three different server types available to choose from. The server type that you choose affects the decisions that the MySQL Server Configuration Wizard makes with regard to memory, disk, and processor usage. MySQL Server Configuration Wizard: Server Type * `Developer Machine': Choose this option for a typical desktop workstation where MySQL is intended only for personal use. It is assumed that many other desktop applications are running. The MySQL server is configured to use minimal system resources. * `Server Machine': Choose this option for a server machine where the MySQL server is running alongside other server applications such as FTP, email, and Web servers. The MySQL server is configured to use a moderate portion of the system resources. * `Dedicated MySQL Server Machine': Choose this option for a server machine that is intended to run only the MySQL server. It is assumed that no other applications are running. The MySQL server is configured to use all available system resources. *Note*: By selecting one of the preconfigured configurations, the values and settings of various options in your `my.cnf' or `my.ini' will be altered accordingly. The default values and options as described in the reference manual may therefore be different to the options and values that were created during the execution of the configuration wizard.  File: manual.info, Node: mysql-config-wizard-database-usage, Next: mysql-config-wizard-tablespace, Prev: mysql-config-wizard-server-type, Up: mysql-config-wizard 2.3.3.9 The Database Usage Dialog ................................. The `Database Usage' dialog allows you to indicate the storage engines that you expect to use when creating MySQL tables. The option you choose determines whether the `InnoDB' storage engine is available and what percentage of the server resources are available to `InnoDB'. MySQL Server Configuration Wizard: Usage Dialog * `Multifunctional Database': This option enables both the `InnoDB' and `MyISAM' storage engines and divides resources evenly between the two. This option is recommended for users who use both storage engines on a regular basis. * `Transactional Database Only': This option enables both the `InnoDB' and `MyISAM' storage engines, but dedicates most server resources to the `InnoDB' storage engine. This option is recommended for users who use `InnoDB' almost exclusively and make only minimal use of `MyISAM'. * `Non-Transactional Database Only': This option disables the `InnoDB' storage engine completely and dedicates all server resources to the `MyISAM' storage engine. This option is recommended for users who do not use `InnoDB'.  File: manual.info, Node: mysql-config-wizard-tablespace, Next: mysql-config-wizard-connections, Prev: mysql-config-wizard-database-usage, Up: mysql-config-wizard 2.3.3.10 The InnoDB Tablespace Dialog ..................................... Some users may want to locate the `InnoDB' tablespace files in a different location than the MySQL server data directory. Placing the tablespace files in a separate location can be desirable if your system has a higher capacity or higher performance storage device available, such as a RAID storage system. MySQL Server Configuration Wizard: InnoDB Data Tablespace To change the default location for the `InnoDB' tablespace files, choose a new drive from the drop-down list of drive letters and choose a new path from the drop-down list of paths. To create a custom path, click the `...' button. If you are modifying the configuration of an existing server, you must click the `Modify' button before you change the path. In this situation you must move the existing tablespace files to the new location manually before starting the server.  File: manual.info, Node: mysql-config-wizard-connections, Next: mysql-config-wizard-networking, Prev: mysql-config-wizard-tablespace, Up: mysql-config-wizard 2.3.3.11 The Concurrent Connections Dialog .......................................... To prevent the server from running out of resources, it is important to limit the number of concurrent connections to the MySQL server that can be established. The `Concurrent Connections' dialog allows you to choose the expected usage of your server, and sets the limit for concurrent connections accordingly. It is also possible to set the concurrent connection limit manually. MySQL Server Configuration Wizard: Connections * `Decision Support (DSS)/OLAP': Choose this option if your server does not require a large number of concurrent connections. The maximum number of connections is set at 100, with an average of 20 concurrent connections assumed. * `Online Transaction Processing (OLTP)': Choose this option if your server requires a large number of concurrent connections. The maximum number of connections is set at 500. * `Manual Setting': Choose this option to set the maximum number of concurrent connections to the server manually. Choose the number of concurrent connections from the drop-down box provided, or enter the maximum number of connections into the drop-down box if the number you desire is not listed.  File: manual.info, Node: mysql-config-wizard-networking, Next: mysql-config-wizard-character-set, Prev: mysql-config-wizard-connections, Up: mysql-config-wizard 2.3.3.12 The Networking and Strict Mode Options Dialog ...................................................... Use the `Networking Options' dialog to enable or disable TCP/IP networking and to configure the port number that is used to connect to the MySQL server. MySQL Server Configuration Wizard: Network Configuration TCP/IP networking is enabled by default. To disable TCP/IP networking, uncheck the box next to the `Enable TCP/IP Networking' option. Port 3306 is used by default. To change the port used to access MySQL, choose a new port number from the drop-down box or type a new port number directly into the drop-down box. If the port number you choose is in use, you are prompted to confirm your choice of port number. Set the `Server SQL Mode' to either enable or disable strict mode. Enabling strict mode (default) makes MySQL behave more like other database management systems. _If you run applications that rely on MySQL's old `forgiving' behavior, make sure to either adapt those applications or to disable strict mode._ For more information about strict mode, see *Note server-sql-mode::.  File: manual.info, Node: mysql-config-wizard-character-set, Next: mysql-config-wizard-service, Prev: mysql-config-wizard-networking, Up: mysql-config-wizard 2.3.3.13 The Character Set Dialog ................................. The MySQL server supports multiple character sets and it is possible to set a default server character set that is applied to all tables, columns, and databases unless overridden. Use the `Character Set' dialog to change the default character set of the MySQL server. MySQL Server Configuration Wizard: Character Set * `Standard Character Set': Choose this option if you want to use `latin1' as the default server character set. `latin1' is used for English and many Western European languages. * `Best Support For Multilingualism': Choose this option if you want to use `utf8' as the default server character set. This is a Unicode character set that can store characters from many different languages. * `Manual Selected Default Character Set / Collation': Choose this option if you want to pick the server's default character set manually. Choose the desired character set from the provided drop-down list.  File: manual.info, Node: mysql-config-wizard-service, Next: mysql-config-wizard-security, Prev: mysql-config-wizard-character-set, Up: mysql-config-wizard 2.3.3.14 The Service Options Dialog ................................... This section does not apply to MySQL Community Server users. On Windows platforms, the MySQL server can be installed as a Windows service. When installed this way, the MySQL server can be started automatically during system startup, and even restarted automatically by Windows in the event of a service failure. The MySQL Server Configuration Wizard installs the MySQL server as a service by default, using the service name `MySQL'. If you do not wish to install the service, uncheck the box next to the `Install As Windows Service' option. You can change the service name by picking a new service name from the drop-down box provided or by entering a new service name into the drop-down box. To install the MySQL server as a service but not have it started automatically at startup, uncheck the box next to the `Launch the MySQL Server Automatically' option.  File: manual.info, Node: mysql-config-wizard-security, Next: mysql-config-wizard-confirmation, Prev: mysql-config-wizard-service, Up: mysql-config-wizard 2.3.3.15 The Security Options Dialog .................................... _It is strongly recommended that you set a `root' password for your MySQL server_, and the MySQL Server Configuration Wizard requires by default that you do so. If you do not wish to set a `root' password, uncheck the box next to the `Modify Security Settings' option. MySQL Server Configuration Wizard: Security To set the `root' password, enter the desired password into both the `New root password' and `Confirm' boxes. If you are reconfiguring an existing server, you need to enter the existing `root' password into the `Current root password' box. To prevent `root' logins from across the network, check the box next to the `Root may only connect from localhost' option. This increases the security of your `root' account. To create an anonymous user account, check the box next to the `Create An Anonymous Account' option. Creating an anonymous account can decrease server security and cause login and permission difficulties. For this reason, it is not recommended.  File: manual.info, Node: mysql-config-wizard-confirmation, Prev: mysql-config-wizard-security, Up: mysql-config-wizard 2.3.3.16 The Confirmation Dialog ................................ The final dialog in the MySQL Server Configuration Wizard is the `Confirmation Dialog'. To start the configuration process, click the `Execute' button. To return to a previous dialog, click the `Back' button. To exit the MySQL Server Configuration Wizard without configuring the server, click the `Cancel' button. MySQL Server Configuration Wizard: Confirmation After you click the `Execute' button, the MySQL Server Configuration Wizard performs a series of tasks and displays the progress onscreen as the tasks are performed. The MySQL Server Configuration Wizard first determines configuration file options based on your choices using a template prepared by MySQL AB developers and engineers. This template is named `my-template.ini' and is located in your server installation directory. The MySQL Configuration Wizard then writes these options to the corresponding configuration file. If you chose to create a service for the MySQL server, the MySQL Server Configuration Wizard creates and starts the service. If you are reconfiguring an existing service, the MySQL Server Configuration Wizard restarts the service to apply your configuration changes. If you chose to set a `root' password, the MySQL Configuration Wizard connects to the server, sets your new `root' password, and applies any other security settings you may have selected. After the MySQL Server Configuration Wizard has completed its tasks, it displays a summary. Click the `Finish' button to exit the MySQL Server Configuration Wizard.  File: manual.info, Node: installing-es-upgrade, Next: installing-es-uninstall, Prev: installing-es-installer, Up: installing-es 2.3.4 Upgrading MySQL Enterprise Server --------------------------------------- This section does not apply to MySQL Community Server users. When upgrading to MySQL Enterprise from Community Server you need only follow the installation process to install and upgrade the packages to the latest version provided by MySQL Enterprise. You will also need to install the latest MySQL Enterprise Service Pack and any outstanding MySQL Hot-fix packs. Be aware, however, that you must take into account any of the changes when moving between major releases. You should also check the release notes (see *Note releasenotes-es::) for details on major changes between revisions of MySQL Enterprise Server. For details of changes in other packages in MySQL Enterprise, see *Note news::. You should also review the notes and advice contained within *Note upgrade::.  File: manual.info, Node: installing-es-uninstall, Prev: installing-es-upgrade, Up: installing-es 2.3.5 Uninstalling MySQL Enterprise ----------------------------------- * Menu: * installing-es-windows-uninstall:: Uninstalling on Windows * installing-es-uninstall-linux-rpm:: Uninstalling on Linux (RPMs) This section does not apply to MySQL Community Server users. You can uninstall MySQL Enterprise using the standard tools according to your operating system. *Note*: When uninstalling, any data files created are not removed. You will need to separately remove these files to completely remove MySQL from your system.  File: manual.info, Node: installing-es-windows-uninstall, Next: installing-es-uninstall-linux-rpm, Prev: installing-es-uninstall, Up: installing-es-uninstall 2.3.5.1 Uninstalling on Windows ............................... To uninstall MySQL Enterprise on Windows you should use the Add or Remove Programs utility located within the Control Panel. Uninstalling MySQL Enterprise Packages within MySQL Enterprise must be removed individually. You may also use this option to remove packages that you no longer want or use. Any data you created while MySQL Enterprise was installed will not be removed. You will need to separately delete this information.  File: manual.info, Node: installing-es-uninstall-linux-rpm, Prev: installing-es-windows-uninstall, Up: installing-es-uninstall 2.3.5.2 Uninstalling on Linux (RPMs) .................................... To uninstall MySQL Enterprise on a Linux operating system that uses the RPM package format, you must remove each of the packages that were installed by the MySQL Enterprise Installer individually. To do this, first obtain a list of the installed packages: shell> rpm -q -a|grep -i mysql mysql-docs-en-5.0.26-1 MySQL-server-standard-5.0.26-0.rhel4 mysql-connector-j-5.0.3-1 MySQL-devel-standard-5.0.26-0.rhel4 mysql-query-browser-5.0r4-1rhel4 mysql-connector-odbc-3.51.12-1 MySQL-client-standard-5.0.26-0.rhel4 mysql-administrator-5.0r4-1rhel4 mysql-gui-tools-5.0r4-1rhel4 mysql-setup-wizard-1.0-1 mysql-connector-net-1.0.7-1 You can remove these packages individually, or all together automatically, like this: shell> rpm -q -a|grep -i mysql|xargs rpm --erase  File: manual.info, Node: installing-cs, Prev: installing-es, Up: installing 2.4 Installing MySQL Community Server ===================================== * Menu: * installing-cs-overview:: Overview of MySQL Community Server Installation * which-os:: Operating Systems Supported by MySQL Community Server * which-version:: Choosing Which MySQL Distribution to Install * getting-mysql:: How to Get MySQL * verifying-package-integrity:: Verifying Package Integrity Using MD5 Checksums or `GnuPG' * installation-layouts:: Installation Layouts * quick-standard-installation:: Standard MySQL Installation Using a Binary Distribution * windows-installation:: Installing MySQL on Windows * linux-rpm:: Installing MySQL from RPM Packages on Linux * mac-os-x-installation:: Installing MySQL on Mac OS X * solaris-installation:: Installing MySQL on Solaris * netware-installation:: Installing MySQL on NetWare * installing-binary:: Installing MySQL from `tar.gz' Packages on Other Unix-Like Systems * installing-source:: MySQL Installation Using a Source Distribution * post-installation:: Post-Installation Setup and Testing * upgrade:: Upgrading MySQL * downgrading:: Downgrading MySQL * operating-system-specific-notes:: Operating System-Specific Notes * environment-variables:: Environment Variables * perl-support:: Perl Installation Notes  File: manual.info, Node: installing-cs-overview, Next: which-os, Prev: installing-cs, Up: installing-cs 2.4.1 Overview of MySQL Community Server Installation ----------------------------------------------------- 1. *Determine whether MySQL runs and is supported on your platform.* Please note that not all platforms are equally suitable for running MySQL, and that not all platforms on which MySQL is known to run are officially supported by MySQL AB. For a list of platforms on which MySQL Community Server runs, see *Note which-os::. 2. *Choose which distribution to install.* Several versions of MySQL are available, and most are available in several distribution formats. You can choose from prepackaged distributions containing binary (precompiled) programs or source code. When in doubt, use a binary distribution. We also provide public access to our current source tree for those who want to see our most recent developments and help us test new code. To determine which version and type of distribution you should use, see *Note which-version::. 3. *Download the distribution that you want to install.* For instructions, see *Note getting-mysql::. To verify the integrity of the distribution, use the instructions in *Note verifying-package-integrity::. 4. *Install the distribution.* To install MySQL from a binary distribution, use the instructions in *Note quick-standard-installation::. To install MySQL from a source distribution or from the current development source tree, use the instructions in *Note installing-source::. If you encounter installation difficulties, see *Note operating-system-specific-notes::, for information on solving problems for particular platforms. 5. *Perform any necessary post-installation setup.* After installing MySQL, read *Note post-installation::. This section contains important information about making sure the MySQL server is working properly. It also describes how to secure the initial MySQL user accounts, _which have no passwords_ until you assign passwords. The section applies whether you install MySQL using a binary or source distribution. 6. If you want to run the MySQL benchmark scripts, Perl support for MySQL must be available. See *Note perl-support::. The immediately following sections contain the information necessary to choose, download, and verify your distribution. The instructions in later sections of the chapter describe how to install the distribution that you choose. For binary distributions, see the instructions at *Note quick-standard-installation::. To build MySQL from source, use the instructions at *Note installing-source::.  File: manual.info, Node: which-os, Next: which-version, Prev: installing-cs-overview, Up: installing-cs 2.4.2 Operating Systems Supported by MySQL Community Server ----------------------------------------------------------- This section does not apply to MySQL Enterprise Server users. This section lists the operating systems on which MySQL Community Server is known to run. *Important*: MySQL AB does not necessarily provide official support for all the platforms listed in this section. For information about those platforms which MySQL AB officially supports, see MySQL Server Supported Platforms (http://www.mysql.com/support/supportedplatforms.html) on the MySQL Web site. We use GNU Autoconf, so it is possible to port MySQL to all modern systems that have a C++ compiler and a working implementation of POSIX threads. (Thread support is needed for the server. To compile only the client code, the only requirement is a C++ compiler.) MySQL has been reported to compile successfully on the following combinations of operating system and thread package. * AIX 4.x, 5.x with native threads. See *Note ibm-aix::. * Amiga. * FreeBSD 5.x and up with native threads. * HP-UX 11.x with the native threads. See *Note hp-ux-11-x::. * Linux, builds on all fairly recent Linux distributions with `glibc' 2.3. See *Note linux::. * Mac OS X. See *Note mac-os-x::. * NetBSD 1.3/1.4 Intel and NetBSD 1.3 Alpha. See *Note netbsd::. * Novell NetWare 6.0 and 6.5. See *Note netware-installation::. * OpenBSD 2.5 and with native threads. OpenBSD earlier than 2.5 with the MIT-pthreads package. See *Note openbsd::. * SCO OpenServer 5.0.X with a recent port of the FSU Pthreads package. See *Note sco::. * SCO Openserver 6.0.x. See *Note sco-openserver::. * SCO UnixWare 7.1.x. See *Note sco-unixware::. * SGI Irix 6.x with native threads. See *Note sgi-irix::. * Solaris 2.5 and above with native threads on SPARC and x86. See *Note solaris::. * Tru64 Unix. See *Note alpha-dec-unix::. * Windows 2000, XP, and Windows Server 2003. See *Note windows-installation::. MySQL has also been known to run on other systems in the past. See *Note operating-system-specific-notes::. Some porting effort might be required for current versions of MySQL on these systems. Not all platforms are equally well suited for running MySQL. How well a certain platform is suited for a high-load mission-critical MySQL server is determined by the following factors: * General stability of the thread library. A platform may have an excellent reputation otherwise, but MySQL is only as stable as the thread library it calls, even if everything else is perfect. * The capability of the kernel and the thread library to take advantage of symmetric multi-processor (SMP) systems. In other words, when a process creates a thread, it should be possible for that thread to run on a CPU different from the original process. * The capability of the kernel and the thread library to run many threads that acquire and release a mutex over a short critical region frequently without excessive context switches. If the implementation of `pthread_mutex_lock()' is too anxious to yield CPU time, this hurts MySQL tremendously. If this issue is not taken care of, adding extra CPUs actually makes MySQL slower. * General filesystem stability and performance. * If your tables are large, performance is affected by the ability of the filesystem to deal with large files at all and to deal with them efficiently. * Our level of expertise here at MySQL AB with the platform. If we know a platform well, we enable platform-specific optimizations and fixes at compile time. We can also provide advice on configuring your system optimally for MySQL. * The amount of testing we have done internally for similar configurations. * The number of users that have run MySQL successfully on the platform in similar configurations. If this number is high, the likelihood of encountering platform-specific surprises is much smaller.  File: manual.info, Node: which-version, Next: getting-mysql, Prev: which-os, Up: installing-cs 2.4.3 Choosing Which MySQL Distribution to Install -------------------------------------------------- * Menu: * choosing-version:: Choosing Which Version of MySQL to Install * choosing-distribution-format:: Choosing a Distribution Format * many-versions:: How and When Updates Are Released * release-philosophy:: Release Philosophy---No Known Bugs in Releases * mysql-binaries:: MySQL Binaries Compiled by MySQL AB This section does not apply to MySQL Enterprise Server users. When preparing to install MySQL, you should decide which version to use. MySQL development occurs in several release series, and you can pick the one that best fits your needs. After deciding which version to install, you can choose a distribution format. Releases are available in binary or source format.  File: manual.info, Node: choosing-version, Next: choosing-distribution-format, Prev: which-version, Up: which-version 2.4.3.1 Choosing Which Version of MySQL to Install .................................................. This section does not apply to MySQL Enterprise Server users. The first decision to make is whether you want to use a production (stable) release or a development release. In the MySQL development process, multiple release series co-exist, each at a different stage of maturity: * MySQL 5.1 is the current development release series. * MySQL 5.0 is the current stable (production-quality) release series. New releases are issued for bugfixes only; no new features are being added that could effect stability. * MySQL 4.1 is the previous stable (production-quality) release series. New releases are issued for critical bugfixes and security fixes. No significant new features are to be added to this series. * MySQL 4.0 and 3.23 are the old stable (production-quality) release series. These versions are now retired, so new releases are issued only to fix extremely critical bugs (primarily security issues). We do not believe in a complete code freeze because this prevents us from making bugfixes and other fixes that must be done. By `somewhat frozen' we mean that we may add small things that should not affect anything that currently works in a production release. Naturally, relevant bugfixes from an earlier series propagate to later series. Normally, if you are beginning to use MySQL for the first time or trying to port it to some system for which there is no binary distribution, we recommend going with the production release series. Currently, this is MySQL 5.0. All MySQL releases, even those from development series, are checked with the MySQL benchmarks and an extensive test suite before being issued. If you are running an older system and want to upgrade, but do not want to take the chance of having a non-seamless upgrade, you should upgrade to the latest version in the same release series you are using (where only the last part of the version number is newer than yours). We have tried to fix only fatal bugs and make only small, relatively `safe' changes to that version. If you want to use new features not present in the production release series, you can use a version from a development series. Note that development releases are not as stable as production releases. If you want to use the very latest sources containing all current patches and bugfixes, you can use one of our BitKeeper repositories. These are not `releases' as such, but are available as previews of the code on which future releases are to be based. The MySQL naming scheme uses release names that consist of three numbers and a suffix; for example, *mysql-5.0.12-beta*. The numbers within the release name are interpreted as follows: * The first number (*5*) is the major version and describes the file format. All MySQL 5 releases have the same file format. * The second number (*0*) is the release level. Taken together, the major version and release level constitute the release series number. * The third number (*12*) is the version number within the release series. This is incremented for each new release. Usually you want the latest version for the series you have chosen. For each minor update, the last number in the version string is incremented. When there are major new features or minor incompatibilities with previous versions, the second number in the version string is incremented. When the file format changes, the first number is increased. Release names also include a suffix to indicates the stability level of the release. Releases within a series progress through a set of suffixes to indicate how the stability level improves. The possible suffixes are: * *alpha* indicates that the release is for preview purposes only. Known bugs should be documented in the News section (see *Note news::). Most alpha releases implement new commands and extensions. Active development that may involve major code changes can occur in an alpha release. However, we do conduct testing before issuing a release. * *beta* indicates that the release is appropriate for use with new development. Within beta releases, the features and compatibility should remain consistent. However, beta releases may contain numerous and major unaddressed bugs. All APIs, externally visible structures, and columns for SQL statements will not change during future beta, release candidate, or production releases. * *rc* indicates a Release Candidate. Release candidates are believed to be stable, having passed all of MySQL's internal testing, and with all known fatal runtime bugs fixed. However, the release has not been in widespread use long enough to know for sure that all bugs have been identified. Only minor fixes are added. (A release candidate is what formerly was known as a gamma release.) * If there is no suffix, it indicates that the release is a General Availability (GA) or Production release. GA releases are stable, having successfully passed through all earlier release stages and are believed to be reliable, free of serious bugs, and suitable for use in production systems. Only critical bugfixes are applied to the release. MySQL uses a naming scheme that is slightly different from most other products. In general, it is usually safe to use any version that has been out for a couple of weeks without being replaced by a new version within the same release series. All releases of MySQL are run through our standard tests and benchmarks to ensure that they are relatively safe to use. Because the standard tests are extended over time to check for all previously found bugs, the test suite keeps getting better. All releases have been tested at least with these tools: * An internal test suite The `mysql-test' directory contains an extensive set of test cases. We run these tests for every server binary. See *Note mysql-test-suite::, for more information about this test suite. * The MySQL benchmark suite This suite runs a range of common queries. It is also a test to determine whether the latest batch of optimizations actually made the code faster. See *Note mysql-benchmarks::. * The `crash-me' test This test tries to determine what features the database supports and what its capabilities and limitations are. See *Note mysql-benchmarks::. We also test the newest MySQL version in our internal production environment, on at least one machine. We have more than 100GB of data to work with.  File: manual.info, Node: choosing-distribution-format, Next: many-versions, Prev: choosing-version, Up: which-version 2.4.3.2 Choosing a Distribution Format ...................................... This section does not apply to MySQL Enterprise Server users. After choosing which version of MySQL to install, you should decide whether to use a binary distribution or a source distribution. In most cases, you should probably use a binary distribution, if one exists for your platform. Binary distributions are available in native format for many platforms, such as RPM files for Linux or PKG package installers for Mac OS X or Solaris. Distributions also are available as Zip archives or compressed `tar' files. Reasons to choose a binary distribution include the following: * Binary distributions generally are easier to install than source distributions. * To satisfy different user requirements, we provide several servers in binary distributions. `mysqld' is an optimized server that is a smaller, faster binary. `mysqld-debug' is compiled with debugging support. Each of these servers is compiled from the same source distribution, though with different configuration options. All native MySQL clients can connect to servers from either MySQL version. Under some circumstances, you may be better off installing MySQL from a source distribution: * You want to install MySQL at some explicit location. The standard binary distributions are ready to run at any installation location, but you might require even more flexibility to place MySQL components where you want. * You want to configure `mysqld' to ensure that features are available that might not be included in the standard binary distributions. Here is a list of the most common extra options that you may want to use to ensure feature availability: * `--with-berkeley-db' (not available on all platforms) * `--with-libwrap' * `--with-named-z-libs' (this is done for some of the binaries) * `--with-debug[=full]' * You want to configure `mysqld' without some features that are included in the standard binary distributions. For example, distributions normally are compiled with support for all character sets. If you want a smaller MySQL server, you can recompile it with support for only the character sets you need. * You have a special compiler (such as `pgcc') or want to use compiler options that are better optimized for your processor. Binary distributions are compiled with options that should work on a variety of processors from the same processor family. * You want to use the latest sources from one of the BitKeeper repositories to have access to all current bugfixes. For example, if you have found a bug and reported it to the MySQL development team, the bugfix is committed to the source repository and you can access it there. The bugfix does not appear in a release until a release actually is issued. * You want to read (or modify) the C and C++ code that makes up MySQL. For this purpose, you should get a source distribution, because the source code is always the ultimate manual. * Source distributions contain more tests and examples than binary distributions.  File: manual.info, Node: many-versions, Next: release-philosophy, Prev: choosing-distribution-format, Up: which-version 2.4.3.3 How and When Updates Are Released ......................................... MySQL is evolving quite rapidly and we want to share new developments with other MySQL users. We try to produce a new release whenever we have new and useful features that others also seem to have a need for. We also try to help users who request features that are easy to implement. We take note of what our licensed users want, and we especially take note of what our support customers want and try to help them in this regard. No one is _required_ to download a new release. The News section helps you determine whether the new release has something you really want. See *Note news::. We use the following policy when updating MySQL: * Enterprise Server releases are meant to appear every 18 months, supplemented by quarterly service packs and monthly rapid updates. Community Server releases are meant to appear 2-3 times per year. * Releases are issued within each series. Enterprise Server releases are numbered using even numbers (for example, 5.0.20). Community Server releases are numbered using odd numbers (for example, 5.0.21). * Binary distributions for some platforms are made by us for major releases. Other people may make binary distributions for other systems, but probably less frequently. * We make fixes available as soon as we have identified and corrected small or non-critical but annoying bugs. The fixes are available in source form immediately from our public BitKeeper repositories, and are included in the next release. * If by any chance a security vulnerability or critical bug is found in a release, our policy is to fix it in a new release as soon as possible. (We would like other companies to do this, too!)  File: manual.info, Node: release-philosophy, Next: mysql-binaries, Prev: many-versions, Up: which-version 2.4.3.4 Release Philosophy--No Known Bugs in Releases ..................................................... This section does not apply to MySQL Enterprise Server users. We put considerable time and effort into making our releases bug-free. Our policy is never to release a version of MySQL intended for production use that has any known fatal, repeatable bugs. We have documented all open problems, bugs, and issues that are dependent on design decisions. See *Note bugs::. Our aim is to fix everything that is fixable without making a stable MySQL version less stable. In certain cases, this means we can fix an issue in the development versions, but not in the stable (production) version. Naturally, we document such issues so that users are aware of them. Here is a description of our build process: * We monitor bugs from our customer support list, the bugs database at `http://bugs.mysql.com/', and the MySQL external mailing lists. * All reported bugs for live versions are entered into the bugs database. * When we fix a bug, we always try to make a test case for it and include it into our test system to ensure that the bug can never recur without being detected. (About 90% of all fixed bugs have test cases.) * We create test cases for each new feature that we add to MySQL. * Before we start to build a new MySQL release, we ensure that all reported repeatable bugs for that MySQL version (3.23.x, 4.0.x, 4.1.x, 5.0.x, 5.1.x, and so on) are fixed. If something is impossible to fix due to some internal design decision in MySQL, we document this in the manual. See *Note bugs::. * We do a build on all platforms for which we support binaries and run our test suite and benchmark suite on all of them. * We do not publish a binary for a platform for which the test or benchmark suite fails. If the problem is due to a general error in the source, we fix it and do the build plus tests on all systems again from scratch. * The build and test process takes a week. If we receive a report regarding a fatal bug during this process (for example, one that causes a core dump), we fix the problem and restart the build process. * After publishing the binaries on `http://dev.mysql.com/', we send out an announcement message to the `mysql' and `announce' mailing lists. See *Note mailing-lists::. The announcement message contains a list of all changes to the release and any known problems with the release. The *Known Problems* section in the release notes has been needed for only a handful of releases. * To quickly give our users access to the latest MySQL features, we try to produce a new MySQL release every 4-8 weeks. Source code snapshots are built daily and are available at `http://downloads.mysql.com/snapshots.php'. * If, despite our best efforts, we receive any bug reports after a release is issued that a critical problem exists for the build on a specific platform, we fix it at once and build a new `'a'' release for that platform. Thanks to our large user base, problems are found and resolved very quickly. * Our track record for making stable releases is quite good. In the last 150 releases, we had to do a new build for fewer than 10 of them. In three of these cases, the bug was a faulty `glibc' library on one of our build machines that took us a long time to track down.  File: manual.info, Node: mysql-binaries, Prev: release-philosophy, Up: which-version 2.4.3.5 MySQL Binaries Compiled by MySQL AB ........................................... This section does not apply to MySQL Enterprise Server users. As a service of MySQL AB, we provide a set of binary distributions of MySQL that are compiled on systems at our site or on systems where supporters of MySQL kindly have given us access to their machines. In addition to the binaries provided in platform-specific package formats, we offer binary distributions for a number of platforms in the form of compressed `tar' files (`.tar.gz' files). See *Note quick-standard-installation::. The RPM distributions for MySQL 5.0 releases that we make available through our Web site are generated by MySQL AB. For Windows distributions, see *Note windows-installation::. These distributions are generated using the script `Build-tools/Do-compile', which compiles the source code and creates the binary `tar.gz' archive using `scripts/make_binary_distribution'. These binaries are configured and built with the following compilers and options. This information can also be obtained by looking at the variables `COMP_ENV_INFO' and `CONFIGURE_LINE' inside the script `bin/mysqlbug' of every binary `tar' file distribution. Anyone who has more optimal options for any of the following `configure' commands can mail them to the MySQL `internals' mailing list. See *Note mailing-lists::. If you want to compile a debug version of MySQL, you should add `--with-debug' or `--with-debug=full' to the following `configure' commands and remove any `-fomit-frame-pointer' options. The following binaries are built on MySQL AB development systems: * Linux 2.4.xx x86 with `gcc' 2.95.3: CFLAGS="-O2 -mcpu=pentiumpro" CXX=gcc CXXFLAGS="-O2 -mcpu=pentiumpro -felide-constructors" ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex --enable-thread-safe-client --enable-local-infile --enable-assembler --disable-shared --with-client-ldflags=-all-static --with-mysqld-ldflags=-all-static * Linux 2.4.x x86 with `icc' (Intel C++ Compiler 8.1 or later releases): CC=icc CXX=icpc CFLAGS="-O3 -unroll2 -ip -mp -no-gcc -restrict" CXXFLAGS="-O3 -unroll2 -ip -mp -no-gcc -restrict" ./configure --prefix=/usr/local/mysql --localstatedir=/usr/local/mysql/data --libexecdir=/usr/local/mysql/bin --with-extra-charsets=complex --enable-thread-safe-client --enable-local-infile --enable-assembler --disable-shared --with-client-ldflags=-all-static --with-mysqld-ldflags=-all-static --with-embedded-server --with-innodb Note that versions 8.1 and newer of the Intel compiler have separate drivers for 'pure' C (`icc') and C++ (`icpc'); if you use `icc' version 8.0 or older for building MySQL, you will need to set `CXX=icc'. * Linux 2.4.xx Intel Itanium 2 with `ecc' (Intel C++ Itanium Compiler 7.0): CC=ecc CFLAGS="-O2 -tpp2 -ip -nolib_inline" CXX=ecc CXXFLAGS="-O2 -tpp2 -ip -nolib_inline" ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex --enable-thread-safe-client --enable-local-infile * Linux 2.4.xx Intel Itanium with `ecc' (Intel C++ Itanium Compiler 7.0): CC=ecc CFLAGS=-tpp1 CXX=ecc CXXFLAGS=-tpp1 ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex --enable-thread-safe-client --enable-local-infile * Linux 2.4.xx alpha with `ccc' (Compaq C V6.2-505 / Compaq C++ V6.3-006): CC=ccc CFLAGS="-fast -arch generic" CXX=cxx CXXFLAGS="-fast -arch generic -noexceptions -nortti" ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex --enable-thread-safe-client --enable-local-infile --with-mysqld-ldflags=-non_shared --with-client-ldflags=-non_shared --disable-shared * Linux 2.x.xx ppc with `gcc' 2.95.4: CC=gcc CFLAGS="-O3 -fno-omit-frame-pointer" CXX=gcc CXXFLAGS="-O3 -fno-omit-frame-pointer -felide-constructors -fno-exceptions -fno-rtti" ./configure --prefix=/usr/local/mysql --localstatedir=/usr/local/mysql/data --libexecdir=/usr/local/mysql/bin --with-extra-charsets=complex --enable-thread-safe-client --enable-local-infile --disable-shared --with-embedded-server --with-innodb * Linux 2.4.xx s390 with `gcc' 2.95.3: CFLAGS="-O2" CXX=gcc CXXFLAGS="-O2 -felide-constructors" ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex --enable-thread-safe-client --enable-local-infile --disable-shared --with-client-ldflags=-all-static --with-mysqld-ldflags=-all-static * Linux 2.4.xx x86_64 (AMD64) with `gcc' 3.2.1: CXX=gcc ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex --enable-thread-safe-client --enable-local-infile --disable-shared * Sun Solaris 8 x86 with `gcc' 3.2.3: CC=gcc CFLAGS="-O3 -fno-omit-frame-pointer" CXX=gcc CXXFLAGS="-O3 -fno-omit-frame-pointer -felide-constructors -fno-exceptions -fno-rtti" ./configure --prefix=/usr/local/mysql --localstatedir=/usr/local/mysql/data --libexecdir=/usr/local/mysql/bin --with-extra-charsets=complex --enable-thread-safe-client --enable-local-infile --disable-shared --with-innodb * Sun Solaris 8 SPARC with `gcc' 3.2: CC=gcc CFLAGS="-O3 -fno-omit-frame-pointer" CXX=gcc CXXFLAGS="-O3 -fno-omit-frame-pointer -felide-constructors -fno-exceptions -fno-rtti" ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex --enable-thread-safe-client --enable-local-infile --enable-assembler --with-named-z-libs=no --with-named-curses-libs=-lcurses --disable-shared * Sun Solaris 8 SPARC 64-bit with `gcc' 3.2: CC=gcc CFLAGS="-O3 -m64 -fno-omit-frame-pointer" CXX=gcc CXXFLAGS="-O3 -m64 -fno-omit-frame-pointer -felide-constructors -fno-exceptions -fno-rtti" ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex --enable-thread-safe-client --enable-local-infile --with-named-z-libs=no --with-named-curses-libs=-lcurses --disable-shared * Sun Solaris 9 SPARC with `gcc' 2.95.3: CC=gcc CFLAGS="-O3 -fno-omit-frame-pointer" CXX=gcc CXXFLAGS="-O3 -fno-omit-frame-pointer -felide-constructors -fno-exceptions -fno-rtti" ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex --enable-thread-safe-client --enable-local-infile --enable-assembler --with-named-curses-libs=-lcurses --disable-shared * Sun Solaris 9 SPARC with `cc-5.0' (Sun Forte 5.0): CC=cc-5.0 CXX=CC ASFLAGS="-xarch=v9" CFLAGS="-Xa -xstrconst -mt -D_FORTEC_ -xarch=v9" CXXFLAGS="-noex -mt -D_FORTEC_ -xarch=v9" ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex --enable-thread-safe-client --enable-local-infile --enable-assembler --with-named-z-libs=no --enable-thread-safe-client --disable-shared * IBM AIX 4.3.2 ppc with `gcc' 3.2.3: CFLAGS="-O2 -mcpu=powerpc -Wa,-many " CXX=gcc CXXFLAGS="-O2 -mcpu=powerpc -Wa,-many -felide-constructors -fno-exceptions -fno-rtti" ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex --enable-thread-safe-client --enable-local-infile --with-named-z-libs=no --disable-shared * IBM AIX 4.3.3 ppc with `xlC_r' (IBM Visual Age C/C++ 6.0): CC=xlc_r CFLAGS="-ma -O2 -qstrict -qoptimize=2 -qmaxmem=8192" CXX=xlC_r CXXFLAGS ="-ma -O2 -qstrict -qoptimize=2 -qmaxmem=8192" ./configure --prefix=/usr/local/mysql --localstatedir=/usr/local/mysql/data --libexecdir=/usr/local/mysql/bin --with-extra-charsets=complex --enable-thread-safe-client --enable-local-infile --with-named-z-libs=no --disable-shared --with-innodb * IBM AIX 5.1.0 ppc with `gcc' 3.3: CFLAGS="-O2 -mcpu=powerpc -Wa,-many" CXX=gcc CXXFLAGS="-O2 -mcpu=powerpc -Wa,-many -felide-constructors -fno-exceptions -fno-rtti" ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex --enable-thread-safe-client --enable-local-infile --with-named-z-libs=no --disable-shared * IBM AIX 5.2.0 ppc with `xlC_r' (IBM Visual Age C/C++ 6.0): CC=xlc_r CFLAGS="-ma -O2 -qstrict -qoptimize=2 -qmaxmem=8192" CXX=xlC_r CXXFLAGS="-ma -O2 -qstrict -qoptimize=2 -qmaxmem=8192" ./configure --prefix=/usr/local/mysql --localstatedir=/usr/local/mysql/data --libexecdir=/usr/local/mysql/bin --with-extra-charsets=complex --enable-thread-safe-client --enable-local-infile --with-named-z-libs=no --disable-shared --with-embedded-server --with-innodb * HP-UX 10.20 pa-risc1.1 with `gcc' 3.1: CFLAGS="-DHPUX -I/opt/dce/include -O3 -fPIC" CXX=gcc CXXFLAGS="-DHPUX -I/opt/dce /include -felide-constructors -fno-exceptions -fno-rtti -O3 -fPIC" ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex --enable-thread-safe-client --enable-local-infile --with-pthread --with-named-thread-libs=-ldce --with-lib-ccflags=-fPIC --disable-shared * HP-UX 11.00 pa-risc with `aCC' (HP ANSI C++ B3910B A.03.50): CC=cc CXX=aCC CFLAGS=+DAportable CXXFLAGS=+DAportable ./configure --prefix=/usr/local/mysql --localstatedir=/usr/local/mysql/data --libexecdir=/usr/local/mysql/bin --with-extra-charsets=complex --enable-thread-safe-client --enable-local-infile --disable-shared --with-embedded-server --with-innodb * HP-UX 11.11 pa-risc2.0 64bit with `aCC' (HP ANSI C++ B3910B A.03.33): CC=cc CXX=aCC CFLAGS=+DD64 CXXFLAGS=+DD64 ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex --enable-thread-safe-client --enable-local-infile --disable-shared * HP-UX 11.11 pa-risc2.0 32bit with `aCC' (HP ANSI C++ B3910B A.03.33): CC=cc CXX=aCC CFLAGS="+DAportable" CXXFLAGS="+DAportable" ./configure --prefix=/usr/local/mysql --localstatedir=/usr/local/mysql/data --libexecdir=/usr/local/mysql/bin --with-extra-charsets=complex --enable-thread-safe-client --enable-local-infile --disable-shared --with-innodb * HP-UX 11.22 ia64 64bit with `aCC' (HP aC++/ANSI C B3910B A.05.50): CC=cc CXX=aCC CFLAGS="+DD64 +DSitanium2" CXXFLAGS="+DD64 +DSitanium2" ./configure --prefix=/usr/local/mysql --localstatedir=/usr/local/mysql/data --libexecdir=/usr/local/mysql/bin --with-extra-charsets=complex --enable-thread-safe-client --enable-local-infile --disable-shared --with-embedded-server --with-innodb * Apple Mac OS X 10.2 powerpc with `gcc' 3.1: CC=gcc CFLAGS="-O3 -fno-omit-frame-pointer" CXX=gcc CXXFLAGS="-O3 -fno-omit-frame-pointer -felide-constructors -fno-exceptions -fno-rtti" ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex --enable-thread-safe-client --enable-local-infile --disable-shared * FreeBSD 4.7 i386 with `gcc' 2.95.4: CFLAGS=-DHAVE_BROKEN_REALPATH ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex --enable-thread-safe-client --enable-local-infile --enable-assembler --with-named-z-libs=not-used --disable-shared * FreeBSD 4.7 i386 using LinuxThreads with `gcc' 2.95.4: CFLAGS="-DHAVE_BROKEN_REALPATH -D__USE_UNIX98 -D_REENTRANT -D_THREAD_SAFE -I/usr/local/include/pthread/linuxthreads" CXXFLAGS="-DHAVE_BROKEN_REALPATH -D__USE_UNIX98 -D_REENTRANT -D_THREAD_SAFE -I/usr/local/include/pthread/linuxthreads" ./configure --prefix=/usr/local/mysql --localstatedir=/usr/local/mysql/data --libexecdir=/usr/local/mysql/bin --enable-thread-safe-client --enable-local-infile --enable-assembler --with-named-thread-libs="-DHAVE_GLIBC2_STYLE_GETHOSTBYNAME_R -D_THREAD_SAFE -I /usr/local/include/pthread/linuxthreads -L/usr/local/lib -llthread -llgcc_r" --disable-shared --with-embedded-server --with-innodb * QNX Neutrino 6.2.1 i386 with `gcc' 2.95.3qnx-nto 20010315: CC=gcc CFLAGS="-O3 -fno-omit-frame-pointer" CXX=gcc CXXFLAGS="-O3 -fno-omit-frame-pointer -felide-constructors -fno-exceptions -fno-rtti" ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex --enable-thread-safe-client --enable-local-infile --disable-shared The following binaries are built on third-party systems kindly provided to MySQL AB by other users. These are provided only as a courtesy; MySQL AB does not have full control over these systems, so we can provide only limited support for the binaries built on them. * SCO Unix 3.2v5.0.7 i386 with `gcc' 2.95.3: CFLAGS="-O3 -mpentium" LDFLAGS=-static CXX=gcc CXXFLAGS="-O3 -mpentium -felide-constructors" ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex --enable-thread-safe-client --enable-local-infile --with-named-z-libs=no --enable-thread-safe-client --disable-shared * SCO UnixWare 7.1.4 i386 with `CC' 3.2: CC=cc CFLAGS="-O" CXX=CC ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex --enable-thread-safe-client --enable-local-infile --with-named-z-libs=no --enable-thread-safe-client --disable-shared --with-readline * SCO OpenServer 6.0.0 i386 with `CC' 3.2: CC=cc CFLAGS="-O" CXX=CC ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex --enable-thread-safe-client --enable-local-infile --with-named-z-libs=no --enable-thread-safe-client --disable-shared --with-readline * Compaq Tru64 OSF/1 V5.1 732 alpha with `cc/cxx' (Compaq C V6.3-029i / DIGITAL C++ V6.1-027): CC="cc -pthread" CFLAGS="-O4 -ansi_alias -ansi_args -fast -inline speed -speculate all" CXX="cxx -pthread" CXXFLAGS="-O4 -ansi_alias -fast -inline speed -speculate all -noexceptions -nortti" ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex --enable-thread-safe-client --enable-local-infile --with-named-thread-libs="-lpthread -lmach -lexc -lc" --disable-shared --with-mysqld-ldflags=-all-static * SGI Irix 6.5 IP32 with `gcc' 3.0.1: CC=gcc CFLAGS="-O3 -fno-omit-frame-pointer" CXXFLAGS="-O3 -fno-omit-frame-pointer -felide-constructors -fno-exceptions -fno-rtti" ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex --enable-thread-safe-client --enable-local-infile --disable-shared * FreeBSD/sparc64 5.0 with `gcc' 3.2.1: CFLAGS=-DHAVE_BROKEN_REALPATH ./configure --prefix=/usr/local/mysql --localstatedir=/usr/local/mysql/data --libexecdir=/usr/local/mysql/bin --with-extra-charsets=complex --enable-thread-safe-client --enable-local-infile --disable-shared --with-innodb The following compile options have been used for binary packages that MySQL AB provided in the past. These binaries no longer are being updated, but the compile options are listed here for reference purposes. * Linux 2.2.xx SPARC with `egcs' 1.1.2: CC=gcc CFLAGS="-O3 -fno-omit-frame-pointer" CXX=gcc CXXFLAGS="-O3 -fno-omit-frame-pointer -felide-constructors -fno-exceptions -fno-rtti" ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex --enable-thread-safe-client --enable-local-infile --enable-assembler --disable-shared * Linux 2.2.x with x686 with `gcc' 2.95.2: CFLAGS="-O3 -mpentiumpro" CXX=gcc CXXFLAGS="-O3 -mpentiumpro -felide-constructors -fno-exceptions -fno-rtti" ./configure --prefix=/usr/local/mysql --enable-assembler --with-mysqld-ldflags=-all-static --disable-shared --with-extra-charsets=complex * SunOS 4.1.4 2 sun4c with `gcc' 2.7.2.1: CC=gcc CXX=gcc CXXFLAGS="-O3 -felide-constructors" ./configure --prefix=/usr/local/mysql --disable-shared --with-extra-charsets=complex --enable-assembler * SunOS 5.5.1 (and above) sun4u with `egcs' 1.0.3a or 2.90.27 or `gcc' 2.95.2 and newer: CC=gcc CFLAGS="-O3" CXX=gcc CXXFLAGS="-O3 -felide-constructors -fno-exceptions -fno-rtti" ./configure --prefix=/usr/local/mysql --with-low-memory --with-extra-charsets=complex --enable-assembler * SunOS 5.6 i86pc with `gcc' 2.8.1: CC=gcc CXX=gcc CXXFLAGS=-O3 ./configure --prefix=/usr/local/mysql --with-low-memory --with-extra-charsets=complex * BSDI BSD/OS 3.1 i386 with `gcc' 2.7.2.1: CC=gcc CXX=gcc CXXFLAGS=-O ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex * BSDI BSD/OS 2.1 i386 with `gcc' 2.7.2: CC=gcc CXX=gcc CXXFLAGS=-O3 ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex * AIX 4.2 with `gcc' 2.7.2.2: CC=gcc CXX=gcc CXXFLAGS=-O3 ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex  File: manual.info, Node: getting-mysql, Next: verifying-package-integrity, Prev: which-version, Up: installing-cs 2.4.4 How to Get MySQL ---------------------- This section does not apply to MySQL Enterprise Server users. Check our downloads page at `http://dev.mysql.com/downloads/' for information about the current version of MySQL and for downloading instructions. For a complete up-to-date list of MySQL download mirror sites, see `http://dev.mysql.com/downloads/mirrors.html'. You can also find information there about becoming a MySQL mirror site and how to report a bad or out-of-date mirror. Our main mirror is located at `http://mirrors.sunsite.dk/mysql/'.  File: manual.info, Node: verifying-package-integrity, Next: installation-layouts, Prev: getting-mysql, Up: installing-cs 2.4.5 Verifying Package Integrity Using MD5 Checksums or `GnuPG' ---------------------------------------------------------------- * Menu: * verifying-md5-checksum:: Verifying the MD5 Checksum * checking-gpg-signature:: Signature Checking Using `GnuPG' * checking-rpm-signature:: Signature Checking Using `RPM' This section does not apply to MySQL Enterprise Server users. After you have downloaded the MySQL package that suits your needs and before you attempt to install it, you should make sure that it is intact and has not been tampered with. MySQL AB offers three means of integrity checking: * MD5 checksums * Cryptographic signatures using `GnuPG', the GNU Privacy Guard * For RPM packages, the built-in RPM integrity verification mechanism The following sections describe how to use these methods. If you notice that the MD5 checksum or GPG signatures do not match, first try to download the respective package one more time, perhaps from another mirror site. If you repeatedly cannot successfully verify the integrity of the package, please notify us about such incidents, including the full package name and the download site you have been using, at or . Do not report downloading problems using the bug-reporting system.  File: manual.info, Node: verifying-md5-checksum, Next: checking-gpg-signature, Prev: verifying-package-integrity, Up: verifying-package-integrity 2.4.5.1 Verifying the MD5 Checksum .................................. This section does not apply to MySQL Enterprise Server users. After you have downloaded a MySQL package, you should make sure that its MD5 checksum matches the one provided on the MySQL download pages. Each package has an individual checksum that you can verify with the following command, where PACKAGE_NAME is the name of the package you downloaded: shell> md5sum PACKAGE_NAME Example: shell> md5sum mysql-standard-5.0.46-linux-i686.tar.gz aaab65abbec64d5e907dcd41b8699945 mysql-standard-5.0.46-linux-i686.tar.gz You should verify that the resulting checksum (the string of hexadecimal digits) matches the one displayed on the download page immediately below the respective package. *Note*: Make sure to verify the checksum of the _archive file_ (for example, the `.zip' or `.tar.gz' file) and not of the files that are contained inside of the archive. Note that not all operating systems support the `md5sum' command. On some, it is simply called `md5', and others do not ship it at all. On Linux, it is part of the *GNU Text Utilities* package, which is available for a wide range of platforms. You can download the source code from `http://www.gnu.org/software/textutils/' as well. If you have OpenSSL installed, you can use the command `openssl md5 PACKAGE_NAME' instead. A Windows implementation of the `md5' command line utility is available from `http://www.fourmilab.ch/md5/'. `winMd5Sum' is a graphical MD5 checking tool that can be obtained from `http://www.nullriver.com/index/products/winmd5sum'.  File: manual.info, Node: checking-gpg-signature, Next: checking-rpm-signature, Prev: verifying-md5-checksum, Up: verifying-package-integrity 2.4.5.2 Signature Checking Using `GnuPG' ........................................ This section does not apply to MySQL Enterprise Server users. Another method of verifying the integrity and authenticity of a package is to use cryptographic signatures. This is more reliable than using MD5 checksums, but requires more work. At MySQL AB, we sign MySQL downloadable packages with `GnuPG' (GNU Privacy Guard). `GnuPG' is an Open Source alternative to the well-known Pretty Good Privacy (`PGP') by Phil Zimmermann. See `http://www.gnupg.org/' for more information about `GnuPG' and how to obtain and install it on your system. Most Linux distributions ship with `GnuPG' installed by default. For more information about `GnuPG', see `http://www.openpgp.org/'. To verify the signature for a specific package, you first need to obtain a copy of MySQL AB's public GPG build key, which you can download from `http://www.keyserver.net/'. The key that you want to obtain is named `build@mysql.com'. Alternatively, you can cut and paste the key directly from the following text: Key ID: pub 1024D/5072E1F5 2003-02-03 MySQL Package signing key (www.mysql.com) Fingerprint: A4A9 4068 76FC BD3C 4567 70C8 8C71 8D3B 5072 E1F5 Public Key (ASCII-armored): -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org mQGiBD4+owwRBAC14GIfUfCyEDSIePvEW3SAFUdJBtoQHH/nJKZyQT7h9bPlUWC3 RODjQReyCITRrdwyrKUGku2FmeVGwn2u2WmDMNABLnpprWPkBdCk96+OmSLN9brZ fw2vOUgCmYv2hW0hyDHuvYlQA/BThQoADgj8AW6/0Lo7V1W9/8VuHP0gQwCgvzV3 BqOxRznNCRCRxAuAuVztHRcEAJooQK1+iSiunZMYD1WufeXfshc57S/+yeJkegNW hxwR9pRWVArNYJdDRT+rf2RUe3vpquKNQU/hnEIUHJRQqYHo8gTxvxXNQc7fJYLV K2HtkrPbP72vwsEKMYhhr0eKCbtLGfls9krjJ6sBgACyP/Vb7hiPwxh6rDZ7ITnE kYpXBACmWpP8NJTkamEnPCia2ZoOHODANwpUkP43I7jsDmgtobZX9qnrAXw+uNDI QJEXM6FSbi0LLtZciNlYsafwAPEOMDKpMqAK6IyisNtPvaLd8lH0bPAnWqcyefep rv0sxxqUEMcM3o7wwgfN83POkDasDbs3pjwPhxvhz6//62zQJ7Q7TXlTUUwgUGFj a2FnZSBzaWduaW5nIGtleSAod3d3Lm15c3FsLmNvbSkgPGJ1aWxkQG15c3FsLmNv bT6IXQQTEQIAHQUCPj6jDAUJCWYBgAULBwoDBAMVAwIDFgIBAheAAAoJEIxxjTtQ cuH1cY4AnilUwTXn8MatQOiG0a/bPxrvK/gCAJ4oinSNZRYTnblChwFaazt7PF3q zIhMBBMRAgAMBQI+PqPRBYMJZgC7AAoJEElQ4SqycpHyJOEAn1mxHijft00bKXvu cSo/pECUmppiAJ41M9MRVj5VcdH/KN/KjRtW6tHFPYhMBBMRAgAMBQI+QoIDBYMJ YiKJAAoJELb1zU3GuiQ/lpEAoIhpp6BozKI8p6eaabzF5MlJH58pAKCu/ROofK8J Eg2aLos+5zEYrB/LsrkCDQQ+PqMdEAgA7+GJfxbMdY4wslPnjH9rF4N2qfWsEN/l xaZoJYc3a6M02WCnHl6ahT2/tBK2w1QI4YFteR47gCvtgb6O1JHffOo2HfLmRDRi Rjd1DTCHqeyX7CHhcghj/dNRlW2Z0l5QFEcmV9U0Vhp3aFfWC4Ujfs3LU+hkAWzE 7zaD5cH9J7yv/6xuZVw411x0h4UqsTcWMu0iM1BzELqX1DY7LwoPEb/O9Rkbf4fm Le11EzIaCa4PqARXQZc4dhSinMt6K3X4BrRsKTfozBu74F47D8Ilbf5vSYHbuE5p /1oIDznkg/p8kW+3FxuWrycciqFTcNz215yyX39LXFnlLzKUb/F5GwADBQf+Lwqq a8CGrRfsOAJxim63CHfty5mUc5rUSnTslGYEIOCR1BeQauyPZbPDsDD9MZ1ZaSaf anFvwFG6Llx9xkU7tzq+vKLoWkm4u5xf3vn55VjnSd1aQ9eQnUcXiL4cnBGoTbOW I39EcyzgslzBdC++MPjcQTcA7p6JUVsP6oAB3FQWg54tuUo0Ec8bsM8b3Ev42Lmu QT5NdKHGwHsXTPtl0klk4bQk4OajHsiy1BMahpT27jWjJlMiJc+IWJ0mghkKHt92 6s/ymfdf5HkdQ1cyvsz5tryVI3Fx78XeSYfQvuuwqp2H139pXGEkg0n6KdUOetdZ Whe70YGNPw1yjWJT1IhMBBgRAgAMBQI+PqMdBQkJZgGAAAoJEIxxjTtQcuH17p4A n3r1QpVC9yhnW2cSAjq+kr72GX0eAJ4295kl6NxYEuFApmr1+0uUq/SlsQ== =YJkx -----END PGP PUBLIC KEY BLOCK----- To import the build key into your personal public GPG keyring, use `gpg --import'. For example, if you have saved the key in a file named `mysql_pubkey.asc', the import command looks like this: shell> gpg --import mysql_pubkey.asc After you have downloaded and imported the public build key, download your desired MySQL package and the corresponding signature, which also is available from the download page. The signature file has the same name as the distribution file with an `.asc' extension. For example: Distribution `mysql-standard-5.0.46-linux-i686.tar.gz' file Signature file `mysql-standard-5.0.46-linux-i686.tar.gz.asc' Make sure that both files are stored in the same directory and then run the following command to verify the signature for the distribution file: shell> gpg --verify PACKAGE_NAME.asc Example: shell> gpg --verify mysql-standard-5.0.46-linux-i686.tar.gz.asc gpg: Signature made Tue 12 Jul 2005 23:35:41 EST using DSA key ID 5072E1F5 gpg: Good signature from "MySQL Package signing key (www.mysql.com) " The `Good signature' message indicates that everything is all right. You can ignore any `insecure memory' warning you might obtain. See the GPG documentation for more information on how to work with public keys.  File: manual.info, Node: checking-rpm-signature, Prev: checking-gpg-signature, Up: verifying-package-integrity 2.4.5.3 Signature Checking Using `RPM' ...................................... This section does not apply to MySQL Enterprise Server users. For RPM packages, there is no separate signature. RPM packages have a built-in GPG signature and MD5 checksum. You can verify a package by running the following command: shell> rpm --checksig PACKAGE_NAME.rpm Example: shell> rpm --checksig MySQL-server-5.0.46-0.glibc23.i386.rpm MySQL-server-5.0.46-0.glibc23.i386.rpm: md5 gpg OK *Note*: If you are using RPM 4.1 and it complains about `(GPG) NOT OK (MISSING KEYS: GPG#5072e1f5)', even though you have imported the MySQL public build key into your own GPG keyring, you need to import the key into the RPM keyring first. RPM 4.1 no longer uses your personal GPG keyring (or GPG itself). Rather, it maintains its own keyring because it is a system-wide application and a user's GPG public keyring is a user-specific file. To import the MySQL public key into the RPM keyring, first obtain the key as described in *Note checking-gpg-signature::. Then use `rpm --import' to import the key. For example, if you have saved the public key in a file named `mysql_pubkey.asc', import it using this command: shell> rpm --import mysql_pubkey.asc If you need to obtain the MySQL public key, see *Note checking-gpg-signature::.  File: manual.info, Node: installation-layouts, Next: quick-standard-installation, Prev: verifying-package-integrity, Up: installing-cs 2.4.6 Installation Layouts -------------------------- This section describes the default layout of the directories created by installing binary or source distributions provided by MySQL AB. A distribution provided by another vendor might use a layout different from those shown here. For MySQL 5.0 on Windows, the default installation directory is `C:\Program Files\MySQL\MySQL Server 5.0'. (Some Windows users prefer to install in `C:\mysql', the directory that formerly was used as the default. However, the layout of the subdirectories remains the same.) The installation directory has the following subdirectories: *Directory* *Contents of Directory* `bin' Client programs and the `mysqld' server `data' Log files, databases `Docs' Manual in CHM format `examples' Example programs and scripts `include' Include (header) files `lib' Libraries `scripts' Utility scripts `share' Error message files Installations created from MySQL AB's Linux RPM distributions result in files under the following system directories: *Directory* *Contents of Directory* `/usr/bin' Client programs and scripts `/usr/sbin' The `mysqld' server `/var/lib/mysql' Log files, databases `/usr/share/info' Manual in Info format `/usr/share/man' Unix manual pages `/usr/include/mysql' Include (header) files `/usr/lib/mysql' Libraries `/usr/share/mysql' Error message and character set files `/usr/share/sql-bench' Benchmarks On Unix, a `tar' file binary distribution is installed by unpacking it at the installation location you choose (typically `/usr/local/mysql') and creates the following directories in that location: *Directory* *Contents of Directory* `bin' Client programs and the `mysqld' server `data' Log files, databases `docs' Manual in Info format `man' Unix manual pages `include' Include (header) files `lib' Libraries `scripts' `mysql_install_db' `share/mysql' Error message files `sql-bench' Benchmarks A source distribution is installed after you configure and compile it. By default, the installation step installs files under `/usr/local', in the following subdirectories: *Directory* *Contents of Directory* `bin' Client programs and scripts `include/mysql' Include (header) files `Docs' Manual in Info, CHM formats `man' Unix manual pages `lib/mysql' Libraries `libexec' The `mysqld' server `share/mysql' Error message files `sql-bench' Benchmarks and `crash-me' test `var' Databases and log files Within its installation directory, the layout of a source installation differs from that of a binary installation in the following ways: * The `mysqld' server is installed in the `libexec' directory rather than in the `bin' directory. * The data directory is `var' rather than `data'. * `mysql_install_db' is installed in the `bin' directory rather than in the `scripts' directory. * The header file and library directories are `include/mysql' and `lib/mysql' rather than `include' and `lib'. You can create your own binary installation from a compiled source distribution by executing the `scripts/make_binary_distribution' script from the top directory of the source distribution.  File: manual.info, Node: quick-standard-installation, Next: windows-installation, Prev: installation-layouts, Up: installing-cs 2.4.7 Standard MySQL Installation Using a Binary Distribution ------------------------------------------------------------- This section does not apply to MySQL Enterprise Server users. The next several sections cover the installation of MySQL on platforms where we offer packages using the native packaging format of the respective platform. (This is also known as performing a `binary install.') However, binary distributions of MySQL are available for many other platforms as well. See *Note installing-binary::, for generic installation instructions for these packages that apply to all platforms. See *Note installing-cs::, for more information on what other binary distributions are available and how to obtain them.  File: manual.info, Node: windows-installation, Next: linux-rpm, Prev: quick-standard-installation, Up: installing-cs 2.4.8 Installing MySQL on Windows --------------------------------- * Menu: * windows-choosing-package:: Choosing An Installation Package * windows-using-installer:: Installing MySQL with the Automated Installer * windows-install-wizard:: Using the MySQL Installation Wizard * windows-config-wizard:: MySQL Windows Configuration Wizard * windows-install-archive:: Installing MySQL from a Noinstall Zip Archive * windows-extract-archive:: Extracting the Install Archive * windows-create-option-file:: Creating an Option File * windows-select-server:: Selecting a MySQL Server Type * windows-server-first-start:: Starting the Server for the First Time * windows-start-command-line:: Starting MySQL from the Windows Command Line * windows-start-service:: Starting MySQL as a Windows Service * windows-testing:: Testing The MySQL Installation * windows-troubleshooting:: Troubleshooting a MySQL Installation Under Windows * windows-upgrading:: Upgrading MySQL on Windows * windows-vs-unix:: MySQL on Windows Compared to MySQL on Unix This section does not apply to MySQL Enterprise Server users. A native Windows distribution of MySQL has been available from MySQL AB since version 3.21 and represents a sizable percentage of the daily downloads of MySQL. This section describes the process for installing MySQL on Windows. *Note*: If you are upgrading MySQL from an existing installation older than MySQL 4.1.5, you must first perform the procedure described in *Note windows-upgrading::. To run MySQL on Windows, you need the following: * A 32-bit Windows operating system such as 2000, XP, or Windows Server 2003. A Windows operating system permits you to run the MySQL server as a service. See *Note windows-start-service::. Generally, you should install MySQL on Windows using an account that has administrator rights. Otherwise, you may encounter problems with certain operations such as editing the `PATH' environment variable or accessing the `Service Control Manager'. * TCP/IP protocol support. * Enough space on the hard drive to unpack, install, and create the databases in accordance with your requirements (generally a minimum of 200 megabytes is recommended.) There may also be other requirements, depending on how you plan to use MySQL: * If you plan to connect to the MySQL server via ODBC, you need a Connector/ODBC driver. See *Note connectors::. * If you need tables with a size larger than 4GB, install MySQL on an NTFS or newer filesystem. Don't forget to use `MAX_ROWS' and `AVG_ROW_LENGTH' when you create tables. See *Note create-table::. MySQL for Windows is available in several distribution formats: * Binary distributions are available that contain a setup program that installs everything you need so that you can start the server immediately. Another binary distribution format contains an archive that you simply unpack in the installation location and then configure yourself. For details, see *Note windows-choosing-package::. * The source distribution contains all the code and support files for building the executables using the Visual Studio compiler system. Generally speaking, you should use a binary distribution that includes an installer. It is simpler to use than the others, and you need no additional tools to get MySQL up and running. The installer for the Windows version of MySQL, combined with a GUI Configuration Wizard, automatically installs MySQL, creates an option file, starts the server, and secures the default user accounts. The following section describes how to install MySQL on Windows using a binary distribution. To use an installation package that does not include an installer, follow the procedure described in *Note windows-install-archive::. To install using a source distribution, see *Note windows-source-build::. MySQL distributions for Windows can be downloaded from `http://dev.mysql.com/downloads/'. See *Note getting-mysql::.  File: manual.info, Node: windows-choosing-package, Next: windows-using-installer, Prev: windows-installation, Up: windows-installation 2.4.8.1 Choosing An Installation Package ........................................ This section does not apply to MySQL Enterprise Server users. For MySQL 5.0, there are three installation packages to choose from when installing MySQL on Windows: * *The Essentials Package*: This package has a filename similar to `mysql-essential-5.0.46-win32.msi' and contains the minimum set of files needed to install MySQL on Windows, including the Configuration Wizard. This package does not include optional components such as the embedded server and benchmark suite. * *The Complete Package*: This package has a filename similar to `mysql-5.0.46-win32.zip' and contains all files needed for a complete Windows installation, including the Configuration Wizard. This package includes optional components such as the embedded server and benchmark suite. * *The Noinstall Archive*: This package has a filename similar to `mysql-noinstall-5.0.46-win32.zip' and contains all the files found in the Complete install package, with the exception of the Configuration Wizard. This package does not include an automated installer, and must be manually installed and configured. The Essentials package is recommended for most users. It is provided as an `.msi' file for use with the Windows Installer. The Complete and Noinstall distributions are packaged as Zip archives. To use them, you must have a tool that can unpack `.zip' files. Your choice of install package affects the installation process you must follow. If you choose to install either the Essentials or Complete install packages, see *Note windows-using-installer::. If you choose to install MySQL from the Noinstall archive, see *Note windows-install-archive::.  File: manual.info, Node: windows-using-installer, Next: windows-install-wizard, Prev: windows-choosing-package, Up: windows-installation 2.4.8.2 Installing MySQL with the Automated Installer ..................................................... New MySQL users can use the MySQL Installation Wizard and MySQL Configuration Wizard to install MySQL on Windows. These are designed to install and configure MySQL in such a way that new users can immediately get started using MySQL. The MySQL Installation Wizard and MySQL Configuration Wizard are available in the Essentials and Complete install packages. They are recommended for most standard MySQL installations. Exceptions include users who need to install multiple instances of MySQL on a single server host and advanced users who want complete control of server configuration.  File: manual.info, Node: windows-install-wizard, Next: windows-config-wizard, Prev: windows-using-installer, Up: windows-installation 2.4.8.3 Using the MySQL Installation Wizard ........................................... * Menu: * mysql-install-wizard-introduction:: Introduction to the Installation Wizard * mysql-install-wizard-starting:: Downloading and Starting the MySQL Installation Wizard * mysql-install-wizard-install-type:: Choosing an Install Type * mysql-install-wizard-custom-install:: The Custom Install Dialog * mysql-install-wizard-confirmation-dialog:: The Confirmation Dialog * mysql-install-wizard-changes:: Changes Made by MySQL Installation Wizard * mysql-install-wizard-upgrading:: Upgrading MySQL with the Installation Wizard  File: manual.info, Node: mysql-install-wizard-introduction, Next: mysql-install-wizard-starting, Prev: windows-install-wizard, Up: windows-install-wizard 2.4.8.4 Introduction to the Installation Wizard ............................................... MySQL Installation Wizard is an installer for the MySQL server that uses the latest installer technologies for Microsoft Windows. The MySQL Installation Wizard, in combination with the MySQL Configuration Wizard, allows a user to install and configure a MySQL server that is ready for use immediately after installation. The MySQL Installation Wizard is the standard installer for all MySQL server distributions, version 4.1.5 and higher. Users of previous versions of MySQL need to shut down and remove their existing MySQL installations manually before installing MySQL with the MySQL Installation Wizard. See *Note mysql-install-wizard-upgrading::, for more information on upgrading from a previous version. Microsoft has included an improved version of their Microsoft Windows Installer (MSI) in the recent versions of Windows. MSI has become the de-facto standard for application installations on Windows 2000, Windows XP, and Windows Server 2003. The MySQL Installation Wizard makes use of this technology to provide a smoother and more flexible installation process. The Microsoft Windows Installer Engine was updated with the release of Windows XP; those using a previous version of Windows can reference this Microsoft Knowledge Base article (http://support.microsoft.com/default.aspx?scid=kb;EN-US;292539) for information on upgrading to the latest version of the Windows Installer Engine. In addition, Microsoft has introduced the WiX (Windows Installer XML) toolkit recently. This is the first highly acknowledged Open Source project from Microsoft. We have switched to WiX because it is an Open Source project and it allows us to handle the complete Windows installation process in a flexible manner using scripts. Improving the MySQL Installation Wizard depends on the support and feedback of users like you. If you find that the MySQL Installation Wizard is lacking some feature important to you, or if you discover a bug, please report it in our bugs database using the instructions given in *Note bug-reports::.  File: manual.info, Node: mysql-install-wizard-starting, Next: mysql-install-wizard-install-type, Prev: mysql-install-wizard-introduction, Up: windows-install-wizard 2.4.8.5 Downloading and Starting the MySQL Installation Wizard .............................................................. This section does not apply to MySQL Enterprise Server users. The MySQL installation packages can be downloaded from `http://dev.mysql.com/downloads/'. If the package you download is contained within a Zip archive, you need to extract the archive first. The process for starting the wizard depends on the contents of the installation package you download. If there is a `setup.exe' file present, double-click it to start the installation process. If there is an `.msi' file present, double-click it to start the installation process.  File: manual.info, Node: mysql-install-wizard-install-type, Next: mysql-install-wizard-custom-install, Prev: mysql-install-wizard-starting, Up: windows-install-wizard 2.4.8.6 Choosing an Install Type ................................ This section does not apply to MySQL Enterprise Server users. There are three installation types available: *Typical*, *Complete*, and *Custom*. The *Typical* installation type installs the MySQL server, the `mysql' command-line client, and the command-line utilities. The command-line clients and utilities include `mysqldump', `myisamchk', and several other tools to help you manage the MySQL server. The *Complete* installation type installs all components included in the installation package. The full installation package includes components such as the embedded server library, the benchmark suite, support scripts, and documentation. The *Custom* installation type gives you complete control over which packages you wish to install and the installation path that is used. See *Note mysql-install-wizard-custom-install::, for more information on performing a custom install. If you choose the *Typical* or *Complete* installation types and click the `Next' button, you advance to the confirmation screen to verify your choices and begin the installation. If you choose the *Custom* installation type and click the `Next' button, you advance to the custom installation dialog, described in *Note mysql-install-wizard-custom-install::.  File: manual.info, Node: mysql-install-wizard-custom-install, Next: mysql-install-wizard-confirmation-dialog, Prev: mysql-install-wizard-install-type, Up: windows-install-wizard 2.4.8.7 The Custom Install Dialog ................................. This section does not apply to MySQL Enterprise Server users. If you wish to change the installation path or the specific components that are installed by the MySQL Installation Wizard, choose the *Custom* installation type. A tree view on the left side of the custom install dialog lists all available components. Components that are not installed have a red `X' icon; components that are installed have a gray icon. To change whether a component is installed, click on that component's icon and choose a new option from the drop-down list that appears. You can change the default installation path by clicking the `Change...' button to the right of the displayed installation path. After choosing your installation components and installation path, click the `Next' button to advance to the confirmation dialog.  File: manual.info, Node: mysql-install-wizard-confirmation-dialog, Next: mysql-install-wizard-changes, Prev: mysql-install-wizard-custom-install, Up: windows-install-wizard 2.4.8.8 The Confirmation Dialog ............................... This section does not apply to MySQL Enterprise Server users. Once you choose an installation type and optionally choose your installation components, you advance to the confirmation dialog. Your installation type and installation path are displayed for you to review. To install MySQL if you are satisfied with your settings, click the `Install' button. To change your settings, click the `Back' button. To exit the MySQL Installation Wizard without installing MySQL, click the `Cancel' button. After installation is complete, you have the option of registering with the MySQL web site. Registration gives you access to post in the MySQL forums at forums.mysql.com (http://forums.mysql.com), along with the ability to report bugs at bugs.mysql.com (http://bugs.mysql.com) and to subscribe to our newsletter. The final screen of the installer provides a summary of the installation and gives you the option to launch the MySQL Configuration Wizard, which you can use to create a configuration file, install the MySQL service, and configure security settings.  File: manual.info, Node: mysql-install-wizard-changes, Next: mysql-install-wizard-upgrading, Prev: mysql-install-wizard-confirmation-dialog, Up: windows-install-wizard 2.4.8.9 Changes Made by MySQL Installation Wizard ................................................. This section does not apply to MySQL Enterprise Server users. Once you click the `Install' button, the MySQL Installation Wizard begins the installation process and makes certain changes to your system which are described in the sections that follow. *Changes to the Registry* The MySQL Installation Wizard creates one Windows registry key in a typical install situation, located in `HKEY_LOCAL_MACHINE\SOFTWARE\MySQL AB'. The MySQL Installation Wizard creates a key named after the major version of the server that is being installed, such as `MySQL Server 5.0'. It contains two string values, `Location' and `Version'. The `Location' string contains the path to the installation directory. In a default installation it contains `C:\Program Files\MySQL\MySQL Server 5.0\'. The `Version' string contains the release number. For example, for an installation of MySQL Server 5.0.46, the key contains a value of `5.0.46'. These registry keys are used to help external tools identify the installed location of the MySQL server, preventing a complete scan of the hard-disk to determine the installation path of the MySQL server. The registry keys are not required to run the server, and if you install MySQL using the `noinstall' Zip archive, the registry keys are not created. *Changes to the Start Menu* The MySQL Installation Wizard creates a new entry in the Windows `Start' menu under a common MySQL menu heading named after the major version of MySQL that you have installed. For example, if you install MySQL 5.0, the MySQL Installation Wizard creates a `MySQL Server 5.0' section in the `Start' menu. The following entries are created within the new `Start' menu section: * `MySQL Command Line Client': This is a shortcut to the `mysql' command-line client and is configured to connect as the `root' user. The shortcut prompts for a `root' user password when you connect. * `MySQL Server Instance Config Wizard': This is a shortcut to the MySQL Configuration Wizard. Use this shortcut to configure a newly installed server, or to reconfigure an existing server. * `MySQL Documentation': This is a link to the MySQL server documentation that is stored locally in the MySQL server installation directory. This option is not available when the MySQL server is installed using the Essentials installation package. *Changes to the File System* The MySQL Installation Wizard by default installs the MySQL 5.0 server to `C:\PROGRAM FILES\MySQL\MySQL Server 5.0', where PROGRAM FILES is the default location for applications in your system, and 5.0 is the major version of your MySQL server. This is the recommended location for the MySQL server, replacing the former default location `C:\mysql'. By default, all MySQL applications are stored in a common directory at `C:\PROGRAM FILES\MySQL', where PROGRAM FILES is the default location for applications in your Windows installation. A typical MySQL installation on a developer machine might look like this: C:\Program Files\MySQL\MySQL Server 5.0 C:\Program Files\MySQL\MySQL Administrator 1.0 C:\Program Files\MySQL\MySQL Query Browser 1.0 This approach makes it easier to manage and maintain all MySQL applications installed on a particular system.  File: manual.info, Node: mysql-install-wizard-upgrading, Prev: mysql-install-wizard-changes, Up: windows-install-wizard 2.4.8.10 Upgrading MySQL with the Installation Wizard ..................................................... This section does not apply to MySQL Enterprise Server users. The MySQL Installation Wizard can perform server upgrades automatically using the upgrade capabilities of MSI. That means you do not need to remove a previous installation manually before installing a new release. The installer automatically shuts down and removes the previous MySQL service before installing the new version. Automatic upgrades are available only when upgrading between installations that have the same major and minor version numbers. For example, you can upgrade automatically from MySQL 4.1.5 to MySQL 4.1.6, but not from MySQL 4.1 to MySQL 5.0. See *Note windows-upgrading::.  File: manual.info, Node: windows-config-wizard, Next: windows-install-archive, Prev: windows-install-wizard, Up: windows-installation 2.4.8.11 MySQL Windows Configuration Wizard ........................................... For instructions on using the MySQL Configuration Wizard for Wizard to configure your MySQL server, see *Note mysql-config-wizard::.  File: manual.info, Node: windows-install-archive, Next: windows-extract-archive, Prev: windows-config-wizard, Up: windows-installation 2.4.8.12 Installing MySQL from a Noinstall Zip Archive ...................................................... This section does not apply to MySQL Enterprise Server users. Users who are installing from the Noinstall package can use the instructions in this section to manually install MySQL. The process for installing MySQL from a Zip archive is as follows: 1. Extract the archive to the desired install directory 2. Create an option file 3. Choose a MySQL server type 4. Start the MySQL server 5. Secure the default user accounts This process is described in the sections that follow.  File: manual.info, Node: windows-extract-archive, Next: windows-create-option-file, Prev: windows-install-archive, Up: windows-installation 2.4.8.13 Extracting the Install Archive ....................................... This section does not apply to MySQL Enterprise Server users. To install MySQL manually, do the following: 1. If you are upgrading from a previous version please refer to *Note windows-upgrading::, before beginning the upgrade process. 2. Make sure that you are logged in as a user with administrator privileges. 3. Choose an installation location. Traditionally, the MySQL server is installed in `C:\mysql'. The MySQL Installation Wizard installs MySQL under `C:\Program Files\MySQL'. If you do not install MySQL at `C:\mysql', you must specify the path to the install directory during startup or in an option file. See *Note windows-create-option-file::. 4. Extract the install archive to the chosen installation location using your preferred Zip archive tool. Some tools may extract the archive to a folder within your chosen installation location. If this occurs, you can move the contents of the subfolder into the chosen installation location.  File: manual.info, Node: windows-create-option-file, Next: windows-select-server, Prev: windows-extract-archive, Up: windows-installation 2.4.8.14 Creating an Option File ................................ If you need to specify startup options when you run the server, you can indicate them on the command line or place them in an option file. For options that are used every time the server starts, you may find it most convenient to use an option file to specify your MySQL configuration. This is particularly true under the following circumstances: * The installation or data directory locations are different from the default locations (`C:\Program Files\MySQL\MySQL Server 5.0' and `C:\Program Files\MySQL\MySQL Server 5.0\data'). * You need to tune the server settings. When the MySQL server starts on Windows, it looks for options in two files: the `my.ini' file in the Windows directory, and the `C:\my.cnf' file. The Windows directory typically is named something like `C:\WINDOWS'. You can determine its exact location from the value of the `WINDIR' environment variable using the following command: C:\> echo %WINDIR% MySQL looks for options first in the `my.ini' file, and then in the `my.cnf' file. However, to avoid confusion, it's best if you use only one file. If your PC uses a boot loader where `C:' is not the boot drive, your only option is to use the `my.ini' file. Whichever option file you use, it must be a plain text file. You can also make use of the example option files included with your MySQL distribution; see *Note option-files-preconfigured::. An option file can be created and modified with any text editor, such as Notepad. For example, if MySQL is installed in `E:\mysql' and the data directory is in `E:\mydata\data', you can create an option file containing a `[mysqld]' section to specify values for the `basedir' and `datadir' parameters: [mysqld] # set basedir to your installation path basedir=E:/mysql # set datadir to the location of your data directory datadir=E:/mydata/data Note that Windows pathnames are specified in option files using (forward) slashes rather than backslashes. If you do use backslashes, you must double them: [mysqld] # set basedir to your installation path basedir=E:\\mysql # set datadir to the location of your data directory datadir=E:\\mydata\\data On Windows, the MySQL installer places the data directory directly under the directory where you install MySQL. If you would like to use a data directory in a different location, you should copy the entire contents of the `data' directory to the new location. For example, if MySQL is installed in `C:\Program Files\MySQL\MySQL Server 5.0', the data directory is by default in `C:\Program Files\MySQL\MySQL Server 5.0\data'. If you want to use `E:\mydata' as the data directory instead, you must do two things: 1. Move the entire `data' directory and all of its contents from `C:\Program Files\MySQL\MySQL Server 5.0\data' to `E:\mydata'. 2. Use a `--datadir' option to specify the new data directory location each time you start the server.  File: manual.info, Node: windows-select-server, Next: windows-server-first-start, Prev: windows-create-option-file, Up: windows-installation 2.4.8.15 Selecting a MySQL Server Type ...................................... This section does not apply to MySQL Enterprise Server users. The following table shows the available servers for Windows in MySQL 5.0. *Binary* *Description* `mysqld-nt' Optimized binary with named-pipe support `mysqld' Optimized binary without named-pipe support `mysqld-debug' Like `mysqld-nt', but compiled with full debugging and automatic memory allocation checking All of the preceding binaries are optimized for modern Intel processors, but should work on any Intel i386-class or higher processor. Each of the servers in a distribution support the same set of storage engines. The `SHOW ENGINES' statement displays which engines a given server supports. All Windows MySQL 5.0 servers have support for symbolic linking of database directories. MySQL supports TCP/IP on all Windows platforms. The `mysqld-nt' and `mysql-debug' servers support named pipes. However, the default is to use TCP/IP regardless of platform. (Named pipes are slower than TCP/IP in many Windows configurations.) Use of named pipes is subject to these conditions: * Named pipes are enabled only if you start the server with the `--enable-named-pipe' option. It is necessary to use this option explicitly because some users have experienced problems with shutting down the MySQL server when named pipes were used. * Named-pipe connections are allowed only by the `mysqld-nt' and `mysqld-debug' servers. *Note*: Most of the examples in this manual use `mysqld' as the server name. If you choose to use a different server, such as `mysqld-nt', make the appropriate substitutions in the commands that are shown in the examples.  File: manual.info, Node: windows-server-first-start, Next: windows-start-command-line, Prev: windows-select-server, Up: windows-installation 2.4.8.16 Starting the Server for the First Time ............................................... This section gives a general overview of starting the MySQL server. The following sections provide more specific information for starting the MySQL server from the command line or as a Windows service. The information here applies primarily if you installed MySQL using the `Noinstall' version, or if you wish to configure and test MySQL manually rather than with the GUI tools. The examples in these sections assume that MySQL is installed under the default location of `C:\Program Files\MySQL\MySQL Server 5.0'. Adjust the pathnames shown in the examples if you have MySQL installed in a different location. Clients have two options. They can use TCP/IP, or they can use a named pipe if the server supports named-pipe connections. MySQL for Windows also supports shared-memory connections if the server is started with the `--shared-memory' option. Clients can connect through shared memory by using the `--protocol=memory' option. For information about which server binary to run, see *Note windows-select-server::. Testing is best done from a command prompt in a console window (or `DOS window'). In this way you can have the server display status messages in the window where they are easy to see. If something is wrong with your configuration, these messages make it easier for you to identify and fix any problems. To start the server, enter this command: C:\> "C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld" --console For a server that includes `InnoDB' support, you should see the messages similar to those following as it starts (the pathnames and sizes may differ): InnoDB: The first specified datafile c:\ibdata\ibdata1 did not exist: InnoDB: a new database to be created! InnoDB: Setting file c:\ibdata\ibdata1 size to 209715200 InnoDB: Database physically writes the file full: wait... InnoDB: Log file c:\iblogs\ib_logfile0 did not exist: new to be created InnoDB: Setting log file c:\iblogs\ib_logfile0 size to 31457280 InnoDB: Log file c:\iblogs\ib_logfile1 did not exist: new to be created InnoDB: Setting log file c:\iblogs\ib_logfile1 size to 31457280 InnoDB: Log file c:\iblogs\ib_logfile2 did not exist: new to be created InnoDB: Setting log file c:\iblogs\ib_logfile2 size to 31457280 InnoDB: Doublewrite buffer not found: creating new InnoDB: Doublewrite buffer created InnoDB: creating foreign key constraint system tables InnoDB: foreign key constraint system tables created 011024 10:58:25 InnoDB: Started When the server finishes its startup sequence, you should see something like this, which indicates that the server is ready to service client connections: mysqld: ready for connections Version: '5.0.46' socket: '' port: 3306 The server continues to write to the console any further diagnostic output it produces. You can open a new console window in which to run client programs. If you omit the `--console' option, the server writes diagnostic output to the error log in the data directory (`C:\Program Files\MySQL\MySQL Server 5.0\data' by default). The error log is the file with the `.err' extension. *Note*: The accounts that are listed in the MySQL grant tables initially have no passwords. After starting the server, you should set up passwords for them using the instructions in *Note post-installation::.  File: manual.info, Node: windows-start-command-line, Next: windows-start-service, Prev: windows-server-first-start, Up: windows-installation 2.4.8.17 Starting MySQL from the Windows Command Line ..................................................... The MySQL server can be started manually from the command line. This can be done on any version of Windows. To start the `mysqld' server from the command line, you should start a console window (or `DOS window') and enter this command: C:\> "C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld" The path to `mysqld' may vary depending on the install location of MySQL on your system. You can stop the MySQL server by executing this command: C:\> "C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqladmin" -u root shutdown *Note*: If the MySQL `root' user account has a password, you need to invoke `mysqladmin' with the `-p' option and supply the password when prompted. This command invokes the MySQL administrative utility `mysqladmin' to connect to the server and tell it to shut down. The command connects as the MySQL `root' user, which is the default administrative account in the MySQL grant system. Note that users in the MySQL grant system are wholly independent from any login users under Windows. If `mysqld' doesn't start, check the error log to see whether the server wrote any messages there to indicate the cause of the problem. The error log is located in the `C:\Program Files\MySQL\MySQL Server 5.0\data' directory. It is the file with a suffix of `.err'. You can also try to start the server as `mysqld --console'; in this case, you may get some useful information on the screen that may help solve the problem. The last option is to start `mysqld' with the `--standalone' and `--debug' options. In this case, `mysqld' writes a log file `C:\mysqld.trace' that should contain the reason why `mysqld' doesn't start. See MySQL Internals: Porting (http://forge.mysql.com/wiki/MySQL_Internals_Porting). Use `mysqld --verbose --help' to display all the options that `mysqld' understands.  File: manual.info, Node: windows-start-service, Next: windows-testing, Prev: windows-start-command-line, Up: windows-installation 2.4.8.18 Starting MySQL as a Windows Service ............................................ On Windows, the recommended way to run MySQL is to install it as a Windows service, whereby MySQL starts and stops automatically when Windows starts and stops. A MySQL server installed as a service can also be controlled from the command line using `NET' commands, or with the graphical `Services' utility. The `Services' utility (the Windows `Service Control Manager') can be found in the Windows Control Panel (under `Administrative Tools' on Windows 2000, XP, and Server 2003). To avoid conflicts, it is advisable to close the `Services' utility while performing server installation or removal operations from the command line. Before installing MySQL as a Windows service, you should first stop the current server if it is running by using the following command: C:\> "C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqladmin" -u root shutdown *Note*: If the MySQL `root' user account has a password, you need to invoke `mysqladmin' with the `-p' option and supply the password when prompted. This command invokes the MySQL administrative utility `mysqladmin' to connect to the server and tell it to shut down. The command connects as the MySQL `root' user, which is the default administrative account in the MySQL grant system. Note that users in the MySQL grant system are wholly independent from any login users under Windows. Install the server as a service using this command: C:\> "C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld" --install The service-installation command does not start the server. Instructions for that are given later in this section. To make it easier to invoke MySQL programs, you can add the pathname of the MySQL `bin' directory to your Windows system `PATH' environment variable: * On the Windows desktop, right-click on the `My Computer' icon, and select `Properties' * Next select the `Advanced' tab from the `System Properties' menu that appears, and click the `Environment Variables' button. * Under `System Variables', select `Path', and then click the `Edit' button. The `Edit System Variable' dialogue should appear. * Place your cursor at the end of the text appearing in the space marked `Variable Value'. (Use the `End' key to ensure that your cursor is positioned at the very end of the text in this space.) Then enter the complete pathname of your MySQL `bin' directory (for example, `C:\Program Files\MySQL\MySQL Server 5.0\bin'), Note that there should be a semicolon separating this path from any values present in this field. Dismiss this dialogue, and each dialogue in turn, by clicking `OK' until all of the dialogues that were opened have been dismissed. You should now be able to invoke any MySQL executable program by typing its name at the DOS prompt from any directory on the system, without having to supply the path. This includes the servers, the `mysql' client, and all MySQL command-line utilities such as `mysqladmin' and `mysqldump'. You should not add the MySQL `bin' directory to your Windows `PATH' if you are running multiple MySQL servers on the same machine. *Warning*: You must exercise great care when editing your system `PATH' by hand; accidental deletion or modification of any portion of the existing `PATH' value can leave you with a malfunctioning or even unusable system. The following additional arguments can be used in MySQL 5.0 when installing the service: * You can specify a service name immediately following the `--install' option. The default service name is `MySQL'. * If a service name is given, it can be followed by a single option. By convention, this should be `--defaults-file=FILE_NAME' to specify the name of an option file from which the server should read options when it starts. It is possible to use a single option other than `--defaults-file', but this is discouraged. `--defaults-file' is more flexible because it enables you to specify multiple startup options for the server by placing them in the named option file. Also, in MySQL 5.0, use of an option different from `--defaults-file' is not supported until 5.0.3. * As of MySQL 5.0.1, you can also specify a `--local-service' option following the service name. This causes the server to run using the `LocalService' Windows account that has limited system privileges. This account is available only for Windows XP or newer. If both `--defaults-file' and `--local-service' are given following the service name, they can be in any order. For a MySQL server that is installed as a Windows service, the following rules determine the service name and option files that the server uses: * If the service-installation command specifies no service name or the default service name (`MySQL') following the `--install' option, the server uses the a service name of `MySQL' and reads options from the `[mysqld]' group in the standard option files. * If the service-installation command specifies a service name other than `MySQL' following the `--install' option, the server uses that service name. It reads options from the group that has the same name as the service, and reads options from the standard option files. The server also reads options from the `[mysqld]' group from the standard option files. This allows you to use the `[mysqld]' group for options that should be used by all MySQL services, and an option group with the same name as a service for use by the server installed with that service name. * If the service-installation command specifies a `--defaults-file' option after the service name, the server reads options only from the `[mysqld]' group of the named file and ignores the standard option files. As a more complex example, consider the following command: C:\> "C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld" --install MySQL --defaults-file=C:\my-opts.cnf Here, the default service name (`MySQL') is given after the `--install' option. If no `--defaults-file' option had been given, this command would have the effect of causing the server to read the `[mysqld]' group from the standard option files. However, because the `--defaults-file' option is present, the server reads options from the `[mysqld]' option group, and only from the named file. You can also specify options as Start parameters in the Windows `Services' utility before you start the MySQL service. Once a MySQL server has been installed as a service, Windows starts the service automatically whenever Windows starts. The service also can be started immediately from the `Services' utility, or by using a `NET START MySQL' command. The `NET' command is not case sensitive. When run as a service, `mysqld' has no access to a console window, so no messages can be seen there. If `mysqld' does not start, check the error log to see whether the server wrote any messages there to indicate the cause of the problem. The error log is located in the MySQL data directory (for example, `C:\Program Files\MySQL\MySQL Server 5.0\data'). It is the file with a suffix of `.err'. When a MySQL server has been installed as a service, and the service is running, Windows stops the service automatically when Windows shuts down. The server also can be stopped manually by using the `Services' utility, the `NET STOP MySQL' command, or the `mysqladmin shutdown' command. You also have the choice of installing the server as a manual service if you do not wish for the service to be started automatically during the boot process. To do this, use the `--install-manual' option rather than the `--install' option: C:\> "C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld" --install-manual To remove a server that is installed as a service, first stop it if it is running by executing `NET STOP MySQL'. Then use the `--remove' option to remove it: C:\> "C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld" --remove If `mysqld' is not running as a service, you can start it from the command line. For instructions, see *Note windows-start-command-line::. Please see *Note windows-troubleshooting::, if you encounter difficulties during installation.  File: manual.info, Node: windows-testing, Next: windows-troubleshooting, Prev: windows-start-service, Up: windows-installation 2.4.8.19 Testing The MySQL Installation ....................................... You can test whether the MySQL server is working by executing any of the following commands: C:\> "C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqlshow" C:\> "C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqlshow" -u root mysql C:\> "C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqladmin" version status proc C:\> "C:\Program Files\MySQL\MySQL Server 5.0\bin\mysql" test If `mysqld' is slow to respond to TCP/IP connections from client programs, there is probably a problem with your DNS. In this case, start `mysqld' with the `--skip-name-resolve' option and use only `localhost' and IP numbers in the `Host' column of the MySQL grant tables. You can force a MySQL client to use a named-pipe connection rather than TCP/IP by specifying the `--pipe' or `--protocol=PIPE' option, or by specifying `.' (period) as the host name. Use the `--socket' option to specify the name of the pipe if you do not want to use the default pipe name. Note that if you have set a password for the `root' account, deleted the anonymous account, or created a new user account, then you must use the appropriate `-u' and `-p' options with the commands shown above in order to connect with the MySQL Server. See *Note connecting::. For more information about `mysqlshow', see *Note mysqlshow::.  File: manual.info, Node: windows-troubleshooting, Next: windows-upgrading, Prev: windows-testing, Up: windows-installation 2.4.8.20 Troubleshooting a MySQL Installation Under Windows ........................................................... When installing and running MySQL for the first time, you may encounter certain errors that prevent the MySQL server from starting. The purpose of this section is to help you diagnose and correct some of these errors. Your first resource when troubleshooting server issues is the error log. The MySQL server uses the error log to record information relevant to the error that prevents the server from starting. The error log is located in the data directory specified in your `my.ini' file. The default data directory location is `C:\Program Files\MySQL\MySQL Server 5.0\data'. See *Note error-log::. Another source of information regarding possible errors is the console messages displayed when the MySQL service is starting. Use the `NET START MySQL' command from the command line after installing `mysqld' as a service to see any error messages regarding the starting of the MySQL server as a service. See *Note windows-start-service::. The following examples show other common error messages you may encounter when installing MySQL and starting the server for the first time: * If the MySQL server cannot find the `mysql' privileges database or other critical files, you may see these messsages: System error 1067 has occurred. Fatal error: Can't open privilege tables: Table 'mysql.host' doesn't exist These messages often occur when the MySQL base or data directories are installed in different locations than the default locations (`C:\Program Files\MySQL\MySQL Server 5.0' and `C:\Program Files\MySQL\MySQL Server 5.0\data', respectively). This situation may occur when MySQL is upgraded and installed to a new location, but the configuration file is not updated to reflect the new location. In addition, there may be old and new configuration files that conflict. Be sure to delete or rename any old configuration files when upgrading MySQL. If you have installed MySQL to a directory other than `C:\Program Files\MySQL\MySQL Server 5.0', you need to ensure that the MySQL server is aware of this through the use of a configuration (`my.ini') file. The `my.ini' file needs to be located in your Windows directory, typically `C:\WINDOWS'. You can determine its exact location from the value of the `WINDIR' environment variable by issuing the following command from the command prompt: C:\> echo %WINDIR% An option file can be created and modified with any text editor, such as Notepad. For example, if MySQL is installed in `E:\mysql' and the data directory is `D:\MySQLdata', you can create the option file and set up a `[mysqld]' section to specify values for the `basedir' and `datadir' parameters: [mysqld] # set basedir to your installation path basedir=E:/mysql # set datadir to the location of your data directory datadir=D:/MySQLdata Note that Windows pathnames are specified in option files using (forward) slashes rather than backslashes. If you do use backslashes, you must double them: [mysqld] # set basedir to your installation path basedir=C:\\Program Files\\MySQL\\MySQL Server 5.0 # set datadir to the location of your data directory datadir=D:\\MySQLdata MySQL Enterprise For expert advice on the start-up options appropriate to your circumstances, subscribe to the MySQL Network Monitoring and Advisory Service. For more information see, `http://www.mysql.com/products/enterprise/advisors.html'. If you change the `datadir' value in your MySQL configuration file, you must move the contents of the existing MySQL data directory before restarting the MySQL server. See *Note windows-create-option-file::. * If you reinstall or upgrade MySQL without first stopping and removing the existing MySQL service and install MySQL using the MySQL Configuration Wizard, you may see this error: Error: Cannot create Windows service for MySql. Error: 0 This occurs when the Configuration Wizard tries to install the service and finds an existing service with the same name. One solution to this problem is to choose a service name other than `mysql' when using the configuration wizard. This allows the new service to be installed correctly, but leaves the outdated service in place. Although this is harmless, it is best to remove old services that are no longer in use. To permanently remove the old `mysql' service, execute the following command as a user with administrative privileges, on the command-line: C:\> sc delete mysql [SC] DeleteService SUCCESS If the `sc' utility is not available for your version of Windows, download the `delsrv' utility from `http://www.microsoft.com/windows2000/techinfo/reskit/tools/existing/delsrv-o.asp' and use the `delsrv mysql' syntax.  File: manual.info, Node: windows-upgrading, Next: windows-vs-unix, Prev: windows-troubleshooting, Up: windows-installation 2.4.8.21 Upgrading MySQL on Windows ................................... This section does not apply to MySQL Enterprise Server users. This section lists some of the steps you should take when upgrading MySQL on Windows. 1. Review *Note upgrade::, for additional information on upgrading MySQL that is not specific to Windows. 2. You should always back up your current MySQL installation before performing an upgrade. See *Note backup::. 3. Download the latest Windows distribution of MySQL from `http://dev.mysql.com/downloads/'. 4. Before upgrading MySQL, you must stop the server. If the server is installed as a service, stop the service with the following command from the command prompt: C:\> NET STOP MySQL If you are not running the MySQL server as a service, use the following command to stop it: C:\> "C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqladmin" -u root shutdown *Note*: If the MySQL `root' user account has a password, you need to invoke `mysqladmin' with the `-p' option and supply the password when prompted. 5. When upgrading to MySQL 5.0 from a version previous to 4.1.5, or when upgrading from a version of MySQL installed from a Zip archive to a version of MySQL installed with the MySQL Installation Wizard, you must manually remove the previous installation and MySQL service (if the server is installed as a service). To remove the MySQL service, use the following command: C:\> C:\mysql\bin\mysqld --remove *If you do not remove the existing service, the MySQL Installation Wizard may fail to properly install the new MySQL service.* 6. If you are using the MySQL Installation Wizard, start the wizard as described in *Note windows-install-wizard::. 7. If you are installing MySQL from a Zip archive, extract the archive. You may either overwrite your existing MySQL installation (usually located at `C:\mysql'), or install it into a different directory, such as `C:\mysql5'. Overwriting the existing installation is recommended. 8. If you were running MySQL as a Windows service and you had to remove the service earlier in this procedure, reinstall the service. (See *Note windows-start-service::.) 9. Restart the server. For example, use `NET START MySQL' if you run MySQL as a service, or invoke `mysqld' directly otherwise. 10. If you encounter errors, see *Note windows-troubleshooting::.  File: manual.info, Node: windows-vs-unix, Prev: windows-upgrading, Up: windows-installation 2.4.8.22 MySQL on Windows Compared to MySQL on Unix ................................................... MySQL for Windows has proven itself to be very stable. The Windows version of MySQL has the same features as the corresponding Unix version, with the following exceptions: * *Limited number of ports* Windows systems have about 4,000 ports available for client connections, and after a connection on a port closes, it takes two to four minutes before the port can be reused. In situations where clients connect to and disconnect from the server at a high rate, it is possible for all available ports to be used up before closed ports become available again. If this happens, the MySQL server appears to be unresponsive even though it is running. Note that ports may be used by other applications running on the machine as well, in which case the number of ports available to MySQL is lower. For more information about this problem, see `http://support.microsoft.com/default.aspx?scid=kb;en-us;196271'. * *Concurrent reads* MySQL depends on the `pread()' and `pwrite()' system calls to be able to mix `INSERT' and `SELECT'. Currently, we use mutexes to emulate `pread()' and `pwrite()'. We intend to replace the file level interface with a virtual interface in the future so that we can use the `readfile()'/`writefile()' interface to get more speed. The current implementation limits the number of open files that MySQL 5.0 can use to 2,048, which means that you cannot run as many concurrent threads on Windows as on Unix. * *Blocking read* MySQL uses a blocking read for each connection. That has the following implications if named-pipe connections are enabled: * A connection is not disconnected automatically after eight hours, as happens with the Unix version of MySQL. * If a connection hangs, it is not possible to break it without killing MySQL. * `mysqladmin kill' does not work on a sleeping connection. * `mysqladmin shutdown' cannot abort as long as there are sleeping connections. We plan to fix this problem in the future. * *`ALTER TABLE'* While you are executing an `ALTER TABLE' statement, the table is locked from being used by other threads. This has to do with the fact that on Windows, you can't delete a file that is in use by another thread. In the future, we may find some way to work around this problem. * *`DROP TABLE'* `DROP TABLE' on a table that is in use by a `MERGE' table does not work on Windows because the `MERGE' handler does the table mapping hidden from the upper layer of MySQL. Because Windows does not allow dropping files that are open, you first must flush all `MERGE' tables (with `FLUSH TABLES') or drop the `MERGE' table before dropping the table. * *`DATA DIRECTORY' and `INDEX DIRECTORY'* The `DATA DIRECTORY' and `INDEX DIRECTORY' options for `CREATE TABLE' are ignored on Windows, because Windows doesn't support symbolic links. These options also are ignored on systems that have a non-functional `realpath()' call. * *`DROP DATABASE'* You cannot drop a database that is in use by some thread. * *Case-insensitive names* Filenames are not case sensitive on Windows, so MySQL database and table names are also not case sensitive on Windows. The only restriction is that database and table names must be specified using the same case throughout a given statement. See *Note identifier-case-sensitivity::. * *The ``\'' pathname separator character* Pathname components in Windows are separated by the ``\'' character, which is also the escape character in MySQL. If you are using `LOAD DATA INFILE' or `SELECT ... INTO OUTFILE', use Unix-style filenames with ``/'' characters: mysql> LOAD DATA INFILE 'C:/tmp/skr.txt' INTO TABLE skr; mysql> SELECT * INTO OUTFILE 'C:/tmp/skr.txt' FROM skr; Alternatively, you must double the ``\'' character: mysql> LOAD DATA INFILE 'C:\\tmp\\skr.txt' INTO TABLE skr; mysql> SELECT * INTO OUTFILE 'C:\\tmp\\skr.txt' FROM skr; * *Problems with pipes* Pipes do not work reliably from the Windows command-line prompt. If the pipe includes the character `^Z' / `CHAR(24)', Windows thinks that it has encountered end-of-file and aborts the program. This is mainly a problem when you try to apply a binary log as follows: C:\> mysqlbinlog BINARY_LOG_FILE | mysql --user=root If you have a problem applying the log and suspect that it is because of a `^Z' / `CHAR(24)' character, you can use the following workaround: C:\> mysqlbinlog BINARY_LOG_FILE --result-file=/tmp/bin.sql C:\> mysql --user=root --execute "source /tmp/bin.sql" The latter command also can be used to reliably read in any SQL file that may contain binary data. * *`Access denied for user' error* If MySQL cannot resolve your hostname properly, you may get the following error when you attempt to run a MySQL client program to connect to a server running on the same machine: Access denied for user 'SOME_USER'@'unknown' to database 'mysql' To fix this problem, you should create a file named `\windows\hosts' containing the following information: 127.0.0.1 localhost Here are some open issues for anyone who might want to help us improve MySQL on Windows: * Add macros to use the faster thread-safe increment/decrement methods provided by Windows.  File: manual.info, Node: linux-rpm, Next: mac-os-x-installation, Prev: windows-installation, Up: installing-cs 2.4.9 Installing MySQL from RPM Packages on Linux ------------------------------------------------- The recommended way to install MySQL on RPM-based Linux distributions is by using the RPM packages. The RPMs provided by MySQL AB to the community should work on all versions of Linux that support RPM packages and use `glibc' 2.3. MySQL AB also provides RPMs with binaries that are statically linked to a patched version of `glibc' 2.2, but only for the x86 (32-bit) architecture. To obtain RPM packages, see *Note getting-mysql::. For non-RPM Linux distributions, you can install MySQL using a `.tar.gz' package. See *Note installing-binary::. MySQL AB does provide some platform-specific RPMs; the difference between a platform-specific RPM and a generic RPM is that a platform-specific RPM is built on the targeted platform and is linked dynamically whereas a generic RPM is linked statically with LinuxThreads. *Note*: RPM distributions of MySQL often are provided by other vendors. Be aware that they may differ in features and capabilities from those built by MySQL AB, and that the instructions in this manual do not necessarily apply to installing them. The vendor's instructions should be consulted instead. If you have problems with an RPM file (for example, if you receive the error `Sorry, the host 'XXXX' could not be looked up'), see *Note binary-notes-linux::. In most cases, you need to install only the `MySQL-server' and `MySQL-client' packages to get a functional MySQL installation. The other packages are not required for a standard installation. If you get a dependency failure when trying to install MySQL packages (for example, `error: removing these packages would break dependencies: libmysqlclient.so.10 is needed by ...'), you should also install the `MySQL-shared-compat' package, which includes both the shared libraries for backward compatibility (`libmysqlclient.so.12' for MySQL 4.0 and `libmysqlclient.so.10' for MySQL 3.23). Some Linux distributions still ship with MySQL 3.23 and they usually link applications dynamically to save disk space. If these shared libraries are in a separate package (for example, `MySQL-shared'), it is sufficient to simply leave this package installed and just upgrade the MySQL server and client packages (which are statically linked and do not depend on the shared libraries). For distributions that include the shared libraries in the same package as the MySQL server (for example, Red Hat Linux), you could either install our 3.23 `MySQL-shared' RPM, or use the `MySQL-shared-compat' package instead. (Do not install both.) The RPM packages shown in the following list are available. The names shown here use a suffix of `.glibc23.i386.rpm', but particular packages can have different suffixes, as described later. Packages that have `community' in the names are Community Server builds, available from MySQL 5.0.27 on. * `MySQL-server-VERSION.glibc23.i386.rpm', `MySQL-server-community-VERSION.glibc23.i386.rpm' The MySQL server. You need this unless you only want to connect to a MySQL server running on another machine. * `MySQL-client-VERSION.glibc23.i386.rpm', `MySQL-client-community-VERSION.glibc23.i386.rpm' The standard MySQL client programs. You probably always want to install this package. * `MySQL-bench-VERSION.glibc23.i386.rpm' Tests and benchmarks. Requires Perl and the `DBI' and `DBD::mysql' modules. * `MySQL-devel-VERSION.glibc23.i386.rpm', `MySQL-devel-community-VERSION.glibc23.i386.rpm' The libraries and include files that are needed if you want to compile other MySQL clients, such as the Perl modules. * `MySQL-debuginfo-VERSION.glibc23.i386.rpm', `MySQL-community-debuginfo-VERSION.glibc23.i386.rpm' This package contains debugging information. `debuginfo' RPMs are never needed to use MySQL software; this is true both for the server and for client programs. However, they contain additional information that might be needed by a debugger to analyze a crash. * `MySQL-shared-VERSION.glibc23.i386.rpm', `MySQL-shared-community-VERSION.glibc23.i386.rpm' This package contains the shared libraries (`libmysqlclient.so*') that certain languages and applications need to dynamically load and use MySQL. It contains single-threaded and thread-safe libraries. If you install this package, do not install the `MySQL-shared-compat' package. * `MySQL-shared-compat-VERSION.glibc23.i386.rpm' This package includes the shared libraries for MySQL 3.23, 4.0, 4.1, and 5.0. It contains single-threaded and thread-safe libraries. Install this package instead of `MySQL-shared' if you have applications installed that are dynamically linked against older versions of MySQL but you want to upgrade to the current version without breaking the library dependencies. * `MySQL-clustermanagement-communityVERSION.glibc23.i386.rpm', `MySQL-clusterstorage-communityVERSION.glibc23.i386.rpm', `MySQL-clustertools-communityVERSION.glibc23.i386.rpm', `MySQL-clusterextra-communityVERSION.glibc23.i386.rpm' Packages that contain additional files for MySQL Cluster installations. These are platform-specific RPMs, in contrast to the platform-independent `ndb-XXX' RPMs. * `MySQL-ndb-management-VERSION.glibc23.i386.rpm', `MySQL-ndb-storage-VERSION.glibc23.i386.rpm', `MySQL-ndb-tools-VERSION.glibc23.i386.rpm', `MySQL-ndb-extra-VERSION.glibc23.i386.rpm' Packages that contain additional files for MySQL Cluster installations. These are platform-independent RPMs, in contrast to the platform-specific `clusterXXX-community' RPMs. * `MySQL-test-community-VERSION.glibc23.i386.rpm' This package includes the MySQL test suite. * `MySQL-VERSION.src.rpm' This contains the source code for all of the previous packages. It can also be used to rebuild the RPMs on other architectures (for example, Alpha or SPARC). The suffix of RPM package names (following the VERSION value) has the following syntax: [.PLATFORM].CPU.rpm The PLATFORM and CPU values indicate the type of system for which the package is built. PLATFORM, if present, indicates the platform, and CPU indicates the processor type or family. If the PLATFORM value is missing (for example, `MySQL-server-VERSION.i386.rpm'), the package is statically linked against a version of `glibc' 2.2 that has been patched to handle larger numbers of threads with larger stack sizes than the stock library. If PLATFORM is present, the package is dynamically linked against `glibc' 2.3 and the PLATFORM value indicates whether the package is platform independent or intended for a specific platform: `glibc23' Platform independent, should run on any Linux distribution that supports `glibc' 2.3 `rhel3', `rhel4' Red Hat Enterprise Linux 3 or 4 `sles9', `sles10' SuSE Linux Enterprise Server 9 or 10 The CPU value indicates the processor type or family for which the package is built: `i386' x86 processor, 386 and up `i586' x86 processor, Pentium and up `x86_64' 64-bit x86 processor `ia64' Itanium (IA-64) processor To see all files in an RPM package (for example, a `MySQL-server' RPM), run a command like this: shell> rpm -qpl MySQL-server-VERSION.glibc23.i386.rpm To perform a standard minimal installation, install the server and client RPMs: shell> rpm -i MySQL-server-VERSION.glibc23.i386.rpm shell> rpm -i MySQL-client-VERSION.glibc23.i386.rpm To install only the client programs, install just the client RPM: shell> rpm -i MySQL-client-VERSION.glibc23.i386.rpm RPM provides a feature to verify the integrity and authenticity of packages before installing them. If you would like to learn more about this feature, see *Note verifying-package-integrity::. The server RPM places data under the `/var/lib/mysql' directory. The RPM also creates a login account for a user named `mysql' (if one does not exist) to use for running the MySQL server, and creates the appropriate entries in `/etc/init.d/' to start the server automatically at boot time. (This means that if you have performed a previous installation and have made changes to its startup script, you may want to make a copy of the script so that you don't lose it when you install a newer RPM.) See *Note automatic-start::, for more information on how MySQL can be started automatically on system startup. If you want to install the MySQL RPM on older Linux distributions that do not support initialization scripts in `/etc/init.d' (directly or via a symlink), you should create a symbolic link that points to the location where your initialization scripts actually are installed. For example, if that location is `/etc/rc.d/init.d', use these commands before installing the RPM to create `/etc/init.d' as a symbolic link that points there: shell> cd /etc shell> ln -s rc.d/init.d . However, all current major Linux distributions should support the new directory layout that uses `/etc/init.d', because it is required for LSB (Linux Standard Base) compliance. If the RPM files that you install include `MySQL-server', the `mysqld' server should be up and running after installation. You should be able to start using MySQL. If something goes wrong, you can find more information in the binary installation section. See *Note installing-binary::. *Note*: The accounts that are listed in the MySQL grant tables initially have no passwords. After starting the server, you should set up passwords for them using the instructions in *Note post-installation::.  File: manual.info, Node: mac-os-x-installation, Next: solaris-installation, Prev: linux-rpm, Up: installing-cs 2.4.10 Installing MySQL on Mac OS X ----------------------------------- You can install MySQL on Mac OS X 10.3.x (`Panther') or newer using a Mac OS X binary package in PKG format instead of the binary tarball distribution. Please note that older versions of Mac OS X (for example, 10.1.x or 10.2.x) are *not* supported by this package. The package is located inside a disk image (`.dmg') file that you first need to mount by double-clicking its icon in the Finder. It should then mount the image and display its contents. To obtain MySQL, see *Note getting-mysql::. *Note*: Before proceeding with the installation, be sure to shut down all running MySQL server instances by either using the MySQL Manager Application (on Mac OS X Server) or via `mysqladmin shutdown' on the command line. To actually install the MySQL PKG file, double-click on the package icon. This launches the Mac OS X Package Installer, which guides you through the installation of MySQL. Due to a bug in the Mac OS X package installer, you may see this error message in the destination disk selection dialog: You cannot install this software on this disk. (null) If this error occurs, simply click the `Go Back' button once to return to the previous screen. Then click `Continue' to advance to the destination disk selection again, and you should be able to choose the destination disk correctly. We have reported this bug to Apple and it is investigating this problem. The Mac OS X PKG of MySQL installs itself into `/usr/local/mysql-VERSION' and also installs a symbolic link, `/usr/local/mysql', that points to the new location. If a directory named `/usr/local/mysql' exists, it is renamed to `/usr/local/mysql.bak' first. Additionally, the installer creates the grant tables in the `mysql' database by executing `mysql_install_db'. The installation layout is similar to that of a `tar' file binary distribution; all MySQL binaries are located in the directory `/usr/local/mysql/bin'. The MySQL socket file is created as `/tmp/mysql.sock' by default. See *Note installation-layouts::. MySQL installation requires a Mac OS X user account named `mysql'. A user account with this name should exist by default on Mac OS X 10.2 and up. If you are running Mac OS X Server, a version of MySQL should already be installed. The following table shows the versions of MySQL that ship with Mac OS X Server versions. *Mac OS X Server *MySQL Version* Version* 10.2-10.2.2 3.23.51 10.2.3-10.2.6 3.23.53 10.3 4.0.14 10.3.2 4.0.16 10.4.0 4.1.10a This manual section covers the installation of the official MySQL Mac OS X PKG only. Make sure to read Apple's help information about installing MySQL: Run the `Help View' application, select `Mac OS X Server' help, do a search for `MySQL,' and read the item entitled `Installing MySQL.' For preinstalled versions of MySQL on Mac OS X Server, note especially that you should start `mysqld' with `safe_mysqld' instead of `mysqld_safe' if MySQL is older than version 4.0. If you previously used Marc Liyanage's MySQL packages for Mac OS X from `http://www.entropy.ch', you can simply follow the update instructions for packages using the binary installation layout as given on his pages. If you are upgrading from Marc's 3.23.x versions or from the Mac OS X Server version of MySQL to the official MySQL PKG, you also need to convert the existing MySQL privilege tables to the current format, because some new security privileges have been added. See *Note mysql-upgrade::. If you want MySQL to start automatically during system startup, you also need to install the MySQL Startup Item. It is part of the Mac OS X installation disk images as a separate installation package. Simply double-click the `MySQLStartupItem.pkg' icon and follow the instructions to install it. The Startup Item need be installed only once. There is no need to install it each time you upgrade the MySQL package later. The Startup Item for MySQL is installed into `/Library/StartupItems/MySQLCOM'. (Before MySQL 4.1.2, the location was `/Library/StartupItems/MySQL', but that collided with the MySQL Startup Item installed by Mac OS X Server.) Startup Item installation adds a variable `MYSQLCOM=-YES-' to the system configuration file `/etc/hostconfig'. If you want to disable the automatic startup of MySQL, simply change this variable to `MYSQLCOM=-NO-'. On Mac OS X Server, the default MySQL installation uses the variable `MYSQL' in the `/etc/hostconfig' file. The MySQL AB Startup Item installer disables this variable by setting it to `MYSQL=-NO-'. This avoids boot time conflicts with the `MYSQLCOM' variable used by the MySQL AB Startup Item. However, it does not shut down a running MySQL server. You should do that yourself. After the installation, you can start up MySQL by running the following commands in a terminal window. You must have administrator privileges to perform this task. If you have installed the Startup Item, use this command: shell> sudo /Library/StartupItems/MySQLCOM/MySQLCOM start (ENTER YOUR PASSWORD, IF NECESSARY) (PRESS CONTROL-D OR ENTER "EXIT" TO EXIT THE SHELL) If you don't use the Startup Item, enter the following command sequence: shell> cd /usr/local/mysql shell> sudo ./bin/mysqld_safe (ENTER YOUR PASSWORD, IF NECESSARY) (PRESS CONTROL-Z) shell> bg (PRESS CONTROL-D OR ENTER "EXIT" TO EXIT THE SHELL) You should be able to connect to the MySQL server, for example, by running `/usr/local/mysql/bin/mysql'. *Note*: The accounts that are listed in the MySQL grant tables initially have no passwords. After starting the server, you should set up passwords for them using the instructions in *Note post-installation::. You might want to add aliases to your shell's resource file to make it easier to access commonly used programs such as `mysql' and `mysqladmin' from the command line. The syntax for `bash' is: alias mysql=/usr/local/mysql/bin/mysql alias mysqladmin=/usr/local/mysql/bin/mysqladmin For `tcsh', use: alias mysql /usr/local/mysql/bin/mysql alias mysqladmin /usr/local/mysql/bin/mysqladmin Even better, add `/usr/local/mysql/bin' to your `PATH' environment variable. For example, add the following line to your `$HOME/.bashrc' file if your shell is `bash': PATH=${PATH}:/usr/local/mysql/bin Add the following line to your `$HOME/.tcshrc' file if your shell is `tcsh': setenv PATH ${PATH}:/usr/local/mysql/bin If no `.bashrc' or `.tcshrc' file exists in your home directory, create it with a text editor. If you are upgrading an existing installation, note that installing a new MySQL PKG does not remove the directory of an older installation. Unfortunately, the Mac OS X Installer does not yet offer the functionality required to properly upgrade previously installed packages. To use your existing databases with the new installation, you'll need to copy the contents of the old data directory to the new data directory. Make sure that neither the old server nor the new one is running when you do this. After you have copied over the MySQL database files from the previous installation and have successfully started the new server, you should consider removing the old installation files to save disk space. Additionally, you should also remove older versions of the Package Receipt directories located in `/Library/Receipts/mysql-VERSION.pkg'.  File: manual.info, Node: solaris-installation, Next: netware-installation, Prev: mac-os-x-installation, Up: installing-cs 2.4.11 Installing MySQL on Solaris ---------------------------------- If you install MySQL using a binary tarball distribution on Solaris, you may run into trouble even before you get the MySQL distribution unpacked, as the Solaris `tar' cannot handle long filenames. This means that you may see errors when you try to unpack MySQL. If this occurs, you must use GNU `tar' (`gtar') to unpack the distribution. You can find a precompiled copy for Solaris at `http://dev.mysql.com/downloads/os-solaris.html'. You can install MySQL on Solaris using a binary package in PKG format instead of the binary tarball distribution. Before installing using the binary PKG format, you should create the `mysql' user and group, for example: groupadd mysql useradd -g mysql mysql Some basic PKG-handling commands follow: * To add a package: pkgadd -d PACKAGE_NAME.pkg * To remove a package: pkgrm PACKAGE_NAME * To get a full list of installed packages: pkginfo * To get detailed information for a package: pkginfo -l PACKAGE_NAME * To list the files belonging to a package: pkgchk -v PACKAGE_NAME * To get packaging information for an arbitrary file: pkgchk -l -p FILE_NAME For additional information about installing MySQL on Solaris, see *Note solaris::.  File: manual.info, Node: netware-installation, Next: installing-binary, Prev: solaris-installation, Up: installing-cs 2.4.12 Installing MySQL on NetWare ---------------------------------- This section does not apply to MySQL Enterprise Server users. Porting MySQL to NetWare was an effort spearheaded by Novell. Novell customers should be pleased to note that NetWare 6.5 ships with bundled MySQL binaries, complete with an automatic commercial use license for all servers running that version of NetWare. MySQL for NetWare is compiled using a combination of Metrowerks CodeWarrior for NetWare and special cross-compilation versions of the GNU autotools. The latest binary packages for NetWare can be obtained at `http://dev.mysql.com/downloads/'. See *Note getting-mysql::. To host MySQL, the NetWare server must meet these requirements: * The latest Support Pack of NetWare 6.5 (http://support.novell.com/filefinder/18197/index.html) must be installed. * The system must meet Novell's minimum requirements to run the respective version of NetWare. * MySQL data and the program binaries must be installed on an NSS volume; traditional volumes are not supported. To install MySQL for NetWare, use the following procedure: 1. If you are upgrading from a prior installation, stop the MySQL server. This is done from the server console, using the following command: SERVER: mysqladmin -u root shutdown *Note*: If the MySQL `root' user account has a password, you need to invoke `mysqladmin' with the `-p' option and supply the password when prompted. 2. Log on to the target server from a client machine with access to the location where you are installing MySQL. 3. Extract the binary package Zip file onto the server. Be sure to allow the paths in the Zip file to be used. It is safe to simply extract the file to `SYS:\'. If you are upgrading from a prior installation, you may need to copy the data directory (for example, `SYS:MYSQL\DATA'), as well as `my.cnf', if you have customized it. You can then delete the old copy of MySQL. 4. You might want to rename the directory to something more consistent and easy to use. The examples in this manual use `SYS:MYSQL' to refer to the installation directory. Note that MySQL installation on NetWare does not detect if a version of MySQL is already installed outside the NetWare release. Therefore, if you have installed the latest MySQL version from the Web (for example, MySQL 4.1 or later) in `SYS:\MYSQL', you must rename the folder before upgrading the NetWare server; otherwise, files in `SYS:\MySQL' are overwritten by the MySQL version present in NetWare Support Pack. 5. At the server console, add a search path for the directory containing the MySQL NLMs. For example: SERVER: SEARCH ADD SYS:MYSQL\BIN 6. Initialize the data directory and the grant tables, if necessary, by executing `mysql_install_db' at the server console. 7. Start the MySQL server using `mysqld_safe' at the server console. 8. To finish the installation, you should also add the following commands to `autoexec.ncf'. For example, if your MySQL installation is in `SYS:MYSQL' and you want MySQL to start automatically, you could add these lines: #Starts the MySQL 5.0.x database server SEARCH ADD SYS:MYSQL\BIN MYSQLD_SAFE If you are running MySQL on NetWare 6.0, we strongly suggest that you use the `--skip-external-locking' option on the command line: #Starts the MySQL 5.0.x database server SEARCH ADD SYS:MYSQL\BIN MYSQLD_SAFE --skip-external-locking It is also necessary to use `CHECK TABLE' and `REPAIR TABLE' instead of `myisamchk', because `myisamchk' makes use of external locking. External locking is known to have problems on NetWare 6.0; the problem has been eliminated in NetWare 6.5. Note that the use of MySQL on Netware 6.0 is not officially supported. `mysqld_safe' on NetWare provides a screen presence. When you unload (shut down) the `mysqld_safe' NLM, the screen does not go away by default. Instead, it prompts for user input: ** If you want NetWare to close the screen automatically instead, use the `--autoclose' option to `mysqld_safe'. For example: #Starts the MySQL 5.0.x database server SEARCH ADD SYS:MYSQL\BIN MYSQLD_SAFE --autoclose The behavior of `mysqld_safe' on NetWare is described further in *Note mysqld-safe::. 9. When installing MySQL, either for the first time or upgrading from a previous version, download and install the latest and appropriate Perl module and PHP extensions for NetWare: * Perl: `http://forge.novell.com/modules/xfcontent/downloads.php/perl/Modules/' * PHP: `http://forge.novell.com/modules/xfcontent/downloads.php/php/Modules/' If there was an existing installation of MySQL on the NetWare server, be sure to check for existing MySQL startup commands in `autoexec.ncf', and edit or delete them as necessary. *Note*: The accounts that are listed in the MySQL grant tables initially have no passwords. After starting the server, you should set up passwords for them using the instructions in *Note post-installation::.  File: manual.info, Node: installing-binary, Next: installing-source, Prev: netware-installation, Up: installing-cs 2.4.13 Installing MySQL from `tar.gz' Packages on Other Unix-Like Systems ------------------------------------------------------------------------- This section does not apply to MySQL Enterprise Server users. This section covers the installation of MySQL binary distributions that are provided for various platforms in the form of compressed `tar' files (files with a `.tar.gz' extension). See *Note mysql-binaries::, for a detailed list. To obtain MySQL, see *Note getting-mysql::. MySQL `tar' file binary distributions have names of the form `mysql-VERSION-OS.tar.gz', where `VERSION' is a number (for example, `5.0.46'), and OS indicates the type of operating system for which the distribution is intended (for example, `pc-linux-i686'). In addition to these generic packages, we also offer binaries in platform-specific package formats for selected platforms. See *Note quick-standard-installation::, for more information on how to install these. You need the following tools to install a MySQL `tar' file binary distribution: * GNU `gunzip' to uncompress the distribution. * A reasonable `tar' to unpack the distribution. GNU `tar' is known to work. Some operating systems come with a preinstalled version of `tar' that is known to have problems. For example, Mac OS X `tar' and Sun `tar' are known to have problems with long filenames. On Mac OS X, you can use the preinstalled `gnutar' program. On other systems with a deficient `tar', you should install GNU `tar' first. If you run into problems and need to file a bug report, please use the instructions in *Note bug-reports::. The basic commands that you must execute to install and use a MySQL binary distribution are: shell> groupadd mysql shell> useradd -g mysql mysql shell> cd /usr/local shell> gunzip < /PATH/TO/MYSQL-VERSION-OS.tar.gz | tar xvf - shell> ln -s FULL-PATH-TO-MYSQL-VERSION-OS mysql shell> cd mysql shell> chown -R mysql . shell> chgrp -R mysql . shell> scripts/mysql_install_db --user=mysql shell> chown -R root . shell> chown -R mysql data shell> bin/mysqld_safe --user=mysql & *Note*: This procedure does not set up any passwords for MySQL accounts. After following the procedure, proceed to *Note post-installation::. A more detailed version of the preceding description for installing a binary distribution follows: 1. Add a login user and group for `mysqld' to run as: shell> groupadd mysql shell> useradd -g mysql mysql These commands add the `mysql' group and the `mysql' user. The syntax for `useradd' and `groupadd' may differ slightly on different versions of Unix, or they may have different names such as `adduser' and `addgroup'. You might want to call the user and group something else instead of `mysql'. If so, substitute the appropriate name in the following steps. 2. Pick the directory under which you want to unpack the distribution and change location into it. In the following example, we unpack the distribution under `/usr/local'. (The instructions, therefore, assume that you have permission to create files and directories in `/usr/local'. If that directory is protected, you must perform the installation as `root'.) shell> cd /usr/local 3. Obtain a distribution file using the instructions in *Note getting-mysql::. For a given release, binary distributions for all platforms are built from the same MySQL source distribution. 4. Unpack the distribution, which creates the installation directory. Then create a symbolic link to that directory: shell> gunzip < /PATH/TO/MYSQL-VERSION-OS.tar.gz | tar xvf - shell> ln -s FULL-PATH-TO-MYSQL-VERSION-OS mysql The `tar' command creates a directory named `mysql-VERSION-OS'. The `ln' command makes a symbolic link to that directory. This lets you refer more easily to the installation directory as `/usr/local/mysql'. With GNU `tar', no separate invocation of `gunzip' is necessary. You can replace the first line with the following alternative command to uncompress and extract the distribution: shell> tar zxvf /PATH/TO/MYSQL-VERSION-OS.tar.gz 5. Change location into the installation directory: shell> cd mysql You will find several files and subdirectories in the `mysql' directory. The most important for installation purposes are the `bin' and `scripts' subdirectories: * The `bin' directory contains client programs and the server. You should add the full pathname of this directory to your `PATH' environment variable so that your shell finds the MySQL programs properly. See *Note environment-variables::. * The `scripts' directory contains the `mysql_install_db' script used to initialize the `mysql' database containing the grant tables that store the server access permissions. 6. Ensure that the distribution contents are accessible to `mysql'. If you unpacked the distribution as `mysql', no further action is required. If you unpacked the distribution as `root', its contents will be owned by `root'. Change its ownership to `mysql' by executing the following commands as `root' in the installation directory: shell> chown -R mysql . shell> chgrp -R mysql . The first command changes the owner attribute of the files to the `mysql' user. The second changes the group attribute to the `mysql' group. 7. If you have not installed MySQL before, you must create the MySQL data directory and initialize the grant tables: shell> scripts/mysql_install_db --user=mysql If you run the command as `root', include the `--user' option as shown. If you run the command while logged in as that user, you can omit the `--user' option. The command should create the data directory and its contents with `mysql' as the owner. After creating or updating the grant tables, you need to restart the server manually. 8. Most of the MySQL installation can be owned by `root' if you like. The exception is that the data directory must be owned by `mysql'. To accomplish this, run the following commands as `root' in the installation directory: shell> chown -R root . shell> chown -R mysql data 9. If you want MySQL to start automatically when you boot your machine, you can copy `support-files/mysql.server' to the location where your system has its startup files. More information can be found in the `support-files/mysql.server' script itself and in *Note automatic-start::. 10. You can set up new accounts using the `bin/mysql_setpermission' script if you install the `DBI' and `DBD::mysql' Perl modules. See *Note mysql-setpermission::. For Perl module installation instructions, see *Note perl-support::. 11. If you would like to use `mysqlaccess' and have the MySQL distribution in some non-standard location, you must change the location where `mysqlaccess' expects to find the `mysql' client. Edit the `bin/mysqlaccess' script at approximately line 18. Search for a line that looks like this: $MYSQL = '/usr/local/bin/mysql'; # path to mysql executable Change the path to reflect the location where `mysql' actually is stored on your system. If you do not do this, a `Broken pipe' error will occur when you run `mysqlaccess'. After everything has been unpacked and installed, you should test your distribution. To start the MySQL server, use the following command: shell> bin/mysqld_safe --user=mysql & If you run the command as `root', you must use the `--user' option as shown. The value of the option is the name of the login account that you created in the first step to use for running the server. If you run the command while logged in as `mysql', you can omit the `--user' option. If the command fails immediately and prints `mysqld ended', you can find some information in the `HOST_NAME.err' file in the data directory. More information about `mysqld_safe' is given in *Note mysqld-safe::. *Note*: The accounts that are listed in the MySQL grant tables initially have no passwords. After starting the server, you should set up passwords for them using the instructions in *Note post-installation::.  File: manual.info, Node: installing-source, Next: post-installation, Prev: installing-binary, Up: installing-cs 2.4.14 MySQL Installation Using a Source Distribution ----------------------------------------------------- * Menu: * quick-install:: Source Installation Overview * configure-options:: Typical `configure' Options * installing-source-tree:: Installing from the Development Source Tree * compilation-problems:: Dealing with Problems Compiling MySQL * mit-pthreads:: MIT-pthreads Notes * windows-source-build:: Installing MySQL from Source on Windows * windows-client-compiling:: Compiling MySQL Clients on Windows This section does not apply to MySQL Enterprise Server users. Before you proceed with an installation from source, first check whether our binary is available for your platform and whether it works for you. We put a great deal of effort into ensuring that our binaries are built with the best possible options. To obtain a source distribution for MySQL, *Note getting-mysql::. If you want to build MySQL from source on Windows, see *Note windows-source-build::. MySQL source distributions are provided as compressed `tar' archives and have names of the form `mysql-VERSION.tar.gz', where VERSION is a number like `5.0.46'. You need the following tools to build and install MySQL from source: * GNU `gunzip' to uncompress the distribution. * A reasonable `tar' to unpack the distribution. GNU `tar' is known to work. Some operating systems come with a preinstalled version of `tar' that is known to have problems. For example, the `tar' provided with early versions of Mac OS X `tar', SunOS 4.x and Solaris 8 and earlier are known to have problems with long filenames. On Mac OS X, you can use the preinstalled `gnutar' program. On other systems with a deficient `tar', you should install GNU `tar' first. * A working ANSI C++ compiler. `gcc' 2.95.2 or later, `egcs' 1.0.2 or later or `egcs 2.91.66', SGI C++, and SunPro C++ are some of the compilers that are known to work. `libg++' is not needed when using `gcc'. `gcc' 2.7.x has a bug that makes it impossible to compile some perfectly legal C++ files, such as `sql/sql_base.cc'. If you have only `gcc' 2.7.x, you must upgrade your `gcc' to be able to compile MySQL. `gcc' 2.8.1 is also known to have problems on some platforms, so it should be avoided if a new compiler exists for the platform. `gcc' 2.95.2 or later is recommended when compiling MySQL 3.23.x. * A good `make' program. GNU `make' is always recommended and is sometimes required. If you have problems, we recommend GNU `make' 3.75 or newer. If you are using a version of `gcc' recent enough to understand the `-fno-exceptions' option, it is _very important_ that you use this option. Otherwise, you may compile a binary that crashes randomly. We also recommend that you use `-felide-constructors' and `-fno-rtti' along with `-fno-exceptions'. When in doubt, do the following: CFLAGS="-O3" CXX=gcc CXXFLAGS="-O3 -felide-constructors \ -fno-exceptions -fno-rtti" ./configure \ --prefix=/usr/local/mysql --enable-assembler \ --with-mysqld-ldflags=-all-static On most systems, this gives you a fast and stable binary. If you run into problems and need to file a bug report, please use the instructions in *Note bug-reports::.  File: manual.info, Node: quick-install, Next: configure-options, Prev: installing-source, Up: installing-source 2.4.14.1 Source Installation Overview ..................................... This section does not apply to MySQL Enterprise Server users. The basic commands that you must execute to install a MySQL source distribution are: shell> groupadd mysql shell> useradd -g mysql mysql shell> gunzip < mysql-VERSION.tar.gz | tar -xvf - shell> cd mysql-VERSION shell> ./configure --prefix=/usr/local/mysql shell> make shell> make install shell> cp support-files/my-medium.cnf /etc/my.cnf shell> cd /usr/local/mysql shell> chown -R mysql . shell> chgrp -R mysql . shell> bin/mysql_install_db --user=mysql shell> chown -R root . shell> chown -R mysql var shell> bin/mysqld_safe --user=mysql & If you start from a source RPM, do the following: shell> rpmbuild --rebuild --clean MySQL-VERSION.src.rpm This makes a binary RPM that you can install. For older versions of RPM, you may have to replace the command `rpmbuild' with `rpm' instead. *Note*: This procedure does not set up any passwords for MySQL accounts. After following the procedure, proceed to *Note post-installation::, for post-installation setup and testing. A more detailed version of the preceding description for installing MySQL from a source distribution follows: 1. Add a login user and group for `mysqld' to run as: shell> groupadd mysql shell> useradd -g mysql mysql These commands add the `mysql' group and the `mysql' user. The syntax for `useradd' and `groupadd' may differ slightly on different versions of Unix, or they may have different names such as `adduser' and `addgroup'. You might want to call the user and group something else instead of `mysql'. If so, substitute the appropriate name in the following steps. 2. Perform the following steps as the `mysql' user, except as noted. 3. Pick the directory under which you want to unpack the distribution and change location into it. 4. Obtain a distribution file using the instructions in *Note getting-mysql::. 5. Unpack the distribution into the current directory: shell> gunzip < /PATH/TO/MYSQL-VERSION.tar.gz | tar xvf - This command creates a directory named `mysql-VERSION'. With GNU `tar', no separate invocation of `gunzip' is necessary. You can use the following alternative command to uncompress and extract the distribution: shell> tar zxvf /PATH/TO/MYSQL-VERSION-OS.tar.gz 6. Change location into the top-level directory of the unpacked distribution: shell> cd mysql-VERSION Note that currently you must configure and build MySQL from this top-level directory. You cannot build it in a different directory. 7. Configure the release and compile everything: shell> ./configure --prefix=/usr/local/mysql shell> make When you run `configure', you might want to specify other options. Run `./configure --help' for a list of options. *Note configure-options::, discusses some of the more useful options. If `configure' fails and you are going to send mail to a MySQL mailing list to ask for assistance, please include any lines from `config.log' that you think can help solve the problem. Also include the last couple of lines of output from `configure'. To file a bug report, please use the instructions in *Note bug-reports::. If the compile fails, see *Note compilation-problems::, for help. 8. Install the distribution: shell> make install You might need to run this command as `root'. If you want to set up an option file, use one of those present in the `support-files' directory as a template. For example: shell> cp support-files/my-medium.cnf /etc/my.cnf You might need to run this command as `root'. If you want to configure support for `InnoDB' tables, you should edit the `/etc/my.cnf' file, remove the `#' character before the option lines that start with `innodb_...', and modify the option values to be what you want. See *Note option-files::, and *Note innodb-configuration::. 9. Change location into the installation directory: shell> cd /usr/local/mysql 10. If you ran the `make install' command as `root', the installed files will be owned by `root'. Ensure that the installation is accessible to `mysql' by executing the following commands as `root' in the installation directory: shell> chown -R mysql . shell> chgrp -R mysql . The first command changes the owner attribute of the files to the `mysql' user. The second changes the group attribute to the `mysql' group. 11. If you have not installed MySQL before, you must create the MySQL data directory and initialize the grant tables: shell> bin/mysql_install_db --user=mysql If you run the command as `root', include the `--user' option as shown. If you run the command while logged in as `mysql', you can omit the `--user' option. The command should create the data directory and its contents with `mysql' as the owner. After using `mysql_install_db' to create the grant tables for MySQL, you must restart the server manually. The `mysqld_safe' command to do this is shown in a later step. 12. Most of the MySQL installation can be owned by `root' if you like. The exception is that the data directory must be owned by `mysql'. To accomplish this, run the following commands as `root' in the installation directory: shell> chown -R root . shell> chown -R mysql var 13. If you want MySQL to start automatically when you boot your machine, you can copy `support-files/mysql.server' to the location where your system has its startup files. More information can be found in the `support-files/mysql.server' script itself; see also *Note automatic-start::. 14. You can set up new accounts using the `bin/mysql_setpermission' script if you install the `DBI' and `DBD::mysql' Perl modules. See *Note mysql-setpermission::. For Perl module installation instructions, see *Note perl-support::. After everything has been installed, you should test your distribution. To start the MySQL server, use the following command: shell> /usr/local/mysql/bin/mysqld_safe --user=mysql & If you run the command as `root', you should use the `--user' option as shown. The value of the option is the name of the login account that you created in the first step to use for running the server. If you run the command while logged in as that user, you can omit the `--user' option. If the command fails immediately and prints `mysqld ended', you can find some information in the `HOST_NAME.err' file in the data directory. More information about `mysqld_safe' is given in *Note mysqld-safe::. *Note*: The accounts that are listed in the MySQL grant tables initially have no passwords. After starting the server, you should set up passwords for them using the instructions in *Note post-installation::.  File: manual.info, Node: configure-options, Next: installing-source-tree, Prev: quick-install, Up: installing-source 2.4.14.2 Typical `configure' Options .................................... This section does not apply to MySQL Enterprise Server users. The `configure' script gives you a great deal of control over how you configure a MySQL source distribution. Typically you do this using options on the `configure' command line. You can also affect `configure' using certain environment variables. See *Note environment-variables::. For a full list of options supported by `configure', run this command: shell> ./configure --help Some of the `configure' options available are described here: * To compile just the MySQL client libraries and client programs and not the server, use the `--without-server' option: shell> ./configure --without-server If you have no C++ compiler, some client programs such as `mysql' cannot be compiled because they require C++.. In this case, you can remove the code in `configure' that tests for the C++ compiler and then run `./configure' with the `--without-server' option. The compile step should still try to build all clients, but you can ignore any warnings about files such as `mysql.cc'. (If `make' stops, try `make -k' to tell it to continue with the rest of the build even if errors occur.) * If you want to build the embedded MySQL library (`libmysqld.a'), use the `--with-embedded-server' option. * If you don't want your log files and database directories located under `/usr/local/var', use a `configure' command something like one of these: shell> ./configure --prefix=/usr/local/mysql shell> ./configure --prefix=/usr/local \ --localstatedir=/usr/local/mysql/data The first command changes the installation prefix so that everything is installed under `/usr/local/mysql' rather than the default of `/usr/local'. The second command preserves the default installation prefix, but overrides the default location for database directories (normally `/usr/local/var') and changes it to `/usr/local/mysql/data'. You can also specify the installation directory and data directory locations at server startup time by using the `--basedir' and `--datadir' options. These can be given on the command line or in an MySQL option file, although it is more common to use an option file. See *Note option-files::. * If you are using Unix and you want the MySQL socket file location to be somewhere other than the default location (normally in the directory `/tmp' or `/var/run'), use a `configure' command like this: shell> ./configure \ --with-unix-socket-path=/usr/local/mysql/tmp/mysql.sock The socket filename must be an absolute pathname. You can also change the location of `mysql.sock' at server startup by using a MySQL option file. See *Note problems-with-mysql-sock::. * If you want to compile statically linked programs (for example, to make a binary distribution, to get better performance, or to work around problems with some Red Hat Linux distributions), run `configure' like this: shell> ./configure --with-client-ldflags=-all-static \ --with-mysqld-ldflags=-all-static * If you are using `gcc' and don't have `libg++' or `libstdc++' installed, you can tell `configure' to use `gcc' as your C++ compiler: shell> CC=gcc CXX=gcc ./configure When you use `gcc' as your C++ compiler, it does not attempt to link in `libg++' or `libstdc++'. This may be a good thing to do even if you have those libraries installed. Some versions of them have caused strange problems for MySQL users in the past. The following list indicates some compilers and environment variable settings that are commonly used with each one. * `gcc' 2.7.2: CC=gcc CXX=gcc CXXFLAGS="-O3 -felide-constructors" * `egcs' 1.0.3a: CC=gcc CXX=gcc CXXFLAGS="-O3 -felide-constructors \ -fno-exceptions -fno-rtti" * `gcc' 2.95.2: CFLAGS="-O3 -mpentiumpro" CXX=gcc CXXFLAGS="-O3 -mpentiumpro \ -felide-constructors -fno-exceptions -fno-rtti" * `pgcc' 2.90.29 or newer: CFLAGS="-O3 -mpentiumpro -mstack-align-double" CXX=gcc \ CXXFLAGS="-O3 -mpentiumpro -mstack-align-double \ -felide-constructors -fno-exceptions -fno-rtti" In most cases, you can get a reasonably optimized MySQL binary by using the options from the preceding list and adding the following options to the `configure' line: --prefix=/usr/local/mysql --enable-assembler \ --with-mysqld-ldflags=-all-static The full `configure' line would, in other words, be something like the following for all recent `gcc' versions: CFLAGS="-O3 -mpentiumpro" CXX=gcc CXXFLAGS="-O3 -mpentiumpro \ -felide-constructors -fno-exceptions -fno-rtti" ./configure \ --prefix=/usr/local/mysql --enable-assembler \ --with-mysqld-ldflags=-all-static The binaries we provide on the MySQL Web site at `http://dev.mysql.com/downloads/' are all compiled with full optimization and should be perfect for most users. See *Note mysql-binaries::. There are some configuration settings you can tweak to build an even faster binary, but these are only for advanced users. See *Note compile-and-link-options::. If the build fails and produces errors about your compiler or linker not being able to create the shared library `libmysqlclient.so.N' (where N is a version number), you can work around this problem by giving the `--disable-shared' option to `configure'. In this case, `configure' does not build a shared `libmysqlclient.so.N' library. * By default, MySQL uses the `latin1' (cp1252 West European) character set. To change the default set, use the `--with-charset' option: shell> ./configure --with-charset=CHARSET CHARSET may be one of `binary', `armscii8', `ascii', `big5', `cp1250', `cp1251', `cp1256', `cp1257', `cp850', `cp852', `cp866', `cp932', `dec8', `eucjpms', `euckr', `gb2312', `gbk', `geostd8', `greek', `hebrew', `hp8', `keybcs2', `koi8r', `koi8u', `latin1', `latin2', `latin5', `latin7', `macce', `macroman', `sjis', `swe7', `tis620', `ucs2', `ujis', `utf8'. See *Note character-sets::. (Additional character sets might be available. Check the output from `./configure --help' for the current list.) The default collation may also be specified. MySQL uses the `latin1_swedish_ci' collation by default. To change this, use the `--with-collation' option: shell> ./configure --with-collation=COLLATION To change both the character set and the collation, use both the `--with-charset' and `--with-collation' options. The collation must be a legal collation for the character set. (Use the `SHOW COLLATION' statement to determine which collations are available for each character set.) *Warning:* If you change character sets after having created any tables, you must run `myisamchk -r -q --set-collation=COLLATION_NAME' _on every `MyISAM' table_. Your indexes may be sorted incorrectly otherwise. This can happen if you install MySQL, create some tables, and then reconfigure MySQL to use a different character set and reinstall it. With the `configure' option `--with-extra-charsets=LIST', you can define which additional character sets should be compiled into the server. LIST is one of the following: * A list of character set names separated by spaces * `complex' to include all character sets that can't be dynamically loaded * `all' to include all character sets into the binaries Clients that want to convert characters between the server and the client should use the `SET NAMES' statement. See *Note set-option::, and *Note charset-connection::. * To configure MySQL with debugging code, use the `--with-debug' option: shell> ./configure --with-debug This causes a safe memory allocator to be included that can find some errors and that provides output about what is happening. See MySQL Internals: Porting (http://forge.mysql.com/wiki/MySQL_Internals_Porting). As of MySQL 5.0.25, using `--with-debug' to configure MySQL with debugging support enables you to use the `--debug="d,parser_debug"' 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. * If your client programs are using threads, you must compile a thread-safe version of the MySQL client library with the `--enable-thread-safe-client' configure option. This creates a `libmysqlclient_r' library with which you should link your threaded applications. See *Note threaded-clients::. * It is possible to build MySQL 5.0 with large table support using the `--with-big-tables' option, beginning with MySQL 5.0.4. This option causes the variables that store table row counts to be declared as `unsigned long long' rather than `unsigned long'. This enables tables to hold up to approximately 1.844E+19 ((2^32)^2) rows rather than 2^32 (~4.295E+09) rows. Previously it was necessary to pass `-DBIG_TABLES' to the compiler manually in order to enable this feature. * Run `configure' with the `--disable-grant-options' option to cause the the `--bootstrap', `--skip-grant-tables', and `--init-file' options for `mysqld' to be disabled. For Windows, the `configure.js' script recognizes the `DISABLE_GRANT_OPTIONS' flag, which has the same effect. The capability is available as of MySQL 5.0.34. * See *Note operating-system-specific-notes::, for options that pertain to particular operating systems. * See *Note secure-using-ssl::, for options that pertain to configuring MySQL to support secure (encrypted) connections.  File: manual.info, Node: installing-source-tree, Next: compilation-problems, Prev: configure-options, Up: installing-source 2.4.14.3 Installing from the Development Source Tree .................................................... This section does not apply to MySQL Enterprise Server users. *Caution*: You should read this section only if you are interested in helping us test our new code. If you just want to get MySQL up and running on your system, you should use a standard release distribution (either a binary or source distribution). To obtain our most recent development source tree, first download and install the BitKeeper free client if you do not have it. The client can be obtained from `http://www.bitmover.com/bk-client2.0.shar'. Note that you will need `gcc' and `make' to build the BitKeeper free client, and `patch' and `tar' to use the BitKeeper free client. _Note that old 1.1 versions of the BitKeeper free client will not work!_ To install the BitKeeper client on Unix, use these commands: shell> /bin/sh bk-client2.0.shar shell> cd bk-client2.0 shell> make If you get a `cc: command not found' error, invoke this command before running `make': shell> make CC=gcc The step above will create the utility `bkf', which is the free BitKeeper client. To install the BitKeeper client on Windows, use these instructions: 1. Download and install Cygwin from http://cygwin.com (http://cygwin.com/). 2. Make sure `patch', `tar', `gcc' and `make' have been installed under Cygwin. You can test this by issuing `which GCC' for each command. If a required tool is not installed, run Cygwin's package manager, select the required tools and install them. 3. For the installation of the BitKeeper free client, use the same installations as given for Unix-like systems above. For more information on `bkf', use: shell> bkf --help After you have installed the BitKeeper client, you can access the MySQL development source tree: 1. Change location to the directory you want to work from, and then use the following command to make a local copy of the MySQL 5.0 branch: shell> bkf clone bk://mysql.bkbits.net/mysql-5.0 mysql-5.0 In the preceding example, the source tree is set up in the `mysql-5.0/' subdirectory of your current directory. The initial download of the source tree may take a while, depending on the speed of your connection. Please be patient. 2. You need GNU `make', `autoconf' 2.58 (or newer), `automake' 1.8.1, `libtool' 1.5, and `m4' to run the next set of commands. Even though many operating systems come with their own implementation of `make', chances are high that the compilation fails with strange error messages. Therefore, it is highly recommended that you use GNU `make' (sometimes named `gmake') instead. Fortunately, a large number of operating systems ship with the GNU toolchain preinstalled or supply installable packages of these. In any case, they can also be downloaded from the following locations: * `http://www.gnu.org/software/autoconf/' * `http://www.gnu.org/software/automake/' * `http://www.gnu.org/software/libtool/' * `http://www.gnu.org/software/m4/' * `http://www.gnu.org/software/make/' To configure MySQL 5.0, you also need GNU `bison'. You should use the latest version of bison where possible. Version 1.75 and version 2.1 are known to work. There have been reported problems with `bison' 1.875. If you experience problems, upgrade to a later, rather than earlier, version. Versions of `bison' older than 1.75 may report this error: sql_yacc.yy:#####: fatal error: maximum table size (32767) exceeded Note: The maximum table size is not actually exceeded; the error is caused by bugs in older versions of `bison'. The following example shows the typical commands required to configure a source tree. The first `cd' command changes location into the top-level directory of the tree; replace `mysql-5.0' with the appropriate directory name. shell> cd mysql-5.0 shell> (cd bdb/dist; sh s_all) shell> (cd innobase; autoreconf --force --install) shell> autoreconf --force --install shell> ./configure # Add your favorite options here shell> make Or you can use `BUILD/autorun.sh' as a shortcut for the following sequence of commands: shell> aclocal; autoheader shell> libtoolize --automake --force shell> automake --force --add-missing; autoconf shell> (cd innobase; aclocal; autoheader; autoconf; automake) shell> (cd bdb/dist; sh s_all) The command lines that change directory into the `innobase' and `bdb/dist' directories are used to configure the `InnoDB' and Berkeley DB (`BDB') storage engines. You can omit these command lines if you to not require `InnoDB' or `BDB' support. If you get some strange errors during this stage, verify that you really have `libtool' installed. A collection of our standard configuration scripts is located in the `BUILD/' subdirectory. You may find it more convenient to use the `BUILD/compile-pentium-debug' script than the preceding set of shell commands. To compile on a different architecture, modify the script by removing flags that are Pentium-specific. 3. When the build is done, run `make install'. Be careful with this on a production machine; the command may overwrite your live release installation. If you have another installation of MySQL, we recommend that you run `./configure' with different values for the `--prefix', `--with-tcp-port', and `--unix-socket-path' options than those used for your production server. 4. Play hard with your new installation and try to make the new features crash. Start by running `make test'. See *Note mysql-test-suite::. 5. If you have gotten to the `make' stage, but the distribution does not compile, please enter the problem into our bugs database using the instructions given in *Note bug-reports::. If you have installed the latest versions of the required GNU tools, and they crash trying to process our configuration files, please report that also. However, if you execute `aclocal' and get a `command not found' error or a similar problem, do not report it. Instead, make sure that all the necessary tools are installed and that your `PATH' variable is set correctly so that your shell can find them. 6. After initially copying the repository with `bkf' to obtain the source tree, you should use `pull' option to periodically update your local copy. To do this any time after you have set up the repository, use this command: shell> bkf pull 7. You can examine the changeset comments for the tree by using the `changes' option to `bkf': shell> bkf changes To get a list of the changes that would be applied with the next `bkf pull': shell> bkf changes -R To obtain a patch file for a specific changeset (`CSETID'), use: shell> bkf changes -vvrCSETID If you see diffs or code that you have a question about, do not hesitate to send email to the MySQL Internals mailing list. (See *Note mailing-lists::.) Also, if you think you have a better idea on how to do something, send an email message to the list with your proposed patch. You can also browse changesets, comments, and source code online. To browse this information for MySQL 5.0, go to `http://mysql.bkbits.net:8080/mysql-5.0'.  File: manual.info, Node: compilation-problems, Next: mit-pthreads, Prev: installing-source-tree, Up: installing-source 2.4.14.4 Dealing with Problems Compiling MySQL .............................................. This section does not apply to MySQL Enterprise Server users. All MySQL programs compile cleanly for us with no warnings on Solaris or Linux using `gcc'. On other systems, warnings may occur due to differences in system include files. See *Note mit-pthreads::, for warnings that may occur when using MIT-pthreads. For other problems, check the following list. The solution to many problems involves reconfiguring. If you do need to reconfigure, take note of the following: * If `configure' is run after it has previously been run, it may use information that was gathered during its previous invocation. This information is stored in `config.cache'. When `configure' starts up, it looks for that file and reads its contents if it exists, on the assumption that the information is still correct. That assumption is invalid when you reconfigure. * Each time you run `configure', you must run `make' again to recompile. However, you may want to remove old object files from previous builds first because they were compiled using different configuration options. To prevent old configuration information or object files from being used, run these commands before re-running `configure': shell> rm config.cache shell> make clean Alternatively, you can run `make distclean'. The following list describes some of the problems when compiling MySQL that have been found to occur most often: * If you get errors such as the ones shown here when compiling `sql_yacc.cc', you probably have run out of memory or swap space: Internal compiler error: program cc1plus got fatal signal 11 Out of virtual memory Virtual memory exhausted The problem is that `gcc' requires a huge amount of memory to compile `sql_yacc.cc' with inline functions. Try running `configure' with the `--with-low-memory' option: shell> ./configure --with-low-memory This option causes `-fno-inline' to be added to the compile line if you are using `gcc' and `-O0' if you are using something else. You should try the `--with-low-memory' option even if you have so much memory and swap space that you think you can't possibly have run out. This problem has been observed to occur even on systems with generous hardware configurations, and the `--with-low-memory' option usually fixes it. * By default, `configure' picks `c++' as the compiler name and GNU `c++' links with `-lg++'. If you are using `gcc', that behavior can cause problems during configuration such as this: configure: error: installation or configuration problem: C++ compiler cannot create executables. You might also observe problems during compilation related to `g++', `libg++', or `libstdc++'. One cause of these problems is that you may not have `g++', or you may have `g++' but not `libg++', or `libstdc++'. Take a look at the `config.log' file. It should contain the exact reason why your C++ compiler didn't work. To work around these problems, you can use `gcc' as your C++ compiler. Try setting the environment variable `CXX' to `"gcc -O3"'. For example: shell> CXX="gcc -O3" ./configure This works because `gcc' compiles C++ source files as well as `g++' does, but does not link in `libg++' or `libstdc++' by default. Another way to fix these problems is to install `g++', `libg++', and `libstdc++'. However, we recommend that you not use `libg++' or `libstdc++' with MySQL because this only increases the binary size of `mysqld' without providing any benefits. Some versions of these libraries have also caused strange problems for MySQL users in the past. * If your compile fails with errors such as any of the following, you must upgrade your version of `make' to GNU `make': making all in mit-pthreads make: Fatal error in reader: Makefile, line 18: Badly formed macro assignment Or: make: file `Makefile' line 18: Must be a separator (: Or: pthread.h: No such file or directory Solaris and FreeBSD are known to have troublesome `make' programs. GNU `make' 3.75 is known to work. * If you want to define flags to be used by your C or C++ compilers, do so by adding the flags to the `CFLAGS' and `CXXFLAGS' environment variables. You can also specify the compiler names this way using `CC' and `CXX'. For example: shell> CC=gcc shell> CFLAGS=-O3 shell> CXX=gcc shell> CXXFLAGS=-O3 shell> export CC CFLAGS CXX CXXFLAGS See *Note mysql-binaries::, for a list of flag definitions that have been found to be useful on various systems. * If you get errors such as those shown here when compiling `mysqld', `configure' did not correctly detect the type of the last argument to `accept()', `getsockname()', or `getpeername()': cxx: Error: mysqld.cc, line 645: In this statement, the referenced type of the pointer value ''length'' is ''unsigned long'', which is not compatible with ''int''. new_sock = accept(sock, (struct sockaddr *)&cAddr, &length); To fix this, edit the `config.h' file (which is generated by `configure'). Look for these lines: /* Define as the base type of the last arg to accept */ #define SOCKET_SIZE_TYPE XXX Change `XXX' to `size_t' or `int', depending on your operating system. (You must do this each time you run `configure' because `configure' regenerates `config.h'.) * The `sql_yacc.cc' file is generated from `sql_yacc.yy'. Normally, the build process does not need to create `sql_yacc.cc' because MySQL comes with a pre-generated copy. However, if you do need to re-create it, you might encounter this error: "sql_yacc.yy", line XXX fatal: default action causes potential... This is a sign that your version of `yacc' is deficient. You probably need to install `bison' (the GNU version of `yacc') and use that instead. * On Debian Linux 3.0, you need to install `gawk' instead of the default `mawk' if you want to compile MySQL with Berkeley DB support. * If you need to debug `mysqld' or a MySQL client, run `configure' with the `--with-debug' option, and then recompile and link your clients with the new client library. See MySQL Internals: Porting (http://forge.mysql.com/wiki/MySQL_Internals_Porting). * If you get a compilation error on Linux (for example, SuSE Linux 8.1 or Red Hat Linux 7.3) similar to the following one, you probably do not have `g++' installed: libmysql.c:1329: warning: passing arg 5 of `gethostbyname_r' from incompatible pointer type libmysql.c:1329: too few arguments to function `gethostbyname_r' libmysql.c:1329: warning: assignment makes pointer from integer without a cast make[2]: *** [libmysql.lo] Error 1 By default, the `configure' script attempts to determine the correct number of arguments by using `g++' (the GNU C++ compiler). This test yields incorrect results if `g++' is not installed. There are two ways to work around this problem: * Make sure that the GNU C++ `g++' is installed. On some Linux distributions, the required package is called `gpp'; on others, it is named `gcc-c++'. * Use `gcc' as your C++ compiler by setting the `CXX' environment variable to `gcc': export CXX="gcc" You must run `configure' again after making either of those changes.  File: manual.info, Node: mit-pthreads, Next: windows-source-build, Prev: compilation-problems, Up: installing-source 2.4.14.5 MIT-pthreads Notes ........................... This section does not apply to MySQL Enterprise Server users. This section describes some of the issues involved in using MIT-pthreads. On Linux, you should _not_ use MIT-pthreads. Use the installed LinuxThreads implementation instead. See *Note linux::. If your system does not provide native thread support, you should build MySQL using the MIT-pthreads package. This includes older FreeBSD systems, SunOS 4.x, Solaris 2.4 and earlier, and some others. See *Note which-os::. MIT-pthreads is not part of the MySQL 5.0 source distribution. If you require this package, you need to download it separately from `http://dev.mysql.com/Downloads/Contrib/pthreads-1_60_beta6-mysql.tar.gz' After downloading, extract this source archive into the top level of the MySQL source directory. It creates a new subdirectory named `mit-pthreads'. * On most systems, you can force MIT-pthreads to be used by running `configure' with the `--with-mit-threads' option: shell> ./configure --with-mit-threads Building in a non-source directory is not supported when using MIT-pthreads because we want to minimize our changes to this code. * The checks that determine whether to use MIT-pthreads occur only during the part of the configuration process that deals with the server code. If you have configured the distribution using `--without-server' to build only the client code, clients do not know whether MIT-pthreads is being used and use Unix socket file connections by default. Because Unix socket files do not work under MIT-pthreads on some platforms, this means you need to use `-h' or `--host' with a value other than `localhost' when you run client programs. * When MySQL is compiled using MIT-pthreads, system locking is disabled by default for performance reasons. You can tell the server to use system locking with the `--external-locking' option. This is needed only if you want to be able to run two MySQL servers against the same data files, but that is not recommended, anyway. * Sometimes the pthread `bind()' command fails to bind to a socket without any error message (at least on Solaris). The result is that all connections to the server fail. For example: shell> mysqladmin version mysqladmin: connect to server at '' failed; error: 'Can't connect to mysql server on localhost (146)' The solution to this problem is to kill the `mysqld' server and restart it. This has happened to us only when we have forcibly stopped the server and restarted it immediately. * With MIT-pthreads, the `sleep()' system call isn't interruptible with `SIGINT' (break). This is noticeable only when you run `mysqladmin --sleep'. You must wait for the `sleep()' call to terminate before the interrupt is served and the process stops. * When linking, you might receive warning messages like these (at least on Solaris); they can be ignored: ld: warning: symbol `_iob' has differing sizes: (file /my/local/pthreads/lib/libpthread.a(findfp.o) value=0x4; file /usr/lib/libc.so value=0x140); /my/local/pthreads/lib/libpthread.a(findfp.o) definition taken ld: warning: symbol `__iob' has differing sizes: (file /my/local/pthreads/lib/libpthread.a(findfp.o) value=0x4; file /usr/lib/libc.so value=0x140); /my/local/pthreads/lib/libpthread.a(findfp.o) definition taken * Some other warnings also can be ignored: implicit declaration of function `int strtoll(...)' implicit declaration of function `int strtoul(...)' * We have not been able to make `readline' work with MIT-pthreads. (This is not necessary, but may be of interest to some.)  File: manual.info, Node: windows-source-build, Next: windows-client-compiling, Prev: mit-pthreads, Up: installing-source 2.4.14.6 Installing MySQL from Source on Windows ................................................ * Menu: * windows-source-build-cmake:: Building MySQL from Source Using CMake and Visual Studio * windows-vc-plus-plus-build:: Building MySQL from Source Using VC++ * borland-c-plus-plus:: Building MySQL from Source Using Borland C++ * windows-bitkeeper-build:: Creating a Windows Source Package from the Latest Development Source This section does not apply to MySQL Enterprise Server users. These instructions describe how to build binaries from source for MySQL 5.0 on Windows. Instructions are provided for building binaries from a standard source distribution or from the BitKeeper tree that contains the latest development source. *Note*: The instructions here are strictly for users who want to test MySQL on Microsoft Windows from the latest source distribution or from the BitKeeper tree. For production use, MySQL AB does not advise using a MySQL server built by yourself from source. Normally, it is best to use precompiled binary distributions of MySQL that are built specifically for optimal performance on Windows by MySQL AB. Instructions for installing binary distributions are available in *Note windows-installation::. To build MySQL on Windows from source, you must satisfy the following system, compiler, and resource requirements: * Windows 2000, Windows XP, or newer version. Windows Vista is not supported until Microsoft certifies Visual Studio 2005 on Vista. * CMake, which can be downloaded from `http://www.cmake.org'. After installing, modify your path to include the `cmake' binary. * Microsoft Visual C++ 2005 Express Edition, Visual Studio .Net 2003 (7.1), or Visual Studio 2005 (8.0) compiler system. * If you are using Visual C++ 2005 Express Edition, you must also install an appropriate Platform SDK. More information and links to downloads for various Windows platforms is available from `http://msdn.microsoft.com/platformsdk/'. * If you are compiling from a BitKeeper tree or making changes to the parser, you need `bison' for Windows, which can be downloaded from `http://gnuwin32.sourceforge.net/packages/bison.htm'. Download the package labeled `Complete package, excluding sources'. After installing the package, modify your path to include the `bison' binary and ensure that this binary is accessible from Visual Studio. * Cygwin might be necessary if you want to run the test script or package the compiled binaries and support files into a Zip archive. (Cygwin is needed only to test or package the distribution, not to build it.) Cygwin is available from `http://cygwin.com'. * 3GB to 5GB of disk space. The exact system requirements can be found here: `http://msdn.microsoft.com/vstudio/Previous/2003/sysreqs/default.aspx' and `http://msdn.microsoft.com/vstudio/products/sysreqs/default.aspx' You also need a MySQL source distribution for Windows, which can be obtained two ways: * Obtain a Windows source distribution packaged by MySQL AB for the particular version of MySQL in which you are interested. These are available from `http://dev.mysql.com/downloads/'. * Package a source distribution yourself from the latest BitKeeper developer source tree. If you plan to do this, and you are not using the CMake build method, you must create the package on a Unix system and then transfer it to your Windows system. (Some of the configuration and build steps require tools that work only on Unix.) Thus, if you are not using CMake, the BitKeeper approach requires: * A system running Unix, or a Unix-like system such as Linux. * BitKeeper installed on that system. See *Note installing-source-tree::, for instructions how to download and install BitKeeper. If you are using a Windows source distribution, you can go directly to *Note windows-source-build-cmake::, or *Note windows-vc-plus-plus-build::. To build from the BitKeeper tree without CMake, proceed to *Note windows-bitkeeper-build::. If you find something not working as expected, or you have suggestions about ways to improve the current build process on Windows, please send a message to the `win32' mailing list. See *Note mailing-lists::.  File: manual.info, Node: windows-source-build-cmake, Next: windows-vc-plus-plus-build, Prev: windows-source-build, Up: windows-source-build 2.4.14.7 Building MySQL from Source Using CMake and Visual Studio ................................................................. This section does not apply to MySQL Enterprise Server users. Follow this procedure to build MySQL: 1. If you are installing from a packaged source distribution, create a work directory (for example, `C:\workdir'), and unpack the source distribution there using `WinZip' or another Windows tool that can read `.zip' files. This directory is the work directory in the following instructions. 2. If you are installing from a BitKeeper tree, the root directory of that tree is the work directory in the following instructions. 3. Using a command shell, navigate to the work directory and run the following command: C:\workdir>win\configure OPTIONS These options are available: * `WITH_INNOBASE_STORAGE_ENGINE': Enable the `InnoDB' storage engine. * `WITH_PARTITION_STORAGE_ENGINE': Enable user-defined partitioning. * `WITH_ARCHIVE_STORAGE_ENGINE': Enable the `ARCHIVE' storage engine. * `WITH_BLACKHOLE_STORAGE_ENGINE': Enable the `BLACKHOLE' storage engine. * `WITH_EXAMPLE_STORAGE_ENGINE': Enable the `EXAMPLE' storage engine. * `WITH_FEDERATED_STORAGE_ENGINE': Enable the `FEDERATED' storage engine. * `__NT__': Enable support for named pipes. * `MYSQL_SERVER_SUFFIX=SUFFIX': Server suffix, default none. * `COMPILATION_COMMENT=COMMENT': Server comment, default "Source distribution". * `MYSQL_TCP_PORT=PORT': Server port, default 3306. * `DISABLE_GRANT_OPTIONS': Disables the the `--bootstrap', `--skip-grant-tables', and `--init-file' options for `mysqld'. This option is available as of MySQL 5.0.36. For example (type the command on one line): C:\workdir>win\configure WITH_INNOBASE_STORAGE_ENGINE WITH_PARTITION_STORAGE_ENGINE MYSQL_SERVER_SUFFIX=-pro 4. From the work directory, execute the `win\build-vs8.bat' or `win\build-vs71.bat' file, depending on the version of Visual Studio you have installed. The script invokes CMake, which generates the `mysql.sln' solution file. You can also use `win\build-vs8_x64.bat' to build the 64-bit version of MySQL. However, you cannot build the 64-bit version with Visual Studio Express Edition. You must use Visual Studio 2005 (8.0) or higher. 5. From the work directory, open the generated `mysql.sln' file with Visual Studio and select the proper configuration using the `Configuration' menu. The menu provides `Debug', `Release', `RelwithDebInfo', `MinRelInfo' options. Then select `Solution' > `Build' to build the solution. Remember the configuration that you use in this step. It is important later when you run the test script because that script needs to know which configuration you used. 6. Test the server. The server built using the preceding instructions expects that the MySQL base directory and data directory are `C:\mysql' and `C:\mysql\data' by default. If you want to test your server using the source tree root directory and its data directory as the base directory and data directory, you need to tell the server their pathnames. You can either do this on the command line with the `--basedir' and `--datadir' options, or by placing appropriate options in an option file. (See *Note option-files::.) If you have an existing data directory elsewhere that you want to use, you can specify its pathname instead. When the server is running in standalone fashion or as a service based on your configuration, try to connect to it from the `mysql' interactive command-line utility. You can also run the standard test script, `mysql-test-run.pl'. This script is written in Perl, so 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 `mysql-test' directory under the work directory, set the `MTR_VS_CONFIG' environment variable to the configuration you selected earlier (or use the `--vs-config' option), and invoke `mysql-test-run.pl'. For example (using Cygwin and the `bash' shell): shell> `cd mysql-test' shell> `export MTS_VS_CONFIG=debug' shell> `./mysqltest-run.pl --force --timer' shell> `./mysqltest-run.pl --force --timer --ps-protocol' When you are satisfied that the programs you have built are working correctly, stop the server. Now you can install the distribution. One way to do this is to use the `make_win_bin_dist' script in the `scripts' directory of the MySQL source distribution (see *Note make-win-bin-dist::). This is a shell script, so you must have Cygwin installed if you want to use it. It creates a Zip archive of the built executables and support files that you can unpack in the location at which you want to install MySQL. It is also possible to install MySQL by copying directories and files directly: 1. Create the directories where you want to install MySQL. For example, to install into `C:\mysql', use these commands: C:\> mkdir C:\mysql C:\> mkdir C:\mysql\bin C:\> mkdir C:\mysql\data C:\> mkdir C:\mysql\share C:\> mkdir C:\mysql\scripts If you want to compile other clients and link them to MySQL, you should also create several additional directories: C:\> mkdir C:\mysql\include C:\> mkdir C:\mysql\lib C:\> mkdir C:\mysql\lib\debug C:\> mkdir C:\mysql\lib\opt If you want to benchmark MySQL, create this directory: C:\> mkdir C:\mysql\sql-bench Benchmarking requires Perl support. See *Note perl-support::. 2. From the work directory, copy into the `C:\mysql' directory the following directories: C:\> cd \workdir C:\workdir> copy client_release\*.exe C:\mysql\bin C:\workdir> copy client_debug\mysqld.exe C:\mysql\bin\mysqld-debug.exe C:\workdir> xcopy scripts\*.* C:\mysql\scripts /E C:\workdir> xcopy share\*.* C:\mysql\share /E If you want to compile other clients and link them to MySQL, you should also copy several libraries and header files: C:\workdir> copy lib_debug\mysqlclient.lib C:\mysql\lib\debug C:\workdir> copy lib_debug\libmysql.* C:\mysql\lib\debug C:\workdir> copy lib_debug\zlib.* C:\mysql\lib\debug C:\workdir> copy lib_release\mysqlclient.lib C:\mysql\lib\opt C:\workdir> copy lib_release\libmysql.* C:\mysql\lib\opt C:\workdir> copy lib_release\zlib.* C:\mysql\lib\opt C:\workdir> copy include\*.h C:\mysql\include C:\workdir> copy libmysql\libmysql.def C:\mysql\include If you want to benchmark MySQL, you should also do this: C:\workdir> xcopy sql-bench\*.* C:\mysql\bench /E After installation, set up and start the server in the same way as for binary Windows distributions. See *Note windows-installation::.  File: manual.info, Node: windows-vc-plus-plus-build, Next: borland-c-plus-plus, Prev: windows-source-build-cmake, Up: windows-source-build 2.4.14.8 Building MySQL from Source Using VC++ .............................................. This section does not apply to MySQL Enterprise Server users. *Note*: VC++ workspace files for MySQL 4.1 and above are compatible with Microsoft Visual Studio 7.1 and tested by MySQL AB staff before each release. Follow this procedure to build MySQL: 1. Create a work directory (for example, `C:\workdir'). 2. Unpack the source distribution in the aforementioned directory using `WinZip' or another Windows tool that can read `.zip' files. 3. Start Visual Studio .Net 2003 (7.1). 4. From the `File' menu, select `Open Solution...'. 5. Open the `mysql.sln' solution you find in the work directory. 6. From the `Build' menu, select `Configuration Manager...'. 7. In the `Active Solution Configuration' pop-up menu, select the configuration to use. You likely want to use one of `nt' (normal server), `Max nt' (more engines and features), or `Debug' configuration. 8. From the `Build' menu, select `Build Solution'. 9. Debug versions of the programs and libraries are placed in the `client_debug' and `lib_debug' directories. Release versions of the programs and libraries are placed in the `client_release' and `lib_release' directories. 10. Test the server. The server built using the preceding instructions expects that the MySQL base directory and data directory are `C:\mysql' and `C:\mysql\data' by default. If you want to test your server using the source tree root directory and its data directory as the base directory and data directory, you need to tell the server their pathnames. You can either do this on the command line with the `--basedir' and `--datadir' options, or by placing appropriate options in an option file. (See *Note option-files::.) If you have an existing data directory elsewhere that you want to use, you can specify its pathname instead. 11. Start your server from the `client_release' or `client_debug' directory, depending on which server you built or want to use. The general server startup instructions are in *Note windows-installation::. You must adapt the instructions appropriately if you want to use a different base directory or data directory. 12. When the server is running in standalone fashion or as a service based on your configuration, try to connect to it from the `mysql' interactive command-line utility that exists in your `client_release' or `client_debug' directory. When you are satisfied that the programs you have built are working correctly, stop the server. Then install MySQL using the instructions at the end of *Note windows-source-build-cmake::. After installation, set up and start the server in the same way as for binary Windows distributions. See *Note windows-installation::.  File: manual.info, Node: borland-c-plus-plus, Next: windows-bitkeeper-build, Prev: windows-vc-plus-plus-build, Up: windows-source-build 2.4.14.9 Building MySQL from Source Using Borland C++ ..................................................... This section does not apply to MySQL Enterprise Server users. You can compile the MySQL Windows source with Borland C++ 5.02. (The Windows source includes only projects for Microsoft VC++, for Borland C++ you have to do the project files yourself.) One known problem with Borland C++ is that it uses a different structure alignment than VC++. This means that you run into problems if you try to use the default `libmysql.dll' libraries (that were compiled using VC++) with Borland C++. To avoid this problem, only call `mysql_init()' with `NULL' as an argument, not a pre-allocated `MYSQL' structure.  File: manual.info, Node: windows-bitkeeper-build, Prev: borland-c-plus-plus, Up: windows-source-build 2.4.14.10 Creating a Windows Source Package from the Latest Development Source .............................................................................. This section does not apply to MySQL Enterprise Server users. To create a Windows source package from the current BitKeeper source tree, use the instructions here. This procedure must be performed on a system running a Unix or Unix-like operating system because some of the configuration and build steps require tools that work only on Unix. For example, the following procedure is known to work well on Linux. 1. Copy the BitKeeper source tree for MySQL 5.0. For instructions on how to do this, see *Note installing-source-tree::. 2. Configure and build the distribution so that you have a server binary to work with. One way to do this is to run the following command in the top-level directory of your source tree: shell> ./BUILD/compile-pentium-max 3. After making sure that the build process completed successfully, run the following utility script from top-level directory of your source tree: shell> ./scripts/make_win_src_distribution This script creates a Windows source package to be used on your Windows system. You can supply different options to the script based on your needs. See *Note make-win-src-distribution::, for a list of allowable options. By default, `make_win_src_distribution' creates a Zip-format archive with the name `mysql-VERSION-win-src.zip', where VERSION represents the version of your MySQL source tree. 4. Copy or upload the Windows source package that you have just created to your Windows machine. To compile it, use the instructions in *Note windows-vc-plus-plus-build::.  File: manual.info, Node: windows-client-compiling, Prev: windows-source-build, Up: installing-source 2.4.14.11 Compiling MySQL Clients on Windows ............................................ This section does not apply to MySQL Enterprise Server users. In your source files, you should include `my_global.h' before `mysql.h': #include #include `my_global.h' includes any other files needed for Windows compatibility (such as `windows.h') if you compile your program on Windows. You can either link your code with the dynamic `libmysql.lib' library, which is just a wrapper to load in `libmysql.dll' on demand, or link with the static `mysqlclient.lib' library. The MySQL client libraries are compiled as threaded libraries, so you should also compile your code to be multi-threaded.  File: manual.info, Node: post-installation, Next: upgrade, Prev: installing-source, Up: installing-cs 2.4.15 Post-Installation Setup and Testing ------------------------------------------ * Menu: * windows-post-installation:: Windows Post-Installation Procedures * unix-post-installation:: Unix Post-Installation Procedures * default-privileges:: Securing the Initial MySQL Accounts After installing MySQL, there are some issues that you should address. For example, on Unix, you should initialize the data directory and create the MySQL grant tables. On all platforms, an important security concern is that the initial accounts in the grant tables have no passwords. You should assign passwords to prevent unauthorized access to the MySQL server. Optionally, you can create time zone tables to enable recognition of named time zones. The following sections include post-installation procedures that are specific to Windows systems and to Unix systems. Another section, *Note starting-server::, applies to all platforms; it describes what to do if you have trouble getting the server to start. *Note default-privileges::, also applies to all platforms. You should follow its instructions to make sure that you have properly protected your MySQL accounts by assigning passwords to them. When you are ready to create additional user accounts, you can find information on the MySQL access control system and account management in *Note privilege-system::, and *Note user-account-management::.  File: manual.info, Node: windows-post-installation, Next: unix-post-installation, Prev: post-installation, Up: post-installation 2.4.15.1 Windows Post-Installation Procedures ............................................. On Windows, the data directory and the grant tables do not have to be created. MySQL Windows distributions include the grant tables with a set of preinitialized accounts in the `mysql' database under the data directory. It is unnecessary to run the `mysql_install_db' script that is used on Unix. Regarding passwords, if you installed MySQL using the Windows Installation Wizard, you may have already assigned passwords to the accounts. (See *Note windows-install-wizard::.) Otherwise, use the password-assignment procedure given in *Note default-privileges::. Before setting up passwords, you might want to try running some client programs to make sure that you can connect to the server and that it is operating properly. Make sure that the server is running (see *Note windows-server-first-start::), and then issue the following commands to verify that you can retrieve information from the server. The output should be similar to what is shown here: C:\> C:\mysql\bin\mysqlshow +-----------+ | Databases | +-----------+ | mysql | | test | +-----------+ C:\> C:\mysql\bin\mysqlshow mysql Database: mysql +---------------------------+ | Tables | +---------------------------+ | columns_priv | | db | | func | | help_category | | help_keyword | | help_relation | | help_topic | | host | | proc | | procs_priv | | tables_priv | | time_zone | | time_zone_leap_second | | time_zone_name | | time_zone_transition | | time_zone_transition_type | | user | +---------------------------+ C:\> C:\mysql\bin\mysql -e "SELECT Host,Db,User FROM db" mysql +------+-------+------+ | host | db | user | +------+-------+------+ | % | test% | | +------+-------+------+ If you are running a version of Windows that supports services and you want the MySQL server to run automatically when Windows starts, see *Note windows-start-service::.  File: manual.info, Node: unix-post-installation, Next: default-privileges, Prev: windows-post-installation, Up: post-installation 2.4.15.2 Unix Post-Installation Procedures .......................................... * Menu: * mysql-install-db-problems:: Problems Running `mysql_install_db' * automatic-start:: Starting and Stopping MySQL Automatically * starting-server:: Starting and Troubleshooting the MySQL Server After installing MySQL on Unix, you need to initialize the grant tables, start the server, and make sure that the server works satisfactorily. You may also wish to arrange for the server to be started and stopped automatically when your system starts and stops. You should also assign passwords to the accounts in the grant tables. On Unix, the grant tables are set up by the `mysql_install_db' program. For some installation methods, this program is run for you automatically: * If you install MySQL on Linux using RPM distributions, the server RPM runs `mysql_install_db'. * If you install MySQL on Mac OS X using a PKG distribution, the installer runs `mysql_install_db'. Otherwise, you will need to run `mysql_install_db' yourself. The following procedure describes how to initialize the grant tables (if that has not previously been done) and then start the server. It also suggests some commands that you can use to test whether the server is accessible and working properly. For information about starting and stopping the server automatically, see *Note automatic-start::. After you complete the procedure and have the server running, you should assign passwords to the accounts created by `mysql_install_db'. Instructions for doing so are given in *Note default-privileges::. In the examples shown here, the server runs under the user ID of the `mysql' login account. This assumes that such an account exists. Either create the account if it does not exist, or substitute the name of a different existing login account that you plan to use for running the server. 1. Change location into the top-level directory of your MySQL installation, represented here by BASEDIR: shell> cd BASEDIR BASEDIR is likely to be something like `/usr/local/mysql' or `/usr/local'. The following steps assume that you are located in this directory. 2. If necessary, run the `mysql_install_db' program to set up the initial MySQL grant tables containing the privileges that determine how users are allowed to connect to the server. You'll need to do this if you used a distribution type for which the installation procedure doesn't run the program for you. Typically, `mysql_install_db' needs to be run only the first time you install MySQL, so you can skip this step if you are upgrading an existing installation, However, `mysql_install_db' does not overwrite any existing privilege tables, so it should be safe to run in any circumstances. To initialize the grant tables, use one of the following commands, depending on whether `mysql_install_db' is located in the `bin' or `scripts' directory: shell> bin/mysql_install_db --user=mysql shell> scripts/mysql_install_db --user=mysql The `mysql_install_db' script creates the server's data directory. Under the data directory, it creates directories for the `mysql' database that holds all database privileges and the `test' database that you can use to test MySQL. The script also creates privilege table entries for `root' and anonymous-user accounts. The accounts have no passwords initially. A description of their initial privileges is given in *Note default-privileges::. Briefly, these privileges allow the MySQL `root' user to do anything, and allow anybody to create or use databases with a name of `test' or starting with `test_'. It is important to make sure that the database directories and files are owned by the `mysql' login account so that the server has read and write access to them when you run it later. To ensure this, the `--user' option should be used as shown if you run `mysql_install_db' as `root'. Otherwise, you should execute the script while logged in as `mysql', in which case you can omit the `--user' option from the command. `mysql_install_db' creates several tables in the `mysql' database, including `user', `db', `host', `tables_priv', `columns_priv', `func', and others. See *Note privilege-system::, for a complete listing and description of these tables. If you don't want to have the `test' database, you can remove it with `mysqladmin -u root drop test' after starting the server. If you have trouble with `mysql_install_db' at this point, see *Note mysql-install-db-problems::. 3. Start the MySQL server: shell> bin/mysqld_safe --user=mysql & It is important that the MySQL server be run using an unprivileged (non-`root') login account. To ensure this, the `--user' option should be used as shown if you run `mysql_safe' as system `root'. Otherwise, you should execute the script while logged in to the system as `mysql', in which case you can omit the `--user' option from the command. Further instructions for running MySQL as an unprivileged user are given in *Note changing-mysql-user::. If you neglected to create the grant tables before proceeding to this step, the following message appears in the error log file when you start the server: mysqld: Can't find file: 'host.frm' If you have other problems starting the server, see *Note starting-server::. 4. Use `mysqladmin' to verify that the server is running. The following commands provide simple tests to check whether the server is up and responding to connections: shell> bin/mysqladmin version shell> bin/mysqladmin variables The output from `mysqladmin version' varies slightly depending on your platform and version of MySQL, but should be similar to that shown here: shell> bin/mysqladmin version mysqladmin Ver 14.12 Distrib 5.0.46, for pc-linux-gnu on i686 Copyright (C) 2000 MySQL AB & MySQL Finland AB & TCX DataKonsult AB This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to modify and redistribute it under the GPL license Server version 5.0.46 Protocol version 10 Connection Localhost via UNIX socket UNIX socket /var/lib/mysql/mysql.sock Uptime: 14 days 5 hours 5 min 21 sec Threads: 1 Questions: 366 Slow queries: 0 Opens: 0 Flush tables: 1 Open tables: 19 Queries per second avg: 0.000 To see what else you can do with `mysqladmin', invoke it with the `--help' option. 5. Verify that you can shut down the server: shell> bin/mysqladmin -u root shutdown 6. Verify that you can start the server again. Do this by using `mysqld_safe' or by invoking `mysqld' directly. For example: shell> bin/mysqld_safe --user=mysql --log & If `mysqld_safe' fails, see *Note starting-server::. 7. Run some simple tests to verify that you can retrieve information from the server. The output should be similar to what is shown here: shell> bin/mysqlshow +-----------+ | Databases | +-----------+ | mysql | | test | +-----------+ shell> bin/mysqlshow mysql Database: mysql +---------------------------+ | Tables | +---------------------------+ | columns_priv | | db | | func | | help_category | | help_keyword | | help_relation | | help_topic | | host | | proc | | procs_priv | | tables_priv | | time_zone | | time_zone_leap_second | | time_zone_name | | time_zone_transition | | time_zone_transition_type | | user | +---------------------------+ shell> bin/mysql -e "SELECT Host,Db,User FROM db" mysql +------+--------+------+ | host | db | user | +------+--------+------+ | % | test | | | % | test_% | | +------+--------+------+ 8. There is a benchmark suite in the `sql-bench' directory (under the MySQL installation directory) that you can use to compare how MySQL performs on different platforms. The benchmark suite is written in Perl. It requires the Perl DBI module that provides a database-independent interface to the various databases, and some other additional Perl modules: DBI DBD::mysql Data::Dumper Data::ShowTable These modules can be obtained from CPAN (`http://www.cpan.org/'). See also *Note perl-installation::. The `sql-bench/Results' directory contains the results from many runs against different databases and platforms. To run all tests, execute these commands: shell> cd sql-bench shell> perl run-all-tests If you don't have the `sql-bench' directory, you probably installed MySQL using RPM files other than the source RPM. (The source RPM includes the `sql-bench' benchmark directory.) In this case, you must first install the benchmark suite before you can use it. There are separate benchmark RPM files named `mysql-bench-VERSION.i386.rpm' that contain benchmark code and data. If you have a source distribution, there are also tests in its `tests' subdirectory that you can run. For example, to run `auto_increment.tst', execute this command from the top-level directory of your source distribution: shell> mysql -vvf test < ./tests/auto_increment.tst The expected result of the test can be found in the `./tests/auto_increment.res' file. 9. At this point, you should have the server running. However, none of the initial MySQL accounts have a password, so you should assign passwords using the instructions found in *Note default-privileges::. The MySQL 5.0 installation procedure creates time zone tables in the `mysql' database. However, you must populate the tables manually using the instructions in *Note time-zone-support::.  File: manual.info, Node: mysql-install-db-problems, Next: automatic-start, Prev: unix-post-installation, Up: unix-post-installation 2.4.15.3 Problems Running `mysql_install_db' ............................................ This section does not apply to MySQL Enterprise Server users. The purpose of the `mysql_install_db' script is to generate new MySQL privilege tables. It does not overwrite existing MySQL privilege tables, and it does not affect any other data. If you want to re-create your privilege tables, first stop the `mysqld' server if it's running. Then rename the `mysql' directory under the data directory to save it, and then run `mysql_install_db'. Suppose that your current directory is the MySQL installation directory and that `mysql_install_db' is located in the `bin' directory and the data directory is named `data'. To rename the `mysql' database and re-run `mysql_install_db', use these commands. shell> mv data/mysql data/mysql.old shell> bin/mysql_install_db --user=mysql When you run `mysql_install_db', you might encounter the following problems: * *`mysql_install_db' fails to install the grant tables* You may find that `mysql_install_db' fails to install the grant tables and terminates after displaying the following messages: Starting mysqld daemon with databases from XXXXXX mysqld ended In this case, you should examine the error log file very carefully. The log should be located in the directory `XXXXXX' named by the error message and should indicate why `mysqld' didn't start. If you do not understand what happened, include the log when you post a bug report. See *Note bug-reports::. * *There is a `mysqld' process running* This indicates that the server is running, in which case the grant tables have probably been created already. If so, there is no need to run `mysql_install_db' at all because it needs to be run only once (when you install MySQL the first time). * *Installing a second `mysqld' server does not work when one server is running* This can happen when you have an existing MySQL installation, but want to put a new installation in a different location. For example, you might have a production installation, but you want to create a second installation for testing purposes. Generally the problem that occurs when you try to run a second server is that it tries to use a network interface that is in use by the first server. In this case, you should see one of the following error messages: Can't start server: Bind on TCP/IP port: Address already in use Can't start server: Bind on unix socket... For instructions on setting up multiple servers, see *Note multiple-servers::. * *You do not have write access to the `/tmp' directory* If you do not have write access to create temporary files or a Unix socket file in the default location (the `/tmp' directory), an error occurs when you run `mysql_install_db' or the `mysqld' server. You can specify different locations for the temporary directory and Unix socket file by executing these commands prior to starting `mysql_install_db' or `mysqld', where SOME_TMP_DIR is the full pathname to some directory for which you have write permission: shell> TMPDIR=/SOME_TMP_DIR/ shell> MYSQL_UNIX_PORT=/SOME_TMP_DIR/mysql.sock shell> export TMPDIR MYSQL_UNIX_PORT Then you should be able to run `mysql_install_db' and start the server with these commands: shell> bin/mysql_install_db --user=mysql shell> bin/mysqld_safe --user=mysql & If `mysql_install_db' is located in the `scripts' directory, modify the first command to `scripts/mysql_install_db'. See *Note problems-with-mysql-sock::, and *Note environment-variables::. There are some alternatives to running the `mysql_install_db' script provided in the MySQL distribution: * If you want the initial privileges to be different from the standard defaults, you can modify `mysql_install_db' before you run it. However, it is preferable to use `GRANT' and `REVOKE' to change the privileges _after_ the grant tables have been set up. In other words, you can run `mysql_install_db', and then use `mysql -u root mysql' to connect to the server as the MySQL `root' user so that you can issue the necessary `GRANT' and `REVOKE' statements. If you want to install MySQL on several machines with the same privileges, you can put the `GRANT' and `REVOKE' statements in a file and execute the file as a script using `mysql' after running `mysql_install_db'. For example: shell> bin/mysql_install_db --user=mysql shell> bin/mysql -u root < your_script_file By doing this, you can avoid having to issue the statements manually on each machine. * It is possible to re-create the grant tables completely after they have previously been created. You might want to do this if you're just learning how to use `GRANT' and `REVOKE' and have made so many modifications after running `mysql_install_db' that you want to wipe out the tables and start over. To re-create the grant tables, remove all the `.frm', `.MYI', and `.MYD' files in the `mysql' database directory. Then run the `mysql_install_db' script again. * You can start `mysqld' manually using the `--skip-grant-tables' option and add the privilege information yourself using `mysql': shell> bin/mysqld_safe --user=mysql --skip-grant-tables & shell> bin/mysql mysql From `mysql', manually execute the SQL commands contained in `mysql_install_db'. Make sure that you run `mysqladmin flush-privileges' or `mysqladmin reload' afterward to tell the server to reload the grant tables. Note that by not using `mysql_install_db', you not only have to populate the grant tables manually, you also have to create them first.  File: manual.info, Node: automatic-start, Next: starting-server, Prev: mysql-install-db-problems, Up: unix-post-installation 2.4.15.4 Starting and Stopping MySQL Automatically .................................................. Generally, you start the `mysqld' server in one of these ways: * By invoking `mysqld' directly. This works on any platform. * By running the MySQL server as a Windows service. The service can be set to start the server automatically when Windows starts, or as a manual service that you start on request. For instructions, see *Note windows-start-service::. * By invoking `mysqld_safe', which tries to determine the proper options for `mysqld' and then runs it with those options. This script is used on Unix and Unix-like systems. See *Note mysqld-safe::. * By invoking `mysql.server'. This script is used primarily at system startup and shutdown on systems that use System V-style run directories, where it usually is installed under the name `mysql'. The `mysql.server' script starts the server by invoking `mysqld_safe'. See *Note mysql-server::. * On Mac OS X, you can install a separate MySQL Startup Item package to enable the automatic startup of MySQL on system startup. The Startup Item starts the server by invoking `mysql.server'. See *Note mac-os-x-installation::, for details. The `mysqld_safe' and `mysql.server' scripts and the Mac OS X Startup Item can be used to start the server manually, or automatically at system startup time. `mysql.server' and the Startup Item also can be used to stop the server. To start or stop the server manually using the `mysql.server' script, invoke it with `start' or `stop' arguments: shell> mysql.server start shell> mysql.server stop Before `mysql.server' starts the server, it changes location to the MySQL installation directory, and then invokes `mysqld_safe'. If you want the server to run as some specific user, add an appropriate `user' option to the `[mysqld]' group of the `/etc/my.cnf' option file, as shown later in this section. (It is possible that you will need to edit `mysql.server' if you've installed a binary distribution of MySQL in a non-standard location. Modify it to `cd' into the proper directory before it runs `mysqld_safe'. If you do this, your modified version of `mysql.server' may be overwritten if you upgrade MySQL in the future, so you should make a copy of your edited version that you can reinstall.) `mysql.server stop' stops the server by sending a signal to it. You can also stop the server manually by executing `mysqladmin shutdown'. To start and stop MySQL automatically on your server, you need to add start and stop commands to the appropriate places in your `/etc/rc*' files. If you use the Linux server RPM package (`MySQL-server-VERSION.rpm'), the `mysql.server' script is installed in the `/etc/init.d' directory with the name `mysql'. You need not install it manually. See *Note linux-rpm::, for more information on the Linux RPM packages. Some vendors provide RPM packages that install a startup script under a different name such as `mysqld'. If you install MySQL from a source distribution or using a binary distribution format that does not install `mysql.server' automatically, you can install it manually. The script can be found in the `support-files' directory under the MySQL installation directory or in a MySQL source tree. To install `mysql.server' manually, copy it to the `/etc/init.d' directory with the name `mysql', and then make it executable. Do this by changing location into the appropriate directory where `mysql.server' is located and executing these commands: shell> cp mysql.server /etc/init.d/mysql shell> chmod +x /etc/init.d/mysql Older Red Hat systems use the `/etc/rc.d/init.d' directory rather than `/etc/init.d'. Adjust the preceding commands accordingly. Alternatively, first create `/etc/init.d' as a symbolic link that points to `/etc/rc.d/init.d': shell> cd /etc shell> ln -s rc.d/init.d . After installing the script, the commands needed to activate it to run at system startup depend on your operating system. On Linux, you can use `chkconfig': shell> chkconfig --add mysql On some Linux systems, the following command also seems to be necessary to fully enable the `mysql' script: shell> chkconfig --level 345 mysql on On FreeBSD, startup scripts generally should go in `/usr/local/etc/rc.d/'. The `rc(8)' manual page states that scripts in this directory are executed only if their basename matches the `*.sh' shell filename pattern. Any other files or directories present within the directory are silently ignored. In other words, on FreeBSD, you should install the `mysql.server' script as `/usr/local/etc/rc.d/mysql.server.sh' to enable automatic startup. As an alternative to the preceding setup, some operating systems also use `/etc/rc.local' or `/etc/init.d/boot.local' to start additional services on startup. To start up MySQL using this method, you could append a command like the one following to the appropriate startup file: /bin/sh -c 'cd /usr/local/mysql; ./bin/mysqld_safe --user=mysql &' For other systems, consult your operating system documentation to see how to install startup scripts. You can add options for `mysql.server' in a global `/etc/my.cnf' file. A typical `/etc/my.cnf' file might look like this: [mysqld] datadir=/usr/local/mysql/var socket=/var/tmp/mysql.sock port=3306 user=mysql [mysql.server] basedir=/usr/local/mysql The `mysql.server' script understands the following options: `basedir', `datadir', and `pid-file'. If specified, they _must_ be placed in an option file, not on the command line. `mysql.server' understands only `start' and `stop' as command-line arguments. The following table shows which option groups the server and each startup script read from option files: *Script* *Option Groups* `mysqld' `[mysqld]', `[server]', `[mysqld-MAJOR_VERSION]' `mysqld_safe' `[mysqld]', `[server]', `[mysqld_safe]' `mysql.server' `[mysqld]', `[mysql.server]', `[server]' `[mysqld-MAJOR_VERSION]' means that groups with names like `[mysqld-4.1]' and `[mysqld-5.0]' are read by servers having versions 4.1.x, 5.0.x, and so forth. This feature can be used to specify options that can be read only by servers within a given release series. For backward compatibility, `mysql.server' also reads the `[mysql_server]' group and `mysqld_safe' also reads the `[safe_mysqld]' group. However, you should update your option files to use the `[mysql.server]' and `[mysqld_safe]' groups instead when using MySQL 5.0. See *Note option-files::.  File: manual.info, Node: starting-server, Prev: automatic-start, Up: unix-post-installation 2.4.15.5 Starting and Troubleshooting the MySQL Server ...................................................... This section provides troubleshooting suggestions for problems starting the server on Unix. If you are using Windows, see *Note windows-troubleshooting::. If you have problems starting the server, here are some things to try: * Check the error log to see why the server does not start. * Specify any special options needed by the storage engines you are using. * Make sure that the server knows where to find the data directory. * Make sure that the server can access the data directory. The ownership and permissions of the data directory and its contents must be set such that the server can read and modify them. * Verify that the network interfaces the server wants to use are available. Some storage engines have options that control their behavior. You can create a `my.cnf' file and specify startup options for the engines that you plan to use. If you are going to use storage engines that support transactional tables (`InnoDB', `BDB', `NDB'), be sure that you have them configured the way you want before starting the server: MySQL Enterprise For expert advice on start-up options appropriate to your circumstances, subscribe to The MySQL Network Monitoring and Advisory Service. For more information see, `http://www.mysql.com/products/enterprise/advisors.html'. * If you are using `InnoDB' tables, see *Note innodb-configuration::. * If you are using `BDB' (Berkeley DB) tables, see *Note bdb-start::. * If you are using MySQL Cluster, see *Note mysql-cluster-configuration::. Storage engines will use default option values if you specify none, but it is recommended that you review the available options and specify explicit values for those for which the defaults are not appropriate for your installation. When the `mysqld' server starts, it changes location to the data directory. This is where it expects to find databases and where it expects to write log files. The server also writes the pid (process ID) file in the data directory. The data directory location is hardwired in when the server is compiled. This is where the server looks for the data directory by default. If the data directory is located somewhere else on your system, the server will not work properly. You can determine what the default path settings are by invoking `mysqld' with the `--verbose' and `--help' options. If the default locations don't match the MySQL installation layout on your system, you can override them by specifying options to `mysqld' or `mysqld_safe' on the command line or in an option file. To specify the location of the data directory explicitly, use the `--datadir' option. However, normally you can tell `mysqld' the location of the base directory under which MySQL is installed and it looks for the data directory there. You can do this with the `--basedir' option. To check the effect of specifying path options, invoke `mysqld' with those options followed by the `--verbose' and `--help' options. For example, if you change location into the directory where `mysqld' is installed and then run the following command, it shows the effect of starting the server with a base directory of `/usr/local': shell> ./mysqld --basedir=/usr/local --verbose --help You can specify other options such as `--datadir' as well, but `--verbose' and `--help' must be the last options. Once you determine the path settings you want, start the server without `--verbose' and `--help'. If `mysqld' is currently running, you can find out what path settings it is using by executing this command: shell> mysqladmin variables Or: shell> mysqladmin -h HOST_NAME variables HOST_NAME is the name of the MySQL server host. If you get `Errcode 13' (which means `Permission denied') when starting `mysqld', this means that the privileges of the data directory or its contents do not allow the server access. In this case, you change the permissions for the involved files and directories so that the server has the right to use them. You can also start the server as `root', but this raises security issues and should be avoided. On Unix, change location into the data directory and check the ownership of the data directory and its contents to make sure the server has access. For example, if the data directory is `/usr/local/mysql/var', use this command: shell> ls -la /usr/local/mysql/var If the data directory or its files or subdirectories are not owned by the login account that you use for running the server, change their ownership to that account. If the account is named `mysql', use these commands: shell> chown -R mysql /usr/local/mysql/var shell> chgrp -R mysql /usr/local/mysql/var If the server fails to start up correctly, check the error log. Log files are located in the data directory (typically `C:\Program Files\MySQL\MySQL Server 5.0\data' on Windows, `/usr/local/mysql/data' for a Unix binary distribution, and `/usr/local/var' for a Unix source distribution). Look in the data directory for files with names of the form `HOST_NAME.err' and `HOST_NAME.log', where HOST_NAME is the name of your server host. Then examine the last few lines of these files. On Unix, you can use `tail' to display them: shell> tail HOST_NAME.err shell> tail HOST_NAME.log The error log should contain information that indicates why the server couldn't start. For example, you might see something like this in the log: 000729 14:50:10 bdb: Recovery function for LSN 1 27595 failed 000729 14:50:10 bdb: warning: ./test/t1.db: No such file or directory 000729 14:50:10 Can't init databases This means that you did not start `mysqld' with the `--bdb-no-recover' option and Berkeley DB found something wrong with its own log files when it tried to recover your databases. To be able to continue, you should move the old Berkeley DB log files from the database directory to some other place, where you can later examine them. The `BDB' log files are named in sequence beginning with `log.0000000001', where the number increases over time. If you are running `mysqld' with `BDB' table support and `mysqld' dumps core at startup, this could be due to problems with the `BDB' recovery log. In this case, you can try starting `mysqld' with `--bdb-no-recover'. If that helps, you should remove all `BDB' log files from the data directory and try starting `mysqld' again without the `--bdb-no-recover' option. If either of the following errors occur, it means that some other program (perhaps another `mysqld' server) is using the TCP/IP port or Unix socket file that `mysqld' is trying to use: Can't start server: Bind on TCP/IP port: Address already in use Can't start server: Bind on unix socket... Use `ps' to determine whether you have another `mysqld' server running. If so, shut down the server before starting `mysqld' again. (If another server is running, and you really want to run multiple servers, you can find information about how to do so in *Note multiple-servers::.) If no other server is running, try to execute the command `telnet YOUR_HOST_NAME TCP_IP_PORT_NUMBER'. (The default MySQL port number is 3306.) Then press Enter a couple of times. If you don't get an error message like `telnet: Unable to connect to remote host: Connection refused', some other program is using the TCP/IP port that `mysqld' is trying to use. You'll need to track down what program this is and disable it, or else tell `mysqld' to listen to a different port with the `--port' option. In this case, you'll also need to specify the port number for client programs when connecting to the server via TCP/IP. Another reason the port might be inaccessible is that you have a firewall running that blocks connections to it. If so, modify the firewall settings to allow access to the port. If the server starts but you can't connect to it, you should make sure that you have an entry in `/etc/hosts' that looks like this: 127.0.0.1 localhost This problem occurs only on systems that do not have a working thread library and for which MySQL must be configured to use MIT-pthreads. If you cannot get `mysqld' to start, you can try to make a trace file to find the problem by using the `--debug' option. See MySQL Internals: Porting (http://forge.mysql.com/wiki/MySQL_Internals_Porting).  File: manual.info, Node: default-privileges, Prev: unix-post-installation, Up: post-installation 2.4.15.6 Securing the Initial MySQL Accounts ............................................ Part of the MySQL installation process is to set up the `mysql' database that contains the grant tables: * Windows distributions contain preinitialized grant tables that are installed automatically. * On Unix, the grant tables are populated by the `mysql_install_db' program. Some installation methods run this program for you. Others require that you execute it manually. For details, see *Note unix-post-installation::. The grant tables define the initial MySQL user accounts and their access privileges. These accounts are set up as follows: * Accounts with the username `root' are created. These are superuser accounts that can do anything. The initial `root' account passwords are empty, so anyone can connect to the MySQL server as `root' -- _without a password_ -- and be granted all privileges. * On Windows, one `root' account is created; this account allows connecting from the local host only. The Windows installer will optionally create an account allowing for connections from any host only if the user selects the `Enable root access from remote machines' option during installation. * On Unix, both `root' accounts are for connections from the local host. Connections must be made from the local host by specifying a hostname of `localhost' for one of the accounts, or the actual hostname or IP number for the other. * Two anonymous-user accounts are created, each with an empty username. The anonymous accounts have no password, so anyone can use them to connect to the MySQL server. * On Windows, one anonymous account is for connections from the local host. It has no global privileges. (Before MySQL 5.1.16, it has all global privileges, just like the `root' accounts.) The other is for connections from any host and has all privileges for the `test' database and for other databases with names that start with `test'. * On Unix, both anonymous accounts are for connections from the local host. Connections must be made from the local host by specifying a hostname of `localhost' for one of the accounts, or the actual hostname or IP number for the other. These accounts have all privileges for the `test' database and for other databases with names that start with `test_'. As noted, none of the initial accounts have passwords. This means that your MySQL installation is unprotected until you do something about it: * If you want to prevent clients from connecting as anonymous users without a password, you should either assign a password to each anonymous account or else remove the accounts. * You should assign a password to each MySQL `root' account. The following instructions describe how to set up passwords for the initial MySQL accounts, first for the anonymous accounts and then for the `root' accounts. Replace `NEWPWD' in the examples with the actual password that you want to use. The instructions also cover how to remove the anonymous accounts, should you prefer not to allow anonymous access at all. You might want to defer setting the passwords until later, so that you don't need to specify them while you perform additional setup or testing. However, be sure to set them before using your installation for production purposes. *Anonymous Account Password Assignment* To assign passwords to the anonymous accounts, connect to the server as `root' and then use either `SET PASSWORD' or `UPDATE'. In either case, be sure to encrypt the password using the `PASSWORD()' function. To use `SET PASSWORD' on Windows, do this: shell> mysql -u root mysql> SET PASSWORD FOR ''@'localhost' = PASSWORD('NEWPWD'); mysql> SET PASSWORD FOR ''@'%' = PASSWORD('NEWPWD'); To use `SET PASSWORD' on Unix, do this: shell> mysql -u root mysql> SET PASSWORD FOR ''@'localhost' = PASSWORD('NEWPWD'); mysql> SET PASSWORD FOR ''@'HOST_NAME' = PASSWORD('NEWPWD'); In the second `SET PASSWORD' statement, replace HOST_NAME with the name of the server host. This is the name that is specified in the `Host' column of the non-`localhost' record for `root' in the `user' table. If you don't know what hostname this is, issue the following statement before using `SET PASSWORD': mysql> SELECT Host, User FROM mysql.user; Look for the record that has `root' in the `User' column and something other than `localhost' in the `Host' column. Then use that `Host' value in the second `SET PASSWORD' statement. The other way to assign passwords to the anonymous accounts is by using `UPDATE' to modify the `user' table directly. Connect to the server as `root' and issue an `UPDATE' statement that assigns a value to the `Password' column of the appropriate `user' table records. The procedure is the same for Windows and Unix. The following `UPDATE' statement assigns a password to both anonymous accounts at once: shell> mysql -u root mysql> UPDATE mysql.user SET Password = PASSWORD('NEWPWD') -> WHERE User = ''; mysql> FLUSH PRIVILEGES; After you update the passwords in the `user' table directly using `UPDATE', you must tell the server to re-read the grant tables with `FLUSH PRIVILEGES'. Otherwise, the change goes unnoticed until you restart the server. *Anonymous Account Removal* If you prefer to remove the anonymous accounts instead, do so as follows: shell> mysql -u root mysql> DELETE FROM mysql.user WHERE User = ''; mysql> FLUSH PRIVILEGES; The `DELETE' statement applies both to Windows and to Unix. On Windows, if you want to remove only the anonymous account that has the same privileges as `root', do this instead: shell> mysql -u root mysql> DELETE FROM mysql.user WHERE Host='localhost' AND User=''; mysql> FLUSH PRIVILEGES; That account allows anonymous access but has full privileges, so removing it improves security. *`root' Account Password Assignment* You can assign passwords to the `root' accounts in several ways. The following discussion demonstrates three methods: * Use the `SET PASSWORD' statement * Use the `mysqladmin' command-line client program * Use the `UPDATE' statement To assign passwords using `SET PASSWORD', connect to the server as `root' and issue two `SET PASSWORD' statements. Be sure to encrypt the password using the `PASSWORD()' function. For Windows, do this: shell> mysql -u root mysql> SET PASSWORD FOR 'root'@'localhost' = PASSWORD('NEWPWD'); mysql> SET PASSWORD FOR 'root'@'%' = PASSWORD('NEWPWD'); For Unix, do this: shell> mysql -u root mysql> SET PASSWORD FOR 'root'@'localhost' = PASSWORD('NEWPWD'); mysql> SET PASSWORD FOR 'root'@'HOST_NAME' = PASSWORD('NEWPWD'); In the second `SET PASSWORD' statement, replace HOST_NAME with the name of the server host. This is the same hostname that you used when you assigned the anonymous account passwords. To assign passwords to the `root' accounts using `mysqladmin', execute the following commands: shell> mysqladmin -u root password "NEWPWD" shell> mysqladmin -u root -h HOST_NAME password "NEWPWD" These commands apply both to Windows and to Unix. In the second command, replace HOST_NAME with the name of the server host. The double quotes around the password are not always necessary, but you should use them if the password contains spaces or other characters that are special to your command interpreter. You can also use `UPDATE' to modify the `user' table directly. The following `UPDATE' statement assigns a password to both `root' accounts at once: shell> mysql -u root mysql> UPDATE mysql.user SET Password = PASSWORD('NEWPWD') -> WHERE User = 'root'; mysql> FLUSH PRIVILEGES; The `UPDATE' statement applies both to Windows and to Unix. After the passwords have been set, you must supply the appropriate password whenever you connect to the server. For example, if you want to use `mysqladmin' to shut down the server, you can do so using this command: shell> mysqladmin -u root -p shutdown Enter password: (ENTER ROOT PASSWORD HERE) *Note*: If you forget your `root' password after setting it up, *Note resetting-permissions::, covers the procedure for resetting it. To set up additional accounts, you can use the `GRANT' statement. For instructions, see *Note adding-users::.  File: manual.info, Node: upgrade, Next: downgrading, Prev: post-installation, Up: installing-cs 2.4.16 Upgrading MySQL ---------------------- * Menu: * upgrading-from-5-0:: Upgrading from MySQL 5.0 to 5.1 * upgrading-from-4-1:: Upgrading from MySQL 4.1 to 5.0 * upgrading-to-arch:: Copying MySQL Databases to Another Machine As a general rule, we recommend that when upgrading from one release series to another, you should go to the next series rather than skipping a series. For example, if you currently are running MySQL 3.23 and wish to upgrade to a newer series, upgrade to MySQL 4.0 rather than to 4.1 or 5.0. The following items form a checklist of things that you should do whenever you perform an upgrade: * Before upgrading from MySQL 4.1 to 5.0, read *Note upgrading-from-4-1::) as well as *Note news::. These provide information about features that are new in MySQL 5.0 or differ from those found in MySQL 4.1. If you wish to upgrade from a release series previous to MySQL 4.1, you should upgrade to each successive release series in turn until you have reached MySQL 4.1, and then proceed with the upgrade to MySQL 5.0. For information on upgrading from MySQL 4.1 or earlier releases, see the `MySQL 3.23, 4.0, 4.1 Reference Manual'. * Before you perform an upgrade, back up your databases, including the `mysql' database that contains the grant tables. * Some releases of MySQL introduce incompatible changes to tables. (Our aim is to avoid these changes, but occasionally they are necessary to correct problems that would be worse than an incompatibility between releases.) Some releases of MySQL introduce changes to the structure of the grant tables to add new privileges or features. To avoid problems due to such changes, after you upgrade to a new version of MySQL, you should run `mysql_upgrade' to check your tables (and repair them if necessary), and to update your grant tables to make sure that they have the current structure so that you can take advantage of any new capabilities. See *Note mysql-upgrade::. * If you are running MySQL Server on Windows, see *Note windows-upgrading::. * If you are using replication, see *Note replication-upgrade::, for information on upgrading your replication setup. * MySQL 5.0.27 is the last version in MySQL 5.0 for which MySQL-Max binary distributions are provided, except for RPM distributions. For RPMs, MySQL 5.0.37 is the last release. After these versions, the features previously included in the `mysqld-max' server are included in `mysqld'. If you previously installed a MySQL-Max distribution that includes a server named `mysqld-max', and then upgrade later to a non-Max version of MySQL, `mysqld_safe' still attempts to run the old `mysqld-max' server. If you perform such an upgrade, you should remove the old `mysqld-max' server manually to ensure that `mysqld_safe' runs the new `mysqld' server. * If you have created a user-defined function (UDF) with a given name and upgrade MySQL to a version that implements a new built-in function with the same name, the UDF becomes inaccessible. To correct this, use `DROP FUNCTION' to drop the UDF, and then use `CREATE FUNCTION' to re-create the UDF with a different non-conflicting name. If a new version of MySQL implements a built-in function with the same name as an existing stored function, you have two choices: Rename the stored function to use a non-conflicting name, or change calls to the function so that they use a database qualifier (that is, use `DB_NAME.FUNC_NAME()' syntax). See *Note function-resolution::, for the rules describing how the server interprets references to different kinds of functions. You can always move the MySQL format files and data files between different versions on the same architecture as long as you stay within versions for the same release series of MySQL. If you change the character set when running MySQL, you must run `myisamchk -r -q --set-collation=COLLATION_NAME' on all `MyISAM' tables. Otherwise, your indexes may not be ordered correctly, because changing the character set may also change the sort order. If you are cautious about using new versions, you can always rename your old `mysqld' before installing a newer one. For example, if you are using MySQL 4.1.13 and want to upgrade to 5.0.10, rename your current server from `mysqld' to `mysqld-4.1.13'. If your new `mysqld' then does something unexpected, you can simply shut it down and restart with your old `mysqld'. If, after an upgrade, you experience problems with recompiled client programs, such as `Commands out of sync' or unexpected core dumps, you probably have used old header or library files when compiling your programs. In this case, you should check the date for your `mysql.h' file and `libmysqlclient.a' library to verify that they are from the new MySQL distribution. If not, recompile your programs with the new headers and libraries. If problems occur, such as that the new `mysqld' server does not start or that you cannot connect without a password, verify that you do not have an old `my.cnf' file from your previous installation. You can check this with the `--print-defaults' option (for example, `mysqld --print-defaults'). If this command displays anything other than the program name, you have an active `my.cnf' file that affects server or client operation. It is a good idea to rebuild and reinstall the Perl `DBD::mysql' module whenever you install a new release of MySQL. The same applies to other MySQL interfaces as well, such as the PHP `mysql' extension and the Python `MySQLdb' module.  File: manual.info, Node: upgrading-from-5-0, Next: upgrading-from-4-1, Prev: upgrade, Up: upgrade 2.4.16.1 Upgrading from MySQL 5.0 to 5.1 ........................................ This section does not apply to MySQL Enterprise Server users. *When upgrading a 5.0 installation to 5.0.10 or above* note that it is _necessary_ to upgrade your grant tables. Otherwise, creating stored procedures and functions might not work. The procedure for doing this is described in *Note mysql-upgrade::.  File: manual.info, Node: upgrading-from-4-1, Next: upgrading-to-arch, Prev: upgrading-from-5-0, Up: upgrade 2.4.16.2 Upgrading from MySQL 4.1 to 5.0 ........................................ *Note*: It is good practice to back up your data before installing any new version of software. Although MySQL works very hard to ensure a high level of quality, you should protect your data by making a backup. MySQL recommends that you dump and reload your tables from any previous version to upgrade to 5.0. In general, you should do the following when upgrading from MySQL 4.1 from 5.0: * Check the items in *Note upgrade::, to see whether any of them might affect your applications. * Check the items in the change lists found later in this section to see whether any of them might affect your applications. Note particularly any that are marked *Incompatible change*. These result in incompatibilities with earlier versions of MySQL, and may require your attention _before you upgrade_. * Some releases of MySQL introduce incompatible changes to tables. (Our aim is to avoid these changes, but occasionally they are necessary to correct problems that would be worse than an incompatibility between releases.) Some releases of MySQL introduce changes to the structure of the grant tables to add new privileges or features. To avoid problems due to such changes, after you upgrade to a new version of MySQL, you should check your tables (and repair them if necessary), and update your grant tables to make sure that they have the current structure so that you can take advantage of any new capabilities. See *Note mysql-upgrade::. * Read the MySQL 5.0 change history to see what significant new features you can use in 5.0. See *Note news-5-0-x::. * If you are running MySQL Server on Windows, see *Note windows-upgrading::. * MySQL 5.0 adds support for stored procedures. This support requires the `mysql.proc' table. To create this table, you should run the `mysql_upgrade' program as described in *Note mysql-upgrade::. * MySQL 5.0 adds support for views. This support requires extra privilege columns in the `mysql.user' and `mysql.db' tables. To create these columns, you should run the `mysql_upgrade' program as described in *Note mysql-upgrade::. * If you are using replication, see *Note replication-upgrade::, for information on upgrading your replication setup. Several visible behaviors have changed between MySQL 4.1 and MySQL 5.0 to make MySQL more compatible with standard SQL. These changes may affect your applications. The following lists describe changes that may affect applications and that you should watch out for when upgrading to MySQL 5.0. *Server Changes:* * *Incompatible change*: The indexing order for end-space in `TEXT' columns for `InnoDB' and `MyISAM' tables has changed. Starting from 5.0.3, `TEXT' indexes are compared as space-padded at the end (just as MySQL sorts `CHAR', `VARCHAR' and `TEXT' fields). If you have a index on a `TEXT' column, you should run `CHECK TABLE' on it. If the check reports errors, rebuild the indexes: Dump and reload the table if it is an `InnoDB' table, or run `OPTIMIZE TABLE' or `REPAIR TABLE' if it is a `MyISAM' table. * *Incompatible change*. For `BINARY' columns, the pad value and how it is handled has changed as of MySQL 5.0.15. The pad value for inserts now is `0x00' rather than space, and there is no stripping of the pad value for retrievals. For details, see *Note binary-varbinary::. * *Incompatible change*: As of MySQL 5.0.3, the server by default no longer loads user-defined functions (UDFs) unless they have at least one auxiliary symbol (for example, an `xxx_init' or `xxx_deinit' symbol) defined in addition to the main function symbol. This behavior can be overridden with the `--allow-suspicious-udfs' option. See *Note udf-security::. * *Incompatible change*: Previously, a lock wait timeout caused `InnoDB' to roll back the entire current transaction. As of MySQL 5.0.13, it rolls back only the most recent SQL statement. * *Incompatible change*: For `ENUM' columns that had enumeration values containing commas, the commas were mapped to 0xff internally. However, this rendered the commas indistinguishable from true 0xff characters in the values. This no longer occurs. However, the fix requires that you dump and reload any tables that have `ENUM' columns containing true 0xff in their values: Dump the tables using `mysqldump' with the current server before upgrading from a version of MySQL 5.0 older than 5.0.36 to version 5.0.36 or newer. * *Incompatible change*: The update log has been removed in MySQL 5.0. If you had enabled it previously, you should enable the binary log instead. * *Incompatible change:* Support for the `ISAM' storage engine has been removed in MySQL 5.0. If you have any `ISAM' tables, you should convert them _before_ upgrading. For example, to convert an `ISAM' table to use the `MyISAM' storage engine, use this statement: ALTER TABLE TBL_NAME ENGINE = MyISAM; Use a similar statement for every `ISAM' table in each of your databases. * *Incompatible change*: Support for `RAID' options in `MyISAM' tables has been removed in MySQL 5.0. If you have tables that use these options, you should convert them before upgrading. One way to do this is to dump them with `mysqldump', edit the dump file to remove the `RAID' options in the `CREATE TABLE' statements, and reload the dump file. Another possibility is to use `CREATE TABLE NEW_TBL ... SELECT RAID_TBL' to create a new table from the `RAID' table. However, the `CREATE TABLE' part of the statement must contain sufficient information to re-create column attributes as well as indexes, or column attributes may be lost and indexes will not appear in the new table. See *Note create-table::. The `.MYD' files for `RAID' tables in a given database are stored under the database directory in subdirectories that have names consisting of two hex digits in the range from `00' to `ff'. After converting all tables that use `RAID' options, these `RAID'-related subdirectories still will exist but can be removed. Verify that they are empty, and then remove them manually. (If they are not empty, there is some `RAID' table that has not been converted.) * As of MySQL 5.0.25, the `lc_time_names' system 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. See *Note locale-support::. * In MySQL 5.0.6, binary logging of stored routines and triggers was changed. This change has implications for security, replication, and data recovery, as discussed in *Note stored-procedure-logging::. * As of MySQL 5.0.28, `mysqld_safe' no longer implicitly invokes `mysqld-max' if it exists. Instead, it invokes `mysqld' unless a `--mysqld' or `--mysqld-version' option is given to specify another server explicitly. If you previously relied on the implicit invocation of `mysqld-max', you should use an appropriate option now. *SQL Changes:* * *Incompatible change:* Beginning with MySQL 5.0.12, natural joins and joins with `USING', including outer join variants, are processed according to the SQL:2003 standard. The changes include elimination of redundant output columns for `NATURAL' joins and joins specified with a `USING' clause and proper ordering of output columns. The precedence of the comma operator also now is lower compared to `JOIN', `LEFT JOIN', and so forth. These changes make MySQL more compliant with standard SQL. However, they can result in different output columns for some joins. Also, some queries that appeared to work correctly prior to 5.0.12 must be rewritten to comply with the standard. For details about the scope of the changes and examples that show what query rewrites are necessary, see *Note join::. * *Incompatible change:* The namespace for triggers has changed in MySQL 5.0.10. Previously, trigger names had to be unique per table. Now they must be unique within the schema (database). An implication of this change is that `DROP TRIGGER' syntax now uses a schema name instead of a table name (schema name is optional and, if omitted, the current schema will be used). When upgrading from a previous version of MySQL 5 to MySQL 5.0.10 or newer, you must drop all triggers and re-create them or `DROP TRIGGER' will not work after the upgrade. Here is a suggested procedure for doing this: 1. Upgrade to MySQL 5.0.10 or later to be able to access trigger information in the `INFORMATION_SCHEMA.TRIGGERS' table. (It should work even for pre-5.0.10 triggers.) 2. Dump all trigger definitions using the following `SELECT' statement: SELECT CONCAT('CREATE TRIGGER ', t.TRIGGER_SCHEMA, '.', t.TRIGGER_NAME, ' ', t.ACTION_TIMING, ' ', t.EVENT_MANIPULATION, ' ON ', t.EVENT_OBJECT_SCHEMA, '.', t.EVENT_OBJECT_TABLE, ' FOR EACH ROW ', t.ACTION_STATEMENT, '//' ) INTO OUTFILE '/tmp/triggers.sql' FROM INFORMATION_SCHEMA.TRIGGERS AS t; The statement uses `INTO OUTFILE', so you must have the `FILE' privilege. The file will be created on the server host. Use a different filename if you like. To be 100% safe, inspect the trigger definitions in the `triggers.sql' file, and perhaps make a backup of the file. 3. Stop the server and drop all triggers by removing all `.TRG' files in your database directories. Change location to your data directory and issue this command: shell> rm */*.TRG 4. Start the server and re-create all triggers using the `triggers.sql' file. For the file created earlier, use these commands in the `mysql' program: mysql> delimiter // ; mysql> source /tmp/triggers.sql // 5. Use the `SHOW TRIGGERS' statement to check that all triggers were created successfully. * *Incompatible change:* As of MySQL 5.0.15, the `CHAR()' function returns a binary string rather than a string in the connection character set. An optional `USING CHARSET_NAME' clause may be used to produce a result in a specific character set instead. Also, arguments larger than 256 produce multiple characters. They are no longer interpreted modulo 256 to produce a single character each. These changes may cause some incompatibilities: * `CHAR(ORD('A')) = 'a'' is no longer true: mysql> SELECT CHAR(ORD('A')) = 'a'; +----------------------+ | CHAR(ORD('A')) = 'a' | +----------------------+ | 0 | +----------------------+ To perform a case-insensitive comparison, you can produce a result string in a non-binary character set by adding a `USING' clause or converting the result: mysql> SELECT CHAR(ORD('A') USING latin1) = 'a'; +-----------------------------------+ | CHAR(ORD('A') USING latin1) = 'a' | +-----------------------------------+ | 1 | +-----------------------------------+ mysql> SELECT CONVERT(CHAR(ORD('A')) USING latin1) = 'a'; +--------------------------------------------+ | CONVERT(CHAR(ORD('A')) USING latin1) = 'a' | +--------------------------------------------+ | 1 | +--------------------------------------------+ * `CREATE TABLE ... SELECT CHAR(...)' produces a `VARBINARY' column, not a `VARCHAR' column. To produce a `VARCHAR' column, use `USING' or `CONVERT()' as just described to convert the `CHAR()' result into a non-binary character set. * Previously, the following statements inserted the value `0x00410041' (`'AA'' as a `ucs2' string) into the table: CREATE TABLE t (ucs2_column CHAR(2) CHARACTER SET ucs2); INSERT INTO t VALUES (CHAR(0x41,0x41)); As of MySQL 5.0.15, the statements insert a single `ucs2' character with value `0x4141'. * *Incompatible change:* By default, integer subtraction involving an unsigned value should produce an unsigned result. Tracking of the `unsignedness' of an expression was improved in MySQL 5.0.13. This means that, in some cases where an unsigned subtraction would have resulted in a signed integer, it now results in an unsigned integer. One context in which this difference manifests itself is when a subtraction involving an unsigned operand would be negative. Suppose that `i' is a `TINYINT UNSIGNED' column and has a value of 0. The server evaluates the following expression using 64-bit unsigned integer arithmetic with the following result: mysql> SELECT i - 1 FROM t; +----------------------+ | i - 1 | +----------------------+ | 18446744073709551615 | +----------------------+ If the expression is used in an `UPDATE t SET i = i - 1' statement, the expression is evaluated and the result assigned to `i' according to the usual rules for handling values outside the column range or 0 to 255. That is, the value is clipped to the nearest endpoint of the range. However, the result is version-specific: * Before MySQL 5.0.13, the expression is evaluated but is treated as the equivalent 64-bit signed value (-1) for the assignment. The value of -1 is clipped to the nearest endpoint of the column range, resulting in a value of 0: mysql> UPDATE t SET i = i - 1; SELECT i FROM t; +------+ | i | +------+ | 0 | +------+ * As of MySQL 5.0.13, the expression is evaluated and retains its unsigned attribute for the assignment. The value of 18446744073709551615 is clipped to the nearest endpoint of the column range, resulting in a value of 255: mysql> UPDATE t SET i = i - 1; SELECT i FROM t; +------+ | i | +------+ | 255 | +------+ To get the older behavior, use `CAST()' to convert the expression result to a signed value: UPDATE t SET i = CAST(i - 1 AS SIGNED); Alternatively, set the `NO_UNSIGNED_SUBTRACTION' SQL mode. However, this will affect all integer subtractions involving unsigned values. * *Incompatible change:* Before MySQL 5.0.13, `NOW()' and `SYSDATE()' return the same value (the time at which the statement in which the function occurs begins executing). As of MySQL 5.0.13, `SYSDATE()' returns the time at which it it executes, which can differ from the value returned by `NOW()'. For information about the implications for binary logging and replication, see the description for `SYSDATE()' in *Note date-and-time-functions:: and for `SET TIMESTAMP' in *Note set-option::. To restore the former behavior for `SYSDATE()' and cause it to be an alias for `NOW()', start the server with the `--sysdate-is-now' option (available as of MySQL 5.0.20). * *Incompatible change:* Before MySQL 5.0.13, `GREATEST(X,NULL)' and `LEAST(X,NULL)' return X when X is a non-`NULL' value. As of 5.0.3, both functions return `NULL' if any argument is `NULL', the same as Oracle. This change can cause problems for applications that rely on the old behavior. * *Incompatible change:* Before MySQL 4.1.13/5.0.8, conversion of `DATETIME' values to numeric form by adding zero produced a result in `YYYYMMDDHHMMSS' format. The result of `DATETIME+0' is now in `YYYYMMDDHHMMSS.000000' format. * *Incompatible change:* In MySQL 4.1.12/5.0.6, the behavior of `LOAD DATA INFILE' and `SELECT ... INTO OUTFILE' has changed when the `FIELDS TERMINATED BY' and `FIELDS ENCLOSED BY' values both are empty. Formerly, a column was read or written the display width of the column. For example, `INT(4)' was read or written using a field with a width of 4. Now columns are read and written using a field width wide enough to hold all values in the field. However, data files written before this change was made might not be reloaded correctly with `LOAD DATA INFILE' for MySQL 4.1.12/5.0.6 and up. This change also affects data files read by `mysqlimport' and written by `mysqldump --tab', which use `LOAD DATA INFILE' and `SELECT ... INTO OUTFILE'. For more information, see *Note load-data::. * *Incompatible change*: The implementation of `DECIMAL' has changed in MySQL 5.0.3. You should make your applications aware of this change. For information about this change, and about possible incompatibilities with old applications, see *Note precision-math::. `DECIMAL' columns are stored in a more efficient format. To convert a table to use the new `DECIMAL' type, you should do an `ALTER TABLE' on it. (The `ALTER TABLE' also will change the table's `VARCHAR' columns to use the new `VARCHAR' data type properties, described in a separate item.) A consequence of the change in handling of the `DECIMAL' and `NUMERIC' fixed-point data types is that the server is more strict to follow standard SQL. For example, a data type of `DECIMAL(3,1)' stores a maximum value of 99.9. Before MySQL 5.0.3, the server allowed larger numbers to be stored. That is, it stored a value such as 100.0 as 100.0. As of MySQL 5.0.3, the server clips 100.0 to the maximum allowable value of 99.9. If you have tables that were created before MySQL 5.0.3 and that contain floating-point data not strictly legal for the data type, you should alter the data types of those columns. For example: ALTER TABLE TBL_NAME MODIFY COL_NAME DECIMAL(4,1); The behavior used by the server for `DECIMAL' columns in a table depends on the version of MySQL used to create the table. If your server is from MySQL 5.0.3 or higher, but you have `DECIMAL' columns in tables that were created before 5.0.3, the old behavior still applies to those columns. To convert the tables to the newer `DECIMAL' format, dump them with `mysqldump' and reload them. * *Incompatible change:* MySQL 5.0.3 and up uses precision math when calculating with `DECIMAL' and integer columns (64 decimal digits) and for rounding exact-value numbers. Rounding behavior is well-defined, not dependent on the implementation of the underlying C library. However, this might result in incompatibilities for applications that rely on the old behavior. (For example, inserting .5 into an `INT' column results in 1 as of MySQL 5.0.3, but might be 0 in older versions.) For more information about rounding behavior, see *Note precision-math-rounding::, and *Note precision-math-examples::. * *Incompatible change*: `MyISAM' and `InnoDB' tables created with `DECIMAL' columns in MySQL 5.0.3 to 5.0.5 will appear corrupt after an upgrade to MySQL 5.0.6. (The same incompatibility will occur for these tables created in MySQL 5.0.6 after a downgrade to MySQL 5.0.3 to 5.0.5.) If you have such tables, check and repair them with `mysql_upgrade' after upgrading. See *Note mysql-upgrade::. * *Incompatible change:* For user-defined functions, exact-value decimal arguments such as `1.3' or `DECIMAL' column values were passed as `REAL_RESULT' values prior to MySQL 5.0.3. As of 5.0.3, they are passed as strings with a type of `DECIMAL_RESULT'. If you upgrade to 5.0.3 and find that your UDF now receives string values, use the initialization function to coerce the arguments to numbers as described in *Note udf-arguments::. * *Incompatible change:* Before MySQL 5.0.2, `SHOW STATUS' returned global status values. The default as of 5.0.2 is to return session values, which 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: SHOW /*!50002 GLOBAL */ STATUS; * *Incompatible change:* User variables are not case sensitive in MySQL 5.0. In MySQL 4.1, `SET @x = 0; SET @X = 1; SELECT @x;' created two variables and returned `0'. In MySQL 5.0, it creates one variable and returns `1'. Replication setups that rely on the old behavior may be affected by this change. * Some keywords are reserved in MySQL 5.0 that were not reserved in MySQL 4.1. See *Note reserved-words::. * The `LOAD DATA FROM MASTER' and `LOAD TABLE FROM MASTER' statements are deprecated. See *Note load-data-from-master::, for recommended alternatives. * As of MySQL 5.0.3, trailing spaces no longer are removed from values stored in `VARCHAR' and `VARBINARY' columns. The maximum lengths for `VARCHAR' and `VARBINARY' columns in MySQL 5.0.3 and later are 65,535 characters and 65,535 bytes, respectively. When a binary upgrade (filesystem-level copy of data files) to MySQL 5.0 is performed for a table with a `VARBINARY' column, the column is space-padded to the full allowable width of the column. This causes values in `VARBINARY' columns that do not occupy the full width of the column to include extra trailing spaces after the upgrade, which means that the data in the column is different. In addition, new rows inserted into a table upgraded in this way will be space padded to the full width of the column. This issue can be resolved as follows: 1. For each table containing `VARBINARY' columns, execute the statement ALTER TABLE TABLE_NAME ENGINE=ENGINE_NAME; where TABLE_NAME is the name of the table and ENGINE_NAME is the name of the storage engine currently used by TABLE_NAME. In other words, if the table named `mytable' uses the `MyISAM' storage engine, then you would use this statement: ALTER TABLE mytable ENGINE=MYISAM; This rebuilds the table so that it uses the 5.0 `VARBINARY' format. 2. Then you must remove all trailing spaces from any `VARBINARY' column values. For each `VARBINARY' column VARBINARY_COLUMN, you should perform the following statement (where TABLE_NAME is the name of the table containing the `VARBINARY' column): UPDATE TABLE_NAME SET VARBINARY_COLUMN = RTRIM(VARBINARY_COLUMN); This is necessary and safe because trailing spaces are stripped before 5.0.3, meaning that any trailing spaces are erroneous. This problem does not occur (and thus these two steps are not required) for tables upgraded using the recommended procedure of dumping tables prior to the upgrade and reloading them afterwards. *Note*: If you create a table with new `VARCHAR' or `VARBINARY' columns in MySQL 5.0.3 or later, the table will not be usable if you downgrade to a version older than 5.0.3. Dump the table with `mysqldump' before downgrading and reload it after downgrading. * Comparisons made between `FLOAT' or `DOUBLE' values that happened to work in MySQL 4.1 may not do so in 5.0. Values of these types are imprecise in all MySQL versions, and you are _strongly advised_ to avoid such comparisons as `WHERE COL_NAME=SOME_DOUBLE', _regardless of the MySQL version you are using_. See *Note problems-with-float::. * As of MySQL 5.0.3, `BIT' is a separate data type, not a synonym for `TINYINT(1)'. See *Note numeric-type-overview::. * MySQL 5.0.2 adds several SQL modes that allow stricter control over rejecting records that have invalid or missing values. See *Note server-sql-mode::, and *Note constraint-invalid-data::. If you want to enable this control but continue to use MySQL's capability for storing incorrect dates such as `'2004-02-31'', you should start the server with `--sql_mode="TRADITIONAL,ALLOW_INVALID_DATES"'. * As of MySQL 5.0.2, the `SCHEMA' and `SCHEMAS' keywords are accepted as synonyms for `DATABASE' and `DATABASES', respectively. (While `schemata' is grammatically correct and even appears in some MySQL 5.0 system database and table names, it cannot be used as a keyword.) * As of MySQL 5.0.25, `TIMESTAMP' columns that are `NOT NULL' now are reported that way by `SHOW COLUMNS' and `INFORMATION_SCHEMA', rather than as `NULL'. *C API Changes:* * *Incompatible change*: Because the MySQL 5.0 server has a new implementation of the `DECIMAL' data type, a problem may occur if the server is used by older clients that still are linked against MySQL 4.1 client libraries. If a client uses the binary client/server protocol to execute prepared statements that generate result sets containing numeric values, an error will be raised: `'Using unsupported buffer type: 246'' This error occurs because the 4.1 client libraries do not support the new `MYSQL_TYPE_NEWDECIMAL' type value added in 5.0. There is no way to disable the new `DECIMAL' data type on the server side. You can avoid the problem by relinking the application with the client libraries from MySQL 5.0. * *Incompatible change*: The `ER_WARN_DATA_TRUNCATED' warning symbol was renamed to `WARN_DATA_TRUNCATED' in MySQL 5.0.3. * The `reconnect' flag in the `MYSQL' structure is set to 0 by `mysql_real_connect()'. Only those client programs which did not explicitly set this flag to 0 or 1 after `mysql_real_connect()' experience a change. Having automatic reconnection enabled by default was considered too dangerous (due to the fact that table locks, temporary tables, user variables, and session variables are lost after reconnection).  File: manual.info, Node: upgrading-to-arch, Prev: upgrading-from-4-1, Up: upgrade 2.4.16.3 Copying MySQL Databases to Another Machine ................................................... You can copy the `.frm', `.MYI', and `.MYD' files for `MyISAM' tables between different architectures that support the same floating-point format. (MySQL takes care of any byte-swapping issues.) See *Note myisam-storage-engine::. In cases where you need to transfer databases between different architectures, you can use `mysqldump' to create a file containing SQL statements. You can then transfer the file to the other machine and feed it as input to the `mysql' client. Use `mysqldump --help' to see what options are available. If you are moving the data to a newer version of MySQL, you should use `mysqldump --opt' to take advantage of any optimizations that result in a dump file that is smaller and can be processed more quickly. The easiest (although not the fastest) way to move a database between two machines is to run the following commands on the machine on which the database is located: shell> mysqladmin -h 'OTHER_HOSTNAME' create DB_NAME shell> mysqldump --opt DB_NAME | mysql -h 'OTHER_HOSTNAME' DB_NAME If you want to copy a database from a remote machine over a slow network, you can use these commands: shell> mysqladmin create DB_NAME shell> mysqldump -h 'OTHER_HOSTNAME' --opt --compress DB_NAME | mysql DB_NAME You can also store the dump in a file, transfer the file to the target machine, and then load the file into the database there. For example, you can dump a database to a compressed file on the source machine like this: shell> mysqldump --quick DB_NAME | gzip > DB_NAME.gz Transfer the file containing the database contents to the target machine and run these commands there: shell> mysqladmin create DB_NAME shell> gunzip < DB_NAME.gz | mysql DB_NAME You can also use `mysqldump' and `mysqlimport' to transfer the database. For large tables, this is much faster than simply using `mysqldump'. In the following commands, DUMPDIR represents the full pathname of the directory you use to store the output from `mysqldump'. First, create the directory for the output files and dump the database: shell> mkdir DUMPDIR shell> mysqldump --tab=DUMPDIR DB_NAME Then transfer the files in the DUMPDIR directory to some corresponding directory on the target machine and load the files into MySQL there: shell> mysqladmin create DB_NAME # create database shell> cat DUMPDIR/*.sql | mysql DB_NAME # create tables in database shell> mysqlimport DB_NAME DUMPDIR/*.txt # load data into tables Do not forget to copy the `mysql' database because that is where the grant tables are stored. You might have to run commands as the MySQL `root' user on the new machine until you have the `mysql' database in place. After you import the `mysql' database on the new machine, execute `mysqladmin flush-privileges' so that the server reloads the grant table information.  File: manual.info, Node: downgrading, Next: operating-system-specific-notes, Prev: upgrade, Up: installing-cs 2.4.17 Downgrading MySQL ------------------------ * Menu: * downgrading-to-4-1:: Downgrading to MySQL 4.1 This section does not apply to MySQL Enterprise Server users. This section describes what you should do to downgrade to an older MySQL version in the unlikely case that the previous version worked better than the new one. If you are downgrading within the same release series (for example, from 4.1.13 to 4.1.12) the general rule is that you just have to install the new binaries on top of the old ones. There is no need to do anything with the databases. As always, however, it is always a good idea to make a backup. The following items form a checklist of things you should do whenever you perform a downgrade: * Read the upgrading section for the release series from which you are downgrading to be sure that it does not have any features you really need. *Note upgrade::. * If there is a downgrading section for that version, you should read that as well. In most cases, you can move the MySQL format files and data files between different versions on the same architecture as long as you stay within versions for the same release series of MySQL. If you downgrade from one release series to another, there may be incompatibilities in table storage formats. In this case, you can use `mysqldump' to dump your tables before downgrading. After downgrading, reload the dump file using `mysql' or `mysqlimport' to re-create your tables. For examples, see *Note upgrading-to-arch::. The normal symptom of a downward-incompatible table format change when you downgrade is that you can't open tables. In that case, use the following procedure: 1. Stop the older MySQL server that you are downgrading to. 2. Restart the newer MySQL server you are downgrading from. 3. Dump any tables that were inaccessible to the older server by using `mysqldump' to create a dump file. 4. Stop the newer MySQL server and restart the older one. 5. Reload the dump file into the older server. Your tables should be accessible.  File: manual.info, Node: downgrading-to-4-1, Prev: downgrading, Up: downgrading 2.4.17.1 Downgrading to MySQL 4.1 ................................. This section does not apply to MySQL Enterprise Server users. MySQL 4.1 does not support stored routines or triggers. If your databases contain stored routines or triggers, prevent them from being dumped when you use `mysqldump' by using the `--skip-routines' and `--skip-triggers' options. (See *Note mysqldump::.) MySQL 4.1 does not support views. If your databases contain views, remove them with `DROP VIEW' before using `mysqldump'. (See *Note drop-view::.) After downgrading from MySQL 5.0, you may see the following information in the `mysql.err' file: Incorrect information in file: './mysql/user.frm' In this case, you can do the following: 1. Start MySQL 5.0.4 (or newer). 2. Run `mysql_fix_privilege_tables', which will change the `mysql.user' table to a format that both MySQL 4.1 and 5.0 can use. 3. Stop the MySQL server. 4. Start MySQL 4.1. If the preceding procedure fails, you should be able to do the following instead: 1. Start MySQL 5.0.4 (or newer). 2. Run `mysqldump --opt --add-drop-table mysql > /tmp/mysql.dump'. 3. Stop the MySQL server. 4. Start MySQL 4.1 with the `--skip-grant' option. 5. Run `mysql mysql < /tmp/mysql.dump'. 6. Run `mysqladmin flush-privileges'.  File: manual.info, Node: operating-system-specific-notes, Next: environment-variables, Prev: downgrading, Up: installing-cs 2.4.18 Operating System-Specific Notes -------------------------------------- * Menu: * linux:: Linux Notes * mac-os-x:: Mac OS X Notes * solaris:: Solaris Notes * bsd-notes:: BSD Notes * other-unix-notes:: Other Unix Notes * os-2:: OS/2 Notes  File: manual.info, Node: linux, Next: mac-os-x, Prev: operating-system-specific-notes, Up: operating-system-specific-notes 2.4.18.1 Linux Notes .................... * Menu: * linux-os:: Linux Operating System Notes * binary-notes-linux:: Linux Binary Distribution Notes * source-notes-linux:: Linux Source Distribution Notes * linux-post-install:: Linux Post-Installation Notes * linux-x86:: Linux x86 Notes * linux-sparc:: Linux SPARC Notes * linux-alpha:: Linux Alpha Notes * linux-powerpc:: Linux PowerPC Notes * linux-mips:: Linux MIPS Notes * linux-ia-64:: Linux IA-64 Notes * selinux:: SELinux Notes This section discusses issues that have been found to occur on Linux. The first few subsections describe general operating system-related issues, problems that can occur when using binary or source distributions, and post-installation issues. The remaining subsections discuss problems that occur with Linux on specific platforms. Note that most of these problems occur on older versions of Linux. If you are running a recent version, you may see none of them.  File: manual.info, Node: linux-os, Next: binary-notes-linux, Prev: linux, Up: linux 2.4.18.2 Linux Operating System Notes ..................................... MySQL needs at least Linux version 2.0. *Warning:* We have seen some strange problems with Linux 2.2.14 and MySQL on SMP systems. We also have reports from some MySQL users that they have encountered serious stability problems using MySQL with kernel 2.2.14. If you are using this kernel, you should upgrade to 2.2.19 (or newer) or to a 2.4 kernel. If you have a multiple-CPU box, you should seriously consider using 2.4 because it gives you a significant speed boost. Your system should be more stable. When using LinuxThreads, you should see a minimum of three `mysqld' processes running. These are in fact threads. There is one thread for the LinuxThreads manager, one thread to handle connections, and one thread to handle alarms and signals.  File: manual.info, Node: binary-notes-linux, Next: source-notes-linux, Prev: linux-os, Up: linux 2.4.18.3 Linux Binary Distribution Notes ........................................ The Linux-Intel binary and RPM releases of MySQL are configured for the highest possible speed. We are always trying to use the fastest stable compiler available. The binary release is linked with `-static', which means you do not normally need to worry about which version of the system libraries you have. You need not install LinuxThreads, either. A program linked with `-static' is slightly larger than a dynamically linked program, but also slightly faster (3-5%). However, one problem with a statically linked program is that you can't use user-defined functions (UDFs). If you are going to write or use UDFs (this is something for C or C++ programmers only), you must compile MySQL yourself using dynamic linking. A known issue with binary distributions is that on older Linux systems that use `libc' (such as Red Hat 4.x or Slackware), you get some (non-fatal) issues with hostname resolution. If your system uses `libc' rather than `glibc2', you probably will encounter some difficulties with hostname resolution and `getpwnam()'. This happens because `glibc' (unfortunately) depends on some external libraries to implement hostname resolution and `getpwent()', even when compiled with `-static'. These problems manifest themselves in two ways: * You may see the following error message when you run `mysql_install_db': Sorry, the host 'XXXX' could not be looked up You can deal with this by executing `mysql_install_db --force', which does not execute the `resolveip' test in `mysql_install_db'. The downside is that you cannot use hostnames in the grant tables: except for `localhost', you must use IP numbers instead. If you are using an old version of MySQL that does not support `--force', you must manually remove the `resolveip' test in `mysql_install' using a text editor. * You also may see the following error when you try to run `mysqld' with the `--user' option: getpwnam: No such file or directory To work around this problem, start `mysqld' by using the `su' command rather than by specifying the `--user' option. This causes the system itself to change the user ID of the `mysqld' process so that `mysqld' need not do so. Another solution, which solves both problems, is not to use a binary distribution. Obtain a MySQL source distribution (in RPM or `tar.gz' format) and install that instead. On some Linux 2.2 versions, you may get the error `Resource temporarily unavailable' when clients make a great many new connections to a `mysqld' server over TCP/IP. The problem is that Linux has a delay between the time that you close a TCP/IP socket and the time that the system actually frees it. There is room for only a finite number of TCP/IP slots, so you encounter the resource-unavailable error if clients attempt too many new TCP/IP connections over a short period of time. For example, you may see the error when you run the MySQL `test-connect' benchmark over TCP/IP. We have inquired about this problem a few times on different Linux mailing lists but have never been able to find a suitable resolution. The only known `fix' is for clients to use persistent connections, or, if you are running the database server and clients on the same machine, to use Unix socket file connections rather than TCP/IP connections.  File: manual.info, Node: source-notes-linux, Next: linux-post-install, Prev: binary-notes-linux, Up: linux 2.4.18.4 Linux Source Distribution Notes ........................................ This section does not apply to MySQL Enterprise Server users. The following notes regarding `glibc' apply only to the situation when you build MySQL yourself. If you are running Linux on an x86 machine, in most cases it is much better for you to use our binary. We link our binaries against the best patched version of `glibc' we can find and with the best compiler options, in an attempt to make it suitable for a high-load server. For a typical user, even for setups with a lot of concurrent connections or tables exceeding the 2GB limit, our binary is the best choice in most cases. After reading the following text, if you are in doubt about what to do, try our binary first to determine whether it meets your needs. If you discover that it is not good enough, you may want to try your own build. In that case, we would appreciate a note about it so that we can build a better binary next time. MySQL uses LinuxThreads on Linux. If you are using an old Linux version that doesn't have `glibc2', you must install LinuxThreads before trying to compile MySQL. You can obtain LinuxThreads from `http://dev.mysql.com/downloads/os-linux.html'. Note that `glibc' versions before and including version 2.1.1 have a fatal bug in `pthread_mutex_timedwait()' handling, which is used when `INSERT DELAYED' statements are issued. We recommend that you not use `INSERT DELAYED' before upgrading `glibc'. Note that Linux kernel and the LinuxThread library can by default handle a maximum of 1,024 threads. If you plan to have more than 1,000 concurrent connections, you need to make some changes to LinuxThreads, as follows: * Increase `PTHREAD_THREADS_MAX' in `sysdeps/unix/sysv/linux/bits/local_lim.h' to 4096 and decrease `STACK_SIZE' in `linuxthreads/internals.h' to 256KB. The paths are relative to the root of `glibc'. (Note that MySQL is not stable with 600-1000 connections if `STACK_SIZE' is the default of 2MB.) * Recompile LinuxThreads to produce a new `libpthread.a' library, and relink MySQL against it. There is another issue that greatly hurts MySQL performance, especially on SMP systems. The mutex implementation in LinuxThreads in `glibc' 2.1 is very poor for programs with many threads that hold the mutex only for a short time. This produces a paradoxical result: If you link MySQL against an unmodified LinuxThreads, removing processors from an SMP actually improves MySQL performance in many cases. We have made a patch available for `glibc' 2.1.3 to correct this behavior (`http://dev.mysql.com/Downloads/Linux/linuxthreads-2.1-patch'). With `glibc' 2.2.2, MySQL uses the adaptive mutex, which is much better than even the patched one in `glibc' 2.1.3. Be warned, however, that under some conditions, the current mutex code in `glibc' 2.2.2 overspins, which hurts MySQL performance. The likelihood that this condition occurs can be reduced by re-nicing the `mysqld' process to the highest priority. We have also been able to correct the overspin behavior with a patch, available at `http://dev.mysql.com/Downloads/Linux/linuxthreads-2.2.2.patch'. It combines the correction of overspin, maximum number of threads, and stack spacing all in one. You need to apply it in the `linuxthreads' directory with `patch -p0 cat /proc/sys/fs/file-max shell> cat /proc/sys/fs/dquot-max shell> cat /proc/sys/fs/super-max If you have more than 16MB of memory, you should add something like the following to your init scripts (for example, `/etc/init.d/boot.local' on SuSE Linux): echo 65536 > /proc/sys/fs/file-max echo 8192 > /proc/sys/fs/dquot-max echo 1024 > /proc/sys/fs/super-max You can also run the `echo' commands from the command line as `root', but these settings are lost the next time your computer restarts. Alternatively, you can set these parameters on startup by using the `sysctl' tool, which is used by many Linux distributions (including SuSE Linux 8.0 and later). Put the following values into a file named `/etc/sysctl.conf': # Increase some values for MySQL fs.file-max = 65536 fs.dquot-max = 8192 fs.super-max = 1024 You should also add the following to `/etc/my.cnf': [mysqld_safe] open-files-limit=8192 This should allow the server a limit of 8,192 for the combined number of connections and open files. The `STACK_SIZE' constant in LinuxThreads controls the spacing of thread stacks in the address space. It needs to be large enough so that there is plenty of room for each individual thread stack, but small enough to keep the stack of some threads from running into the global `mysqld' data. Unfortunately, as we have experimentally discovered, the Linux implementation of `mmap()' successfully unmaps a mapped region if you ask it to map out an address currently in use, zeroing out the data on the entire page instead of returning an error. So, the safety of `mysqld' or any other threaded application depends on the `gentlemanly' behavior of the code that creates threads. The user must take measures to make sure that the number of running threads at any given time is sufficiently low for thread stacks to stay away from the global heap. With `mysqld', you should enforce this behavior by setting a reasonable value for the `max_connections' variable. If you build MySQL yourself, you can patch LinuxThreads for better stack use. See *Note source-notes-linux::. If you do not want to patch LinuxThreads, you should set `max_connections' to a value no higher than 500. It should be even less if you have a large key buffer, large heap tables, or some other things that make `mysqld' allocate a lot of memory, or if you are running a 2.2 kernel with a 2GB patch. If you are using our binary or RPM version, you can safely set `max_connections' at 1500, assuming no large key buffer or heap tables with lots of data. The more you reduce `STACK_SIZE' in LinuxThreads the more threads you can safely create. We recommend values between 128KB and 256KB. If you use a lot of concurrent connections, you may suffer from a `feature' in the 2.2 kernel that attempts to prevent fork bomb attacks by penalizing a process for forking or cloning a child. This causes MySQL not to scale well as you increase the number of concurrent clients. On single-CPU systems, we have seen this manifest as very slow thread creation; it may take a long time to connect to MySQL (as long as one minute), and it may take just as long to shut it down. On multiple-CPU systems, we have observed a gradual drop in query speed as the number of clients increases. In the process of trying to find a solution, we have received a kernel patch from one of our users who claimed it helped for his site. This patch is available at `http://dev.mysql.com/Downloads/Patches/linux-fork.patch'. We have done rather extensive testing of this patch on both development and production systems. It has significantly improved MySQL performance without causing any problems and we recommend it to our users who still run high-load servers on 2.2 kernels. This issue has been fixed in the 2.4 kernel, so if you are not satisfied with the current performance of your system, rather than patching your 2.2 kernel, it might be easier to upgrade to 2.4. On SMP systems, upgrading also gives you a nice SMP boost in addition to fixing the fairness bug. We have tested MySQL on the 2.4 kernel on a two-CPU machine and found MySQL scales _much_ better. There was virtually no slowdown on query throughput all the way up to 1,000 clients, and the MySQL scaling factor (computed as the ratio of maximum throughput to the throughput for one client) was 180%. We have observed similar results on a four-CPU system: Virtually no slowdown as the number of clients was increased up to 1,000, and a 300% scaling factor. Based on these results, for a high-load SMP server using a 2.2 kernel, we definitely recommend upgrading to the 2.4 kernel at this point. We have discovered that it is essential to run the `mysqld' process with the highest possible priority on the 2.4 kernel to achieve maximum performance. This can be done by adding a `renice -20 $$' command to `mysqld_safe'. In our testing on a four-CPU machine, increasing the priority resulted in a 60% throughput increase with 400 clients. We are currently also trying to collect more information on how well MySQL performs with a 2.4 kernel on four-way and eight-way systems. If you have access such a system and have done some benchmarks, please send an email message to with the results. We will review them for inclusion in the manual. If you see a dead `mysqld' server process with `ps', this usually means that you have found a bug in MySQL or you have a corrupted table. See *Note crashing::. To get a core dump on Linux if `mysqld' dies with a `SIGSEGV' signal, you can start `mysqld' with the `--core-file' option. Note that you also probably need to raise the core file size by adding `ulimit -c 1000000' to `mysqld_safe' or starting `mysqld_safe' with `--core-file-size=1000000'. See *Note mysqld-safe::.  File: manual.info, Node: linux-x86, Next: linux-sparc, Prev: linux-post-install, Up: linux 2.4.18.6 Linux x86 Notes ........................ MySQL requires `libc' 5.4.12 or newer. It is known to work with `libc' 5.4.46. `glibc' 2.0.6 and later should also work. There have been some problems with the `glibc' RPMs from Red Hat, so if you have problems, check whether there are any updates. The `glibc' 2.0.7-19 and 2.0.7-29 RPMs are known to work. If you are using Red Hat 8.0 or a new `glibc' 2.2.x library, you may see `mysqld' die in `gethostbyaddr()'. This happens because the new `glibc' library requires a stack size greater than 128KB for this call. To fix the problem, start `mysqld' with the `--thread-stack=192K' option. (Use `-O thread_stack=192K' before MySQL 4.) This stack size is the default on MySQL 4.0.10 and above, so you should not see the problem. If you are using `gcc' 3.0 and above to compile MySQL, you must install the `libstdc++v3' library before compiling MySQL; if you don't do this, you get an error about a missing `__cxa_pure_virtual' symbol during linking. On some older Linux distributions, `configure' may produce an error like this: Syntax error in sched.h. Change _P to __P in the /usr/include/sched.h file. See the Installation chapter in the Reference Manual. Just do what the error message says. Add an extra underscore to the `_P' macro name that has only one underscore, and then try again. You may get some warnings when compiling. Those shown here can be ignored: mysqld.cc -o objs-thread/mysqld.o mysqld.cc: In function `void init_signals()': mysqld.cc:315: warning: assignment of negative value `-1' to `long unsigned int' mysqld.cc: In function `void * signal_hand(void *)': mysqld.cc:346: warning: assignment of negative value `-1' to `long unsigned int' If `mysqld' always dumps core when it starts, the problem may be that you have an old `/lib/libc.a'. Try renaming it, and then remove `sql/mysqld' and do a new `make install' and try again. This problem has been reported on some Slackware installations. If you get the following error when linking `mysqld', it means that your `libg++.a' is not installed correctly: /usr/lib/libc.a(putc.o): In function `_IO_putc': putc.o(.text+0x0): multiple definition of `_IO_putc' You can avoid using `libg++.a' by running `configure' like this: shell> CXX=gcc ./configure  File: manual.info, Node: linux-sparc, Next: linux-alpha, Prev: linux-x86, Up: linux 2.4.18.7 Linux SPARC Notes .......................... In some implementations, `readdir_r()' is broken. The symptom is that the `SHOW DATABASES' statement always returns an empty set. This can be fixed by removing `HAVE_READDIR_R' from `config.h' after configuring and before compiling.  File: manual.info, Node: linux-alpha, Next: linux-powerpc, Prev: linux-sparc, Up: linux 2.4.18.8 Linux Alpha Notes .......................... We have tested MySQL 5.0 on Alpha with our benchmarks and test suite, and it appears to work well. We currently build the MySQL binary packages on SuSE Linux 7.0 for AXP, kernel 2.4.4-SMP, Compaq C compiler (V6.2-505) and Compaq C++ compiler (V6.3-006) on a Compaq DS20 machine with an Alpha EV6 processor. You can find the preceding compilers at `http://www.support.compaq.com/alpha-tools/'. By using these compilers rather than `gcc', we get about 9-14% better MySQL performance. For MySQL on Alpha, we use the `-arch generic' flag to our compile options, which ensures that the binary runs on all Alpha processors. We also compile statically to avoid library problems. The `configure' command looks like this: CC=ccc CFLAGS="-fast -arch generic" CXX=cxx \ CXXFLAGS="-fast -arch generic -noexceptions -nortti" \ ./configure --prefix=/usr/local/mysql --disable-shared \ --with-extra-charsets=complex --enable-thread-safe-client \ --with-mysqld-ldflags=-non_shared --with-client-ldflags=-non_shared If you want to use `egcs', the following `configure' line worked for us: CFLAGS="-O3 -fomit-frame-pointer" CXX=gcc \ CXXFLAGS="-O3 -fomit-frame-pointer -felide-constructors \ -fno-exceptions -fno-rtti" \ ./configure --prefix=/usr/local/mysql --disable-shared Some known problems when running MySQL on Linux-Alpha: * Debugging threaded applications like MySQL does not work with `gdb 4.18'. You should use `gdb' 5.1 instead. * If you try linking `mysqld' statically when using `gcc', the resulting image dumps core at startup time. In other words, _do not_ use `--with-mysqld-ldflags=-all-static' with `gcc'.  File: manual.info, Node: linux-powerpc, Next: linux-mips, Prev: linux-alpha, Up: linux 2.4.18.9 Linux PowerPC Notes ............................ MySQL should work on MkLinux with the newest `glibc' package (tested with `glibc' 2.0.7).  File: manual.info, Node: linux-mips, Next: linux-ia-64, Prev: linux-powerpc, Up: linux 2.4.18.10 Linux MIPS Notes .......................... To get MySQL to work on Qube2 (Linux Mips), you need the newest `glibc' libraries. `glibc-2.0.7-29C2' is known to work. You must also use the `egcs' C++ compiler (`egcs' 1.0.2-9, `gcc' 2.95.2 or newer).  File: manual.info, Node: linux-ia-64, Next: selinux, Prev: linux-mips, Up: linux 2.4.18.11 Linux IA-64 Notes ........................... To get MySQL to compile on Linux IA-64, we use the following `configure' command for building with `gcc' 2.96: CC=gcc \ CFLAGS="-O3 -fno-omit-frame-pointer" \ CXX=gcc \ CXXFLAGS="-O3 -fno-omit-frame-pointer -felide-constructors \ -fno-exceptions -fno-rtti" \ ./configure --prefix=/usr/local/mysql \ "--with-comment=Official MySQL binary" \ --with-extra-charsets=complex On IA-64, the MySQL client binaries use shared libraries. This means that if you install our binary distribution at a location other than `/usr/local/mysql', you need to add the path of the directory where you have `libmysqlclient.so' installed either to the `/etc/ld.so.conf' file or to the value of your `LD_LIBRARY_PATH' environment variable. See *Note link-errors::.  File: manual.info, Node: selinux, Prev: linux-ia-64, Up: linux 2.4.18.12 SELinux Notes ....................... RHEL4 comes with SELinux, which supports tighter access control for processes. If SELinux is enabled (`SELINUX' in `/etc/selinux/config' is set to `enforcing', `SELINUXTYPE' is set to either `targeted' or `strict'), you might encounter problems installing MySQL AB RPM packages. Red Hat has an update that solves this. It involves an update of the `security policy' specification to handle the install structure of the RPMs provided by MySQL AB. For further information, see `https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=167551' and `http://rhn.redhat.com/errata/RHBA-2006-0049.html'.  File: manual.info, Node: mac-os-x, Next: solaris, Prev: linux, Up: operating-system-specific-notes 2.4.18.13 Mac OS X Notes ........................ * Menu: * mac-os-x-10-x:: Mac OS X 10.x (Darwin) * mac-os-x-server:: Mac OS X Server 1.2 (Rhapsody) On Mac OS X, `tar' cannot handle long filenames. If you need to unpack a `.tar.gz' distribution, use `gnutar' instead.  File: manual.info, Node: mac-os-x-10-x, Next: mac-os-x-server, Prev: mac-os-x, Up: mac-os-x 2.4.18.14 Mac OS X 10.x (Darwin) ................................ MySQL should work without major problems on Mac OS X 10.x (Darwin). Known issues: * If you have problems with performance under heavy load, try using the `--skip-thread-priority' option to `mysqld'. This runs all threads with the same priority. On Mac OS X, this gives better performance, at least until Apple fixes its thread scheduler. * The connection times (`wait_timeout', `interactive_timeout' and `net_read_timeout') values are not honored. This is probably a signal handling problem in the thread library where the signal doesn't break a pending read and we hope that a future update to the thread libraries will fix this. Our binary for Mac OS X is compiled on Darwin 6.3 with the following `configure' line: CC=gcc CFLAGS="-O3 -fno-omit-frame-pointer" CXX=gcc \ CXXFLAGS="-O3 -fno-omit-frame-pointer -felide-constructors \ -fno-exceptions -fno-rtti" \ ./configure --prefix=/usr/local/mysql \ --with-extra-charsets=complex --enable-thread-safe-client \ --enable-local-infile --disable-shared See *Note mac-os-x-installation::.  File: manual.info, Node: mac-os-x-server, Prev: mac-os-x-10-x, Up: mac-os-x 2.4.18.15 Mac OS X Server 1.2 (Rhapsody) ........................................ For current versions of Mac OS X Server, no operating system changes are necessary before compiling MySQL. Compiling for the Server platform is the same as for the client version of Mac OS X. For older versions (Mac OS X Server 1.2, a.k.a. Rhapsody), you must first install a pthread package before trying to configure MySQL. See *Note mac-os-x-installation::.  File: manual.info, Node: solaris, Next: bsd-notes, Prev: mac-os-x, Up: operating-system-specific-notes 2.4.18.16 Solaris Notes ....................... * Menu: * solaris-2-7:: Solaris 2.7/2.8 Notes * solaris-x86:: Solaris x86 Notes For information about installing MySQL on Solaris using PKG distributions, see *Note solaris-installation::. On Solaris, you may run into trouble even before you get the MySQL distribution unpacked, as the Solaris `tar' cannot handle long filenames. This means that you may see errors when you try to unpack MySQL. If this occurs, you must use GNU `tar' (`gtar') to unpack the distribution. You can find a precompiled copy for Solaris at `http://dev.mysql.com/downloads/os-solaris.html'. Sun native threads work only on Solaris 2.5 and higher. For Solaris 2.4 and earlier, MySQL automatically uses MIT-pthreads. See *Note mit-pthreads::. If you get the following error from `configure', it means that you have something wrong with your compiler installation: checking for restartable system calls... configure: error can not run test programs while cross compiling In this case, you should upgrade your compiler to a newer version. You may also be able to solve this problem by inserting the following row into the `config.cache' file: ac_cv_sys_restartable_syscalls=${ac_cv_sys_restartable_syscalls='no'} If you are using Solaris on a SPARC, the recommended compiler is `gcc' 2.95.2 or 3.2. You can find this at `http://gcc.gnu.org/'. Note that `egcs' 1.1.1 and `gcc' 2.8.1 do not work reliably on SPARC. The recommended `configure' line when using `gcc' 2.95.2 is: CC=gcc CFLAGS="-O3" \ CXX=gcc CXXFLAGS="-O3 -felide-constructors -fno-exceptions -fno-rtti" \ ./configure --prefix=/usr/local/mysql --with-low-memory \ --enable-assembler If you have an UltraSPARC system, you can get 4% better performance by adding `-mcpu=v8 -Wa,-xarch=v8plusa' to the `CFLAGS' and `CXXFLAGS' environment variables. If you have Sun's Forte 5.0 (or newer) compiler, you can run `configure' like this: CC=cc CFLAGS="-Xa -fast -native -xstrconst -mt" \ CXX=CC CXXFLAGS="-noex -mt" \ ./configure --prefix=/usr/local/mysql --enable-assembler To create a 64-bit binary with Sun's Forte compiler, use the following configuration options: CC=cc CFLAGS="-Xa -fast -native -xstrconst -mt -xarch=v9" \ CXX=CC CXXFLAGS="-noex -mt -xarch=v9" ASFLAGS="-xarch=v9" \ ./configure --prefix=/usr/local/mysql --enable-assembler To create a 64-bit Solaris binary using `gcc', add `-m64' to `CFLAGS' and `CXXFLAGS' and remove `--enable-assembler' from the `configure' line. In the MySQL benchmarks, we obtained a 4% speed increase on UltraSPARC when using Forte 5.0 in 32-bit mode, as compared to using `gcc' 3.2 with the `-mcpu' flag. If you create a 64-bit `mysqld' binary, it is 4% slower than the 32-bit binary, but can handle more threads and memory. When using Solaris 10 for x86_64, you should mount any filesystems on which you intend to store `InnoDB' files with the `forcedirectio' option. (By default mounting is done without this option.) Failing to do so will cause a significant drop in performance when using the `InnoDB' storage engine on this platform. If you get a problem with `fdatasync' or `sched_yield', you can fix this by adding `LIBS=-lrt' to the `configure' line For compilers older than WorkShop 5.3, you might have to edit the `configure' script. Change this line: #if !defined(__STDC__) || __STDC__ != 1 To this: #if !defined(__STDC__) If you turn on `__STDC__' with the `-Xc' option, the Sun compiler can't compile with the Solaris `pthread.h' header file. This is a Sun bug (broken compiler or broken include file). If `mysqld' issues the following error message when you run it, you have tried to compile MySQL with the Sun compiler without enabling the `-mt' multi-thread option: libc internal error: _rmutex_unlock: rmutex not held Add `-mt' to `CFLAGS' and `CXXFLAGS' and recompile. If you are using the SFW version of `gcc' (which comes with Solaris 8), you must add `/opt/sfw/lib' to the environment variable `LD_LIBRARY_PATH' before running `configure'. If you are using the `gcc' available from `sunfreeware.com', you may have many problems. To avoid this, you should recompile `gcc' and GNU `binutils' on the machine where you are running them. If you get the following error when compiling MySQL with `gcc', it means that your `gcc' is not configured for your version of Solaris: shell> gcc -O3 -g -O2 -DDBUG_OFF -o thr_alarm ... ./thr_alarm.c: In function `signal_hand': ./thr_alarm.c:556: too many arguments to function `sigwait' The proper thing to do in this case is to get the newest version of `gcc' and compile it with your current `gcc' compiler. At least for Solaris 2.5, almost all binary versions of `gcc' have old, unusable include files that break all programs that use threads, and possibly other programs as well. Solaris does not provide static versions of all system libraries (`libpthreads' and `libdl'), so you cannot compile MySQL with `--static'. If you try to do so, you get one of the following errors: ld: fatal: library -ldl: not found undefined reference to `dlopen' cannot find -lrt If you link your own MySQL client programs, you may see the following error at runtime: ld.so.1: fatal: libmysqlclient.so.#: open failed: No such file or directory This problem can be avoided by one of the following methods: * Link clients with the `-Wl,r/full/path/to/libmysqlclient.so' flag rather than with `-Lpath'). * Copy `libmysqclient.so' to `/usr/lib'. * Add the pathname of the directory where `libmysqlclient.so' is located to the `LD_RUN_PATH' environment variable before running your client. If you have problems with `configure' trying to link with `-lz' when you don't have `zlib' installed, you have two options: * If you want to be able to use the compressed communication protocol, you need to get and install `zlib' from `ftp.gnu.org'. * Run `configure' with the `--with-named-z-libs=no' option when building MySQL. If you are using `gcc' and have problems with loading user-defined functions (UDFs) into MySQL, try adding `-lgcc' to the link line for the UDF. If you would like MySQL to start automatically, you can copy `support-files/mysql.server' to `/etc/init.d' and create a symbolic link to it named `/etc/rc3.d/S99mysql.server'. If too many processes try to connect very rapidly to `mysqld', you should see this error in the MySQL log: Error in accept: Protocol error You might try starting the server with the `--back_log=50' option as a workaround for this. (Use `-O back_log=50' before MySQL 4.) Solaris doesn't support core files for `setuid()' applications, so you can't get a core file from `mysqld' if you are using the `--user' option.  File: manual.info, Node: solaris-2-7, Next: solaris-x86, Prev: solaris, Up: solaris 2.4.18.17 Solaris 2.7/2.8 Notes ............................... Normally, you can use a Solaris 2.6 binary on Solaris 2.7 and 2.8. Most of the Solaris 2.6 issues also apply for Solaris 2.7 and 2.8. MySQL should be able to detect new versions of Solaris automatically and enable workarounds for the following problems. Solaris 2.7 / 2.8 has some bugs in the include files. You may see the following error when you use `gcc': /usr/include/widec.h:42: warning: `getwc' redefined /usr/include/wchar.h:326: warning: this is the location of the previous definition If this occurs, you can fix the problem by copying `/usr/include/widec.h' to `.../lib/gcc-lib/os/gcc-version/include' and changing line 41 from this: #if !defined(lint) && !defined(__lint) To this: #if !defined(lint) && !defined(__lint) && !defined(getwc) Alternatively, you can edit `/usr/include/widec.h' directly. Either way, after you make the fix, you should remove `config.cache' and run `configure' again. If you get the following errors when you run `make', it's because `configure' didn't detect the `curses.h' file (probably because of the error in `/usr/include/widec.h'): In file included from mysql.cc:50: /usr/include/term.h:1060: syntax error before `,' /usr/include/term.h:1081: syntax error before `;' The solution to this problem is to do one of the following: * Configure with `CFLAGS=-DHAVE_CURSES_H CXXFLAGS=-DHAVE_CURSES_H ./configure'. * Edit `/usr/include/widec.h' as indicated in the preceding discussion and re-run `configure'. * Remove the `#define HAVE_TERM' line from the `config.h' file and run `make' again. If your linker cannot find `-lz' when linking client programs, the problem is probably that your `libz.so' file is installed in `/usr/local/lib'. You can fix this problem by one of the following methods: * Add `/usr/local/lib' to `LD_LIBRARY_PATH'. * Add a link to `libz.so' from `/lib'. * If you are using Solaris 8, you can install the optional `zlib' from your Solaris 8 CD distribution. * Run `configure' with the `--with-named-z-libs=no' option when building MySQL.  File: manual.info, Node: solaris-x86, Prev: solaris-2-7, Up: solaris 2.4.18.18 Solaris x86 Notes ........................... On Solaris 8 on x86, `mysqld' dumps core if you remove the debug symbols using `strip'. If you are using `gcc' or `egcs' on Solaris x86 and you experience problems with core dumps under load, you should use the following `configure' command: CC=gcc CFLAGS="-O3 -fomit-frame-pointer -DHAVE_CURSES_H" \ CXX=gcc \ CXXFLAGS="-O3 -fomit-frame-pointer -felide-constructors \ -fno-exceptions -fno-rtti -DHAVE_CURSES_H" \ ./configure --prefix=/usr/local/mysql This avoids problems with the `libstdc++' library and with C++ exceptions. If this doesn't help, you should compile a debug version and run it with a trace file or under `gdb'. See MySQL Internals: Porting (http://forge.mysql.com/wiki/MySQL_Internals_Porting).  File: manual.info, Node: bsd-notes, Next: other-unix-notes, Prev: solaris, Up: operating-system-specific-notes 2.4.18.19 BSD Notes ................... * Menu: * freebsd:: FreeBSD Notes * netbsd:: NetBSD Notes * openbsd:: OpenBSD 2.5 Notes * bsdi:: BSD/OS Version 2.x Notes * bsdi3:: BSD/OS Version 3.x Notes * bsdi4:: BSD/OS Version 4.x Notes This section provides information about using MySQL on variants of BSD Unix.  File: manual.info, Node: freebsd, Next: netbsd, Prev: bsd-notes, Up: bsd-notes 2.4.18.20 FreeBSD Notes ....................... FreeBSD 4.x or newer is recommended for running MySQL, because the thread package is much more integrated. To get a secure and stable system, you should use only FreeBSD kernels that are marked `-RELEASE'. The easiest (and preferred) way to install MySQL is to use the `mysql-server' and `mysql-client' ports available at `http://www.freebsd.org/'. Using these ports gives you the following benefits: * A working MySQL with all optimizations enabled that are known to work on your version of FreeBSD. * Automatic configuration and build. * Startup scripts installed in `/usr/local/etc/rc.d'. * The ability to use `pkg_info -L' to see which files are installed. * The ability to use `pkg_delete' to remove MySQL if you no longer want it on your machine. It is recommended you use MIT-pthreads on FreeBSD 2.x, and native threads on FreeBSD 3 and up. It is possible to run with native threads on some late 2.2.x versions, but you may encounter problems shutting down `mysqld'. Unfortunately, certain function calls on FreeBSD are not yet fully thread-safe. Most notably, this includes the `gethostbyname()' function, which is used by MySQL to convert hostnames into IP addresses. Under certain circumstances, the `mysqld' process suddenly causes 100% CPU load and is unresponsive. If you encounter this problem, try to start MySQL using the `--skip-name-resolve' option. Alternatively, you can link MySQL on FreeBSD 4.x against the LinuxThreads library, which avoids a few of the problems that the native FreeBSD thread implementation has. For a very good comparison of LinuxThreads versus native threads, see Jeremy Zawodny's article `FreeBSD or Linux for your MySQL Server?' at `http://jeremy.zawodny.com/blog/archives/000697.html'. Known problem when using LinuxThreads on FreeBSD is: * The connection times (`wait_timeout', `interactive_timeout' and `net_read_timeout') values are not honored. The symptom is that persistent connections can hang for a very long time without getting closed down and that a 'kill' for a thread will not take affect until the thread does it a new command This is probably a signal handling problem in the thread library where the signal doesn't break a pending read. This is supposed to be fixed in FreeBSD 5.0 The MySQL build process requires GNU make (`gmake') to work. If GNU `make' is not available, you must install it first before compiling MySQL. The recommended way to compile and install MySQL on FreeBSD with `gcc' (2.95.2 and up) is: CC=gcc CFLAGS="-O2 -fno-strength-reduce" \ CXX=gcc CXXFLAGS="-O2 -fno-rtti -fno-exceptions \ -felide-constructors -fno-strength-reduce" \ ./configure --prefix=/usr/local/mysql --enable-assembler gmake gmake install cd /usr/local/mysql bin/mysql_install_db --user=mysql bin/mysqld_safe & If you notice that `configure' uses MIT-pthreads, you should read the MIT-pthreads notes. See *Note mit-pthreads::. If you get an error from `make install' that it can't find `/usr/include/pthreads', `configure' didn't detect that you need MIT-pthreads. To fix this problem, remove `config.cache', and then re-run `configure' with the `--with-mit-threads' option. Be sure that your name resolver setup is correct. Otherwise, you may experience resolver delays or failures when connecting to `mysqld'. Also make sure that the `localhost' entry in the `/etc/hosts' file is correct. The file should start with a line similar to this: 127.0.0.1 localhost localhost.your.domain FreeBSD is known to have a very low default file handle limit. See *Note not-enough-file-handles::. Start the server by using the `--open-files-limit' option for `mysqld_safe', or raise the limits for the `mysqld' user in `/etc/login.conf' and rebuild it with `cap_mkdb /etc/login.conf'. Also be sure that you set the appropriate class for this user in the password file if you are not using the default (use `chpass mysqld-user-name'). See *Note mysqld-safe::. FreeBSD limits the size of a process to 512MB, even if you have much more RAM available on the system. So you may get an error such as this: Out of memory (Needed 16391 bytes) In current versions of FreeBSD (at least 4.x and greater), you may increase this limit by adding the following entries to the `/boot/loader.conf' file and rebooting the machine (these are not settings that can be changed at run time with the `sysctl' command): kern.maxdsiz="1073741824" # 1GB kern.dfldsiz="1073741824" # 1GB kern.maxssiz="134217728" # 128MB For older versions of FreeBSD, you must recompile your kernel to change the maximum data segment size for a process. In this case, you should look at the `MAXDSIZ' option in the `LINT' config file for more information. If you get problems with the current date in MySQL, setting the `TZ' variable should help. See *Note environment-variables::.  File: manual.info, Node: netbsd, Next: openbsd, Prev: freebsd, Up: bsd-notes 2.4.18.21 NetBSD Notes ...................... To compile on NetBSD, you need GNU `make'. Otherwise, the build process fails when `make' tries to run `lint' on C++ files.  File: manual.info, Node: openbsd, Next: bsdi, Prev: netbsd, Up: bsd-notes 2.4.18.22 OpenBSD 2.5 Notes ........................... On OpenBSD 2.5, you can compile MySQL with native threads with the following options: CFLAGS=-pthread CXXFLAGS=-pthread ./configure --with-mit-threads=no  File: manual.info, Node: bsdi, Next: bsdi3, Prev: openbsd, Up: bsd-notes 2.4.18.23 BSD/OS Version 2.x Notes .................................. If you get the following error when compiling MySQL, your `ulimit' value for virtual memory is too low: item_func.h: In method `Item_func_ge::Item_func_ge(const Item_func_ge &)': item_func.h:28: virtual memory exhausted make[2]: *** [item_func.o] Error 1 Try using `ulimit -v 80000' and run `make' again. If this doesn't work and you are using `bash', try switching to `csh' or `sh'; some BSDI users have reported problems with `bash' and `ulimit'. If you are using `gcc', you may also use have to use the `--with-low-memory' flag for `configure' to be able to compile `sql_yacc.cc'. If you get problems with the current date in MySQL, setting the `TZ' variable should help. See *Note environment-variables::.  File: manual.info, Node: bsdi3, Next: bsdi4, Prev: bsdi, Up: bsd-notes 2.4.18.24 BSD/OS Version 3.x Notes .................................. Upgrade to BSD/OS 3.1. If that is not possible, install BSDIpatch M300-038. Use the following command when configuring MySQL: env CXX=shlicc++ CC=shlicc2 \ ./configure \ --prefix=/usr/local/mysql \ --localstatedir=/var/mysql \ --without-perl \ --with-unix-socket-path=/var/mysql/mysql.sock The following is also known to work: env CC=gcc CXX=gcc CXXFLAGS=-O3 \ ./configure \ --prefix=/usr/local/mysql \ --with-unix-socket-path=/var/mysql/mysql.sock You can change the directory locations if you wish, or just use the defaults by not specifying any locations. If you have problems with performance under heavy load, try using the `--skip-thread-priority' option to `mysqld'. This runs all threads with the same priority. On BSDI 3.1, this gives better performance, at least until BSDI fixes its thread scheduler. If you get the error `virtual memory exhausted' while compiling, you should try using `ulimit -v 80000' and running `make' again. If this doesn't work and you are using `bash', try switching to `csh' or `sh'; some BSDI users have reported problems with `bash' and `ulimit'.  File: manual.info, Node: bsdi4, Prev: bsdi3, Up: bsd-notes 2.4.18.25 BSD/OS Version 4.x Notes .................................. BSDI 4.x has some thread-related bugs. If you want to use MySQL on this, you should install all thread-related patches. At least M400-023 should be installed. On some BSDI 4.x systems, you may get problems with shared libraries. The symptom is that you can't execute any client programs, for example, `mysqladmin'. In this case, you need to reconfigure not to use shared libraries with the `--disable-shared' option to configure. Some customers have had problems on BSDI 4.0.1 that the `mysqld' binary after a while can't open tables. This occurs because some library/system-related bug causes `mysqld' to change current directory without having asked for that to happen. The fix is to either upgrade MySQL to at least version 3.23.34 or, after running `configure', remove the line `#define HAVE_REALPATH' from `config.h' before running `make'. Note that this means that you can't symbolically link a database directories to another database directory or symbolic link a table to another database on BSDI. (Making a symbolic link to another disk is okay).  File: manual.info, Node: other-unix-notes, Next: os-2, Prev: bsd-notes, Up: operating-system-specific-notes 2.4.18.26 Other Unix Notes .......................... * Menu: * hp-ux-10-20:: HP-UX Version 10.20 Notes * hp-ux-11-x:: HP-UX Version 11.x Notes * ibm-aix:: IBM-AIX notes * sunos:: SunOS 4 Notes * alpha-dec-unix:: Alpha-DEC-UNIX Notes (Tru64) * alpha-dec-osf1:: Alpha-DEC-OSF/1 Notes * sgi-irix:: SGI Irix Notes * sco:: SCO UNIX and OpenServer 5.0.x Notes * sco-openserver:: SCO OpenServer 6.0.x Notes * sco-unixware:: SCO UnixWare 7.1.x and OpenUNIX 8.0.0 Notes  File: manual.info, Node: hp-ux-10-20, Next: hp-ux-11-x, Prev: other-unix-notes, Up: other-unix-notes 2.4.18.27 HP-UX Version 10.20 Notes ................................... This section does not apply to MySQL Enterprise Server users. There are a couple of small problems when compiling MySQL on HP-UX. We recommend that you use `gcc' instead of the HP-UX native compiler, because `gcc' produces better code. We recommend using `gcc' 2.95 on HP-UX. Don't use high optimization flags (such as `-O6') because they may not be safe on HP-UX. The following `configure' line should work with `gcc' 2.95: CFLAGS="-I/opt/dce/include -fpic" \ CXXFLAGS="-I/opt/dce/include -felide-constructors -fno-exceptions \ -fno-rtti" \ CXX=gcc \ ./configure --with-pthread \ --with-named-thread-libs='-ldce' \ --prefix=/usr/local/mysql --disable-shared The following `configure' line should work with `gcc' 3.1: CFLAGS="-DHPUX -I/opt/dce/include -O3 -fPIC" CXX=gcc \ CXXFLAGS="-DHPUX -I/opt/dce/include -felide-constructors \ -fno-exceptions -fno-rtti -O3 -fPIC" \ ./configure --prefix=/usr/local/mysql \ --with-extra-charsets=complex --enable-thread-safe-client \ --enable-local-infile --with-pthread \ --with-named-thread-libs=-ldce --with-lib-ccflags=-fPIC --disable-shared  File: manual.info, Node: hp-ux-11-x, Next: ibm-aix, Prev: hp-ux-10-20, Up: other-unix-notes 2.4.18.28 HP-UX Version 11.x Notes .................................. Because of some critical bugs in the standard HP-UX libraries, you should install the following patches before trying to run MySQL on HP-UX 11.0: PHKL_22840 Streams cumulative PHNE_22397 ARPA cumulative This solves the problem of getting `EWOULDBLOCK' from `recv()' and `EBADF' from `accept()' in threaded applications. If you are using `gcc' 2.95.1 on an unpatched HP-UX 11.x system, you may get the following error: In file included from /usr/include/unistd.h:11, from ../include/global.h:125, from mysql_priv.h:15, from item.cc:19: /usr/include/sys/unistd.h:184: declaration of C function ... /usr/include/sys/pthread.h:440: previous declaration ... In file included from item.h:306, from mysql_priv.h:158, from item.cc:19: The problem is that HP-UX does not define `pthreads_atfork()' consistently. It has conflicting prototypes in `/usr/include/sys/unistd.h':184 and `/usr/include/sys/pthread.h':440. One solution is to copy `/usr/include/sys/unistd.h' into `mysql/include' and edit `unistd.h' and change it to match the definition in `pthread.h'. Look for this line: extern int pthread_atfork(void (*prepare)(), void (*parent)(), void (*child)()); Change it to look like this: extern int pthread_atfork(void (*prepare)(void), void (*parent)(void), void (*child)(void)); After making the change, the following `configure' line should work: CFLAGS="-fomit-frame-pointer -O3 -fpic" CXX=gcc \ CXXFLAGS="-felide-constructors -fno-exceptions -fno-rtti -O3" \ ./configure --prefix=/usr/local/mysql --disable-shared If you are using HP-UX compiler, you can use the following command (which has been tested with `cc' B.11.11.04): CC=cc CXX=aCC CFLAGS=+DD64 CXXFLAGS=+DD64 ./configure \ --with-extra-character-set=complex You can ignore any errors of the following type: aCC: warning 901: unknown option: `-3': use +help for online documentation If you get the following error from `configure', verify that you don't have the path to the K&R compiler before the path to the HP-UX C and C++ compiler: checking for cc option to accept ANSI C... no configure: error: MySQL requires an ANSI C compiler (and a C++ compiler). Try gcc. See the Installation chapter in the Reference Manual. Another reason for not being able to compile is that you didn't define the `+DD64' flags as just described. Another possibility for HP-UX 11 is to use the MySQL binaries provided at `http://dev.mysql.com/downloads/', which we have built and tested ourselves. We have also received reports that the HP-UX 10.20 binaries supplied by MySQL can be run successfully on HP-UX 11. If you encounter problems, you should be sure to check your HP-UX patch level.  File: manual.info, Node: ibm-aix, Next: sunos, Prev: hp-ux-11-x, Up: other-unix-notes 2.4.18.29 IBM-AIX notes ....................... Automatic detection of `xlC' is missing from Autoconf, so a number of variables need to be set before running `configure'. The following example uses the IBM compiler: export CC="xlc_r -ma -O3 -qstrict -qoptimize=3 -qmaxmem=8192 " export CXX="xlC_r -ma -O3 -qstrict -qoptimize=3 -qmaxmem=8192" export CFLAGS="-I /usr/local/include" export LDFLAGS="-L /usr/local/lib" export CPPFLAGS=$CFLAGS export CXXFLAGS=$CFLAGS ./configure --prefix=/usr/local \ --localstatedir=/var/mysql \ --sbindir='/usr/local/bin' \ --libexecdir='/usr/local/bin' \ --enable-thread-safe-client \ --enable-large-files The preceding options are used to compile the MySQL distribution that can be found at `http://www-frec.bull.com/'. If you change the `-O3' to `-O2' in the preceding `configure' line, you must also remove the `-qstrict' option. This is a limitation in the IBM C compiler. If you are using `gcc' or `egcs' to compile MySQL, you _must_ use the `-fno-exceptions' flag, because the exception handling in `gcc'/`egcs' is not thread-safe! (This is tested with `egcs' 1.1.) There are also some known problems with IBM's assembler that may cause it to generate bad code when used with `gcc'. We recommend the following `configure' line with `egcs' and `gcc' 2.95 on AIX: CC="gcc -pipe -mcpu=power -Wa,-many" \ CXX="gcc -pipe -mcpu=power -Wa,-many" \ CXXFLAGS="-felide-constructors -fno-exceptions -fno-rtti" \ ./configure --prefix=/usr/local/mysql --with-low-memory The `-Wa,-many' option is necessary for the compile to be successful. IBM is aware of this problem but is in no hurry to fix it because of the workaround that is available. We don't know if the `-fno-exceptions' is required with `gcc' 2.95, but because MySQL doesn't use exceptions and the option generates faster code, we recommend that you should always use it with `egcs' / `gcc'. If you get a problem with assembler code, try changing the `-mcpu=XXX' option to match your CPU. Typically `power2', `power', or `powerpc' may need to be used. Alternatively, you might need to use `604' or `604e'. We are not positive but suspect that `power' would likely be safe most of the time, even on a power2 machine. If you don't know what your CPU is, execute a `uname -m' command. It produces a string that looks like `000514676700', with a format of `xxyyyyyymmss' where `xx' and `ss' are always `00', `yyyyyy' is a unique system ID and `mm' is the ID of the CPU Planar. A chart of these values can be found at `http://www16.boulder.ibm.com/pseries/en_US/cmds/aixcmds5/uname.htm'. This gives you a machine type and a machine model you can use to determine what type of CPU you have. If you have problems with signals (MySQL dies unexpectedly under high load), you may have found an OS bug with threads and signals. In this case, you can tell MySQL not to use signals by configuring as follows: CFLAGS=-DDONT_USE_THR_ALARM CXX=gcc \ CXXFLAGS="-felide-constructors -fno-exceptions -fno-rtti \ -DDONT_USE_THR_ALARM" \ ./configure --prefix=/usr/local/mysql --with-debug \ --with-low-memory This doesn't affect the performance of MySQL, but has the side effect that you can't kill clients that are `sleeping' on a connection with `mysqladmin kill' or `mysqladmin shutdown'. Instead, the client dies when it issues its next command. On some versions of AIX, linking with `libbind.a' makes `getservbyname()' dump core. This is an AIX bug and should be reported to IBM. For AIX 4.2.1 and `gcc', you have to make the following changes. After configuring, edit `config.h' and `include/my_config.h' and change the line that says this: #define HAVE_SNPRINTF 1 to this: #undef HAVE_SNPRINTF And finally, in `mysqld.cc', you need to add a prototype for `initgroups()'. #ifdef _AIX41 extern "C" int initgroups(const char *,int); #endif If you need to allocate a lot of memory to the `mysqld' process, it's not enough to just use `ulimit -d unlimited'. You may also have to modify `mysqld_safe' to add a line something like this: export LDR_CNTRL='MAXDATA=0x80000000' You can find more information about using a lot of memory at `http://publib16.boulder.ibm.com/pseries/en_US/aixprggd/genprogc/lrg_prg_support.htm'. Users of AIX 4.3 should use `gmake' instead of the `make' utility included with AIX. As of AIX 4.1, the C compiler has been unbundled from AIX as a separate product. We recommend using `gcc' 3.3.2, which can be obtained here: `ftp://ftp.software.ibm.com/aix/freeSoftware/aixtoolbox/RPMS/ppc/gcc/' The steps for compiling MySQL on AIX with `gcc' 3.3.2 are similar to those for using `gcc' 2.95 (in particular, the need to edit `config.h' and `my_config.h' after running `configure'). However, before running `configure', you should also patch the `curses.h' file as follows: /opt/freeware/lib/gcc-lib/powerpc-ibm-aix5.2.0.0/3.3.2/include/curses.h.ORIG Mon Dec 26 02:17:28 2005 --- /opt/freeware/lib/gcc-lib/powerpc-ibm-aix5.2.0.0/3.3.2/include/curses.h Mon Dec 26 02:40:13 2005 *************** *** 2023,2029 **** #endif /* _AIX32_CURSES */ ! #if defined(__USE_FIXED_PROTOTYPES__) || defined(__cplusplus) || defined (__STRICT_ANSI__) extern int delwin (WINDOW *); extern int endwin (void); extern int getcurx (WINDOW *); --- 2023,2029 ---- #endif /* _AIX32_CURSES */ ! #if 0 && (defined(__USE_FIXED_PROTOTYPES__) || defined(__cplusplus) || defined (__STRICT_ANSI__)) extern int delwin (WINDOW *); extern int endwin (void); extern int getcurx (WINDOW *);  File: manual.info, Node: sunos, Next: alpha-dec-unix, Prev: ibm-aix, Up: other-unix-notes 2.4.18.30 SunOS 4 Notes ....................... This section does not apply to MySQL Enterprise Server users. On SunOS 4, MIT-pthreads is needed to compile MySQL. This in turn means you need GNU `make'. Some SunOS 4 systems have problems with dynamic libraries and `libtool'. You can use the following `configure' line to avoid this problem: ./configure --disable-shared --with-mysqld-ldflags=-all-static When compiling `readline', you may get warnings about duplicate defines. These can be ignored. When compiling `mysqld', there are some `implicit declaration of function' warnings. These can be ignored.  File: manual.info, Node: alpha-dec-unix, Next: alpha-dec-osf1, Prev: sunos, Up: other-unix-notes 2.4.18.31 Alpha-DEC-UNIX Notes (Tru64) ...................................... This section does not apply to MySQL Enterprise Server users. If you are using `egcs' 1.1.2 on Digital Unix, you should upgrade to `gcc' 2.95.2, because `egcs' on DEC has some serious bugs! When compiling threaded programs under Digital Unix, the documentation recommends using the `-pthread' option for `cc' and `cxx' and the `-lmach -lexc' libraries (in addition to `-lpthread'). You should run `configure' something like this: CC="cc -pthread" CXX="cxx -pthread -O" \ ./configure --with-named-thread-libs="-lpthread -lmach -lexc -lc" When compiling `mysqld', you may see a couple of warnings like this: mysqld.cc: In function void handle_connections()': mysqld.cc:626: passing long unsigned int *' as argument 3 of accept(int,sockadddr *, int *)' You can safely ignore these warnings. They occur because `configure' can detect only errors, not warnings. If you start the server directly from the command line, you may have problems with it dying when you log out. (When you log out, your outstanding processes receive a `SIGHUP' signal.) If so, try starting the server like this: nohup mysqld [OPTIONS] & `nohup' causes the command following it to ignore any `SIGHUP' signal sent from the terminal. Alternatively, start the server by running `mysqld_safe', which invokes `mysqld' using `nohup' for you. See *Note mysqld-safe::. If you get a problem when compiling `mysys/get_opt.c', just remove the `#define _NO_PROTO' line from the start of that file. If you are using Compaq's CC compiler, the following `configure' line should work: CC="cc -pthread" CFLAGS="-O4 -ansi_alias -ansi_args -fast -inline speed \ -speculate all -arch host" CXX="cxx -pthread" CXXFLAGS="-O4 -ansi_alias -ansi_args -fast -inline speed \ -speculate all -arch host -noexceptions -nortti" export CC CFLAGS CXX CXXFLAGS ./configure \ --prefix=/usr/local/mysql \ --with-low-memory \ --enable-large-files \ --enable-shared=yes \ --with-named-thread-libs="-lpthread -lmach -lexc -lc" gnumake If you get a problem with `libtool' when compiling with shared libraries as just shown, when linking `mysql', you should be able to get around this by issuing these commands: cd mysql /bin/sh ../libtool --mode=link cxx -pthread -O3 -DDBUG_OFF \ -O4 -ansi_alias -ansi_args -fast -inline speed \ -speculate all \ -arch host -DUNDEF_HAVE_GETHOSTBYNAME_R \ -o mysql mysql.o readline.o sql_string.o completion_hash.o \ ../readline/libreadline.a -lcurses \ ../libmysql/.libs/libmysqlclient.so -lm cd .. gnumake gnumake install scripts/mysql_install_db  File: manual.info, Node: alpha-dec-osf1, Next: sgi-irix, Prev: alpha-dec-unix, Up: other-unix-notes 2.4.18.32 Alpha-DEC-OSF/1 Notes ............................... This section does not apply to MySQL Enterprise Server users. If you have problems compiling and have DEC `CC' and `gcc' installed, try running `configure' like this: CC=cc CFLAGS=-O CXX=gcc CXXFLAGS=-O3 \ ./configure --prefix=/usr/local/mysql If you get problems with the `c_asm.h' file, you can create and use a 'dummy' `c_asm.h' file with: touch include/c_asm.h CC=gcc CFLAGS=-I./include \ CXX=gcc CXXFLAGS=-O3 \ ./configure --prefix=/usr/local/mysql Note that the following problems with the `ld' program can be fixed by downloading the latest DEC (Compaq) patch kit from: `http://ftp.support.compaq.com/public/unix/'. On OSF/1 V4.0D and compiler "DEC C V5.6-071 on Digital Unix V4.0 (Rev. 878)," the compiler had some strange behavior (undefined `asm' symbols). `/bin/ld' also appears to be broken (problems with `_exit undefined' errors occurring while linking `mysqld'). On this system, we have managed to compile MySQL with the following `configure' line, after replacing `/bin/ld' with the version from OSF 4.0C: CC=gcc CXX=gcc CXXFLAGS=-O3 ./configure --prefix=/usr/local/mysql With the Digital compiler "C++ V6.1-029," the following should work: CC=cc -pthread CFLAGS=-O4 -ansi_alias -ansi_args -fast -inline speed \ -speculate all -arch host CXX=cxx -pthread CXXFLAGS=-O4 -ansi_alias -ansi_args -fast -inline speed \ -speculate all -arch host -noexceptions -nortti export CC CFLAGS CXX CXXFLAGS ./configure --prefix=/usr/mysql/mysql \ --with-mysqld-ldflags=-all-static --disable-shared \ --with-named-thread-libs="-lmach -lexc -lc" In some versions of OSF/1, the `alloca()' function is broken. Fix this by removing the line in `config.h' that defines `'HAVE_ALLOCA''. The `alloca()' function also may have an incorrect prototype in `/usr/include/alloca.h'. This warning resulting from this can be ignored. `configure' uses the following thread libraries automatically: `--with-named-thread-libs="-lpthread -lmach -lexc -lc"'. When using `gcc', you can also try running `configure' like this: CFLAGS=-D_PTHREAD_USE_D4 CXX=gcc CXXFLAGS=-O3 ./configure ... If you have problems with signals (MySQL dies unexpectedly under high load), you may have found an OS bug with threads and signals. In this case, you can tell MySQL not to use signals by configuring with: CFLAGS=-DDONT_USE_THR_ALARM \ CXXFLAGS=-DDONT_USE_THR_ALARM \ ./configure ... This does not affect the performance of MySQL, but has the side effect that you can't kill clients that are `sleeping' on a connection with `mysqladmin kill' or `mysqladmin shutdown'. Instead, the client dies when it issues its next command. With `gcc' 2.95.2, you may encounter the following compile error: sql_acl.cc:1456: Internal compiler error in `scan_region', at except.c:2566 Please submit a full bug report. To fix this, you should change to the `sql' directory and do a cut-and-paste of the last `gcc' line, but change `-O3' to `-O0' (or add `-O0' immediately after `gcc' if you don't have any `-O' option on your compile line). After this is done, you can just change back to the top-level directory and run `make' again.  File: manual.info, Node: sgi-irix, Next: sco, Prev: alpha-dec-osf1, Up: other-unix-notes 2.4.18.33 SGI Irix Notes ........................ This section does not apply to MySQL Enterprise Server users. As of MySQL 5.0, we don't provide binaries for Irix any more. If you are using Irix 6.5.3 or newer, `mysqld' is able to create threads only if you run it as a user that has `CAP_SCHED_MGT' privileges (such as `root') or give the `mysqld' server this privilege with the following shell command: chcap "CAP_SCHED_MGT+epi" /opt/mysql/libexec/mysqld You may have to undefine some symbols in `config.h' after running `configure' and before compiling. In some Irix implementations, the `alloca()' function is broken. If the `mysqld' server dies on some `SELECT' statements, remove the lines from `config.h' that define `HAVE_ALLOC' and `HAVE_ALLOCA_H'. If `mysqladmin create' doesn't work, remove the line from `config.h' that defines `HAVE_READDIR_R'. You may have to remove the `HAVE_TERM_H' line as well. SGI recommends that you install all the patches on this page as a set: `http://support.sgi.com/surfzone/patches/patchset/6.2_indigo.rps.html' At the very minimum, you should install the latest kernel rollup, the latest `rld' rollup, and the latest `libc' rollup. You definitely need all the POSIX patches on this page, for pthreads support: `http://support.sgi.com/surfzone/patches/patchset/6.2_posix.rps.html' If you get the something like the following error when compiling `mysql.cc': "/usr/include/curses.h", line 82: error(1084): invalid combination of type Type the following in the top-level directory of your MySQL source tree: extra/replace bool curses_bool < /usr/include/curses.h > include/curses.h make There have also been reports of scheduling problems. If only one thread is running, performance is slow. Avoid this by starting another client. This may lead to a two-to-tenfold increase in execution speed thereafter for the other thread. This is a poorly understood problem with Irix threads; you may have to improvise to find solutions until this can be fixed. If you are compiling with `gcc', you can use the following `configure' command: CC=gcc CXX=gcc CXXFLAGS=-O3 \ ./configure --prefix=/usr/local/mysql --enable-thread-safe-client \ --with-named-thread-libs=-lpthread On Irix 6.5.11 with native Irix C and C++ compilers ver. 7.3.1.2, the following is reported to work CC=cc CXX=CC CFLAGS='-O3 -n32 -TARG:platform=IP22 -I/usr/local/include \ -L/usr/local/lib' CXXFLAGS='-O3 -n32 -TARG:platform=IP22 \ -I/usr/local/include -L/usr/local/lib' \ ./configure --prefix=/usr/local/mysql --with-innodb --with-berkeley-db \ --with-libwrap=/usr/local \ --with-named-curses-libs=/usr/local/lib/libncurses.a  File: manual.info, Node: sco, Next: sco-openserver, Prev: sgi-irix, Up: other-unix-notes 2.4.18.34 SCO UNIX and OpenServer 5.0.x Notes ............................................. The current port is tested only on `sco3.2v5.0.5', `sco3.2v5.0.6', and `sco3.2v5.0.7' systems. There has also been progress on a port to `sco3.2v4.2'. Open Server 5.0.8 (Legend) has native threads and allows files greater than 2GB. The current maximum file size is 2GB. We have been able to compile MySQL with the following `configure' command on OpenServer with `gcc' 2.95.3. CC=gcc CFLAGS="-D_FILE_OFFSET_BITS=64 -O3" \ CXX=gcc CXXFLAGS="-D_FILE_OFFSET_BITS=64 -O3" \ ./configure --prefix=/usr/local/mysql \ --enable-thread-safe-client --with-innodb \ --with-openssl --with-vio --with-extra-charsets=complex `gcc' is available at `ftp://ftp.sco.com/pub/openserver5/opensrc/gnutools-5.0.7Kj'. This development system requires the OpenServer Execution Environment Supplement oss646B on OpenServer 5.0.6 and oss656B and The OpenSource libraries found in gwxlibs. All OpenSource tools are in the `opensrc' directory. They are available at `ftp://ftp.sco.com/pub/openserver5/opensrc/'. We recommend using the latest production release of MySQL. SCO provides operating system patches at `ftp://ftp.sco.com/pub/openserver5' for OpenServer