MySQL Community Server 5.5.38 has been released

[Surya Narayana Murthy Narkedimilli]

Dear MySQL users,

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

Enjoy!

Changes in MySQL 5.5.38 (2014-05-31)

   Bugs Fixed

     * InnoDB: For each insert, memset would be called three times to
       allocate memory for system fields. To reduce CPU usage, the
       three memset calls are now combined into a single call. (Bug
       #17858679, Bug #71014)

     * Certain INFORMATION_SCHEMA queries could cause a server exit.
       (Bug #18319790)

     * For indexes on prefixes or character string columns, index
       corruption could occur for assignment of binary data to the
       column due to improper character counting. (Bug #18359924)

     * Solaris-specific scripts were included in and installed by
       non-Solaris packages. (Bug #18305641)

     * EXPLAIN on a query with an EXISTS subquery containing a UNION
       could cause a server exit. Multiple executions of a prepared
       EXPLAIN on a UNION of subqueries could cause a server exit.
       (Bug #18167356)

     * Executing a correlated subquery on an ARCHIVE table which has
       an AUTO_INCREMENT column caused the server to hang. (Bug
       #18065452)

     * Calling mysql_get_server_version() with an invalid connection
       handler argument caused the client to exit. Now it returns 0
       and reports a CR_COMMANDS_OUT_OF_SYNC error. (Bug #18053212)

     * On Windows, calling mysql_thread_init() call without
       mysql_init() caused the client to exit. windows. Now it
       returns a nonzero result because it is an error to call
       mysql_thread_init() before the client library is initialized
       with mysql_library_init(). (Bug #17514920)

     * CMake produced not-useful warnings about
       INTERFACE_LINK_LIBRARIES policy. (Bug #71089, Bug #17905155,
       Bug #17894997)

     * LOAD DATA LOCAL INFILE could use all CPU if import errors
       occurred when there were no line delimiters. (Bug #51840, Bug
       #11759519)

On behalf of Oracle/MySQL RE Team,
Murthy Narkedimilli