MySQL Community Server 5.6.47 has been released

[Gipson Pulla]

Dear MySQL users,

MySQL Server 5.6.47, a new version of the popular Open Source
Database Management System, has been released. MySQL 5.6.47 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.47 on new servers or upgrading
to MySQL 5.6.47 from previous MySQL releases, please see

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

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

  http://dev.mysql.com/downloads

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

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

Enjoy!

Changes in MySQL 5.6.47 (2020-01-13, General Availability)

Bugs Fixed


     * Replication: When GTIDs are enabled on a replication
       master and slave, and the slave connects to the master
       with the MASTER_AUTO_POSITION=1 option set, the master
       must send the slave all the transactions that the slave
       has not already received, committed, or both. If any of
       the transactions that should be sent by the master have
       been already purged from the master's binary log, the
       master sends the error
       ER_MASTER_HAS_PURGED_REQUIRED_GTIDS (1789) to the slave,
       and replication does not start.
       The message provided for the error
       ER_MASTER_HAS_PURGED_REQUIRED_GTIDS has been changed to
       provide advice on the correct action in this situation,
       which is for the slave to replicate the missing
       transactions from another source, or for the slave to be
       replaced by a new slave created from a more recent
       backup. The message advises that the master's binary log
       expiration period can be revised to avoid the situation
       in future. In addition, the master now identifies the
       GTIDs of the purged transactions and supplies them in its
       error log in the warning message ER_FOUND_MISSING_GTIDS
       (11809), so that you do not need to calculate the missing
       GTIDs manually. (Bug #26004541, Bug #29769293)

     * With multiple sessions executing concurrent INSERT ... ON
       DUPLICATE KEY UPDATE statements into a table with an
       AUTO_INCREMENT column but not specifying the
       AUTO_INCREMENT value, inserts could fail with a unique
       index violation. (Bug #30194841, Bug #96578)

     * A SELECT using a WHERE condition of the form A AND (B OR
       C [OR ...]) resulting in an impossible range led to an
       unplanned exit of the server. (Bug #29770705)

     * An incomplete connection packet could cause clients not
       to properly initialize the authentication plugin name.
       (Bug #29630767)

On Behalf of MySQL/ORACLE RE Team
Gipson Pulla