MySQL Community Server 5.5.62 has been released

[Hery Ramilison]

Dear MySQL users,

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

This is the last update to be published for MySQL Server 5.5. To
continue receiving updates for this product, you will need to upgrade to
at least version 5.6.

Enjoy!

Changes in MySQL 5.5.62 (2018-10-22, General availability)

Functionality Added or Changed

      * Previously, file I/O performed in the I/O cache in the
        mysys library was not instrumented, affecting in
        particular file I/O statistics reported by the
        Performance Schema about the binary log index file. Now,
        this I/O is instrumented and Performance Schema
        statistics are accurate. Thanks to Yura Sorokin for the
        contribution. (Bug #27788907, Bug #90264)

      * The zlib library version bundled with MySQL was raised
        from version 1.2.3 to version 1.2.11. MySQL implements
        compression with the help of the zlib library.
        The zlib compressBound() function in zlib 1.2.11 returns
        a slightly higher estimate of the buffer size required to
        compress a given length of bytes than it did in zlib
        version 1.2.3. The compressBound() function is called by
        InnoDB functions that determine the maximum row size
        permitted when creating compressed InnoDB tables or
        inserting rows into compressed InnoDB tables. As a
        result, CREATE TABLE ... ROW_FORMAT=COMPRESSED or INSERT
        operations with row sizes very close to the maximum row
        size that were successful in earlier releases could now
        fail.


Bugs Fixed

      * MySQL Server and test RPM packages were missing
        perl-Data-Dumper as a dependency. (Bug #28144933, Bug
        #72926)

      * For the mysql client, the -b short option was associated
        with two long options, --no-beep and --binary-as-hex. The
        -b option now is associated only with --no-beep. (Bug
        #28093271)

      * During server startup/shutdown, PID files could be
        mishandled. (Bug #27919254)

      * For MEMORY tables, memory overflow errors could occur.
        (Bug #27799513)

      * When converting from a BLOB (or TEXT) type to a smaller
        BLOB (or TEXT) type, no warning or error was reported
        informing about the truncation or data loss. Now an
        appropriate error is issued in strict SQL mode and a
        warning in nonstrict SQL mode. (Bug #27788685, Bug
        #90266)

      * ALTER TABLE ... REORGANIZE PARTITION ... could result in
        incorrect behavior if any partition other than the last
        was missing the VALUES LESS THAN part of the syntax. (Bug
        #26791931)

On Behalf of the MySQL/Oracle Release Engineering Team,
Hery Ramilison