MySQL Community Server 5.5.60 has been released (no replies)

Dear MySQL users,

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

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

Enjoy!

==============================================================================
Changes in MySQL 5.5.60 (2018-04-19, General availability)


     * Functionality Added or Changed

     * Bugs Fixed

Functionality Added or Changed


     * If the server PID file is configured to be created in a
       world-writable location, the server now issues a warning
       suggesting use of a more secure location. (Bug #26585560)

Bugs Fixed


     * InnoDB: A REPLACE operation on a temporary table raised
       an assertion. (Bug #27225649)

     * Replication: A number of changes were made to the binary
       log decoding procedure to improve handling of invalid or
       corrupted binary log entries. (Bug #24365972)

     * Adding a unique index to an InnoDB table on which
       multiple locks were held could raise an assertion. (Bug
       #27216817)

     * For some statements, the FILE privilege was not properly
       checked. (Bug #27160888)

     * Dropping an index from a system table could cause a
       server exit. (Bug #26881798)

     * A server exit could result from simultaneous attempts by
       multiple threads to register and deregister metadata Performance
       Schema objects. (Bug #26502135)

     * The thread pool plugin logged too much information for
       failed connections. (Bug #26368725, Bug #86863)

     * MySQL client programs could exit unexpectedly if
       malformed client/server protocol packets were received.  (Bug
       #25471090)


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