MySQL Community Server 5.5.44 has been released (no replies)

Dear MySQL users,

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

Enjoy!

Changes in MySQL 5.5.44 (2015-05-29)

   Bugs Fixed

     * InnoDB; Partitioning: The CREATE_TIME column of the
       INFORMATION_SCHEMA.TABLES table now shows the correct table
       creation time for partitioned InnoDB tables. The CREATE_TIME
       column of the INFORMATION_SCHEMA.PARTITIONS table now shows the
       correct partition creation time for a partition of partitioned
       InnoDB tables.  The UPDATE_TIME column of the
       INFORMATION_SCHEMA.TABLES table now shows when a partitioned
       InnoDB table was last updated by an INSERT, DELETE, or UPDATE.
       The UPDATE_TIME column of the INFORMATION_SCHEMA.PARTITIONS table
       now shows when a partition of a partitioned InnoDB table was last
       updated.  The CREATE_TIME column of the INFORMATION_SCHEMA.TABLES
       table now shows the correct table creation time for partitioned
       InnoDB tables. The CREATE_TIME column of the
       INFORMATION_SCHEMA.PARTITIONS table now shows the correct
       partition creation time for a partition of partitioned InnoDB
       tables. (Bug #69990, Bug #17299181)

     * InnoDB: An assertion was raised on shutdown due to XA
       PREPARE transactions holding explicit locks. (Bug #20816223)

     * InnoDB: Removal of a foreign key object from the data
       dictionary cache during error handling caused the server to exit.
       (Bug #20442523)

     * InnoDB: SHOW ENGINE INNODB STATUS output showed negative
       reservation and signal count values due to a counter overflow
       error. (Bug #20417397)

     * InnoDB: Estimates that were too low for the size of merge
       chunks in the result sorting algorithm caused a server exit. (Bug
       #20049521)

     * SHOW VARIABLES mutexes were being locked twice, resulting
       in a server exit. (Bug #20788853)

     * A Provides rule in RPM .spec files misspelled
       "mysql-embedded" as "mysql-emdedded". (Bug #20734434)

     * Under certain conditions, the libedit command-line
       library could write outside an array boundary and cause a client
       program crash. (Bug #20318154)

     * Host value matching for the grant tables could fail to
       use the most specific of values that contained wildcard
       characters. (Bug #20181776)

     * A user with a name of event_scheduler could view the
       Event Scheduler process list without the PROCESS privilege. (Bug
       #20007583, Bug #20754369)

     * SHOW GRANTS after connecting using a proxy user could
       display the password hash of the proxied user. (Bug #19817663)

     * 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)

     * Loading corrupt spatial data into a MyISAM table could
       cause the server to exit during index building. (Bug #19573096)

     * Certain queries for the INFORMATION_SCHEMA TABLES and
       COLUMNS tables could lead to excessive memory use when there were
       large numbers of empty InnoDB tables. (Bug #72322, Bug #18592390)

     * MySQL failed to compile using OpenSSL 0.9.8e. (Bug
       #68999, Bug #16861371)

On behalf of Oracle/MySQL RE Team
Balasubramanian Kandasamy