MySQL Lists are EOL. Please join:

List:Announcements« Previous MessageNext Message »
From:Timothy Smith Date:November 27 2008 7:33am
Subject:MySQL Server 5.1.30 has been released
View as plain text  
Dear MySQL users,

We are proud to present to you the MySQL Server 5.1.30 GA release, the
first 5.1 production version of the popular open source database.
MySQL 5.1.30 is recommended for use on production systems.

MySQL 5.1 provides a number of new enhancements including:

- Table and index partitioning
- Row-based and mixed replication
- Built-in job scheduler
- Improved XML handling with XPath support
- New SQL diagnostic aids and performance utilities
- The return of the embedded library (libmysqld)

For a more complete look at what's new in MySQL 5.1, please see

For information on installing MySQL 5.1.30 on new servers or upgrading
to MySQL 5.1.30 from previous MySQL releases, please see

MySQL Server is available in source and binary form for a number of
platforms from our download pages at

Not all mirror sites may be up to date at this point in time, so if
you can't find this version on some mirror, please try again later or
choose another download site.

We welcome and appreciate your feedback, bug reports, bug fixes,
patches, etc.:

For information on open issues in MySQL 5.1, please see the errata
list at

The following section lists the changes in the MySQL source code since
the previous released version of MySQL 5.1. It may also be viewed
online at


Kent Boortz
The MySQL build team at Sun Microsystems


Bugs fixed:

   * Partitioning: A SELECT using a range WHERE condition with an
     ORDER BY on a partitioned table caused a server crash.

   * Partitioning: Dropping or creating an index on a partitioned
     table managed by the InnoDB Plugin locked the table.

   * Replication: Row-based replication failed with non-partitioned
     MyISAM tables having no indexes.

   * With statement-based binary logging format and a transaction
     isolation level of READ COMMITTED or stricter, InnoDB printed
     an error because statement-based logging might lead to
     inconsistency between master and slave databases. However,
     this error was printed even when binary logging was not
     enabled (in which case, no such inconsistency can occur).

   * The CHECK TABLE ... FOR UPGRADE statement did not check for
     incompatible collation changes made in MySQL 5.1.24. (This
     also affects mysqlcheck and mysql_upgrade, which cause that
     statement to be executed.)
     Prior to this fix, a binary upgrade (performed without dumping
     tables with mysqldump before the upgrade and reloading the
     dump file after the upgrade) would corrupt tables. After the
     fix, CHECK TABLE ... FOR UPGRADE properly detects the problem
     and upgrades tables.
     However, the fix is not backward compatible and can result in
     a downgrading problem under these circumstances:

       1. Perform a binary upgrade to a version of MySQL that
          includes the fix.

       2. Run CHECK TABLE ... FOR UPGRADE (or mysqlcheck or
          mysql_upgrade) to upgrade tables.

       3. Perform a binary downgrade to a version of MySQL that
          does not include the fix.

     The solution is to dump tables with mysqldump before the
     downgrade and reload the dump file after the downgrade.
     Alternatively, drop and recreate affected indexes.

   * Some recent releases for Solaris 10 were built on Solaris 10
     U5, which included a new version of that does not
     work on U4 or earlier. To correct this, Solaris 10 builds now
     are created on machines that do not have that upgraded, so that they will work on Solaris 10 installations
     both with and without the upgraded

   * XA transaction rollbacks could result in corrupted transaction
     states and a server crash.

   * ALTER TABLE for an ENUM column could change column values.

MySQL Server 5.1.30 has been releasedTimothy Smith27 Nov