MySQL Community Server 5.5.53 has been released (no replies)

Dear MySQL users,

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

Enjoy!


Changes in MySQL 5.5.53 (2016-10-12)


     * Packaging Notes

     * Security Notes

     * Functionality Added or Changed

   Packaging Notes

     * RPM packages now create the /var/lib/mysql-files
       directory, which is now the default value of the secure_file_priv
       system variable that specifies a directory for import and export
       operations. (Bug #24709892, Bug #24761774)

   Security Notes

     * Incompatible Change: The secure_file_priv system variable
       is used to limit the effect of data import and export operations.
       The following changes have been made to how the server handles
       this variable:

          + secure_file_priv can be set to NULL to disable all import
          and export operations.

          + The server checks the value of secure_file_priv at startup
          and writes a warning to the error log if the value is
          insecure. A non-NULL value is considered insecure if it is
          empty, or the value is the data directory or a subdirectory of
          it, or a directory that is accessible by all users. If
          secure_file_priv is set to a nonexistent path, the server
          writes an error message to the error log and exits.

          + Previously, the secure_file_priv system variable was empty
          by default. Now the default value is platform specific and
          depends on the value of the INSTALL_LAYOUT CMake option, as
          shown in the following table.

 INSTALL_LAYOUT Value          Default secure_file_priv Value
 STANDALONE, WIN      NULL
 DEB, RPM, SLES, SVR4 /var/lib/mysql-files
 Otherwise            mysql-files under the CMAKE_INSTALL_PREFIX value

          + To specify the default secure_file_priv value explicitly if
          you are building from source, use the new
          INSTALL_SECURE_FILE_PRIVDIR CMake option. To specify a
          directory for the embedded server, set the new
          INSTALL_SECURE_FILE_PRIV_EMBEDDEDDIR option. Its default value
          is NULL.  (Bug #24679907, Bug #24695274, Bug #24707666)

   Functionality Added or Changed

     * yaSSL was upgraded to version 2.4.2. This upgrade
       corrects issues with: Potential AES side channel leaks; DSA
       padding for unusual sizes; the SSL_CTX_load_verify_locations()
       OpenSSL compatibility function failing to handle long path
       directory names.  (Bug #24512715, Bug #24740291)

On behalf of Oracle MySQL Release Engineering Team,
Nawaz Nazeer Ahamed