MySQL Community Server 5.5.24 has been released

[Joerg Bruehe]

Dear MySQL users,


MySQL 5.5.24 is a new version of the 5.5 production release of the
world's most popular open source database. MySQL 5.5.24 is recommended
for use on production systems.

MySQL 5.5 includes several high-impact enhancements to improve the
performance and scalability of the MySQL Database, taking advantage of
the latest multi-CPU and multi-core hardware and operating systems. In
addition, with release 5.5, InnoDB is now the default storage engine for
the MySQL Database, delivering ACID transactions, referential integrity
and crash recovery by default.

MySQL 5.5 also provides a number of additional enhancements including:

- Significantly improved performance on Windows, with various
Windows specific features and improvements
- Higher availability, with new semi-synchronous replication and
Replication Heart Beat
- Improved usability, with Improved index and table partitioning,
SIGNAL/RESIGNAL support and enhanced diagnostics, including a new
Performance Schema monitoring capability.

For a more complete look at what's new in MySQL 5.5, please see the
following resources:

MySQL 5.5 is GA, Interview with Tomas Ulin:
http://dev.mysql.com/tech-resources/interviews/thomas-ulin-mysql-55.html

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

Whitepaper: What's New in MySQL 5.5:
http://dev.mysql.com/why-mysql/white-papers/mysql-wp-whatsnew-mysql-55.php

If you are running a MySQL production level system, we would like to
direct your attention to MySQL Enterprise Edition, which includes the
most comprehensive set of MySQL production, backup, monitoring,
modeling, development, and administration tools so businesses can
achieve the highest levels of MySQL performance, security and uptime.
http://mysql.com/products/enterprise/

For information on installing MySQL 5.5.24 on new servers, please see
the MySQL installation documentation at
http://dev.mysql.com/doc/refman/5.5/en/installing.html

For upgrading from previous MySQL releases, please see the important
upgrade considerations at:
http://dev.mysql.com/doc/refman/5.5/en/upgrading.html

MySQL Database 5.5.24 is available in source and binary form for a
number of platforms from our download pages at:
http://dev.mysql.com/downloads/mysql/

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

The following section lists the changes in the MySQL source code since
the previous released version of MySQL 5.5. It may also be viewed
online at:
http://dev.mysql.com/doc/refman/5.5/en/news-5-5-24.html

Enjoy!

On behalf of the MySQL Build Team,
Joerg Bruehe


Changes in MySQL 5.5.24 (2012-May-7)

Functionality Added or Changed

* Important Change: Replication: INSERT ON DUPLICATE KEY UPDATE
is now marked as unsafe for statement-based replication if the
target table has more than one primary or unique key. For more
information, see Section 16.1.2.3, "Determination of Safe and
Unsafe Statements in Binary Logging."

Bugs Fixed

* Security Fix: Bug #64884 was fixed.

* InnoDB: Replication: When binary log statements were replayed
on the slave, the Com_insert, Com_update, and Com_delete
counters were incremented by BEGIN statements initiating
transactions affecting InnoDB tables but not by COMMIT
statements ending such transactions. This affected these
statements whether they were replicated or they were run using
mysqlbinlog. (Bug #12662190)

* If the --bind-address option was given a host name value and
the host name resolved to more than one IP address, the server
failed to start. For example, with --bind-address=localhost,
if localhost resolved to both 127.0.0.1 and ::1, startup
failed. Now the server prefers the IPv4 address in such cases.
(Bug #61713, Bug #12762885)

* mysql_store_result() and mysql_use_result() are not for use
with prepared statements and are not intended to be called
following mysql_stmt_execute(), but failed to return an error
when invoked that way in libmysqld. (Bug #62136, Bug
#13738989)
References: See also Bug #47485.

* On Windows, mysqlslap crashed for attempts to connect using
shared memory. (Bug #31173, Bug #11747181, Bug #59107, Bug
#11766072)