MySQL Community Server 5.5.52 has been released

[Nawaz Nazeer ahamed]

Dear MySQL users,

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

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

Enjoy!


Changes in MySQL 5.5.52 (2016-09-06)

    Bugs Fixed

      * Replication: mysqlbinlog --read-from-remote-server log1
        log2 was opening a new connection for log2 without freeing the
        connection used for log1. Thanks to Laurynas Biveinis for the
        contribution. (Bug #81675, Bug #23540182)

      * For mysqld_safe, the argument to --malloc-lib now must be
        one of the directories /usr/lib, /usr/lib64,
        /usr/lib/i386-linux-gnu, or /usr/lib/x86_64-linux-gnu. In
        addition, the --mysqld and --mysqld-version options can be used
        only on the command line and not in an option file. (Bug
        #24464380)

      * It was possible to write log files ending with .ini or
        .cnf that later could be parsed as option files. The general
        query log and slow query log can no longer be written to a file
        ending with .ini or .cnf. (Bug #24388753)

      * Privilege escalation was possible by exploiting the way
        REPAIR TABLE used temporary files. (Bug #24388746)

      * Certain internal character-handling functions could fail
        to handle a too-large character and cause a server exit.  (Bug
        #23296299)

      * A blank server name in CREATE SERVER statements produced
        a server exit rather than an error. (Bug #23295288)

      * The optimizer failed to check a function return value for
        an area calculation, leading to a server exit. (Bug #23280059)

      * A prepared statement that used a parameter in the select
        list of a derived table that was part of a join could cause a
        server exit. (Bug #22392374, Bug #24380263)

      * MEDIUMINT columns used in operations with long integer
        values could result in buffer overflow. (Bug #19984392)

      * EINTR handling in the client library has been fixed so
        that interrupted read and write calls are retried.  Previously,
        EINTR was ignored. (Bug #82019, Bug #23703570)

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