MySQL Community Server 5.5.13 has been released

[hery ramilison]

Dear MySQL users,

MySQL 5.5.13 is a new version of the 5.5 production release of the
world's most popular open source database. MySQL 5.5.13 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 Heart Beat
   - 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://dev.mysql.com/why-mysql/white-papers/mysql-wp-whatsnew-mysql-55.php

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.13 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 is available in source and binary form for a number
of platforms from our download pages at:

   http://dev.mysql.com/downloads/mysql/

Not all mirror sites may be up to date at this point in time, so if you
can't find this version on some mirror, please try again later or choose
another download site.

We welcome and appreciate your feedback, bug reports, bug fixes,
patches, etc.:

   http://forge.mysql.com/wiki/Contributing

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/refman/5.5/en/news-5-5-13.html

Enjoy!

Changes in MySQL 5.5.13 :

   Note:

   Very old (MySQL 4.0) clients are not working temporarily due to a
   problem discovered after the release of MySQL 5.5.12. We are
   looking at fixing the problem.

   Bugs fixed:

     * InnoDB Storage Engine: If the server crashed while an XA
       transaction was prepared but not yet committed, the
       transaction could remain in the system after restart, and
       cause a subsequent shutdown to hang. (Bug #11766513, Bug
       #59641)

     * InnoDB Storage Engine: Similar problem to the foreign key
       error in bug #11831040 / 60196 / 60909, but with a different
       root cause and occurring on Mac OS X. With the setting
       lower_case_table_names=2, inserts into InnoDB tables covered
       by foreign key constraints could fail after a server restart.

     * Partitioning: The internal get_partition_set() function did
       not take into account the possibility that a key specification
       could be NULL in some cases. (Bug #12380149)

     * Partitioning: When executing a row-ordered retrieval index
       merge, the partitioning handler used memory from that
       allocated for the table, rather than that allocated to the
       query, causing table object memory not to be freed until the
       table was closed. (Bug #11766249, Bug #59316)

     * Replication: A spurious error malformed binlog: it does not
       contain any Format_description_log_event... was generated when
       mysqlbinlog was invoked using --base64-output=decode-row and
       --start-position=pos, where pos is a point in the binary log
       past the format description log event. However, there is
       nothing unsafe about not printing the format description log
       event, so the error has been removed for this case. (Bug
       #12354268)

     * Replication: Typographical errors appeared in the text of
       several replication error messages. (The word "position" was
       misspelled as "postion".) (Bug #11762616, Bug #55229)

     * Assignments to NEW.var_name within triggers, where var_name
       had a BLOB or TEXT type, were not properly handled and
       produced incorrect results. (Bug #12362125)

     * XA COMMIT could fail to clean up the error state if it
       discovered that the current XA transaction had to be rolled
       back. Consequently, the next XA transaction could raise an
       assertion when it checked for proper cleanup of the previous
       transaction. (Bug #12352846)

     * An internal client macro reference was removed from the
       client_plugin.h header file. This reference made the file
       unusable. (Bug #60746, Bug #12325444)

     * The server consumed memory for repeated invocation of some
       stored procedures, which was not released until the connection
       terminated. (Bug #60025, Bug #11848763)

     * The server did not check for certain invalid out of order
       sequences of XA statements, and these sequences raised an
       assertion. (Bug #59936, Bug #11766752, Bug #12348348)

     * With the conversion from GNU autotools to CMake for
       configuring MySQL, the USE_SYMDIR preprocessor symbol was
       omitted. This caused failure of symbolic links (described at
       Section 7.11.3.1, "Using Symbolic Links"). (Bug #59408, Bug
       #11766320)

     * The incorrect max_length value for YEAR values could be used
       in temporary result tables for UNION, leading to incorrect
       results. (Bug #59343, Bug #11766270)

     * In Item_func_in::fix_length_and_dec(), a Valgrind warning for
       uninitialized values was corrected. (Bug #59270, Bug
       #11766212)

     * In ROUND() calculations, a Valgrind warning for uninitialized
       memory was corrected. (Bug #58937, Bug #11765923)

     * Valgrind warnings caused by comparing index values to an
       uninitialized field were corrected. (Bug #58705, Bug
       #11765713)

     * LOAD DATA INFILE errors could leak I/O cache memory. (Bug
       #58072, Bug #11765141)

     * For LOAD DATA INFILE, multibyte character sequences could be
       pushed onto a stack too small to accommodate them. (Bug
       #58069, Bug #11765139)

     * Internal Performance Schema header files were unnecessarily
       installed publicly. (Bug #53281)

     * On Linux, the mysql client built using the bundled libedit did
       not read ~/.editrc. (Bug #49967, Bug #11757855)

     * The optimizer sometimes incorrectly processed HAVING clauses
       for queries that did not also have an ORDER BY clause. (Bug
       #48916, Bug #11756928)

     * PROCEDURE ANALYZE() could leak memory for NULL results, and
       could return incorrect results if used with a LIMIT clause.
       (Bug #48137, Bug #11756242)

     * With DISTINCT CONCAT(col,...) returned incorrect results when
       the arguments to CONCAT() were columns with an integer data
       type declared with a display width narrower than the values in
       the column. (For example, if an INT(1) column contain 1111.)
       (Bug #4082)

Hery Ramilison
MySQL/ORACLE Release Engineering Team