MySQL Community Server 5.1.54 has been released

[sunanda menon]

Dear MySQL users,

MySQL Community Server 5.1.54, a new version of the popular Open
Source Database Management System, has been released. MySQL 5.1.54
is recommended for use on production systems.

For an overview of what's new in MySQL 5.1, please see

http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html

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

http://dev.mysql.com/doc/refman/5.1/en/installing.html

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

http://dev.mysql.com/downloads/

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.:

http://forge.mysql.com/wiki/Contributing

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

http://dev.mysql.com/doc/refman/5.1/en/open-bugs.html

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

http://dev.mysql.com/doc/refman/5.1/en/news-5-1-54.html

Enjoy!

=======================================================================

D.1.1. Changes in MySQL 5.1.54 (26 November 2010)

   Functionality added or changed:

     * Support for the IBMDB2I storage engine has been removed.
       (Bug#58079: http://bugs.mysql.com/bug.php?id=58079)

     * The pstack library was nonfunctional and has been removed,
       along with the --with-pstack option for configure. The
       --enable-pstack option for mysqld is deprecated and will be
       removed in MySQL 5.5.
       (Bug#57210: http://bugs.mysql.com/bug.php?id=57210)

   Bugs fixed:

     * Performance: InnoDB Storage Engine: Improved concurrency when
       several ANALYZE TABLE or SHOW TABLE STATUS statements are run
       simultaneously for InnoDB tables.
       (Bug#53046: http://bugs.mysql.com/bug.php?id=53046)

     * InnoDB Storage Engine: For an InnoDB table created with
       ROW_FORMAT=COMPRESSED or ROW_FORMAT=DYNAMIC, a query using the
       READ UNCOMMITTED isolation level could cause the server to
       stop with an assertion error, if BLOB or other large columns
       that use off-page storage were being inserted at the same
       time. (Bug#57799: http://bugs.mysql.com/bug.php?id=57799)

     * InnoDB Storage Engine: An existing InnoDB could be switched to
       ROW_FORMAT=COMPRESSED implicitly by a KEY_BLOCK_SIZE clause in
       an ALTER TABLE statement. Now, the row format is only switched
       to compressed if there is an explicit ROW_FORMAT=COMPRESSED
       clause. on the ALTER TABLE statement.
       Any valid, non-default ROW_FORMAT parameter takes precedence
       over KEY_BLOCK_SIZE when both are specified. KEY_BLOCK_SIZE
       only enables ROW_FORMAT=COMPRESSED if ROW_FORMAT is not
       specified on either the CREATE TABLE or ALTER TABLE statement,
       or is specified as DEFAULT. In case of a conflict between
       KEY_BLOCK_SIZE and ROW_FORMAT clauses, the KEY_BLOCK_SIZE is
       ignored if innodb_strict_mode is off, and the statement causes
       an error if innodb_strict_mode is on.
       (Bug#56632: http://bugs.mysql.com/bug.php?id=56632)

     * InnoDB Storage Engine: The clause KEY_BLOCK_SIZE=0 is now
       allowed on CREATE TABLE and ALTER TABLE statements for InnoDB
       tables, regardless of the setting of innodb_strict_mode. The
       zero value has the effect of resetting the KEY_BLOCK_SIZE
       table parameter to its default value, depending on the
       ROW_FORMAT parameter, as if it had not been specified. That
       default is 8 if ROW_FORMAT=COMPRESSED. Otherwise,
       KEY_BLOCK_SIZE is not used or stored with the table
       parameters.
       As a consequence of this fix, ROW_FORMAT=FIXED is not allowed
       when the innodb_strict_mode is enabled.
       (Bug#56628: http://bugs.mysql.com/bug.php?id=56628)

     * InnoDB Storage Engine: InnoDB startup messages now include the
       start and end times for buffer pool initialization, and the
       total buffer pool size.
       (Bug#48026: http://bugs.mysql.com/bug.php?id=48026)

     * Partitioning: An INSERT ... ON DUPLICATE KEY UPDATE column = 0
       statement on an AUTO_INCREMENT column caused the debug server
       to crash. (Bug#57890: http://bugs.mysql.com/bug.php?id=57890)

     * Several compilation problems were fixed.
       (Bug#57992: http://bugs.mysql.com/bug.php?id=57992,
       Bug#57993: http://bugs.mysql.com/bug.php?id=57993,
       Bug#57994: http://bugs.mysql.com/bug.php?id=57994,
       Bug#57995: http://bugs.mysql.com/bug.php?id=57995,
       Bug#57996: http://bugs.mysql.com/bug.php?id=57996,
       Bug#57997: http://bugs.mysql.com/bug.php?id=57997,
       Bug#58057: http://bugs.mysql.com/bug.php?id=58057)

     * Passing a string that was not null-terminated to UpdateXML()
       or ExtractValue() caused the server to fail with an assertion.
       (Bug#57279: http://bugs.mysql.com/bug.php?id=57279)

     * Queries executed using the Index Merge access method and a
       temporary file could return incorrect results.
       (Bug#56862: http://bugs.mysql.com/bug.php?id=56862)

     * Valgrind warnings about overlapping memory when
       double-assigning the same variable were corrected.
       (Bug#56138: http://bugs.mysql.com/bug.php?id=56138)

     * An error in a stored procedure could leave the session in a
       different default database.
       (Bug#54375: http://bugs.mysql.com/bug.php?id=54375)

     * Grouping by a TIME_TO_SEC() function result could cause a
       server crash or incorrect results. Grouping by a function
       returning a BLOB could cause an unexpected "Duplicate entry"
       error and incorrect result.
       (Bug#52160: http://bugs.mysql.com/bug.php?id=52160)

     * The find_files() function used by SHOW statements performed
       redundant and unnecessary memory allocation.
       (Bug#51208: http://bugs.mysql.com/bug.php?id=51208)
 
     * The Windows sample option files contained values more
       appropriate for Linux.
       (Bug#50021: http://bugs.mysql.com/bug.php?id=50021)

     * A failed RENAME TABLE operation could prevent a FLUSH TABLES
       WITH READ LOCK from completing.
       (Bug#47924: http://bugs.mysql.com/bug.php?id=47924)
 
Thanks, 
On behalf of MySQL RE Team,

Sunanda Menon
MySQL Release Engineer
Database Group, Oracle.