MySQL Community Server 5.6.44 has been released

Dear MySQL users,

MySQL Server 5.6.44, a new version of the popular Open Source
Database Management System, has been released. MySQL 5.6.44 is
recommended for use on production systems.

For an overview of what's new in MySQL 5.6, please see

  http://dev.mysql.com/doc/refman/5.6/en/mysql-nutshell.html

     Starting with 5.6.11, Microsoft Windows packages for MySQL 5.6
     are available both as a "full" installer and as a "web" installer.
     The full installer is significantly larger and comes bundled with
     the latest software releases available. This bundle makes it easy
     to download and configure a full server and development suite.

     The web installer doesn't come bundled with any actual products
     and instead relies on download-on-demand to fetch only the
     products you choose to install. This makes the initial download
     much smaller but increases install time as the individual products
     will need to be downloaded.

For information on installing MySQL 5.6.44 on new servers or upgrading
to MySQL 5.6.44 from previous MySQL releases, please see

  http://dev.mysql.com/doc/refman/5.6/en/installing.html

MySQL Server 5.6.44, is available in source and binary form for a number of
platforms from our download pages at

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

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

  http://bugs.mysql.com/report.php

The following link lists the changes in the MySQL 5.6 since
the release of MySQL 5.6.43. It may also be viewed
online at

  http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-44.html

Enjoy!

Changes in MySQL 5.6.44 (2019-04-25, General Availability)

   Beginning with MySQL 5.6.44, Oracle no longer provides
   binaries for SUSE 11.

Security Notes


     * The linked OpenSSL library for the MySQL Commercial
       Server has been updated to version 1.0.2r. Issues fixed
       in the new OpenSSL version are described at
       http://www.openssl.org/news/vulnerabilities.html.
       This change does not affect the Oracle-produced MySQL
       Community build of MySQL Server, which uses the yaSSL
       library instead. (Bug #28988091)

Bugs Fixed


     * Important Note: The libevent library included with the
       MySQL Server was upgraded to version 2.1.8. (Bug
       #28207237, Bug #29041505, Bug #29055011)

     * InnoDB: The INDEX_LENGTH value in
       INFORMATION_SCHEMA.TABLES was not updated when adding an
       index. (Bug #19811005)

     * Partitioning: An AUTO_INCREMENT key added to a
       partitioned table by an ALTER TABLE statement using
       ALGORITHM=3DINPLACE restarted on each partition. (Bug
       #92241, Bug #28573894)

     * Replication: If an applier thread was stopped while it
       was in the process of opening a table, no error was set,
       which could result in a segmentation fault or assertion
       depending on the build type. Error handling is now
       correctly activated in this situation. (Bug #28864557)

     * Replication: If a storage engine has the capability to
       log in STATEMENT format but not in ROW format, when
       binlog_format is set to STATEMENT, an unsafe SQL
       statement should be logged and a warning message should
       be written to the error log. However, such statements
       were instead not executed and an error message was
       written to the error log, which is the correct behavior
       when binlog_format is set to MIXED or ROW. The issue has
       now been corrected so that unsafe statements are logged
       with a warning as expected when binlog_format is set to
       STATEMENT. (Bug #28429993, Bug #73936)

     * Microsoft Windows: Validity testing for the
       named_pipe_full_access_group system variable did not
       account for NULL values. (Bug #29256690)

     * MySQL 5.6 did not build with maintainer mode enabled with
       GCC 7. (Bug #29048768)

     * A damaged mysql.user table could cause a server exit.
       (Bug #28986737)

     * mysqladmin shutdown did not wait for mysqld to shut down.
       (Bug #28466137, Bug #91803)
       References: This issue is a regression of: Bug #25364806.

     * Some status variable values could temporarily increase
       before returning to their original value. (Bug #27839644,
       Bug #90351)

     * The binary file for the udf_example user-defined function
       was omitted from binary distributions. (Bug #26115002,
       Bug #29178542)

     * Compiling the InnoDB memcached plugin did not work on
       some platforms where MySQL was configured using
       -DWITH_LIBEVENT=3Dsystem, for libevent version 2.0 or
       higher. (Bug #80073, Bug #22573379, Bug #23567441)


On Behalf of MySQL/ORACLE RE Team
Gipson Pulla

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/mysql