MySQL Community Server 5.5.42 has been released

[Hery Ramilison]

Dear MySQL users,

MySQL Server 5.5.42 is a new version of the 5.5 production release
of the world's most popular open source database. MySQL 5.5.42 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 Heartbeat
   - 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://www.mysql.com/why-mysql/white-papers/whats-new-in-mysql-5-5/

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.42 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.42 is available in source and binary form for a
number of platforms from our download pages at:

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

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/relnotes/mysql/5.5/en/news-5-5-42.html

Enjoy!

Changes in MySQL 5.5.42 (2015-02-02)

    Functionality Added or Changed

      * Support for the SSL 2.0 and SSL 3.0 protocols has been
        disabled because they provide weak encryption. (Bug
        #19820550)

      * yaSSL was upgraded to version 2.3.7. (Bug #19695101, Bug
        #20201864)

      * The valid date range of the SSL certificates in
        mysql-test/std_data has been extended to the year 2029.
        (Bug #18366947)

    Bugs Fixed

      * InnoDB: A multiple-table delete operation caused the
        server to halt. (Bug #19815702)

      * Replication: If a DROP DATABASE statement failed on the
        master, mismatched tables could be left on the slave,
        breaking replication. This was caused by the DROP TABLE
        statement being binary logged if at least one table was
        deleted during the DROP DATABASE operation. The fix
        ensures that in such a situation the DROP TABLE statement
        is binary logged with the IF EXISTS option. (Bug #74890,
        Bug #20041860)

      * Unlocking a temporary table after locking and truncating
        it could cause a server exit. (Bug #19786309)

      * The Enterprise Encryption plugin could mishandle string
        arguments. (Bug #19688008)

      * FLUSH TABLES on a FEDERATED table failed if the table had
        been idle longer than the wait_timeout time plus the TCP
        keepalive time. (Bug #17599258)

      * Selecting all columns from INFORMATION_SCHEMA.TABLES did
        not reopen tables if they were in the table cache, but
        selecting a subset of those columns under the same
        conditions did reopen tables. (Bug #16869534)

      * MySQL failed to compile with GCC 4.9.1 in debug mode.
        (Bug #74710, Bug #19974500)

      * A file created for an internal temporary table could
        cause problems if the file was orphaned for some reason
        and the file name was reused for later queries. (Bug
        #32917, Bug #11747548)

On behalf of Oracle/MySQL RE Team
Hery Ramilison