MySQL Community Server 5.5.59 has been released

Dear MySQL users,

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

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

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/>http://mysql.com/products/enterprise/

For information on installing MySQL 5.5.59 on new servers, please see
the MySQL installation documentation at

http://dev.mysql.com/doc/refman/5.5/en/installing.html
<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.59 is available in source and binary form for a
number of platforms from our download pages at:

http://dev.mysql.com/downloads/mysql/
<http://dev.mysql.com/downloads/mysql/>
The following link 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-59.html

Enjoy!

Changes in MySQL 5.5.59 (2018-01-15, General availability)


      * Configuration Notes

      * Test Suite Notes

      * Bugs Fixed

    Configuration Notes

      * For RHEL, SLES, and Fedora RPMs, the default plugin
        directory for debug builds has been changed from
        /usr/lib64/mysql/plugin to /usr/lib64/mysql/plugin/debug.  (Bug
        #27072155, Bug #88363)

    Test Suite Notes

      * Documentation for the MySQL Test Suite is now maintained
        in the MySQL source tree using Doxygen (see
http://dev.mysql.com/doc/dev/mysql-server/latest/PAGE_MYSQL_TEST_RUN.html 
<https://dev.mysql.com/doc/dev/mysql-server/latest/PAGE_MYSQL_TEST_RUN.html>).
        The related Unix man pages that previously were
        produced from the old test suite manual are no longer updated and
        have gone out of date. Consequently, they are no longer included
        in MySQL distributions. (Bug #27021754)

    Bugs Fixed

      * InnoDB: While innodb_undo_log_truncate was enabled,
        warnings that should only appear in a debug version of MySQL were
        printed to the error log when the length of the history list
        exceeded 2000000. (Bug #24296076, Bug #82213)

      * Packaging: Initialization of the MySQL Server Docker
        container failed with the message "hostname: command not found"
        when the server was being initialized. That was due to a missing
        library in the Docker image. (Bug #26747305)

      * Partitioning: Queries involving NULL were not always
        handled correctly on tables that were partitioned by LIST. (Bug
        #76418, Bug #20748521) References: See also: Bug #86255, Bug
        #26034430.

      * Microsoft Windows: On Windows, with the myisam_use_mmap
        and flush system variables enabled, MyISAM did not always flush
        table files properly. (Bug #26880757)

      * VALUES() was not handled correctly in some cases. (Bug
        #26881946) References: See also: Bug #19601973, Bug #17458914.

      * Incorrect results or a server exit could result when
        SHA2() was passed a user-defined variable in some character sets.
        (Bug #26704451)

      * Creating a table with excessive index information could
        cause a server exit. (Bug #26529369)

      * Setting the MYSQL_GROUP_SUFFIX environment variable had
        no effect. (Bug #23072792)

      * A circular dependency problem involving
        sql/sql_builtin.cc was resolved. (Bug #16877045)

      * A prepared statement containing an ORDER BY list that
        referred to a parameter was not always handled correctly.  (Bug
        #87863, Bug #26867652)


On Behalf of MySQL/Oracle Release Engineering Team,
Surabhi Bhat