MySQL Forums
Forum List  »  Announcements

MySQL Community Server 5.6.49 has been released
Posted by: Tvarita Jain
Date: July 13, 2020 08:19AM

Dear MySQL users,

MySQL Server 5.6.49, a new version of the popular Open Source Database
Management System, has been released. MySQL 5.6.49 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

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

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

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.48. It may also be viewed online at

Changes in MySQL 5.6.49 (2020-07-13, General Availability)

     * Configuration Notes

     * Security Notes

     * Bugs Fixed

Configuration Notes

     * tcmalloc is no longer a permitted value for the
       mysqld_safe --malloc-lib option. (Bug #31372027)

Security Notes

     * The linked OpenSSL library for MySQL Server has been
       updated to version 1.1.1g. Issues fixed in the new OpenSSL
       version are described at
       and (Bug

Bugs Fixed

     * Partitioning: A query against a partitioned table, which
       used an ORDER BY, returned unordered results under the following

          + The table had a composite index with a prefix on one of the

          + The query's WHERE clause contained an equality condition on
          the prefixed column.

          + The column with the prefix was the leftmost column in the

          + The column used in the ORDER BY was the rightmost column in
          the index.

          + The index was used for handling the ORDER BY. Our thanks to
          Quanan Han for the contribution. (Bug #84070, Bug #25207522)

     * Replication: When a replication source server shuts down
       and restarts, its MEMORY tables become empty. To replicate this
       effect to replicas, the first time that the source uses a given
       MEMORY table after startup, it notifies replicas that the table
       must be emptied by writing a DELETE statement for that table to
       the binary log. Previously, the generated DELETE statement was
       written to the binary log statement cache for the current
       session, which could result in it being logged together with
       other statements under the same GTID, or logged without BEGIN and
       COMMIT statements. Also, in some situations, the generated DELETE
       statement could consume the GTID intended for the transaction
       that triggered it.  The generated DELETE statement is now logged
       with accompanying BEGIN and COMMIT statements, and the resulting
       transaction is flushed to the binary log immediately after it is
       written to the statement cache, so that it always receives its
       own GTID and is kept separate from other transactions. (Bug
       #30527929, Bug #25681518, Bug #77729)

     * Privileges on the INFORMATION_SCHEMA.FILES table were
       being checked incorrectly. (Bug #30350829)

     * mysql_store_result() could fail to detect invalid data
       packets. (Bug #29921423)

     * The server sometimes mistakenly removed a subquery with a
       GROUP BY when optimizing a query, even in some cases when this
       subquery was used by an outer select. This could occur when the
       subquery also used an aggregate function.  (Bug #28240054)

On behalf of the Release Engineering Team,
Tvarita Jain

Options: ReplyQuote

Written By
MySQL Community Server 5.6.49 has been released
July 13, 2020 08:19AM

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.