MySQL Community Server 5.5.41 has been released (no replies)

Dear MySQL users,

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

Enjoy!

Changes in MySQL 5.5.41 (2014-11-28)

   Compilation Notes

     * CMake workarounds for older Mac OS X and XCode versions
       were removed. On Mac OS X, compilation always uses Clang,
       even for 32-bit builds.
       Compilation on Mac OS X is now supported for Mac OS 10.8
       and up, using XCode 5 and up. Compilation on older
       versions may work but is unsupported. (Bug #18510941)

     * Previously, the MYSQL_MAINTAINER_MODE CMake option was
       turned on by default for debug builds and off for release
       builds, and MYSQL_MAINTAINER_MODE caused -Werror to be
       enabled when building with GCC. This made it cumbersome
       to enable -Werror under certain conditions, such as when
       compiling with Clang.
       Now, MYSQL_MAINTAINER_MODE is on by default when
       compiling debug builds with GCC, and
       MYSQL_MAINTAINER_MODE enbles -Werror regardless of
       whether GCC or Clang is used. Enabling -Werror with Clang
       can be done simply by explicitly setting
       -DMYSQL_MAINTAINER_MODE=1 when running CMake. In
       addition, some compilation warnings reported by Clang 3.4
       were fixed, making it possible to build the default debug
       build with -Werror. (Bug #18313717)

     * Build support was modified to produce the same warnings
       for Clang as for gcc. (Bug #17959689)

     * CMake configuration for the Clang compiler sets more
       appropriate flags for building on Linux. Specifically, -g
       -fno-omit-frame-pointer -fno-strict-aliasing is now
       added. (Bug #17633291)

   Functionality Added or Changed

     * The new -DWITH_UBSAN=ON CMake option enables the
       Undefined Behavior Sanitizer. This feature is supported
       by GCC 4.9 and up, and Clang 3.4 and up. (Bug #19587393)

   Bugs Fixed

     * InnoDB: An ALTER TABLE operation raised an assertion.
       When a foreign key object was removed from the dictionary
       cache, an incorrect foreign key object was removed from
       the rb-tree. (Bug #19908343)
       References: This bug is a regression of Bug #18806829.

     * InnoDB: In debug builds, setting the
       innodb_limit_optimistic_insert_debug debug configuration
       option to 1 would cause an infinite B-tree page split.
       (Bug #19904003, Bug #74605)

     * InnoDB: The dict_set_corrupted() function would attempt
       to update the clustered index of the SYS_INDEXES data
       dictionary table incorrectly. (Bug #19584379)

     * InnoDB: A procedure, which was called from a function to
       perform an operation on a temporary table, caused the
       server to halt. (Bug #19306524)

     * InnoDB: A CREATE TABLE operation that failed with
       innodb_strict_mode=ON would succeed without printing a
       warning with innodb_strict_mode=OFF. (Bug #17852083)

     * Replication: When using a MySQL version that had been
       compiled with the WITH_DEBUG option enabled, using
       expire_logs_days to purge binary logs caused a restart to
       crash the server. This problem arose after the fix for
       Bug #17283409. The fix ensures that current_thd is
       checked before calling DEBUG_SYNC(). (Bug #19553099)

     * Replication: A kernel mutex contention was being caused
       because mysqlbinlog was calling localtime() for every
       event read, which in turn called stat(/etc/localtime).
       This fix ensures that mysqlbinlog uses localtime_r(),
       which is optimized to store the read only timezone
       internal structure. This also means that mysqlbinlog now
       establishes the time zone at the beginning of processing
       and you can not change it during processing. This is the
       same behavior as MySQL server. (Bug #72701, Bug
       #18808072)

     * Replication: The global scope for the sql_log_bin system
       variable has been deprecated, and this variable can now
       be set with session scope only. The statement SET GLOBAL
       SQL_LOG_BIN now produces an error. It remains possible
       for now to read the global value of sql_log_bin, but you
       should act to remove from your applications any
       dependencies on reading this value, as the ability to do
       so will be removed in a future MySQL release. (Bug
       #67433, Bug #15868071)

     * InnoDB permitted a foreign key to be created referencing
       a parent table for which the user did not have sufficient
       privileges. (Bug #18790730)

     * On Windows, the replace utility did not work. (Bug
       #16581605)

     * On CentOS 6, specifying a relative path name for the
       --socket option caused MySQL startup script failure. (Bug
       #74111, Bug #19775856)

     * The IS_FREE_LOCK() and IS_USED_LOCK() function
       implementations contained a race condition due to which
       they could access freed memory when a user lock was
       concurrently checked and freed. Accessing freed memory
       could result in an incorrect function return value or
       server exit. (Bug #73123, Bug #19070633)

     * mysql_setpermission failed to properly quote user names
       in SQL statements that it generated. (Bug #66317, Bug
       #14486004)

On behalf of Oracle/MySQL RE Team