Dear MySQL users,

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

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

     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.38 on new servers or upgrading
to MySQL 5.6.38 from previous MySQL releases, please see

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

Not all mirror sites may be up to date at this point in time, so if you
can't find this version on some mirror, please try again later or choose
another download site.

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

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


Changes in MySQL 5.6.38 (2017-10-16, General Availability)

     * Packaging Notes

     * Bugs Fixed

   Packaging Notes

     * mysqlcheck was missing in the MySQL Server Docker image,
       which prevented mysql_upgrade from running.
       (Bug #26400146, Bug #86968)

   Bugs Fixed

     * InnoDB: Replication lag occurred on slave instances
       during large update operations on tables with many
       partitions. (Bug #25687813, Bug #85352)

     * InnoDB: A failure occurred during an end range
       comparison. (Bug #25669686)

     * InnoDB: Enabling the innodb_buffer_pool_load_now setting
       failed in readonly mode. The event that signals the
       buffer pool load thread was not initialized.
       (Bug #25586766)

     * InnoDB: A long wait for a dictionary operation lock held
       by a full-text search synchronization operation caused a
       server exit. (Bug #24938374)

     * Partitioning: Queries involving NULL were not always
       handled correctly on tables that were partitioned by
       LIST. (Bug #76418, Bug #20748521)
       References: See also: Bug #86255, Bug #26034430.

     * Replication: When replicating a partitioned table with an
       index, on a replication slave where HASH_SCAN was
       specified as part of the slave_rows_search_algorithms
       setting, the slave I/O thread sometimes stopped with an
       error HA_ERR_KEY_NOT_FOUND. (Bug #26137159)

     * Replication: Replication clients no longer enable LOCAL
       capability for LOAD DATA statements, because they do not
       use LOAD DATA LOCAL statements. (Bug #24763131)

     * Replication: In case of a failure while creating multiple
       slave applier worker threads, some threads would be left
       orphaned and their resources would not be collected.
       Thanks to Laurynas Biveinis for his contribution to
       fixing this bug. (Bug #24679056, Bug #82980)

     * MSI packages for Windows failed to detect when Microsoft
       Visual C++ 2010 Redistributable Package was installed.
       (Bug #26501092, Bug #87139)

     * yaSSL could incorrectly perform TLS cipher negotiation.
       (Bug #26482173)

     * The server failed to check the maximum path length for
       partition names. (Bug #26390632)

     * Identifiers containing a mixture of backslashes and
       backticks could be parsed incorrectly. (Bug #26372491)

     * Source packages for Debian platforms contained prebuilt
       debug binaries, causing build failures on any
       architectures other than the one on which those binaries
       were built. (Bug #26186911)

     * Uninstalling the daemon_memcached plugin caused a serious
       error. (Bug #25909540)

     * Selecting from a view could yield different results with
       materialization enabled versus materialization disabled.
       (Bug #25782811, Bug #85622)

     * The Performance Schema failed to check the maximum host
       length for client connections. (Bug #25510805)

     * A server error occurred when a full text search result
       exceeded the innodb_ft_result_cache_limit setting. The
       patch for this bug also backports a related patch
       (Bug #21140111). (Bug #25033538)

     * If a stored function was considered a constant by the
       optimizer, calling it from a subquery in a NOT IN
       condition in the WHERE clause could cause a server exit.
       (Bug #23577867)

     * A mysqldump memory leak was fixed. Thanks to Yura Sorokin
       for the patch. (Bug #23531150, Bug #81714)

     * If a session rolled back to a savepoint and then was
       killed, the statements up to the point of the savepoint
       could be committed. (Bug #22350047, Bug #79596)

     * For clients that used Connector/Python and authenticated
       using the sha256_password plugin, the server could handle
       connections incorrectly. (Bug #21421642)

     * NAME_CONST() can return null if incorrect arguments are
       given. In some cases, this was not handled and could
       cause a server exit. (Bug #19143243, Bug #26361149)

On Behalf of MySQL/ORACLE RE Team
Gipson Pulla

MySQL General Mailing List
For list archives:
To unsubscribe:

Reply via email to