MySQL Lists are EOL. Please join:

List:Announcements« Previous MessageNext Message »
From:Hery Ramilison Date:April 7 2015 10:44am
Subject:MySQL Community Server 5.5.43 has been released
View as plain text  
Dear MySQL users,

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

Whitepaper: What's New in MySQL 5.5:

   http://www.mysql.com/why-mysql/white-papers/whats-new-in-mysql-5-5/

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

Enjoy!

Changes in MySQL 5.5.43 (2015-04-06)

    Functionality Added or Changed

      * CMake support was updated to handle CMake version 3.1.
        (Bug #20344207)

      * The server now includes its version number when it writes
        the initial "starting" message to the error log, to make
        it easier to tell which server instance error log output
        applies to. This value is the same as that available from
        the version system variable. (Bug #74917, Bug #20052694)

    Bugs Fixed

      * Replication: When using a slave configured to use a
        special character set such as UTF-16, UTF-32, or UCS-2,
        the receiver (I/O) thread failed to connect. The fix
        ensures that in such a situation, if a slave's character
        set is not supported then default to using the latin1
        character set. (Bug #19855907)

      * Ordering by a GROUP_CONCAT() result could cause a server
        exit. (Bug #19880368, Bug #20730220)

      * A malformed mysql.proc table row could result in a server
        exit for DROP DATABASE of the database associated with
        the proc row. (Bug #19875331)

      * For a prepared statement with an ORDER BY that refers by
        column number to a GROUP_CONCAT() expression that has an
        outer reference, repeated statement execution could cause
        a server exit. (Bug #19814337)

      * Large values of the transaction_prealloc_size system
        variable could cause the server to allocate excessive
        amounts of memory. The maximum value has been adjusted
        down to 128K. A similar change was made for
        transaction_alloc_block_size. Transactions can still
        allocate more than 128K if necessary; this change reduces
        the amount that can be preallocated, as well as the
        maximum size of the incremental allocation blocks. (Bug
        #19770858, Bug #20730053)

      * A server exit could occur for queries that compared two
        rows using the <=> operator and the rows belonged to
        different character sets. (Bug #19699237, Bug #20730155)

      * Certain InnoDB errors caused stored function and trigger
        condition handlers to be ignored. (Bug #19683834, Bug
        #20094067)

      * The optimizer could raise an assertion due to incorrectly
        associating an incorrect field with a temporary table.
        (Bug #19612819, Bug #20730129)

      * The server could exit due to an optimizer failure to
        allocate enough memory for resolving outer references.
        (Bug #18782905, Bug #19892803)

      * Starting the server with start service or mysqld_safe
        could result in failure to use the correct plugin
        directory. (Bug #17619241)

      * Creating a FEDERATED table with an AUTO_INCREMENT column
        using a LIKE clause results in a server exit. (Bug
        #12671631)

On behalf of Oracle/MySQL RE Team
Hery Ramilison
Thread
MySQL Community Server 5.5.43 has been releasedHery Ramilison7 Apr