( mysqld-max

Info Catalog ( Server-Side Overview ( Server-Side Scripts ( mysqld_safe
 5.1.2 The `mysqld-max' Extended MySQL Server
 A MySQL-Max server is a version of the `mysqld' MySQL server that has
 been built to include additional features.
 The distribution to use depends on your platform:
    * For Windows, MySQL binary distributions include both the standard
      server (`mysqld.exe') and the MySQL-Max server (`mysqld-max.exe'),
      so you need not get a special distribution. Just use a regular
      Windows distribution, available at
      `'.   Windows installation.
    * For Linux, if you install MySQL using RPM distributions, use the
      regular `MySQL-server' RPM first to install a standard server named
      `mysqld'.  Then use the `MySQL-Max' RPM to install a server named
      `mysqld-max'.  The `MySQL-Max' RPM presupposes that you have
      installed the regular server RPM.  See  Linux-RPM for more
      information on the Linux RPM packages.
    * All other MySQL-Max distributions contain a single server that is
      named `mysqld' but that has the additional features included.
 You can find the MySQL-Max binaries on the MySQL AB Web site at
 MySQL AB builds the MySQL-Max servers by using the following
 `configure' options:
      This option adds a `-max' suffix to the `mysqld' version string.
      This option enables support for the `InnoDB' storage engine.
      MySQL-Max servers always include `InnoDB' support, but this option
      actually is needed only for MySQL 3.23.  From MySQL 4 on, `InnoDB'
      is included by default in binary distributions, so you do not need
      a MySQL-Max server to obtain `InnoDB' support.
      This option enables support for the Berkeley DB (`BDB') storage
      This define is enabled to turn on database  symbolic link support
      for Windows.  (This applies only before MySQL 4.0. As of MySQL
      4.0, symbolic link support is available for all Windows servers,
      so a Max server is not needed to take advantage of this feature.)
 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 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'
 AIX 4.3        N
 HP-UX 11.0     N
 Linux-Alpha    N
 Linux-IA-64    N
 Linux-Intel    Y
 Mac OS X       N
 NetWare        N
 SCO OSR5       Y
 Solaris-Intel  N
 Solaris-SPARC  Y
 UnixWare       Y
 Windows/NT     Y
 To find out which storage engines your server supports, issue the
 following statement:
      mysql> SHOW ENGINES;
 Before MySQL 4.1.2, `SHOW ENGINES' is unavailable. Use the following
 statement instead and check the value of the variable for the storage
 engine in which you are interested:
      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
 `HOST_NAME.err' error log 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 this option, `InnoDB' disables
 itself.   `InnoDB' in MySQL 3.23 InnoDB in MySQL 3.23.  You can
 specify configuration options for the `BDB' storage engine, too, but
 `BDB' will not disable itself if you do not provide them.   `BDB'
 start BDB start.
 You might 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.
 As of Version 3.23, all MySQL servers support `MyISAM' tables, because
 `MyISAM' is the default storage engine.
Info Catalog ( Server-Side Overview ( Server-Side Scripts ( mysqld_safe
automatically generated byinfo2html