MySQL Lists are EOL. Please join:

List:Announcements« Previous MessageNext Message »
From:Nawaz Date:July 29 2016 5:11pm
Subject:MySQL Community Server 5.5.51 has been released
View as plain text  
Dear MySQL users,

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

Enjoy!


Changes in MySQL 5.5.51 (2016-07-29)

    Bugs Fixed

      * Replication: When using statement-based or mixed binary
        logging format with --read-only=ON, it was not possible to modify
        temporary tables. (Bug #62008, Bug #12818255) References: See
        also: Bug #14294223, Bug #16561483.

      * MySQL Server upgrades performed using RPM packages failed
        when upgrading from MySQL 5.1 Community to MySQL 5.5 Community or
        MySQL 5.1 Commercial to MySQL 5.5 Commercial. (Bug #23736787)

      * A buffer overflow in the regex library was fixed. (Bug
        #23498283)

      * Certain arguments to NAME_CONST() could cause a server
        exit. (Bug #23279858)

      * Installing MySQL from a yum or zypper repository resulted
        in /var/log/mysqld.log being created with incorrect user and
        group permissions. (Bug #21879694, Bug #78512)

      * If a stored function updated a view for which the view
        table had a trigger defined that updated another table, it could
        fail and report an error that an existing table did not exist.
        (Bug #21142859, Bug #76808)

      * If an INSTALL PLUGIN statement contained invalid UTF-8
        characters in the shared library name, it caused the server to
        hang (or to raise an assertion in debug builds). (Bug #14653594,
        Bug #23080148)

      * For multibyte character sets, LOAD DATA could fail to
        allocate space correctly and ignore input rows as a result. (Bug
        #76237, Bug #20683959, Bug #23080148) References: This issue is a
        regression of: Bug #14653594.

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

Thread
MySQL Community Server 5.5.51 has been releasedNawaz29 Jul