MySQL Community Server 5.5.49 has been released

Dear MySQL users,

MySQL Server 5.5.49 is a new version of the 5.5 production release of
the world's most popular open source database. MySQL 5.5.49 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. 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

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.49 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.49 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-49.html

Enjoy!

Changes in MySQL 5.5.49 (2016-04-11)


    Security Notes

      * MySQL client programs now support an --ssl-mode option
        that enables you to specify the security state of the connection
        to the server. The default value is DISABLED (establish an
        unencrypted connection).  --ssl-mode=REQUIRED) can be specified
        to require a secure connection, or fail if a secure connection
        cannot be obtained.  These clients support --ssl-mode: mysql,
        mysqladmin, mysqlcheck, mysqldump, mysqlimport, mysqlshow,
        mysqlpump, mysqlslap, mysqltest, mysql_upgrade.  For more
        information, see Command Options for Secure Connections
        (http://dev.mysql.com/doc/refman/5.5/en/secure-connection 
<http://dev.mysql.com/doc/refman/5.5/en/secure-connection-options.html>
        -options.html 
<http://dev.mysql.com/doc/refman/5.5/en/secure-connection-options.html>).

    Bugs Fixed

      * InnoDB: Running REPLACE operations on multiple
        connections resulted in a hang. (Bug #22530768, Bug #79185)

      * MySQL did not build with GCC 5. (Bug #22680706)

      * The System-V initialization script for RHEL6 or older
        failed to enable the mysqld service by default. (Bug #22600974)

      * Improper host name checking in X509 certificates could
        permit man-in-the-middle attacks. (Bug #22295186, Bug #22738607)

      * A boolean mode full-text search caused a segmentation
        fault. (Bug #22176795)

      * Concurrent selecting and flushing of a FEDERATED table
        while killing connections accessing it could result in a server
        exit. (Bug #21918190)

      * Executing GRANT PROXY statements after altering the
        definition of the mysql.user system table could result in a
        server exit. (Bug #21699037)

      * Certain error messages included part of the SQL statement
        that produced them, possibly exposing data. (Bug #21682356)

      * Character set conversion operations on NULL parameters to
        prepared statements could cause a server exit. (Bug #18823979)

      * For INSERT and UPDATE operations that caused FOREIGN KEY
        constraint violations, errors were reported rather than warnings
        when the IGNORE keyword was used. (Bug #78853, Bug #22037930)

      * Processlist state information was not updated correctly
        for LOAD DATA INFILE and could show a state different from
        executing. (Bug #69375, Bug #16912362)

On behalf of Oracle MySQL Release Engineering Team,
Nawaz Nazeer Ahamed