MySQL Reference Manual for version 4.0.18.

[ < ] [ > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

5.1.2 mysqld-max, An Extended mysqld Server

A MySQL-Max server is a version of the mysqld MySQL server that is configured to include additional features.

You can find the MySQL-Max binaries at http://www.mysql.com/downloads/mysql-max-4.0.html.

The MySQL binary distributions Windows include both the standard server (named mysqld.exe) and the MySQL-Max server (named mysqld-max.exe). http://www.mysql.com/downloads/mysql-4.0.html. See section 2.2.1 Installing MySQL on Windows.

If you install MySQL on Linux using RPM distributions, install the MySQL-server RPM first, and then the MySQL-Max RPM. The latter presupposes that you have already installed the regular server RPM. This process installs a standard server named mysqld and a MySQL-Max server named mysqld-max.

All other MySQL-Max distributions contain a single server that is named mysqld but that has the additional features.

MySQL-Max servers are built by using the following configure options:

Option Comment
--with-server-suffix=-max Add a -max suffix to the mysqld version string
--with-innodb Support for InnoDB tables (MySQL 3.23 only)
--with-bdb Support for Berkeley DB (BDB) tables
CFLAGS=-DUSE_SYMDIR Symbolic link support for Windows

MySQL-Max binary distributions are a convenience for those who wish to install precompiled programs. If you build MySQL using a source distribution, you can build your own Max-like server by enabling the same features at configuration time that the MySQL-Max binary distributions are built with.

MySQL-Max servers always include the InnoDB storage engine. The --with-innodb option for enabling InnoDB support is needed only in MySQL 3.23. (In MySQL 4 and up, InnoDB is included by default. so you do not need a MySQL-Max server to obtain InnoDB support.)

MySQL-Max servers include the BerkeleyDB (BDB) storage engine whenever possible, but not all platforms support BDB. The following table shows which platforms allow MySQL-Max binaries to include BDB:

System BDB
Windows/NT Y
AIX 4.3 N
HP-UX 11.0 N
Linux-Alpha N
Linux-Intel Y
Linux-IA-64 N
Solaris-Intel N
Solaris-SPARC Y
SCO OSR5 Y
UnixWare Y
Mac OS X N

As of Version 3.23, all MySQL servers support MyISAM tables, because MyISAM is the default storage engine. To find out which storage engines your server supports, issue the following statement:

 
mysql> SHOW VARIABLES LIKE "have_%";
+------------------+----------+
| Variable_name    | Value    |
+------------------+----------+
| have_bdb         | NO       |
| have_crypt       | YES      |
| have_innodb      | YES      |
| have_isam        | NO       |
| have_raid        | NO       |
| have_symlink     | DISABLED |
| have_openssl     | NO       |
| have_query_cache | YES      |
+------------------+----------+

The values in the second column indicate the server's level of support for each feature:

Value Meaning
YES The feature is supported and is active.
NO The feature is not supported.
DISABLED The feature is supported but has been disabled.

A value of NO means that the server was compiled without support for the feature, so it cannot be activated at runtime.

A value of DISABLED occurs either because the server was started with an option that disables the feature, or because not all options required to enable it were given. In the latter case, the hostname.err file should contain a reason indicating why the option is disabled.

One situation in which you might see DISABLED occurs with MySQL 3.23 when the InnoDB storage engine is compiled in. In MySQL 3.23, you must supply at least the innodb_data_file_path option at runtime to set up the InnoDB tablespace. Without the options, InnoDB disables itself. See section 14.4.2 InnoDB in MySQL Version 3.23. (You can specify configuration options for the BDB storage engine, too, but BDB will not disable itself without them. See section 14.5.3 BDB Startup Options.)

You may also see DISABLED for the InnoDB, BDB, or ISAM storage engines if the server was compiled to support them, but was started with the --skip-innodb, --skip-bdb, or --skip-isam options at runtime.


[ < ] [ > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

This document was generated by rdg (Feb 25 2004) using texi2html