Dear MySQL users,

MySQL Connector/Net 6.10.7 is the fourth GA release with .NET Core
now supporting various connection-string options and MySQL 8.0 server
features.

To download MySQL Connector/Net 6.10.7 GA, see the "Generally Available
(GA) Releases" tab at http://dev.mysql.com/downloads/connector/net/

Changes in MySQL Connector/Net 6.10.7 (2018-04-30, General Availability)

   Functionality Added or Changed

     * Connections made to MySQL 8.0 (up to and including
       version 8.0.3) and compatibility with the new data dictionary are
       now supported. For information about the data dictionary, see
       MySQL Data Dictionary
       (http://dev.mysql.com/doc/refman/8.0/en/data-dictionary.html).

     * Support for the caching_sha2_password authentication
       plugin through the classic MySQL protocol was added. In addition,
       the sha256_password plugin was extended to support authentication
       when RSA keys are available through non-secure connections.
       Caching SHA-2 pluggable authentication offers faster
       authentication than basic SHA-256 authentication.

     * Support was added for the new caching_sha2_password
       padding mechanism introduced in the MySQL 8.0 release series. The
       new padding mechanism is enabled when all of the following
       conditions apply:

          + The user account is set with the
            caching_sha2_password authentication plugin.

          + SSL is disabled explicitly (SslMode=none).

          + The AllowPublicKeyRetrieval connection option is enabled
          (AllowPublicKeyRetrieval=true).  When enabled, the new padding
          mechanism is used to encode the password during RSA key
          encryption, which applies the correct padding to match the
          server.

Bugs Fixed


     * Attempting to open the MySQL Web Configuration Tool, with
       Connector/Net and MySQL for Visual Studio prerequisites installed
       properly, displayed an error message instead of opening the tool.
       (Bug #27457398, Bug #88544)

     * The ADO.NET Entity Data Model wizard within Visual Studio
       closed unexpectedly without producing the data model.  Thanks to
       Laurents Meyer for the patch. (Bug #27420311, Bug #89338)

     * An exception prevented MySQL.Data.Entity for Entity
       Framework 6 from operating as expected. Thanks to Cédric Luthi
       for the patch. (Bug #27360520, Bug #89134)

     * MySQL Installer could not be installed with NuGet
       packages from Microsoft Visual Studio 2015. (Bug #27251839,
       Bug #88838)

     * With valid references to the DLLs provided, using
       DbConfiguration.SetConfiguration(new
       MySql.Data.Entity.MySqlEFConfiguration()) to set up the DbContext
       threw an exception. (Bug #25185319)

     * Attempting to generate an Entity Framework model from a
       MySQL 5.7 database using either EF5 or EF6 produced an exception
       that prevented the operation from generating the expected model.
       (Bug #22173048, Bug #79163)

Nuget packages are available at:

https://www.nuget.org/packages/MySql.Data/6.10.7
https://www.nuget.org/packages/MySql.Web/6.10.7
https://www.nuget.org/packages/MySql.Data.Entity/6.10.7
https://www.nuget.org/packages/MySql.Data.EntityFrameworkCore/6.10.7
https://www.nuget.org/packages/MySql.Data.EntityFrameworkCore.Design/6.10.7


Enjoy and thanks for the support!

On behalf of the MySQL Release Team,
Nawaz Nazeer Ahamed

Dear MySQL Users,

A new GA (general availability) version of MySQL Connector/C++ has
been made available: MySQL Connector/C++ 1.1.11 GA. The MySQL
Connector/C++ provides a C++ API for connecting client applications to
the MySQL Server 5.5 or newer.

You can download the production release at:

http://dev.mysql.com/downloads/connector/cpp/1.1.html

MySQL Connector C++ (Commercial) will be available for download on the
My Oracle Support (MOS) website. This release will be available on eDelivery
(OSDC) in next month's upload cycle.

The MySQL driver for C++ offers an easy to use API derived from JDBC
4.0. MySQL Workbench has used it successfully for years.

We have improved the driver since the last GA release. Please see the
documentation and the CHANGES file in the source distribution for a
detailed description of bugs that have been fixed. Bug descriptions are
also listed below.

Enjoy!

Changes in MySQL Connector/C++ 1.1.11 (2018-04-30, General
Availability)

Functionality Added or Changed

     * MySQL Connector/C++ 1.1 now works with both MySQL 5.7 GA
       and MySQL 8.0 GA servers.

          + Applications can connect to MySQL 8.0 servers using
            accounts that authenticate using the
            caching_sha2_password authentication plugin.

          + Applications can connect to MySQL 8.0 servers using
            unencrypted connections by using the
            OPT_GET_SERVER_PUBLIC_KEY connection option with a
            value of true.

          + Connector/C++ 1.1 can be built from source against
            either MySQL 5.7 and MySQL 8.0 server installations.

          + A new BUNDLE_DEPENDENCIES CMake option is available.
            If enabled, the external libraries on which
            Connector/C++ depends at runtime (such as OpenSSL),
            are packaged together with the connector.

     * For connections to the server made using the legacy JDBC
       API (that is, not made using X DevAPI or XAPI),
       Connector/C++ now supports an OPT_GET_SERVER_PUBLIC_KEY
       connection option that enables requesting the RSA public
       key from the server. For accounts that use the
       caching_sha2_password or sha256_password authentication
       plugin, this key can be used during the connection
       process for RSA key-pair based password exchange with TLS
       disabled. This capability requires a MySQL 8.0 GA server,
       and is supported only for Connector/C++ built using
       OpenSSL.

Bugs Fixed

     * MySQL Connector/C++ packages now include a BUILDINFO.txt
       file that contains information about the build
       environment used to produce the distribution. (Bug
       #23556661)

On Behalf of the MySQL/ORACLE RE Team
Piotr Obrzut 

Dear MySQL users,

MySQL Connector/Net 6.9.12 is a maintenance release for the 6.9.x series
of the .NET driver for MySQL. It can be used for production
environments.

It is appropriate for use with MySQL server versions 5.5-5.7.

It is now available in source and binary form from
http://dev.mysql.com/downloads/connector/net/#downloadsandmirrorsites
(note that not all mirror sites may be up to date at this point-if you
can't find this version on some mirror, please try again later or choose
another download site.)

Note: C/NET 6.9 will not be supported any more. If users are looking to get latest
updates on C/NET, they should upgrade to using C/NET 6.10 and 8.0 series instead.

Changes in MySQL Connector/Net 6.9.12 (2018-05-04, General
Availability)

Functionality Added or Changed

     * Connections made to MySQL 8.0 (up to and including
       version 8.0.3) and compatibility with the new data
       dictionary are now supported. For information about the
       data dictionary, see MySQL Data Dictionary
       (http://dev.mysql.com/doc/refman/8.0/en/data-dictionary.h
        tml).

     * Support for the caching_sha2_password authentication
       plugin through the classic MySQL protocol was added. In
       addition, the sha256_password plugin was extended to
       support authentication when RSA keys are available
       through non-secure connections. Caching SHA-2 pluggable
       authentication offers faster authentication than basic
       SHA-256 authentication.

     * Support was added for the new caching_sha2_password
       padding mechanism introduced in the MySQL 8.0 release
       series. The new padding mechanism is enabled when all of
       the following conditions apply:

          + The user account is set with the
            caching_sha2_password authentication plugin.

          + SSL is disabled explicitly (SslMode=none).

          + The AllowPublicKeyRetrieval connection option is
            enabled (AllowPublicKeyRetrieval=true).
       When enabled, the new padding mechanism is used to encode
       the password during RSA key encryption, which applies the
       correct padding to match the server.

Bugs Fixed

     * The MySqlConnection.GetSchema("PROCEDURES", restrictions)
       method call generated an error message, instead of
       returning stored procedures, when the server connection
       was to the MySQL 8.0 release series. (Bug #25961782)

     * Attempting to generate an Entity Framework model from a
       MySQL 5.7 database using either EF5 or EF6 produced an
       exception that prevented the operation from generating
       the expected model. (Bug #22173048, Bug #79163)

The documentation is available at:
http://dev.mysql.com/doc/connector-net/en/

Nuget packages are available at:
https://www.nuget.org/packages/MySql.Data/6.9.12
https://www.nuget.org/packages/MySql.Data.Entity/6.9.12
https://www.nuget.org/packages/MySql.Fabric/6.9.12
https://www.nuget.org/packages/MySql.Web/6.9.12

Enjoy and thanks for the support!

On behalf of the MySQL Release Team,
Sreedhar S

Dear MySQL users,

The MySQL Windows Experience Team is proud to announce the release
of MySQL for Visual Studio 1.2.8.

This is a maintenance release for 1.2.x. It can be used for
production environments.

MySQL for Visual Studio is a product that includes all of the
Visual Studio integration functionality to create and manage
MySQL databases when developing .NET applications.

MySQL for Visual Studio is installed using the MySQL Installer
for Windows which comes in 2 versions:
   * Full (386.6 MB) which includes a complete set of MySQL products
     with their binaries included in the downloaded bundle.
   * Web (1.7 MB - a network install) which will just pull MySQL
     for Visual Studio over the web and install it when run.

You can download MySQL Installer from our official Downloads page at
http://dev.mysql.com/downloads/installer/.

MySQL for Visual Studio can also be downloaded by using the product
standalone installer found at
http://dev.mysql.com/downloads/windows/visualstudio/.


Changes in MySQL for Visual Studio 1.2.8 (2018-05-04, General
Availability)


     * Functionality Added or Changed

     * Bugs Fixed

Functionality Added or Changed


     * When Microsoft Visual Studio receives a request to
       register (or unregister) MySQL for Visual Studio within
       the IDE during the installation, Visual Studio might not
       execute the command properly if the host is running
       Windows 7. This fix identifies when Visual Studio does
       not register MySQL for Visual Studio as requested and
       then provides an alert to perform the registration
       manually from the Developer Command Prompt for Visual
       Studio using the following command:

devenv /updateconfiguration /log

       (Bug #27365261, Bug #87902)

     * MySQL for Visual Studio now supports the MySQL 8.0
       release series (requires Connector/Net 6.9.12, 6.10.7, or
       8.0.11) including:

          + MySQL data dictionary, which uses INFORMATION_SCHEMA
            tables rather than tables in the mysql database (see
            MySQL Data Dictionary
            ( http://dev.mysql.com/doc/refman/8.0/en/data-dictionary.html )).

          + The caching_sha2_password authentication plugin
            introduced in MySQL 8.0 (see Caching SHA-2 Pluggable
            Authentication
            ( http://dev.mysql.com/doc/refman/8.0/en/caching-sha2-pluggable-authentication.html )).
          In addition, MySQL for Visual Studio now requires that
          .NET Framework 4.5.2 (or later) be installed for use
          within Visual Studio 2012 and Visual Studio 2013.

Bugs Fixed


     * The Website Configuration Tool was unable to add an
       ADO.NET entity data model to an ADO.NET web application
       successfully. In addition to aligning the web.config file
       with the installed version of Connector/Net, this fix
       also disables the Entity Framework 5 selection when the
       installed connector no longer includes a provider for EF5
       (Connector/Net 6.10 and higher). (Bug #27593219)

     * Queries made with a valid MySQL connection received no
       response from the server. (Bug #27584991)

     * When the MySQL for Visual Studio parser was unable to
       parse an SQL statement, it generated an unhandled
       exception that caused Visual Studio to exit unexpectedly.
       This fix enables the parser to handle exceptions properly
       and updates the parser to include support for CREATE USER
       syntax in the MySQL 8.0 release series. (Bug #27580303)

     * The version for the MySql.Web assembly was incorrectly
       extracted, which prevented the assembly from loading
       properly and the MySQL Website Configuration Tool from
       launching. (Bug #27450530)

     * Attempting to open the MySQL Web Configuration Tool, with
       MySQL Connector/Net and MySQL for Visual Studio
       prerequisites installed properly, displayed an error
       message instead of opening the tool. (Bug #27365141, Bug
       #88570)

On Behalf of MySQL Release Engineering Team,
Surabhi Bhat 

Dear MySQL Users,

MySQL Cluster Manager 1.4.6 can be downloaded from
the My Oracle Support (MOS) website. It will also be available
on Oracle Software Delivery Cloud at http://edelivery.oracle.com with
the next monthly update

MySQL Cluster Manager is an optional component of the MySQL Cluster Carrier
Grade Edition, providing a command-line interface that automates common
management tasks, including the following online operations:
 - Configuring and starting MySQL Cluster
 - Upgrades
 - Adding and removing cluster nodes
 - Adding and removing site hosts
 - Configuration changes
 - Backup and restore

MySQL Cluster Manager is a commercial extension to the MySQL family of products.
More details can be found at http://www.mysql.com/products/cluster/mcm/.

A brief summary of changes in MySQL Cluster Manager version 1.4.6 is listed below:

Changes in MySQL Cluster Manager 1.4.6   (2018-05-09)

 * Functionality Added or Changed

 * Bugs Fixed

Functionality Added or Changed


     * Agent: The list backups command has been extended with a
       new --agent option for listing agent backups created with
       the backup agents command. See the option description for
       details. (Bug #27168819, Bug #27850905)

Bugs Fixed


     * Agent: The collect logs command failed to include logs
       that had been rotated with the rotate log command. (Bug
       #27918231)

     * Agent: A list backups command failed with an Error: 1159
      (timeout reading communication packets) from one of the
       mcmd agents when it had a huge number of backups to list.
       With this fix, mcmd has been optimized to enumerate a
       larger number of backups. (Bug #27868499)

     * Agent: The mcmd agent quit unexpectedly if the cluster's
       global configuration file (config.ini usually) contained
       a [system] section. It was because in MySQL Cluster
       Manager, the handling for the [system] section was
       missing, which has now been added by this fix. The
       addition also allows mcmd to set the name attribute in
       the [system] section, which is required for MySQL
       Enterprise Monitor 4.0 to monitor the cluster.
       (Bug #27638138, Bug #27519205)

     * Agent: The collect logs command hung if a host was
       referenced earlier with the localhost IP address
       127.0.0.1 in the create site or create cluster command.
       (Bug #27551932)

     * Agent: The create cluster command was successful even if
       the format of an IP address submitted with it as a
       hostname was inconsistent with the format used earlier
       with the add hosts command (for example, a host was added
       to a site as 127.0.0.1, and then added to a cluster as
       127.0.01). A subsequent attempt to start the cluster
       failed. This fix added consistency check for the host
       names, so that inconsistent IP addresses are now
       rejected. (Bug #27551776)

     * Agent: When a maintenance restart occurred for a cluster
       node while mcmd was shutting down, the node remained in
       the starting stage indefinitely. With this fix, a node
       restart will not be attempted when mcmd is shutting down.
       (Bug #27513481)

     * Agent: An Internal error occurred when mcmd tried to set
       the MySQL Server system variable
       audit_log_read_buffer_size with a set command. It was
       because of the wrong data type used internally for the
       variable, which has now been fixed. (Bug #27413635)

     * Agent: mcmd quit unexpectedly sometimes when running a
       restore cluster command. It was due to a race condition
       in which mcmd started executing the restore before the
       required ndbapi node was ready for the task. This fix
       added checks to eliminate the race condition. (Bug
       #27342271)

On behalf of MySQL Release Engineering Team,
Surabhi Bhat 

Dear MySQL users,

MySQL Connector/ODBC 8.0.12 is the second version of the MySQL
Connector/ODBC 8.0 series, the ODBC driver for the MySQL Server.

The available downloads include both a Unicode driver and an ANSI
driver based on the same modern codebase. Please select the driver
type you need based on the type of your application - Unicode or ANSI.
Server-side prepared statements are enabled by default. It is suitable
for use with any MySQL server version from 5.5.

This release of the MySQL ODBC driver is conforming to the ODBC 3.8
specification. It contains implementations of key 3.8 features,
including self-identification as a ODBC 3.8 driver, streaming of
output parameters (supported for binary types only), and support of
the SQL_ATTR_RESET_CONNECTION connection attribute (for the Unicode
driver only).

The release is now available in source and binary form for a number of
platforms from our download pages at

  https://dev.mysql.com/downloads/connector/odbc/

For information on installing, please see the documentation at

https://dev.mysql.com/doc/connector-odbc/en/connector-odbc-installation.html

Changes in MySQL Connector/ODBC 8.0.12 (2018-07-27, General
Availability)

Functionality Added or Changed

     * Several code issues identified by Fortify were corrected.

     * Refactored codebase to remove legacy code and implement
       general performance improvements. For example, unused
       ANSI data conversion code and legacy functions were
       removed. Example improvements affect bookmark handling
       for bulk operations, handling of memory buffers for
       prepared statements, and handling of session variables.

     * On Windows, 32-bit support was added and 32-bit binaries
       are now available.

     * An RPM package for installing ARM 64-bit (aarch64)
       binaries of Connector/ODBC on Oracle Linux 7 is now
       available in the MySQL Yum Repository and for direct
       download.
       Known Limitation for this ARM release: You must enable
       the Oracle Linux 7 Software Collections Repository
       (ol7_software_collections) to install this package, and
       must also adjust the libstdc++7 path. See Yum's Platform
       Specific Notes
(http://dev.mysql.com/doc/refman/8.0/en/linux-installation-yum-repo.html#yum-install-platform-specifics)
       for additional details.

Bugs Fixed

     * Added checks for unsupported functionality that return
       SQL_ERROR instead of SQL_SUCCESS, where the error message
       refers to the unsupported functionality. (Bug #28217387)

     * The data source dependent type's name was not always
       returned. For example, the ODBC driver reported TEXT as
       the database type for TINYTEXT, MEDIUMTEXT, and LONGTEXT,
       and reported BLOB for TINYBLOB, MEDIUMBLOB, and LONGBLOB.
       (Bug #11761407, Bug #53900)

On Behalf of Oracle/MySQL Release Engineering Team,
Piotr Obrzut

Dear MySQL users,

MySQL Connector/C++ 8.0.12 is the second GA release version of the MySQL
Connector/C++ 8.0 series.

Connector/C++ 8.0 can be used to access MySQL implementing Document
Store or in a traditional way, using SQL queries. It allows writing
both C++ and plain C applications using X DevAPI and X DevAPI for C.
It also supports the legacy API of Connector/C++ 1.1 based on JDBC4.

To learn more about how to write applications using X DevAPI, see "X
DevAPI User Guide"

   https://dev.mysql.com/doc/x-devapi-userguide/en/

See also "X DevAPI Reference" at

   https://dev.mysql.com/doc/dev/connector-cpp/devapi_ref.html

and "X DevAPI for C Reference" at

   https://dev.mysql.com/doc/dev/connector-cpp/xapi_ref.html

For generic information on using Connector/C++ 8.0, see

   https://dev.mysql.com/doc/dev/connector-cpp/

Note: For X DevAPI applications, Connector/C++ 8.0 requires
MySQL Server 5.7.12 or higher with X Plugin enabled. For applications
that use the legacy JDBC API, Connector/C++ 8.0 can use MySQL Server 5.5
or higher, and X Plugin is not required.

   https://dev.mysql.com/doc/refman/5.7/en/document-store.html

To download MySQL Connector/C++ 8.0.12, see the "Generally Available (GA)
Releases" tab at

   https://dev.mysql.com/downloads/connector/cpp/


Changes in MySQL Connector/C++ 8.0.12 (2018-07-27, General Availability)

     * Installation Notes

     * Packaging Notes

     * Security Notes

     * X DevAPI Notes

     * Bugs Fixed

Installation Notes


     * Because the Microsoft Visual C++ 2017 Redistributable
       installer deletes the Microsoft Visual C++ 2015
       Redistributable registry keys that identify its
       installation, standalone MySQL MSIs may fail to detect
       the Microsoft Visual C++ 2015 Redistributable if both it
       and the Microsoft Visual C++ 2017 Redistributable are
       installed. The solution is to repair the Microsoft Visual
       C++ 2017 Redistributable via the Windows Control Panel to
       recreate the registry keys needed for the runtime
       detection. Unlike the standalone MSIs, MySQL Installer
       for Windows contains a workaround for the detection
       problem.

Packaging Notes


     * An RPM package for installing ARM 64-bit (aarch64)
       binaries of Connector/C++ on Oracle Linux 7 is now
       available in the MySQL Yum Repository and for direct
       download.
       Known Limitation for this ARM release: You must enable
       the Oracle Linux 7 Software Collections Repository
       (ol7_software_collections) to install this package, and
       must also adjust the libstdc++7 path. See Yum's Platform
       Specific Notes
(http://dev.mysql.com/doc/refman/8.0/en/linux-installation-yum-repo.html#yum-install-platform-specifics)
       for additional details.

     * Installers for Connector/C++ are now available in these
       formats: MSI packages (Windows); RPM packages (Linux);
       DMG packages (macOS).

Security Notes


     * yaSSL is no longer included in Connector/C++ source
       distributions. wolfSSL may be used as a functionally
       equivalent alternative that has a GPLv2-compatible
       license. In addition, wolfSSL (like OpenSSL) supports the
       TLSv1.2 protocol, which yaSSL does not.
       To build Connector/C++ using wolfSSL, use the
       -DWITH_SSL=path_name CMake option, where path_name
       indicates the location of the wolfSSL sources. For more
       information, see Source Installation System Prerequisites
(http://dev.mysql.com/doc/connector-cpp/8.0/en/connector-cpp-installation-source-prerequisites.html), 
       and Connector/C++ Source-Configuration Options
(http://dev.mysql.com/doc/connector-cpp/8.0/en/connector-cpp-source-configuration-options.html).

X DevAPI Notes


     * Connector/C++ now supports NOWAIT and SKIP LOCKED lock
       contention modes to be used with lockExclusive() and
       lockShared() clauses of CRUD find/select operations (see
       Locking Read Concurrency with NOWAIT and SKIP LOCKED
(http://dev.mysql.com/doc/refman/8.0/en/innodb-locking-reads.html#innodb-locking-reads-nowait-skip-locked)), 
       and a default lock contention mode. The following list names
       the permitted constants. For each item, the first and
       second constants apply to X DevAPI and X DevAPI for C,
       respectively.

          + LockContention::DEFAULT, LOCK_CONTENTION_DEFAULT:
            Block the query until existing row locks are
            released.

          + LockContention::NOWAIT, LOCK_CONTENTION_NOWAIT:
            Return an error if the lock cannot be obtained
            immediately.

          + LockContention::SKIP_LOCKED,
            LOCK_CONTENTION_SKIP_LOCKED: Execute the query
            immediately, excluding from the query items that are
            locked.
       For X DevAPI and X DevAPI for C applications, lock mode
       methods accept these lock contention constants as a
       parameter. For X DevAPI applications, lock mode methods
       can be called without this parameter, as before; this is
       equivalent to passing a lock mode of DEFAULT.

     * Connector/C++ now supports the SHA256_MEMORY
       authentication mechanism for connections using the X
       Protocol. For X DevAPI applications, SessionOption::AUTH
       supports the new value AuthMethod::SHA256_MEMORY. For X
       DevAPI for C applications, the session option
       MYSQLX_OPT_AUTH supports the new value
       MYSQLX_AUTH_SHA256_MEMORY. These new values request using
       the sha256_memory authentication mechanism when creating
       a session.

     * For compliance with the Core DevAPI, these Connector/C++
       changes were made:

          + getAffectedItemsCount() was moved from Result to
            Result_common.

          + Collection.modify(condition).arrayDelete() was
            removed.

          + getAffectedRowsCount() was removed. Use
            getAffectedItemsCount() instead.

          + getWarningCount() was renamed to getWarningsCount().

Bugs Fixed


     * utf8mb4 character data was handled incorrectly. (Bug
       #28240202)

     * Session creation had a memory leak. (Bug #27917942)

     * When configuring to build Connector/C++ with the legacy
       connector, CMake did not account for the
       MYSQL_CONFIG_EXECUTABLE option. (Bug #27874173, Bug
       #90389)

     * Improper error handling for unknown hosts when creating a
       session could result in unexpected application exit. (Bug
       #27868302)

     * The mysqlx_row_fetch_one() X DevAPI for C function could
       fail to return for large result set exceeding the maximum
       packet size. Now such result sets produce an error. (Bug
       #27732224)

Enjoy and thanks for the support!

On Behalf of Oracle/MySQL Release Engineering Team,
Balasubramanian Kandasamy

Dear MySQL users,

The MySQL developer tools team announces 8.0.12 as our first general
availability (GA) for MySQL Workbench 8.0.

For the full list of changes in this revision, visit
http://dev.mysql.com/doc/relnotes/workbench/en/changes-8-0.html

For discussion, join the MySQL Workbench Forums:
http://forums.mysql.com/index.php?152

The release is now available in source and binary form for a number of
platforms from our download pages at:

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


Enjoy!

Changes in MySQL Workbench 8.0.12 (2018-07-27, General Availability)

   Known limitation of this release: Importing spatial data into
   a MySQL 8.0 server does not work currently, due to an
   outstanding library update. Older versions of the server are
   not affected.

     * Installation Notes

     * Functionality Added or Changed

     * Bugs Fixed

Installation Notes


     * Because the Microsoft Visual C++ 2017 Redistributable
       installer deletes the Microsoft Visual C++ 2015
       Redistributable registry keys that identify its
       installation, standalone MySQL MSIs may fail to detect
       the Microsoft Visual C++ 2015 Redistributable if both it
       and the Microsoft Visual C++ 2017 Redistributable are
       installed. The solution is to repair the Microsoft Visual
       C++ 2017 Redistributable via the Windows Control Panel to
       recreate the registry keys needed for the runtime
       detection. Unlike the standalone MSIs, MySQL Installer
       for Windows contains a workaround for the detection
       problem. (Bug #28345281, Bug #91542)

Functionality Added or Changed


     * Important Change: MySQL model files last saved before
       MySQL Workbench 6.3 are no longer supported unless the
       models can be upgraded for use with the 6.3 release
       series.

     * All editions of MySQL Workbench and the bundled libraries
       were upgraded to use OpenSSL 1.0.2o. (Bug #27829782, Bug
       #28326884)

     * libgnome-keyring was depreciated and replaced with
       libsecret in this release on Linux platforms. Some users
       with existing stored passwords will be prompted to enter
       a password after upgrading. (Bug #27635281, Bug #89898,
       Bug #20291538, Bug #75345)

     * SSH tunneling support was added to the MySQL Workbench
       Migration Wizard and also to the wbcopytables
       command-line utility for copying data. (Bug #27556268,
       Bug #89671)

     * Performing multiple data export operations while the
       Administration - Data Export tab stays open now preserves
       custom file paths, rather than switching to the default
       paths for re-export operations. Exported files are
       automatically renamed with an incremental numeric suffix
       to enable repeated export.
       In addition, a new dialog box prompts for confirmation
       before overwriting an existing exported file when the
       same path and file names are reused. (Bug #27029840)

     * OGRFree() was deprecated and replaced with CPLFree().
       Thanks to Christian Hesse for the patch. (Bug #26086599,
       Bug #86339)

     * The SWIG prerequisite listed in the INSTALL document
       provided with source distributions was updated to the
       latest version. (Bug #25811732, Bug #85717)

     * Support for the --incremental-with-redo-log-only option
       was added to create backups directly from the redo log.
       (Bug #24960233)

     * The option to skip secure authorization is no longer
       available in the advanced options that apply to data
       import and export operations. The --skip-secure-auth
       option was removed in the MySQL 5.7 release. (Bug
       #21697062, Bug #78060)

     * The character set and collation pairings available after
       selecting Create a new schema in the connected server
       (from the main toolbar) now are sorted alphabetically in
       lists. (Bug #21681041, Bug #78079)

     * A new SQL export option in the Forward Engineering SQL
       Script wizard sorts tables alphabetically in the
       generated script, rather than sorting tables according to
       foreign-key references by default. (Bug #18551598, Bug
       #72289)

     * MySQL Workbench now supports the Chinese character set
       gb18030. (Bug #18547307)

     * The SQL editor supports online renaming of indexes with
       the ALTER TABLE statement. For example:
       ALTER TABLE `sakila`.`actor` RENAME INDEX `idx_actor_last_name` TO `id
       x_actor_last_xxxx`;
       (Bug #18547288)

     * MySQL Workbench now uses utf8mb4 as the connection and
       client character set, replacing utf8mb3.

Bugs Fixed


     * Some of the controls and data were not shown within the
       Administration-Users and Privileges tab. (Bug #28246905,
       Bug #91414)

     * An attempt to add a column to an existing multicolumn
       index (primary key) of a table caused MySQL Workbench to
       stop working. (Bug #28244024, Bug #91371)

     * On Windows platforms, pasting valid content into the SQL
       editor was followed by the operating system becoming
       unresponsive. (Bug #28184916, Bug #91249)

     * A query containing SELECT COUNT(*) FROM DUAL, when saved
       to a script file and then opened, caused MySQL Workbench
       to exit. (Bug #28101684, Bug #91070)

     * With code completion enabled, defining a custom variable
       within a subquery caused an unexpected exit. (Bug
       #28040983, Bug #90915)

     * With an active MySQL 8.0.11 server connection, MySQL
       Workbench displayed an error message when a valid attempt
       was made to open Performance Reports or Performance
       Schema Setup. (Bug #28034685, Bug #90889)

     * Attempting to open a new query tab from the home screen
       (File, New Query Tab from the menu) returned an error
       message and closed MySQL Workbench. (Bug #28032431, Bug
       #90885, Bug #27781092)

     * The binlog-format option was not listed as expected
       within the Administration - Options File tab. (Bug
       #28008041)

     * When Alter Stored Procedure was selected from the context
       menu, MySQL Workbench stopped working. (Bug #28006985,
       Bug #90830, Bug #23259608, Bug #81334)

     * The advanced option, $internal$show-internal-schemas,
       within the Administration - Data Export tab did not
       expose internal schemas as expected. (Bug #27938719, Bug
       #90665)

     * MySQL Workbench stopped working when the CHANGE MASTER TO
       statement was typed directly into the SQL editor,
       followed by options. (Bug #27910024, Bug #90568)

     * A stored procedure without a parameter direction (IN or
       OUT) caused MySQL Workbench to exit when it attempted to
       create or alter the procedure. (Bug #27908753, Bug
       #90555)

     * The source-database connection password used to
       reverse-engineer a database was not requested and the
       connection failed if the password was not stored in the
       vault. (Bug #27882813)

     * With SSH enabled, all new connections were made to the
       same MySQL server instance, regardless of the port number
       specified. (Bug #27882278)

     * The operation that synchronizes tables with the MySQL
       database produced an error message when an existing
       column was moved to a position after a newly added
       column. This fix ensures that ADD COLUMN always precedes
       CHANGE COLUMN within the script when both are used
       together. (Bug #27871632, Bug #90459)

     * The table editor did not apply any changes made in the
       order of an index to the generated ALTER TABLE statement.
       (Bug #27868813)

     * Snippet execution finished with an error when the
       scripting shell was used. (Bug #27746883)

     * An unclear error message was displayed during the
       table-export operation when the file path was invalid or
       left empty. (Bug #27746585)

     * The shell script for copying bulk data was not generated
       as expected. Instead, an error message was displayed.
       (Bug #27745372)

     * Setting a valid command-line path for remote-server
       access using SSH tunneling in MySQL Enterprise Backup (on
       Linux) caused the validation step to fail when both the
       SSH and sudo users were the same. (Bug #27745200)

     * MySQL Workbench model files (.mwb) did not open as
       expected when double-clicked from File Explorer on
       Windows platforms. (Bug #27739848)

     * MySQL Workbench editors displayed text from the standard
       exception in the action output, rather than using an
       error message when SQL syntax errors were discovered.
       (Bug #27730102)

     * Two terminals opened when Start Command Line Client was
       selected from the context menu on the home screen
       (right-click an existing MySQL connection). (Bug
       #27721918)

     * Text objects when double-clicked within an EER diagram
       caused MySQL Workbench to stop working. (Bug #27711642,
       Bug #90119)

     * The shell script created during the Data Transfer Setup
       step of the migration process from a MySQL local
       connection to a MySQL SSH connection produced errors that
       prevented the copying of data from outside MySQL
       Workbench. (Bug #27670242)

     * Modifying the column order within an existing index on a
       table caused MySQL Workbench to exit unexpectedly. (Bug
       #27627986, Bug #89886)

     * The Audit Inspector cache process failed when the
       connection was within a group. (Bug #27567546)

     * When using the 'OmitSchemata':1 parameter in a Python
       script to generate a schema from an .mwb file
       automatically, the resulting SQL script still included
       the schema in each table name. This fix introduces the
       OmitSchemas option, which replaces both the UseShortNames
       and OmitSchemata options, to eliminate the schema name as
       expected. (Bug #27557537, Bug #84390)

     * The work area within an EER diagram was hidden after
       double-clicking one of the table objects to open the
       table editor. (Bug #27436624)

     * When two schemas were compared with Synchronize Models
       (from the Database menu), differences were reported
       consistently for stored procedures and functions even
       though the compared items were identical. (Bug #27436115,
       Bug #82151)

     * An existing MySQL model file, when selected from the home
       screen, generated an error (Error unserializing GRT data
       string too long) and did not open. (Bug #27420297, Bug
       #89257)

     * The sidebar panel of the EER diagram editor was cut off,
       making the leftmost subtabs inaccessible and forcing the
       diagram-zoom area to shift to the right. (Bug #27330971,
       Bug #89072)

     * An incorrect INSERT statement was generated when a value
       was inserted into a BIT column. This fix now prefixes all
       BIT data-type values with the character b (for example:
       b'0'). (Bug #27320396, Bug #89068)

     * When using the Reverse Engineer Database wizard, the
       objects selected during the Select Objects step could not
       then be deselected. (Bug #27319905, Bug #89064)

     * Column-collation changes, when made using the table
       editor, could not be applied. Instead, a message
       indicating that no changes were detected was displayed.
       (Bug #27297634, Bug #88985)

     * The tls_version option was not listed as expected within
       the Administration - Options File tab. (Bug #27272808,
       Bug #87964)

     * Syntax errors typed into the SQL editor are highlighted
       and each one can provide usage information within a
       tooltip while the pointer device hovers over the error.
       On hosts running macOS, the tooltip remained visible when
       the pointer device was moved off the highlighted error.
       (Bug #27255488)

     * When only one role in a model was assigned to a user
       account, the role could not be removed. (Bug #27054771)

     * Right-clicking within a new or existing script file that
       was opened with the Workbench Scripting Shell did not
       display the context menu as expected. (Bug #27037750)

     * The edit dialog box did not open when an existing snippet
       from SQL Additions was double-clicked. (Bug #27036975)

     * The on-screen progress of a full backup operation never
       changed from Starting. The correct progress was indicated
       in the log. (Bug #27011013)

     * Creating an MySQL model from a script, with the imported
       objects added to a diagram, caused MySQL Workbench to
       exit. (Bug #27010684)

     * The version of gtkmm30 that shipped with Red Hat
       Enterprise Linux 7.4 was incompatible with the version
       that MySQL Workbench compiled against. The version
       mismatch caused MySQL Workbench to close unexpectedly.
       (Bug #26797891, Bug #26705113, Bug #87380)

     * Catalog objects for an EER diagram were not listed,
       although the tables were visible in the diagram. (Bug
       #26747931, Bug #87662)

     * The JSON tab of the Edit Data for Value dialog box
       displayed large column values as negative numbers when
       the numbers were positive. (Bug #26741970, Bug #87646)

     * Some on-screen text within Workbench Preferences (Fonts &
       Colors) wrapped around to new lines rather than filling
       the open space on the same line. (Bug #26448300, Bug
       #85961)

     * The filter arrows that select objects for forward or
       reverse engineering within wizards generated an error
       instead of moving the objects as expected. (Bug
       #26435349, Bug #26922638, Bug #87980, Bug #25921645, Bug
       #86013, Bug #25852505, Bug #85837)

     * The SQL editor returned an error when valid characters
       were used with the utf8mb4 character set. (Bug #26142347,
       Bug #86454)

     * An error was reported during an attempt to back up
       encrypted tables using MySQL Enterprise Backup. This fix
       introduces the Encrypt Password option in the Options
       subtab for a new job within the Administration - Online
       Backup tab. Setting an encryption password is required to
       perform backup and restore operations on encrypted
       tables. (Bug #26135245)

     * With multiple connection tabs opened, selecting Close All
       But This from the context menu (right-click a connection
       tab) closed tabs at random. (Bug #25983146, Bug #86144)

     * Attempting to alter a table in MySQL Workbench produced
       an error message when the table was previously altered
       using a command-line client with the ENCRYPTION option
       set to Y or N. (Bug #25929075, Bug #86021)

     * When synchronizing a model with a database, none of the
       buttons for the Select Changes to Apply step were
       visible. In addition, some frames and options were
       hidden. (Bug #25906359, Bug #85963, Bug #25527078, Bug
       #84924, Bug #25747524, Bug #85500, Bug #26128307, Bug
       #86426)

     * Time stamps representing the elapsed time of backup
       operations were miscalculated. (Bug #25820146, Bug
       #85764)

     * Long comments in tables were truncated with too few
       characters when pasted into the SQL editor after using
       Copy SQL to Clipboard from the context menu within an EER
       diagram or the MySQL Model tab. This fix extends the
       threshold. (Bug #25760721, Bug #85568)

     * The attribute in source code that set the program name
       ('MySQLWorkbench') was omitted from Unix and Linux
       distributions. Thanks to Daniël van Eeden for
       contributing to the fix. (Bug #25725077, Bug #85460)

     * Double-clicking areas within the spatial view caused
       MySQL Workbench to become unresponsive. (Bug #25723306,
       Bug #85443)

     * The height and width of object-selection lists within the
       Administration - Data Export tab were improperly
       proportioned for the content of the lists and could not
       be resized. A scroll bar now enables access to all listed
       objects. (Bug #25716077, Bug #85308)

     * A message displayed during the startup sequence indicated
       that some valid operating systems were unsupported. For
       current platform information, see
https://www.mysql.com/support/supportedplatforms/workbench.html.
       (Bug #25602334, Bug #85087)

     * A model exported as an SQL script could not be saved to
       disk when using either the Forward Engineer to Database
       or the Synchronize With Any Source wizard. (Bug
       #25569529, Bug #85030)

     * The buttons associated with renaming a diagram (OK and
       Cancel) were partially concealed. (Bug #25557678, Bug
       #85011)

     * The progress bar and Abort button were partially
       concealed on the screen when changes were being applied
       to stored procedures. (Bug #25532963, Bug #84927)

     * Each connection to an incompatible or nonstandard server
       opened a dialog box with a valid warning, but without an
       option to suppress the warning for subsequent
       connections. Thanks to Christian Hesse for the patch.
       (Bug #25519446, Bug #84885)

     * A connection made with an improper file did not return an
       SSL error as expected when the connection was tested.
       (Bug #25517237)

     * An explicit collation set on a column was reverted to the
       default collation each time the column specification was
       modified with the table editor. (Bug #25504264, Bug
       #84815)

     * The process running MySQL Workbench did not end on exit.
       (Bug #25496663)

     * The MySQL Workbench Migration Wizard returned an error
       message after failing to get a row count from source
       tables, which caused the wbcopytables utility to exit.
       (Bug #25496622)

     * Starting MySQL Workbench from the command line was
       unsuccessful on hosts running the Fedora 25 operating
       system. (Bug #25495120)

     * Custom settings made before executing the data export
       operation were not persisted if the operation was
       executed again (by clicking Start Export a second time).
       Instead, the custom settings were discarded and replaced
       by the default settings. (Bug #25488234)

     * Overlapping text boxes covered the full name entered for
       the Create a New Table option within the Select
       Destination step of the Table Data Import Wizard. (Bug
       #25476103)

     * The Copy and Copy Details operations from the Server Logs
       context menu (right-click a row in the log) were swapped.
       The Copy operation copied the details and the Copy
       Details operation performed a simple copy. (Bug
       #25469694)

     * The Copy as PHP Code (Iterate SELECT Results) command
       (select Tools and then Utilities from the menu) was
       unexpectedly disabled for valid query results. (Bug
       #25466399)

     * On Linux platforms, right-clicking Tables within the
       Catalog Tree for a valid EER diagram displayed an empty
       context menu. This fix minimizes the size of the empty
       menu. (Bug #25463963)

     * Exporting a schema from the Administration - Data Export
       tab returned an error when the server was configured for
       use within an InnoDB cluster. (Bug #25444837)

     * After maximizing and then reducing MySQL Workbench, some
       screen options were improperly sized or no longer visible
       on Linux platforms. (Bug #25415064)

     * The set of default target schemas available to choose
       from within the Administration - Data Import/Restore tab
       showed each schema listed twice on Windows platforms.
       (Bug #25239261, Bug #84161)

     * The table editor did not display generated columns within
       a user-defined table and the Alter Table operation
       returned an error message when an attempt was made to
       modify any of the nonvisible columns. (Bug #25209591, Bug
       #84078)

     * An error message was returned when an attempt was made to
       inspect a partitioned table using either the information
       icon or the context menu. (Bug #24973171, Bug #83605)

     * A single MySQL connection tab could not be closed unless
       a second connection tab was opened first. (Bug #24751859,
       Bug #83194)

     * With a connection made to a remote MySQL server, some
       context-menu functionality stopped working. For example,
       right-clicking a valid stored procedure from the Schemas
       list and selecting Alter Stored Procedure or Create
       Stored Procedure did not open a tab in the editor as
       expected. (Bug #24506578, Bug #82659)

     * On occasion, using sudo with a valid password to open a
       log file produced an exception. (Bug #24297921)

     * A variety of error messages were returned when attempts
       were made to open the Output panel (or when using Help,
       System Info from the menu) with older versions of MySQL
       Workbench. System Info was removed from the menu. (Bug
       #23584746)

     * The print-preview operation (File, Print Preview from the
       menu) did not work, or return an error message, on some
       Linux platforms. (Bug #23467065)

     * Executing separate queries (each in its own connection
       tab) caused MySQL Workbench to exit. (Bug #23305283, Bug
       #81480)

     * The PROJ.4 library (libproj) was not found, which
       prevented the initialization of Spatial Viewer. (Bug
       #22931452, Bug #80710)

     * A model diagram could not be reduced in size by clicking
       to the grid or by adjusting its value with the input
       controls. Attempts to reduce the size made the diagram
       larger. (Bug #22929861, Bug #80730)

     * Read-only tables, such as those having an index but no
       primary key, could be selected for update. However, the
       invalid update operation caused MySQL Workbench to become
       unresponsive before the operation finished. (Bug
       #22735577, Bug #80378)

     * An active connection to MySQL server was closed
       unexpectedly with the DBMS connection read time out (in
       seconds) preference option set to zero, which should keep
       the connection open. (Bug #22618750, Bug #80188)

     * Performance Schema instrumentation was not reset from the
       dashboard on Windows, even though confirmation of the
       change was provided. (Bug #22557320, Bug #80021)

     * When using the keyboard shortcut to comment selected
       lines within the SQL editor and with the cursor wrapped
       around to the beginning of the next line, the entire
       unselected next line was also commented. (Bug #22282406,
       Bug #77143)

     * A second view was created unexpectedly when an existing
       view was renamed using ALTER VIEW syntax. (Bug #22170451,
       Bug #79176)

     * An error message (Operation failed with exitcode 7) was
       generated during the dump operation when an attempt was
       made to export data running on a remote server. (Bug
       #22093554, Bug #78937)

     * The MySQL Server start and stop management operations
       generated unhandled exceptions. (Bug #21861171)

     * Stored procedures, when added to a model and synchronized
       with a database, were not listed in the Navigator area of
       the sidebar panel. New functions were not represented in
       the Catalog Tree after synchronization, although each
       function did appear in the Navigator area and in source.
       (Bug #21443566, Bug #76368)

     * Tabs separating multiple schemas within the Physical
       Schemas area of the MySQL Model tab were not visible.
       (Bug #21356922, Bug #77451)

     * The on-screen description of the myisam-repair-threads
       system variable was incomplete. It now indicates that the
       (default) value of 1 disables parallel repair (see the
       MyISAM tab in Administration - Option File). (Bug
       #20667496, Bug #76200)

     * Unexpected differences were displayed after using the
       Forward Engineer to Database wizard and then
       synchronizing the model and database. (Bug #20631631)

     * The keyboard shortcut to open the Find and Replace dialog
       box (or Edit, Replace from the menu) did not work from
       within the Workbench Scripting Shell. (Bug #20630325)

     * When importing data from a CSV file, some rows of data
       were not shown until Apply was clicked. This fix replaces
       the import functionality with a wizard. All rows now
       display correctly in the Configure Import Settings step
       of the Table Data Import wizard. Note that when no column
       header is provided, the first row of data is used as the
       header. (Bug #20630193)

     * The template supplied for the Create a Table Like
       operation (right-click Tables within the schema tree) was
       not complete enough to use without custom modifications.
       (Bug #20578595)

     * The wb.log file did not rotate to a new file (for
       example, wb.log to wb.1.log) as expected on startup. In
       addition, all queries were written to the
       sql_actions_unconnected.log file, instead of to an
       individual log file for each connection. (Bug #20356293,
       Bug #75496)

     * The Zoom + icon in the spatial view toolbar produced
       deteriorating resolution as an image was enlarged. For
       better results, use the Zoom to area icon to recompute a
       portion of the whole shape, instead of simply magnifying
       the visible area with the Zoom + tool. (Bug #20279644,
       Bug #75318)

     * A newly created SSH connection could not be used to
       synchronize a model with a MySQL database. (Bug
       #20144296, Bug #75102)

     * Expired root passwords were not supported by MySQL
       Workbench and could not be changed during the first
       attempt to make a connection to the server where the
       password was expired. (Bug #19654005)

     * Keywords in stored procedures and triggers were not
       highlighted consistently within the SQL editor and code
       blocks with keywords did not expand or collapse as
       expected. (Bug #19000092, Bug #72677)

     * Selecting Server and then Backup Recovery from the menu
       generated an unhandled exception when the server was
       stopped. (Bug #18492268)

     * Returned rows of a column in the result grid did not
       reliably sort by ascending and descending order when the
       column label was clicked. (Bug #18454325)

     * The Delete key did not function within EER diagrams. (Bug
       #18445600)

     * With both a MySQL model and EER diagram open, pressing
       the CTRL+W keyboard shortcut twice closed the diagram,
       but not the model file. (Bug #18445598)

     * On Linux platforms before the home screen was redesigned,
       attempting to drag and drop a connection from within a
       group caused the group to move instead of the connection.
       (Bug #18445563)

     * When editing an EER diagram, the icons within the editor
       overlapped on Linux platforms. (Bug #18426867)

     * Schema transfer and migration operations did not support
       SSH connections and produced error messages when the
       operations were attempted. (Bug #18138798, Bug #71295)

     * The Use defaults from global settings model option
       (Model, Model Options from the menu in the MySQL Model
       tab) when selected did not override the target MySQL
       version (set in Model Options) with the default target
       version (set in Workbench Preferences). (Bug #18130160,
       Bug #71429)

     * Attempting to edit a corrupted MySQL model (.mwb) file
       resulted in an unpredicted shutdown. (Bug #17456147, Bug
       #70334)

     * The Save and Save As dialog boxes did not show the file
       type of a model or SQL script. (Bug #17300401)

     * On macOS platforms, the database-migration operation
       returned various error messages when an attempt was made
       to migrate valid data into MySQL. (Bug #17299915, Bug
       #17299925, Bug #17408230)

     * Selecting multiple objects (tables, views, and so on) in
       a model, and then deleting all of them at once, removed
       only the first object from the model. (Bug #14821928, Bug
       #67214)

     * When an output message in the Action Area panel consisted
       of multiple lines, only the first line was visible. This
       fix provides an information box that appears briefly when
       a pointer device hovers over the truncated message. (Bug
       #14802567, Bug #66988)

     * The Workbench Scripting Shell window on hosts running the
       GNOME Shell lacked the controls to resize or close the
       window. (Bug #14768677, Bug #66810)

     * The context menus associated with tables in the schema
       tree did not function when the schema list was filtered.
       (Bug #14690217, Bug #67001)

     * The combination of Ubuntu with language-pack-tr and
       LANG=tr_TR.UTF-8 produced an error message when columns
       of type INT were parsed during operations that altered
       existing tables. (Bug #13971992, Bug #63872)

     * Chinese characters in the file path of an existing MySQL
       model were misrepresented and rendered the file
       inaccessible. (Bug #11757843, Bug #49950)

     * EER diagrams with long names wrapped around to a second
       line in the Model Overview area and were not fully
       visible when the host was Microsoft Windows. This fix
       inserts a vertical scroll bar into the Model Overview to
       accommodate long names. (Bug #11749931, Bug #40103)


On Behalf of Oracle/MySQL Release Engineering Team,
Balasubramanian Kandasamy

Dear MySQL Users,

MySQL Cluster is the distributed, shared-nothing variant of MySQL.
This storage engine provides:

  - In-Memory storage - Real-time performance (with optional
    checkpointing to disk)
  - Transparent Auto-Sharding - Read & write scalability
  - Active-Active/Multi-Master geographic replication

  - 99.999% High Availability with no single point of failure
    and on-line maintenance
  - NoSQL and SQL APIs (including C++, Java, http, Memcached
    and JavaScript/Node.js)

MySQL Cluster 7.6.7, has been released and can be downloaded from

  http://www.mysql.com/downloads/cluster/

where you will also find Quick Start guides to help you get your
first MySQL Cluster database up and running.

The release notes are available from

  http://dev.mysql.com/doc/relnotes/mysql-cluster/7.6/en/index.html

MySQL Cluster enables users to meet the database challenges of next
generation web, cloud, and communications services with uncompromising
scalability, uptime and agility.

More details can be found at

  http://www.mysql.com/products/cluster/

Enjoy !

==============================================================================
Changes in MySQL NDB Cluster 7.6.7 (5.7.23-ndb-7.6.7) (2018-07-27,
General Availability)

   MySQL NDB Cluster 7.6.7 is a new release of NDB 7.6, based on
   MySQL Server 5.7 and including features in version 7.6 of the
   NDB storage engine, as well as fixing recently discovered
   bugs in previous NDB Cluster releases.

   Obtaining NDB Cluster 7.6.  NDB Cluster 7.6 source code and
   binaries can be obtained from
   http://dev.mysql.com/downloads/cluster/.

   For an overview of changes made in NDB Cluster 7.6, see What
   is New in NDB Cluster 7.6
   (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-what-is
    -new-7-6.html).

   This release also incorporates all bug fixes and changes made
   in previous NDB Cluster releases, as well as all bug fixes
   and feature changes which were added in mainline MySQL 5.7
   through MySQL 5.7.23 (see Changes in MySQL 5.7.23 (2018-07-27,
   General Availability)
   (http://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-23.h
    tml)).

Functionality Added or Changed

     * As part of ongoing work to improve handling of local
       checkpoints and minimize the occurrence of issues
       relating to Error 410 (REDO log overloaded) during LCPs,
       NDB now implements adaptive LCP control, which moderates
       LCP scan priority and LCP writes according to redo log
       usage.
       The following changes have been made with regard to NDB
       configuration parameters:

          + The default value of RecoveryWork is increased from
            50 to 60 (60% of storage reserved for LCP files).

          + The new InsertRecoveryWork parameter controls the
            percentage of RecoveryWork that is reserved for
            insert operations. The default value is 40 (40% of
            RecoveryWork); the minimum and maximum are 0 and 70,
            respectively. Increasing this value allows for more
            writes during an LCP, while limiting the total size
            of the LCP. Decreasing InsertRecoveryWork limits the
            number of writes used during an LCP, but results in
            more space being used.
       Implementing LCP control provides several benefits to NDB
       deployments. Clusters should now survive heavy loads
       using default configurations much better than previously,
       and it should now be possible to run them reliably on
       systems where the available disk space is approximately
       2.1 times the amount of memory allocated to the cluster
       (that is, the amount of DataMemory) or more. It is
       important to bear in mind that the figure just cited does
       not account for disk space used by tables on disk.
       During load testing into a single data node with
       decreasing redo log sizes, it was possible to
       successfully load a very large quantity of data into NDB
       with 16GB reserved for the redo log while using no more
       than 50% of the redo log at any point in time.
       See What is New in NDB Cluster 7.6
       (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-
        what-is-new-7-6.html), as well as the descriptions of the
       parameters mentioned previously, for more information.
       (Bug #90709, Bug #27942974, Bug #27942583)
       References: See also: Bug #27926532, Bug #27169282.

Bugs Fixed

     * ndbinfo Information Database: It was possible following a
       restart for (sometimes incomplete) fallback data to be
       used in populating the ndbinfo.processes table, which
       could lead to rows in this table with empty process_name
       values. Such fallback data is no longer used for this
       purpose. (Bug #27985339)

     * NDB Client Programs: The executable file host_info is no
       longer used by ndb_setup.py. This file, along with its
       parent directory share/mcc/host_info, has been removed
       from the NDB Cluster distribution.
       In addition, installer code relating to an unused
       dojo.zip file was removed. (Bug #90743, Bug #27966467,
       Bug #27967561)
       References: See also: Bug #27621546.

     * MySQL NDB ClusterJ: ClusterJ could not be built from
       source using JDK 9. (Bug #27977985)

     * Local checkpoints did not always handle DROP TABLE
       operations correctly. (Bug #27926532)
       References: This issue is a regression of: Bug #26908347,
       Bug #26968613.

     * During the execution of CREATE TABLE ... IF NOT EXISTS,
       the internal open_table() function calls
       ha_ndbcluster::get_default_num_partitions() implicitly
       whenever open_table() finds out that the requested table
       already exists. In certain cases,
       get_default_num_partitions() was called without the
       associated thd_ndb object being initialized, leading to
       failure of the statement with MySQL error 157 Could not
       connect to storage engine. Now
       get_default_num_partitions() always checks for the
       existence of this thd_ndb object, and initializes it if
       necessary.

On behalf MySQL RE team at Oracle
-Sreedhar S 

Dear MySQL users,

MySQL Router 8.0.12 is the second GA release for MySQL Router 8.0 series.

MySQL Router 8.0 is highly recommended for use with MySQL Server 8.0 and 5.7.
Please upgrade to MySQL Router 8.0.12.

The MySQL Router is a new building block for high availability solutions
based on MySQL InnoDB clusters.

By taking advantage of the new Group Replication technology, and
combined with the MySQL Shell, InnoDB clusters provide an integrated
solution for high availability and scalability for InnoDB based MySQL
databases, that does not require advanced MySQL expertise.

The deployment of applications with high availability requirements is
greatly simplified by MySQL Router. MySQL client connections are
transparently routed to online members of a InnoDB cluster, with MySQL
server outages and cluster reconfigurations being automatically handled
by the Router.

To download MySQL Router 8.0.12, see the "Generally Available (GA)
Releases" tab at http://dev.mysql.com/downloads/router. Package
binaries are available for several platforms and also as a source code
download.

Documentation for MySQL Router can be found at
http://dev.mysql.com/doc/mysql-router/en/

Enjoy!

Changes in MySQL Router 8.0.12   (2018-07-27)

   MySQL Router 8 fully supports MySQL 5.7 and MySQL 8, and it
   replaces the MySQL Router 2.x series. If you currently use
   Router 2.0 or 2.1 then we recommend upgrading your
   installation to MySQL Router 8.

Functionality Added or Changed

     * Added the --master-key-reader and --master-key-writer
       options to decouple key (credentials) retrieval from
       daemon startup, as an alternative to using
       master_key_file.

     * Added the optional --account-host command-line bootstrap
       option to configure the host pattern used for MySQL
       accounts. The default value is '%'.

     * Added the optional --report-host command-line bootstrap
       option to configure Router's externally visible hostname
       that's registered to the MySQL InnoDB cluster metadata
       store.

     * The ttl option now accepts floating point values. The
       default ttl value changed from 5 seconds to 0.5 seconds
       (500 milliseconds), and the maximum allowed value changed
       from 4294967295 to 3600.

     * Two new metadata-cache URI options were added:
       disconnect_on_promoted_to_primary controls whether
       existing client connections to a secondary are closed
       when the secondary is promoted as a primary (default=no),
       and disconnect_on_metadata_unavailable controls whether
       existing client connections are closed when the group is
       overloaded (default=no). See the destinations
       configuration option's documentation for additional
       information.

     * A mysql-server-mock tool was added to help make group
       replication testing more predictable. Execute
       mysql-server-mock --help for usage details.

Bugs Fixed

     * If querying the metadata server failed, then the metadata
       refresh process would fail and log an error. Now the
       system will attempt to use alternative metadata servers
       instead of only one. (Bug #28082473)

     * When a primary or secondary node goes missing, the
       metadata cache refresh frequency increases to one second
       until the Group Replication status is confirmed. The log
       messages and code comments suggested that this mechanism
       only applies to missing primaries, so they were updated
       to clarify that missing secondaries also increase the
       frequency to one second. (Bug #28059228)

     * Exiting a running router instance by issuing Control + C
       emitted an exception before quitting the process. (Bug
       #27802114)

     * Support to compile with Visual Studio 15 2017 was added.
       (Bug #27691313)

     * The optional thread_stack_size configuration option was
       added to define the allocated thread stack size for each
       thread. It is measured in kilobytes and defaults to 64
       with a valid range of 1 to 65535. (Bug #27634367)

     * On Windows, PDB files were added to the Zip download for
       debugging purposes. (Bug #27531828, Bug #89625)

On behalf of Oracle MySQL Release Team
Sreedhar S 

Changes in MySQL 8.0.12 (2018-07-27)


     * Audit Log Notes

     * Compilation Notes

     * Configuration Notes

     * Function Notes

     * Logging Notes

     * MySQL Enterprise Notes

     * Optimizer Notes

     * Packaging Notes

     * Performance Schema Notes

     * Plugin Notes

     * Security Notes

     * Spatial Data Support

     * SQL Syntax Notes

     * X Plugin Notes

     * Functionality Added or Changed

     * Bugs Fixed

Audit Log Notes


     * For new MySQL installations, the USER and HOST columns in
       the audit_log_user table used by MySQL Enterprise Audit
       now have definitions that better correspond to the
       definitions of the User and Host columns in the
       mysql.user system table.
       For upgrades to an installation for which MySQL
       Enterprise Audit is already installed, it is recommended
       that you alter the table definitions as follows:
ALTER TABLE mysql.audit_log_user
  DROP FOREIGN KEY audit_log_user_ibfk_1;
ALTER TABLE mysql.audit_log_filter
  CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_as_ci;
ALTER TABLE mysql.audit_log_user
  CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_as_ci;
ALTER TABLE mysql.audit_log_user
  MODIFY COLUMN USER VARCHAR(32);
ALTER TABLE mysql.audit_log_user
  ADD FOREIGN KEY (FILTERNAME) REFERENCES mysql.audit_log_filter(NAME)
;

       (Bug #23706056)

Compilation Notes


     * Microsoft Windows: For OpenSSL 1.1, the library names
       have changed for Windows. The CMake configuration code
       now accounts for this. Also, it is now possible on
       Windows to use -DWITHOUT_SERVER=1 to build 32-bit client
       binaries. (Bug #28170711, Bug #91223)

     * The minimum version of the Boost library for server
       builds is now 1.67.0. (Bug #27866110)

Configuration Notes


     * For RelWithDebInfo builds on Linux, REPRODUCIBLE_BUILD
       now defaults to ON. (Bug #27483447)

     * The default value for the slave_pending_jobs_size_max
       system variable has increased from 16M to 128M. On a
       multi-threaded slave ( with slave_parallel_workers > 0),
       this value sets the maximum amount of memory that is made
       available to slave worker queues holding events that have
       not yet been applied. The potentially larger memory usage
       should be taken into account when calculating the
       resources required to deploy a multi-threaded slave.
       Masters and single-threaded slaves are not affected by
       this setting.
       The new default is double the recently increased default
       value specified by the max_allowed_packet system variable
       (now 64M). The value of slave_pending_jobs_size_max is a
       soft limit, so events larger than its value (consisting
       of one or more packets) can be queued and processed.
       However, a large transaction is held until all the slave
       workers have empty queues, and then processed. All
       subsequent transactions are held until the large
       transaction has been completed. The delay to clear the
       queues of all the slave workers and the wait to queue
       subsequent transactions can cause lag on the replication
       slave and decreased concurrency of the slave workers. The
       value of slave_pending_jobs_size_max should therefore be
       set high enough to accommodate most expected event sizes.

Function Notes


     * The BIT_AND(), BIT_OR(), and BIT_XOR() aggregate
       functions now can be used as window functions, if an OVER
       clause is present. See Aggregate (GROUP BY) Function
       Descriptions
       (http://dev.mysql.com/doc/refman/8.0/en/group-by-functions.html).

Logging Notes


     * Previously, log components listed in the
       log_error_services system variable had to be separated by
       semicolons. Components now can be separated by commas. A
       given setting cannot use both semicolon and comma
       separators. (Bug #27788925, Bug #90268)

MySQL Enterprise Notes


     * The MySQL Enterprise Firewall firewall_whitelist table
       now contains a primary key column named ID. (Bug
       #27164826)

Optimizer Notes


     * The filesort algorithm (used by the optimizer to satisfy
       an ORDER BY clause when no index can be used) is now more
       memory efficient. The primary change is that the
       optimizer allocates memory buffers incrementally as
       needed, up to the size indicated by the sort_buffer_size
       system variable, rather than allocating a fixed amount of
       sort_buffer_size bytes up front. This enables users to
       set sort_buffer_size to larger values to speed up larger
       sorts, without concern for excessive memory use for small
       sorts. (This benefit may not occur for multiple
       concurrent sorts on Windows, which has a weak
       multithreaded malloc.)
       In addition, filesort is less pessimistic with respect to
       worst-case scenarios. Previously, filesort produced an
       error without starting if merge operations or sort-key
       generation might fail. Now, because the worst case is
       unlikely to occur in practice, filesort produces an error
       only for actual rather than prospective failures.

     * Previously, extended EXPLAIN output was produced only for
       SELECT statements. Extended output is now produced for
       INSERT, REPLACE, UPDATE, and DELETE statements as well.
       (To display extended output, use SHOW WARNINGS following
       EXPLAIN. See Extended EXPLAIN Output Format
       (http://dev.mysql.com/doc/refman/8.0/en/explain-extended.html).)

Packaging Notes


     * Docker disables NUMA-related operations by default, so
       the mysqld included in Docker images now has NUMA support
       disabled so that the error log does not fill with NUMA
       warnings. (Bug #28081363)

     * RPM .spec files were updated to reflect the removal of
       yaSSL and that OpenSSL is the default SSL library for all
       builds. (Bug #28025427)

     * For generic Linux .tar.gz distributions, the mysqlxtest
       client has been moved from the server package to the test
       package. (Bug #27744137)

     * An RPM package for installing ARM 64-bit (aarch64)
       binaries of MySQL Server on Oracle Linux 7 is now
       available in the MySQL Yum Repository and for direct
       download.
       Known Limitation for this ARM release: You must enable
       the Oracle Linux 7 Software Collections Repository
       (ol7_software_collections) to install this package, and
       must also adjust the libstdc++7 path. See Yum's Platform
       Specific Notes
(http://dev.mysql.com/doc/refman/8.0/en/linux-installation-yum-repo.html#yum-install-platform-specifics)
       for additional details.

Performance Schema Notes


     * The maximum value was increased from 256 to 1024 for
       these Performance Schema system variables:
performance_schema_max_cond_classes
performance_schema_max_file_classes
performance_schema_max_mutex_classes
performance_schema_max_rwlock_classes
performance_schema_max_socket_classes
performance_schema_max_stage_classes
performance_schema_max_thread_classes

       The default value was increased from 250 to 300 for this
       Performance Schema system variable:
performance_schema_max_mutex_classes

       (Bug #27647918)

Plugin Notes


     * Previously, the Rewriter query rewrite plugin permitted
       rewriting only for SELECT statements. Rewritable
       statements now include INSERT, REPLACE, UPDATE, and
       DELETE as well. See The Rewriter Query Rewrite Plugin
(http://dev.mysql.com/doc/refman/8.0/en/rewriter-query-rewrite-plugin.html).

Security Notes


     * The linked OpenSSL library for MySQL Server has been
       updated to version 1.0.2o. Issues fixed in the new
       OpenSSL version are described at
       http://www.openssl.org/news/vulnerabilities.html. (Bug
       #28025379)

Spatial Data Support


     * Incompatible Change: The new spatial functions
       ST_Longitude() and ST_Latitude() return the longitude or
       latitude, respectively, of their Point argument. If
       called with a second argument, these functions use the
       argument to set the longitude or latitude, respectively,
       of their Point argument.
       In addition, the ST_X() and ST_Y() functions now
       interpret their Point argument according to its spatial
       reference system definition (SRS):

          + ST_X() returns the coordinate value of the axis that
            appears first in the SRS definition, and ST_Y()
            returns the coordinate value of the axis that
            appears second in the SRS definition.

          + If ST_X() and ST_Y() are used to set the longitude
            or latitude of a Point argument that has a
            geographic SRS, the longitude or latitude value must
            be in the proper range for the SRS, or an error
            occurs.
       Note
       If spatial data contains geometry values that now are
       interpreted differently by ST_X() and ST_Y(), existing
       queries using these functions will return different
       results, compared to previous MySQL versions.
       (Bug #27125600, Bug #88503)

     * The EPSG Dataset containing spatial reference system data
       for spatial calculations has been upgraded from version
       9.2 to 9.3. (Bug #27977721)

     * Previously, the parser recognized USING RTREE in index
       specifications, but this could not be specified for any
       storage engine. Now USING RTREE is permitted for spatial
       index specifications. (Bug #27836608)

     * Indexes on geometry columns now must be spatial indexes.
       Consequently, the SPATIAL keyword is optional but
       implicit for creating an index on a spatial column. A
       spatial index on a geometry column is not permitted for a
       primary key or unique index. Also, ASC and DESC are not
       permitted for spatial indexes. (Bug #21087676)

SQL Syntax Notes


     * Explicit ASC or DESC qualifiers for GROUP BY clauses are
       now deprecated and will be removed in a future MySQL
       version.

X Plugin Notes


     * Authentication errors returned from a MySQL 8.0.11 server
       to an X Plugin client were marked as fatal, which caused
       the client to stop attempting its automatic sequence of
       authentication attempts using different methods. X Plugin
       now ignores fatal authentication errors, and subsequent
       expected errors such as write timeout errors, while the
       sequence of authentication attempts is in progress. If
       none of the authentication methods tried are successful,
       X Plugin now selects and returns the most relevant error
       message received from the server, which is not
       necessarily the last error message received. (Bug
       #28135006)

     * During the X Plugin automated authentication sequence,
       connection attempts are made using different
       authentication methods in a pre-set sequence. X Plugin
       checks before starting the sequence whether the
       connection uses SSL or not, and does not attempt
       connection with the PLAIN authentication method if the
       connection is not encrypted. For additional verification,
       a check and error were added so that the PLAIN
       authentication method is disallowed if attempted when the
       connection is not encrypted. (Bug #27691189)

     * In the event of an authentication failure, X Plugin
       always returned the error code ER_ACCESS_DENIED, with a
       custom X Protocol error message for the error situation.
       The error codes that are received from the MySQL server
       for authentication failures are now passed on to the
       client instead, with the standard MySQL error messages
       that go with them. (Bug #27675699)

     * During the X Plugin automated authentication sequence,
       where connection attempts are made using different
       authentication methods in a pre-set sequence, the error
       returned after every failed connection attempt was marked
       with the severity FATAL. Now, the errors are marked as
       ERROR while there are still other authentication methods
       to be attempted, and only the final error that results in
       disconnection is marked as FATAL. (Bug #27636947)

     * The X Plugin code was being compiled twice with different
       preprocessor definitions. (Bug #27267054)

     * A number of improvements were made to the handling of
       authentication issues by X Plugin:

          + The X Plugin automated authentication sequence,
            where connection attempts are made using different
            authentication methods in a pre-set sequence, is now
            halted if an error response indicates that the
            connection has been broken or reads or writes are
            timing out.

          + The automated authentication sequence is also now
            halted in the event of any fatal error.

          + The last significant error is now reported for an
            abandoned authentication sequence, not just the last
            error that occurred.

          + A more specific error code and message are now
            reported if authentication with the
            caching_sha2_password authentication plugin is
            attempted over an unsecure connection.
       (Bug #27257774)

     * In some circumstances, a MySQL server with X Plugin
       loaded could experience an unexpected halt during a
       shutdown process initiated by a failed start or by the
       RESTART command. The issue has now been fixed. (Bug
       #25474793, Bug #27259783)

Functionality Added or Changed


     * Important Change; Replication: Use the
       group_replication_exit_state_action option to configure
       how Group Replication behaves when a server instance
       leaves the group unintentionally, for example after
       encountering an applier error. When
       group_replication_exit_state_action is set to
       ABORT_SERVER, the instance shuts itself down, and when
       group_replication_exit_state_action is set to READ_ONLY
       the server switches itself to super read only mode
       instead.

     * InnoDB: InnoDB now supports ALGORITHM=INSTANT for the
       following ALTER TABLE operations:

          + Adding a column. This feature is referred to as
            "Instant ADD COLUMN".

          + Adding or dropping a virtual column.

          + Adding or dropping a column default value.

          + Modifying the definition of an ENUM or SET column.

          + Changing the index type.

          + Renaming a table.
       Operations that support ALGORITHM=INSTANT only modify
       metadata in the data dictionary. No exclusive metadata
       locks are taken on the table during preparation and
       execution phases of the operation, and table data is
       unaffected, making the operations instantaneous. If not
       specified explicitly, ALGORITHM=INSTANT is used by
       default by operations that support it. If
       ALGORITHM=INSTANT is specified but not supported, the
       operation fails immediately with an error.
       For more information about operations that support
       ALGORITHM=INSTANT, see Online DDL Operations
(http://dev.mysql.com/doc/refman/8.0/en/innodb-create-index-overview.html).
       Thanks to the Tencent Games DBA team for the
       contribution.

     * InnoDB: Undo logging is now supported for small updates
       to large object (LOB) data, which improves performance of
       LOB updates that are 100 bytes in size or less.
       Previously, LOB updates were a minimum of one LOB page in
       size, which is less than optimal for updates that might
       only modify a few bytes. This enhancement builds upon
       support added in MySQL 8.0.4 for partial fetch and update
       of LOB data.

     * Replication: Information about XCom's memory usage has
       been added to the Performance Schema tables. The
       setup_instruments table now has an entry corresponding to
       the XCom cache, and the
       memory_summary_global_by_event_name table contains the
       memory usage statistics of the XCom cache.

     * Microsoft Windows: On Windows, the forking used to
       implement RESTART was suppressible using the --gdb
       option. However, this was a side effect, performed in
       addition to the other option actions done to set up a
       debugging environment. In non-debug settings, the new
       --no-monitor option may be used for the sole purpose of
       suppressing forking the monitor process. For a server
       started with either --gdb or --no-monitor, executing
       RESTART causes the server to simply exit without
       restarting. (Bug #27801043)

     * Checking for foreign key relationships by DROP TABLE and
       DROP DATABASE was improved. Parent and child tables now
       can be dropped in arbitrary order, as long as they are
       dropped by the same DROP TABLE statement. In addition,
       error reporting was improved for attempts to drop a
       parent table without dropping a child table. (Bug
       #27821060)

     * When support for roles was added, the ADMIN keyword
       became a reserved keyword. ADMIN is now once again a
       nonreserved keyword. (Bug #27814204)

     * When a client shuts down the server, the server now
       writes a message to the error log indicating which user
       performed this action. (Bug #26246628, Bug #86635)

     * Previously, for the --ssl-mode=VERIFY_IDENTITY option,
       the client checked whether the host name that it used for
       connecting matched the Common Name value in the
       certificate but not the Subject Alternative Name value.
       Now, if the client uses OpenSSL 1.0.2 or higher, the
       client checks whether the host name matches either the
       Subject Alternative Name value or the Common Name value
       in the server certificate. Thanks to Daniël van Eeden for
       the patch. (Bug #16211011, Bug #68052, Bug #27511233, Bug
       #89578)

Dear MySQL users,

MySQL Enterprise Backup v4.1.2, a new version of the MySQL backup tool, is
now available for download from the My Oracle Support (MOS) website
as our latest GA release. This release will be available on eDelivery (OSDC)
after the next upload cycle. MySQL Enterprise Backup is a commercial
extension to the MySQL family of products.

MySQL Enterprise Backup 4.1.2 only supports MySQL 5.7.
For MySQL 5.6 and earlier, use MySQL Enterprise Backup 3.12.
For MySQL 8.0, use MySQL Enterprise Backup 8.0.

A brief summary of the changes in MySQL Enterprise Backup (MEB)
version 4.1.2 is given below.

Changes in MySQL Enterprise Backup 4.1.2     (2018-07-27)

Functionality Added or Changed

     * Important Change: Starting from release 4.1.2, the
       storage engine of the mysql.backup_history table on a
       backed-up server has switched from CSV to InnoDB. MySQL
       Enterprise Backup 4.1.2 automatically migrates the table
       when it performs its first backup task on a server backed
       up by 4.1.0 and 4.1.1 before. See Upgrading MySQL
       Enterprise Backup from 4.1.1 or earlier
       (http://dev.mysql.com/doc/mysql-enterprise-backup/4.1/en/
       mysqlbackup.privileges.html#meb-upgrade-to-4.1.2) for the
       new user privileges required by mysqlbackup for the
       mandatory migration to happen.

     * Important Change: When working with a Group Replication
       (http://dev.mysql.com/doc/refman/5.7/en/group-replication
       .html) setup, mysqlbackup now makes the backup history
       available to all members of the server group by making
       sure that the backup_history table is updated on a
       primary node after each mysqlbackup operation. See Using
       MySQL Enterprise Backup with Group Replication
       (http://dev.mysql.com/doc/mysql-enterprise-backup/4.1/
       en/meb-group-replication.html) for details.
       With the implementation of this feature, the new user
       privilege of SELECT on
       performance_schema.replication_group_members is now
       required by mysqlbackup to work with any server, even
       when it does not belong to a Group Replication setup. See
       Grant MySQL Privileges to Backup Administrator
       (http://dev.mysql.com/doc/mysql-enterprise-backup/4.1/
       en/mysqlbackup.privileges.html) for details.

     * The backup_history table now includes a server_uuid
       column, which stores the value of the server_uuid of the
       backed up server.

     * The binary log for a backed-up server, instead of being
       restored always to the data directory on the target
       server, is now restored by default to the same location
       it was found on the backed-up server. It can also be
       restored to a different location specified with the new
       --log-bin option.

     * OAuth is now supported for Oracle Cloud Storage client
       authentication. Two new options, --cloud-storage-url and
       --cloud-oauth-token, have been introduced for the
       purpose. See Cloud Storage Options
       (http://dev.mysql.com/doc/mysql-enterprise-backup/4.1/
       en/backup-cloud-options.html) for details.

Bugs Fixed

     * A mysqlbackup operation on an image stored on an
       OpenStack cloud storage service sometimes failed with a
       segmentation fault or a bad URL error. It was because of
       a race condition caused by an uninitiated variable, which
       has been eliminated by this fix. (Bug #28189239, Bug
       #28183729)

     * A mysqlbackup operation on an image stored on an
       OpenStack cloud storage service failed with a 401
       Unauthorized error when the operation took a long time
       and the authentication token for the cloud access
       expired. With this fix, a separate thread in mysqlbackup
       requests a new token from the OpenStack cloud service in
       that situation, so that the operation can continue. (Bug
       #27893174)

     * The maximum value that could be set for the
       --safe-slave-backup-timeout option was 2700 (seconds),
       which automatically replaced any larger value. With this
       fix, there is no longer a maximum limition, even though a
       high value is not recommended; see the description of
       --safe-slave-backup-timeout for details. (Bug #27883020)

     * When mysqlbackup performed sanity checks on InnoDB
       tablespaces and found a space ID mismatch for an FSP
       header and a page header, the name of the problematic
       tablespace was not given in the error report. (Bug
       #27752703)

     * mysqlbackup issued a warning whenever the number of files
       specified in the system variable innodb_data_file_path of
       the server to be backed up exceeded 100. With this fix, a
       warning is issued only if the number of InnoDB data files
       to be opened exceeds the number specified by the system
       variable innodb_open_files. (Bug #27701402)

     * An apply-incremental-backup operation failed when
       individual tablespaces with relative file paths were
       involved. (Bug #27278876)

     * Backups created with the ---skip-unused-pages option
       failed validation by the mysqlbackup validate command.
       (Bug #27102697)

     * mysqlbackup quit unexpectedly when the --disable-manifest
       option was used in a backup operation. (Bug #26861475)

     * A restore operation for an incremental backup failed when
       individual tablespaces with relative file paths were
       involved. (Bug #26442994)

  On behalf MySQL RE team at Oracle
-Sreedhar S

Bugs Fixed


     * Important Change; JSON: The JSON_TABLE() function now
       automatically decodes base-64 values and prints them
       using the character set given by the column
       specification. (Bug #90157, Bug #27729112)
       References: See also: Bug #89847, Bug #27613276.

     * Important Change: MySQL now allows a query having a WITH
       ROLLUP modifier to use DISTINCT. See SELECT Syntax
       (http://dev.mysql.com/doc/refman/8.0/en/select.html), for
       more information. (Bug #87450, Bug #26640100)

     * Important Change: MySQL now allows the use of ORDER BY
       with grouping functions in SELECT. statements. (Bug
       #86312, Bug #27063525)

     * Important Change: MySQL now allows ORDER BY to be used in
       a query having a WITH ROLLUP modifier. For more
       information, see SELECT Syntax
       (http://dev.mysql.com/doc/refman/8.0/en/select.html).
       (Bug #86311, Bug #26073513)

     * InnoDB: New columns added to
       INFORMATION_SCHEMA.INNODB_TABLES and
       INFORMATION_SCHEMA.INNODB_COLUMNS tables in 8.0.12 did
       not appear after upgrading to 8.0.12. (Bug #28065244)

     * InnoDB: Large object (LOB) version numbers stored in LOB
       index entries were left uninitialized at 0 instead of
       initialized at 1. (Bug #28046298)

     * InnoDB: Adding a column to a table with a generated
       column raised an invalid assertion. (Bug #28040201)

     * InnoDB: An attempt to access freed memory during a
       checkpoint operation caused the server to exit. (Bug
       #28039477)

     * InnoDB: An assertion failure occurred when starting the
       server with experimental system variables that were
       unintentionally exposed in normal MySQL builds. (Bug
       #27899424, Bug #90526, Bug #27898396, Bug #90523, Bug
       #27898344, Bug #90522)

     * InnoDB: An invalid system variable setting raised an
       assertion. (Bug #27898284)

     * InnoDB: Attempting to move a table from a discarded
       file-per-table tablespace to a shared tablespace raised
       an assertion. The operation now produces an error
       instead. (Bug #27861972)

     * InnoDB: Potential failures related to page allocation for
       large objects (LOBs) were not sufficiently handled. (Bug
       #27852003)

     * InnoDB: The ngram full-text search parser permitted comma
       and period characters to be tokenized as words, which
       caused an inconsistency between boolean and natural
       language mode search results. Comma and period characters
       are no longer tokenized. (Bug #27847697)

     * InnoDB: Checksum mismatches and other issues were caused
       by concurrent modification of a tablespace header page,
       and attempting to place a lock on a partially initialized
       page. (Bug #27823064)

     * InnoDB: An I/O error returned by an fsync() operation is
       now treated as a hard error. (Bug #27805553, Bug #90296)

     * InnoDB: In a single thread, two minitransactions latched
       the first page of a large object value (LOB) while
       another thread attempted to allocate the page, causing a
       deadlock. (Bug #27777959)

     * InnoDB: After upgrading to MySQL 8.0.12, table columns
       including the FTS_DOC_ID column were missing from the
       INFORMATION_SCHEMA.INNODB_COLUMNS table. (Bug #27774145)

     * InnoDB: An invalid assertion was raised when the
       optimizer chose a prefix index defined on a virtual
       column. (Bug #27755892)
       References: This issue is a regression of: Bug #19806106.

     * InnoDB: An in-memory table object for a table being
       truncated could be opened under improper metadata locking
       protection.
       A new method of preserving the AUTOINC counter value
       during a TRUNCATE PARTITION operation was implemented.
       (Bug #27754995)

     * InnoDB: The Variance-Aware Transaction Scheduling
       algorithm (VATS) tracks the number of transactions
       waiting for another transaction. In the case of a
       deadlock, the method by which the number of waiting
       transactions is approximated produced inflated values.
       (Bug #27646322)

     * InnoDB: Attempting to acquire an InnoDB ticket while
       holding a victim transaction lock caused a lock order
       violation. (Bug #27626681)
       References: This issue is a regression of: Bug #23476050.

     * InnoDB: An attempt to read a zero-length BLOB value
       raised an assertion failure during recovery. The BLOB
       value was not yet completely inserted. (Bug #27617389)

     * InnoDB: A race condition occurred when acquiring a table
       lock for a table that was already in memory. (Bug
       #27586419, Bug #27577704)
       References: This issue is a regression of: Bug #26848711.

     * InnoDB: After restarting the server, attempting to create
       an encrypted table returned a generic error from the
       storage engine. (Bug #27577339)

     * InnoDB: The use of Variance-Aware Transaction Scheduling
       (VATS) with a spatial index caused a transaction to wait
       indefinitely. (Bug #27572937)

     * InnoDB: Incorrect parsing of a tablespace name that
       included multibyte characters caused a DROP DATABASE
       operation to fail. (Bug #27566937)

     * InnoDB: A check performed to identify temporary tables
       caused an error when the data dictionary attempted to
       open a partitioned table. (Bug #27565997)

     * InnoDB: A schema mismatch error reported during an import
       tablespace operation failed to print mismatched table
       flags in a readable format. (Bug #27542720)

     * InnoDB: A DDL operation failed to wait for a FULLTEXT
       index optimization operation to finish. (Bug #27326796)
       References: This issue is a regression of: Bug #24938374.

     * InnoDB: An unnecessary check for read-only transactions
       was removed from the trx_set_rw_mode() function. Thanks
       to Sandeep Sethia for the patch. (Bug #27211287, Bug
       #88739)

     * InnoDB: A DDL operation that added a foreign key
       constraint raised an assertion when it accessed a stale
       memory object that belonged to the parent table. (Bug
       #27208858)

     * InnoDB: A failing assertion occurred after initiating a
       memcached get operation. (Bug #26876594)

     * InnoDB: A corrupt index ID encountered during a foreign
       key check raised an assertion. (Bug #26654685)

     * InnoDB: A DROP TABLE operation on a table residing in a
       general tablespace raised an assertion when checking
       index status in the post-DDL phase of the operation. (Bug
       #26523254)

     * InnoDB: An internal deadlock during a DDL operation
       resulted in a long semaphore wait followed by a server
       exit. (Bug #26225783)

     * InnoDB: A DDL operation encountered a serious error due
       to an invalid lock upgrade. (Bug #26225783)

     * InnoDB: On a Windows 64-bit system, invalid buffer pool
       configuration values caused the server to exit on
       startup. (Bug #26100239, Bug #86370)

     * InnoDB: A debug code block related to mutex type
       definitions was removed. It no longer differed from the
       non-debug version of the code block. (Bug #24952279, Bug
       #83529)

     * InnoDB: A server failure during recovery occurred due to
       a log parsing buffer overflow. Space is now allocated to
       the log parsing buffer dynamically and incremented as
       necessary until it reaches the size specified by
       innodb_log_buffer_size. (Bug #24734190)

     * Packaging: On Windows, the mysqld.exe --help command
       displayed unnecessary and unexpected details in the
       system output, which this fix eliminates. (Bug #27894020)

     * Partitioning: Rollback of ALTER TABLE ... TRUNCATE
       PARTITION statements was not handled correctly. (Bug
       #27603025)
       References: See also: Bug #87562, Bug #26710839.

     * Partitioning: For a partitioned table, partition update
       time could be incorrect after rebuilding the table or
       restarting the server. (Bug #27073100)

     * Replication: The gtid_purged variable contains the binary
       log events that have been purged from the log by the
       server. When running the Group Replication plugin this
       variable should never be modified, but it was possible.
       Now the variable cannot be modified when Group
       Replication is running. (Bug #27724561)

     * Replication: If the option --skip-log-bin was specified
       at server startup to disable binary logging, no warning
       message was issued if both expire_logs_days and
       binlog_expire_logs_seconds were set to a nonzero value.
       The --skip-log-bin option meant there were no binary log
       files to expire, so the outcome of these binary log
       expiration period settings (which is that the
       expire_logs_days value is ignored) had no practical
       effect. However, the warning message is now issued, so
       that the situation can be corrected before binary logging
       is enabled for the server. (Bug #27699608)

     * Replication: The PIT_TRANSACTIONS_NEGATIVE_CERTIFIED, the
       PIT_TRANSACTIONS_ROWS_VALIDATING and the
       PIT_TRANSACTIONS_LOCAL_ROLLBACK member messages were not
       being correctly decoded. (Bug #27692831)

     * Replication: The log messages generated when a member
       fails to join the group have been improved, for example
       when group_replication_group_name on the member joining
       the group does not match the seed's
       group_replication_group_name this is now described in the
       log message. (Bug #27628695)

     * Replication: The SYSTEM_VARIABLES_ADMIN and
       PERSIST_RO_VARIABLES_ADMIN privileges have been added to
       the mysql.session_user. (Bug #27621869)

     * Replication: The
       ER_GRP_RPL_SQL_SERVICE_FAILED_TO_RUN_SQL_QUERY error was
       being logged incorrectly. (Bug #27590534)

     * Replication: If a MySQL server is started in crash
       recovery mode with an innodb_force_recovery setting of 4
       or greater, which places InnoDB into read-only mode, the
       semisynchronous replication master plugin should not be
       initialized. Due to a change in plugin initialization
       order in MySQL 8.0, the server assumed that if the plugin
       was registered, it had also been initialized, and
       incorrectly attempted to deinitialize it. The handling of
       this plugin in crash recovery mode has now been corrected
       so that the deinitialization function is not executed
       when the plugin has not been initialized. (Bug #27481872)

     * Replication: You can now use a shell pipe to supply an
       archive of compressed binary log files to mysqlbinlog as
       streamed input. Previously, the files had to be extracted
       separately before passing them to mysqlbinlog. Thanks to
       the Facebook team for this contribution.
       In this example, binlog-files_1.gz contains multiple
       binary log files for processing. The pipeline extracts
       the contents of binlog-files_1.gz, pipes the binary log
       files to mysqlbinlog as standard input, and pipes the
       output of mysqlbinlog into the mysql client for
       execution:
gzip -cd binlog-files_1.gz | ./mysqlbinlog - | ./mysql -uroot -p
       (Bug #27445278, Bug #89423)
       References: See also: Bug #27836543.

     * Replication: The use of replication filters or binary log
       filters can cause issues when they are applied to tables
       that are updated with XA transactions. Filtering of
       tables could cause an XA transaction to be empty on a
       replication slave, and empty XA transactions are not
       supported. Also, with the settings
       master_info_repository=TABLE and
       relay_log_info_repository=TABLE on a replication slave,
       which became the defaults in MySQL 8.0, the internal
       state of the data engine transaction is changed following
       a filtered XA transaction, and can become inconsistent
       with the replication transaction context state.
       Due to these issues, the use of replication filters or
       binary log filters in combination with XA transactions is
       not supported. This fix adds the new error
       ER_XA_REPLICATION_FILTERS, which is logged whenever an XA
       transaction is impacted by a replication filter, whether
       or not the transaction was empty as a result. If the
       transaction is not empty, the replication slave is able
       to continue running, but you should take steps to
       discontinue the use of replication filters with XA
       transactions in order to avoid potential issues. If the
       transaction is empty, the replication slave stops. In
       that event, the replication slave might be in an
       undetermined state in which the consistency of the
       replication process might be compromised. In particular,
       the gtid_executed set on a slave of the slave might be
       inconsistent with that on the master. To resolve this
       situation, isolate the master and stop all replication,
       then check GTID consistency across the replication
       topology. Undo the XA transaction that generated the
       error message, then restart replication. (Bug #27442477)

     * Replication: When mysqlbinlog was used to read a binary
       log event larger than 128KB, the read failed because
       128KB was returned as the size, instead of the actual
       size. The issue has now been fixed. Thanks to the
       Facebook team for the patch. (Bug #27417084, Bug #89326)

     * Replication: When a transaction larger than the binary
       log transaction cache size (binlog_cache_size) was
       flushed to a temporary file during processing, and the
       flush failed due to a lack of space in the temporary
       directory, the flush error was not handled correctly. No
       message was written to the error log, and the binary log
       cache was not cleared after the transaction was rolled
       back. Now, in this situation, the server takes an
       appropriate action based on the binlog_error_action
       setting (shut down the server or halt logging), and
       writes a message to the error log. When the transaction
       is rolled back, the server checks for flush errors and
       clears the binary log cache if any occurred. (Bug
       #27399620, Bug #89272)

     * Replication: When GTIDs are in use for replication,
       replicated transactions that are filtered out on the
       slave are persisted. If binary logging is enabled on the
       slave, the filtered-out transaction is written to the
       binary log as a Gtid_log_event followed by an empty
       transaction containing only BEGIN and COMMIT statements.
       If binary logging is disabled, the GTID of the
       filtered-out transaction is written to the
       mysql.gtid_executed table. This process ensures that
       there are no gaps in the set of executed GTIDs, and that
       the filtered-out transactions are not retrieved again if
       the slave reconnects to the master. Previously, this
       process was not done for CREATE DATABASE, ALTER DATABASE,
       and DROP DATABASE statements, but it is now carried out
       for those statements as well as for others. (Bug
       #27308751, Bug #88891)

     * Replication: On a multithreaded slave, when a STOP SLAVE
       statement is executed on the slave, followed by a START
       SLAVE statement, the error log can report a different
       position in the binary log for the slave SQL thread when
       exiting, compared to the position reported for the slave
       SQL thread at the subsequent initialization.
       For a multithreaded slave, the position reported for the
       SQL thread on exit is a low water mark, up to which the
       replication stream is consistent and has no gaps.
       Transactions appearing before the position are guaranteed
       to have committed, but transactions after the position
       may have committed or not. However, this low water mark
       was being reported before the process to stop the worker
       threads was actually carried out, and the low water mark
       was subsequently updated by a checkpoint routine during
       that process. The timing of the log message has now been
       changed so that the final low water mark is reported as
       the position for the SQL thread on exit. (Bug #27300658)

     * Replication: Using group_replication_force_members to
       unblock a group, for example after losing majority,
       sometimes failed with error 1231. (Bug #26394418)

     * Replication: In certain situations, such as during
       distributed recovery procedure, the certification info
       garbage collection was purging more data than it should,
       resulting in conflicts not being detected. The garbage
       collection procedure has been improved to take this case
       in consideration. (Bug #89938, Bug #27652526)

     * Replication: When the group_replication_applier channel's
       applier thread encountered an error, the master_log_name
       and end_log_pos in the error message were incorrect. In
       Group Replication, the events of a transaction are
       replicated before they are written to the binary log of
       the member where the transaction originated. The result
       is that the final master_log_name and the end_log_pos of
       those events are unknown at the time they are applied on
       the replica by group_replication_applier channel's
       applier thread. To avoid confusion, now any such error
       messages encountered by a group_replication_applier
       channel do not contain the binary log name and the binary
       log position. (Bug #89146, Bug #27368735)

     * Microsoft Windows: For debug builds on Windows, CREATE
       SPATIAL REFERENCE SYSTEM with an empty definition string
       could raise assertions. (Bug #27672683)

     * In the client library, signals were incorrectly unblocked
       for ppoll(). Thanks to Facebook for the patch. (Bug
       #28075623, Bug #90999, Bug #28096808, Bug #91067)

     * Certain ALTER TABLE statements could disable table
       encryption. (Bug #28045585)
       References: This issue is a regression of: Bug #27389878.

     * Under some conditions, MyISAM code compilation failed due
       to a missing include file. (Bug #28039150, Bug #90898)

     * The REGEXP_REPLACE() function truncated its result when
       used in an UPDATE statement. (Bug #28027093, Bug #90870)

     * REGEXP_REPLACE() results from one result set row could
       carry forward to the next row, resulting in accumulation
       of previous results in the current row. (Bug #27992118,
       Bug #90803)

     * A heap overflow vulnerability in the MySQL client library
       was fixed. (Bug #27980823)

     * Users who had the SUPER privilege were not permitted to
       modify the keyring_operations system variable. (Bug
       #27976270)

     * Full-text search auxiliary tables created in MySQL 5.7
       and MySQL 8.0.11 with timestamps of 0 caused a data
       dictionary upgrade failure when upgrading from MySQL
       8.0.11 to MySQL 8.0.12. (Bug #27960500)

     * A "source and destination overlap in memcpy" Valgrind
       error was returned when upgrading from MySQL 5.7. (Bug
       #27945658, Bug #90691)

     * The following data dictionary enhancements were
       introduced:

          + An internal method was added to protect against
            global read locks. The method is called before
            storing, updating, or dropping data dictionary
            objects.

          + Assertion code was added to the data dictionary API
            to protect against global read locks when storing,
            updating, or dropping data dictionary objects.

          + Protection is now implicitly acquired against backup
            locks and global read locks when an exclusive
            metadata lock is acquired by a storage engine.

          + A cost model cache validity check is now performed
            before releasing a cost model entry.

          + A data dictionary API function was added for
            committing and rolling back transactions, and for
            releasing transactional meta data locks.
       (Bug #27937059)

     * Linux binaries were unable to dump core after executing a
       setuid() call. (Bug #27929894, Bug #90642, Bug #23337428,
       Bug #21723)

     * RESET PERSIST did not flush variable values from memory.
       (Bug #27924206)

     * Previously, successful assignments to the
       dragnet.log_error_filter_rules system variable resulted
       in a Note and a nonzero warning count. To avoid
       generating a diagnostic for a successful operation, this
       Note is no longer generated. Instead, the dragnet.Status
       status variable can be consulted to determine the result
       of the most recent assignment to
       dragnet.log_error_filter_rules. (Bug #27910708, Bug
       #90571)

     * For debug builds, using CREATE TABLE ... SELECT to create
       a table with a long numeric string and indexing the
       column could lead to an assertion being raised. (Bug
       #27909771)

     * For debug builds, RESET PERSIST for an unknown variable
       could cause an assertion to be raised. (Bug #27903874,
       Bug #90546)
       References: This issue is a regression of: Bug #27374791.

     * Updates to column metadata of a view referencing a
       partitioned table could cause a server exit. (Bug
       #27903842)

     * For debug builds, an assertion could be raised for UNION
       queries when computing the combined data type of a
       GEOMETRY column and SELECT * FROM (SELECT NULL). (Bug
       #27903792, Bug #90550)

     * For debug builds, starting the server with thread_stack=0
       and executing ALTER TABLE could raise an assertion. (Bug
       #27899274, Bug #90525)

     * SHOW TABLE STATUS could cause a server exit. (Bug
       #27897815)

     * For generated columns that used the INTERVAL() function,
       incorrect behavior could occur. (Bug #27881102)

     * For Fedora 28, MySQL Community RPM packages would not
       install if Connector ODBC native packages were installed.
       (Bug #27850721)

     * It was possible to drop the Performance Schema. (Bug
       #27830283)

     * A runtime error could occur for calls to
       mysql_sys_var_longlong() or String::copy(). (Bug
       #27822413, Bug #27808412)

     * An assertion was raised by error logging code that used
       an inappropriate error number. (Bug #27792903)
       References: This issue is a regression of: Bug #27462408.

     * The CONVERT TO CHARACTER SET charset_name clause for
       ALTER TABLE produced a syntax error if charset_name was
       DEFAULT. (Bug #27760787, Bug #90222)
       References: This issue is a regression of: Bug #27389878.

     * An unencrypted connection could result from a client
       connection attempt specifying that an encrypted
       connection was required, if the server was not configured
       to support SSL. (Bug #27759871)

     * INSERT INTO ... SELECT did not perform as many checks as
       INSERT INTO ... VALUES() with respect to requiring valid
       geometry values for geometry columns. (Bug #27756083)

     * REGEXP_INSTR() did not return an error message when used
       with invalid match mode flags. (Bug #27751277)

     * Some data dictionary table definitions were modified to
       align more closely with their initial design.
       Additionally, the data dictionary version number was
       incremented, and code that refers to data dictionary
       table indexes now uses symbolic index names instead of
       numeric values. (Bug #27745526, Bug #90196)

     * Executing a prepared statement to insert rows with large
       number of parameters was very slow. (Bug #27699248)

     * ibd2sdi could exit due to performing a divide-by-zero
       operation. (Bug #27692051, Bug #90071)

     * The mysql-boost-8.0.4.tar.gz source distribution omitted
       NDB sources. (Bug #27690232)

     * SHOW GRANTS could cause a server exit if executed for an
       unprivileged user who inherited privileges from an
       anonymous user. (Bug #27678129)

     * The parser incorrectly permitted the index name for
       CREATE INDEX to be empty. (Bug #27676427)

     * Failures of server restarts initiated by systemd or
       mysqld_safe were not written to the error log. (Bug
       #27675050, Bug #90012)

     * For debug builds, if a transaction was in read-only mode,
       trying to create or drop a histogram could raise an
       assertion. (Bug #27672693)

     * If the server was started with --skip-grant-tables, SET
       ROLE DEFAULT caused a server exit. (Bug #27672154)

     * Casting of VARBINARY values to TIME values was not
       performed correctly. (Bug #27665997)

     * Error checking was not performed after creation of a
       condition for a const reference. (Bug #27665085)

     * The dictionary information object managed by the MeCab
       model was used after the MeCab model was released. (Bug
       #27660368)

     * Attempting to abort events of the
       MYSQL_AUDIT_AUTHENTICATION_CLASS class caused a server
       exit. These events are now not abortable. (Bug #27645636)

     * These resource-group statements are now disallowed in
       stored functions because they cause an implicit commit,
       which is not permitted in a stored function: CREATE
       RESOURCE GROUP, ALTER RESOURCE GROUP, DROP RESOURCE
       GROUP. (Bug #27638623, Bug #89914)

     * Audit log filter rules did not permit class names to be
       specified as an array of strings. That is now possible.
       Example:
{
  "filter": {
    "class": [
      { "name": [ "connection", "general", "table_access" ] }
    ]
  }
}

       (Bug #27628325)

     * On Windows, if the Visual C++ Redistributable for Visual
       Studio had been removed, MySQL uninstallation using the
       MSI installer failed. (Bug #27621546)

     * mysql_secure_installation now loads the validate_password
       component rather than the deprecated validate_password
       plugin. (Bug #27619667)

     * REGEXP_LIKE() using an expression containing a question
       mark (?) was not handled correctly when included in a
       prepared statement. (Bug #27595368)

     * REGEXP_SUBSTR() did not always handle NULL patterns
       correctly. (Bug #27572258)

     * Some SHOW CREATE TABLE statements could raise an
       assertion. (Bug #27569314)

     * Spurious stages could be seen in the Performance Schema
       events_stages_current table. (Bug #27566220)

     * Triggers for a table could execute in an order different
       from that specified by their PRECEDES/FOLLOWS clauses.
       (Bug #27544152)

     * Attempts to set some persisted variables at startup (such
       as keyring_operations and mandatory_roles) produced a
       privilege violation error and the server did not start or
       did not set the variable. (Bug #27523095)

     * Under some conditions, an unused-variable warning
       occurred in the MeCab full-text search code. Thanks to
       Laurynas Biveinis for the patch. (Bug #27519952, Bug
       #89598)

     * Within stored procedures, it was not possible to write a
       condition handler to catch foreign key failures if the
       table involved used the FEDERATED storage engine. (Bug
       #27509959)

     * It was possible to drop a primary key that served as the
       parent key in a foreign key relationship. (Bug #27506922,
       Bug #89570)

     * With the NO_ENGINE_SUBSTITUTION SQL mode disabled, an
       error (rather than substitution) occurred for CREATE
       TABLE and ALTER TABLE if the desired engine was disabled
       using the disabled_storage_engines system variable. (Bug
       #27502530)

     * Key rotation using the keyring_encrypted_File keyring
       plugin could cause a server exit. (Bug #27497018)

     * If MySQL Enterprise Firewall was configured with a large
       number of rules, server shutdown could take a long time.
       (Bug #27492122)

     * SET PERSIST_ONLY var_name = DEFAULT persisted the current
       global value, not the default value. (Bug #27489026)

     * If MySQL is configured with the LINK_RANDOMIZE CMake
       option enabled, the --gc-sections compiler option is now
       disabled; the combination causes segmentation faults.
       (Bug #27484106)

     * During server installation, the mysql.infoschema,
       mysql.session, and mysql.sys reserved users were
       associated with the mysql_native_password authentication
       plugin even when the default plugin was
       caching_sha2_password. (Bug #27454299)

     * Some window functions used the wrong precision for their
       aggregated data types. (Bug #27452179)

     * For a hexadecimal value H, SELECT with WHERE (-1) - H
       raised an assertion. (Bug #27452082)
       References: See also: Bug #27041382. This issue is a
       regression of: Bug #21982792.

     * A memory leak in the pfs-t unit test was fixed. Thanks to
       Yura Sorokin for the patch. (Bug #27440735, Bug #89384)

     * Multiple invocations of CHAR() within a stored program
       could yield different results once an invalid code point
       was passed as the argument. (Bug #27410088)

     * With automatic_sp_privileges enabled, the EXECUTE and
       ALTER ROUTINE privileges were not correctly granted to
       routine creators. (Bug #27407480)

     * Some queries that used ordering could access an
       uninitialized column during optimization and cause a
       server exit. (Bug #27389294)

     * For debug builds, an assertion was raised (rather than an
       error) for ALTER TABLE for an ARCHIVE table with a
       GEOMETRY NOT NULL column containing empty strings. (Bug
       #27330634, Bug #89088)

     * Accounts that authenticated with the auth_sock
       authentication plugin could not connect using older
       clients. (Bug #27306178)

     * If system tables could not be read or initialized, the
       server wrote an incomplete error message. Thanks to
       Daniël van Eeden for a patch related to the fix. (Bug
       #27302337, Bug #89001)

     * RENAME USER failed when used to rename a role that was
       not granted to any account or role. (Bug #27284699)

     * The keyring_okv plugin did not always fail over to the
       standby OKV server when the primary server was
       unavailable. (Bug #27244099)

     * The Performance Schema could attempt to access invalid
       SOURCE column values. (Bug #27231036)

     * Mishandling of internal privilege structures could cause
       a server exit. (Bug #27230925)

     * For debug builds, use of a too-small type for calculating
       the determinant in GIS computations could cause an
       assertion to be raised. (Bug #27135504)

     * For attempts to increase the length of a VARCHAR column
       of an InnoDB table using ALTER TABLE with the INPLACE
       algorithm, the attempt failed if the column was indexed.
       If an index size exceeded the InnoDB limit of 767 bytes
       for COMPACT or REDUNDANT row format, CREATE TABLE and
       ALTER TABLE did not report an error (in strict SQL mode)
       or a warning (in nonstrict mode). (Bug #26848813)

     * In MySQL 5.7.19, the mysql.gtid_executed table was
       excluded from dumps. This table is no longer excluded but
       its data is not dumped. (Bug #26643180, Bug #87455)
       References: This issue is a regression of: Bug #82848,
       Bug #24590891.

     * The slave_rows_search_algorithms system variable controls
       how rows are searched for matches when preparing batches
       of rows for row-based logging and replication. Specifying
       INDEX_SCAN as one of the search algorithms performs an
       index scan if an index is present. In the situation where
       a different primary key is used on the master and the
       slave, and a unique key is present on the slave, a bug in
       the code meant that the index scan was not being
       performed as it should be, and a slower table scan was
       being performed instead. The issue has now been corrected
       so that an index scan is used. (Bug #26450129, Bug
       #81500)

     * Certain cases of subquery materialization could cause a
       server exit. These queries now produce an error
       suggesting that materialization be disabled. (Bug
       #26402045)

     * Spatial operations on geographic GeometryCollection
       values could return ER_GIS_INVALID_DATA for valid
       geometries. (Bug #26174808)

     * For MyISAM tables, particular sequences of INSERT and
       DELETE statements could cause table corruption. (Bug
       #25541037)

     * The SHOW CREATE USER statement requires the SELECT
       privilege for the mysql database, except to see
       information for the current user. In addition, for the
       current user, the statement requires the SELECT privilege
       for the mysql.user system table for display of the
       password hash in the IDENTIFIED AS clause; otherwise, the
       hash displays as <secret>. (Bug #24911117)

     * CREATE FUNCTION produced an error if there was no default
       database and the function body called another function.
       (Bug #24357244, Bug #82350)

     * For debug builds, a SELECT statement executed within a
       stored program could raise an assertion if derived table
       resolution failed. (Bug #23221336)

     * If mysqldump or mysqlpump were used to dump binary data
       without the --hex-blob option, reloading the dump file
       could produce spurious warnings (values were inserted
       correctly regardless of the warnings). Such values are
       now written preceded by the _binary introducer to silence
       the warnings. (Bug #22601255, Bug #80150)

     * String comparisons involving wildcards could reference
       uninitialized memory. (Bug #12635103)

     * REGEXP_REPLACE() raised a valgrind warning when invoked
       with an invalid capture group. (Bug #87842, Bug
       #27612255)

Changes in MySQL Enterprise Backup 8.0.12 (2018-07-27)

     * Functionality Added or Changed

     * Bugs Fixed

Functionality Added or Changed


     * Important Change: Starting from release 8.0.12, the
       storage engine of the mysql.backup_history table on a
       backed-up server has switched from CSV to InnoDB. For a
       MySQL 8.0.12 server that has its database restored from a
       backup of an earlier server version, MySQL Enterprise
       Backup 8.0.12 automatically migrates the table when it
       performs its first backup task on the server. See After
       restoring an earlier backup to MySQL 8.0.12 or later
(http://dev.mysql.com/doc/mysql-enterprise-backup/8.0/en/mysqlbackup.privileges.html#meb-restore-to-8.0.12)
       for the new user privileges required by mysqlbackup for the
       mandatory migration to happen.

     * Important Change: When working with a Group Replication
       (http://dev.mysql.com/doc/refman/8.0/en/group-replication.html)
       setup, mysqlbackup now makes the backup history
       available to all members of the server group by making
       sure that the backup_history table is updated on a
       primary node after each mysqlbackup operation.
       With the implementation of this feature, the new user
       privilege of SELECT on
       performance_schema.replication_group_members is now
       required by mysqlbackup to work with any server, even
       when it does not belong to a Group Replication setup. See
       Grant MySQL Privileges to Backup Administrator
(http://dev.mysql.com/doc/mysql-enterprise-backup/8.0/en/mysqlbackup.privileges.html)
       for details.

     * Version information for mysqlbackup is now printed to the
       stdout instead of the stderr stream when the --version or
       --help option is used. (Bug #27253989)

     * OAuth is now supported for Oracle Cloud Storage client
       authentication. Two new options, --cloud-storage-url and
       --cloud-oauth-token, have been introduced for the
       purpose. See Cloud Storage Options
(http://dev.mysql.com/doc/mysql-enterprise-backup/8.0/en/backup-cloud-options.html)
       for details.

Bugs Fixed


     * Backups for a server failed when it had ANSI_QUOTES in
       its values for sql_mode. (Bug #27939774)

     * The maximum value that could be set for the
       --safe-slave-backup-timeout option was 2700 (seconds),
       which automatically replaced any larger value. With this
       fix, there is no longer a maximum limition, even though a
       high value is not recommended; see the description of
       --safe-slave-backup-timeout for details. (Bug #27883020)

     * Restoring an incrementation backup on top of a data
       directory restored using a compressed backup failed. It
       was because mysqlbackup did not set is_compressed=0 in
       the backup_variables.txt file inside the restored data
       directory. (Bug #27787988)

     * When mysqlbackup performed sanity checks on InnoDB
       tablespaces and found a space ID mismatch for an FSP
       header and a page header, the name of the problematic
       tablespace was not given in the error report. (Bug
       #27752703)

     * If an ALTER TABLE
       (http://dev.mysql.com/doc/refman/8.0/en/alter-table.html)
       statement was executed on the server before an
       incremental backup was taken, a server restored with the
       backup on which the incremental backup was applied (using
       the apply-incremental-backup command) could not be
       started, as the .ibd file of the altered table was
       missing in the restored data. (Bug #27735134)

     * After a server has been restored using an incremental
       backup created with the --incremental-with-redo-log-only
       option, it could not be started. (Bug #27722525)

     * mysqlbackup issued a warning whenever the number of files
       specified in the system variable innodb_data_file_path of
       the server to be backed up exceeded 100. With this fix, a
       warning is issued only if the number of InnoDB data files
       to be opened exceeds the number specified by the system
       variable innodb_open_files. (Bug #27701402)

     * Backups failed for a server that had been started with a
       value for --innodb_log_file_size different from the one
       the server was initiated with. (Bug #27571663)

     * An apply-incremental-backup operation failed when
       individual tablespaces with relative file paths were
       involved. (Bug #27278876)

     * In a Group Replication
       (http://dev.mysql.com/doc/refman/8.0/en/group-replication.html)
       setting for MySQL servers, when changes were made
       to one group member and a backup was taken on another,
       the relay log for the replication applier was missing
       from the backup, so that the restored server could not be
       started. (Bug #25534078)

     * When a compressed backup was restored with the
       --innodb_data_home_dir option pointing to a restore
       location outside of the data directory, .ibd files were
       still being copied into the data directory, causing an
       exception to be thrown at the attempt to start the
       restored server. (Bug #24826986)

Dear MySQL users,

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

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

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

For information on installing MySQL 5.7.23 on new servers, please see
the MySQL installation documentation at

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

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

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

MySQL Server 5.7.23 is also available from our repository for Linux
platforms, go here for details:

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

Windows packages are available via the Installer for Windows or .ZIP
(no-install) packages for more advanced needs. The point and click
configuration wizards and all MySQL products are available in the
unified Installer for Windows:

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

5.7.23 also comes with a web installer as an alternative to the full
installer.

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.

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.7 since
the release of MySQL 5.7.22. It may also be viewed
online at

  http://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-23.html

Enjoy!

Changes in MySQL 5.7.23 (2018-07-27, General Availability)

Audit Log Notes


     * For new MySQL installations, the USER and HOST columns in
       the audit_log_user table used by MySQL Enterprise Audit
       now have definitions that better correspond to the
       definitions of the User and Host columns in the
       mysql.user system table.
       For upgrades to an installation for which MySQL
       Enterprise Audit is already installed, it is recommended
       that you alter the table definitions as follows:
        ALTER TABLE mysql.audit_log_user
          DROP FOREIGN KEY audit_log_user_ibfk_1;
        ALTER TABLE mysql.audit_log_filter
          ENGINE=InnoDB;
        ALTER TABLE mysql.audit_log_filter
          CONVERT TO CHARACTER SET utf8 COLLATE utf8_bin;
        ALTER TABLE mysql.audit_log_user
          ENGINE=InnoDB;
        ALTER TABLE mysql.audit_log_user
          CONVERT TO CHARACTER SET utf8 COLLATE utf8_bin;
        ALTER TABLE mysql.audit_log_user
          MODIFY COLUMN USER VARCHAR(32);
        ALTER TABLE mysql.audit_log_user
          ADD FOREIGN KEY (FILTERNAME) REFERENCES mysql.audit_log_filter(NAME);
       (Bug #23706056)

Compilation Notes


     * Solaris: MySQL now can be compiled on Solaris using gcc.
       (Bug #27802681)

MySQL Enterprise Notes


     * The MySQL Enterprise Firewall firewall_whitelist table
       now contains a primary key column named ID. (Bug
       #27164826)

Security Notes


     * The linked OpenSSL library for the MySQL Commercial
       Server has been updated to version 1.0.2o. 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 #28025379)

     * In MySQL 5.7, the default authentication plugin is
       mysql_native_password. As of MySQL 8.0, the default
       authentication plugin is changed to
       caching_sha2_password. To enable MySQL 5.7 clients to
       connect to 8.0 and higher servers using accounts that
       authenticate with caching_sha2_password, the MySQL 5.7
       client library and client programs now support the
       caching_sha2_password client-side authentication plugin.
       This improves MySQL 5.7 client connect-capability
       compatibility with respect to MySQL 8.0 and higher
       servers, despite the differences in default
       authentication plugin. For more information, see Caching
       SHA-2 Pluggable Authentication
http://dev.mysql.com/doc/refman/5.7/en/caching-sha2-pluggable-authentication.html

SQL Syntax Notes


     * Explicit ASC or DESC qualifiers for GROUP BY clauses are
       now deprecated and will be removed in a future MySQL
       version.

Functionality Added or Changed


     * Previously, for the --ssl-mode=VERIFY_IDENTITY or
       --ssl-verify-server-cert option, the client checked
       whether the host name that it used for connecting matched
       the Common Name value in the certificate but not the
       Subject Alternative Name value. Now, if the client uses
       OpenSSL 1.0.2 or higher, the client checks whether the
       host name matches either the Subject Alternative Name
       value or the Common Name value in the server certificate.
       Thanks to Daniël van Eeden for a patch on which this
       change was based. (Bug #16211011, Bug #68052,
       Bug #27511233, Bug #89578)

Bugs Fixed


     * Important Change; Partitioning: After creating
       partitioned InnoDB tables with very long names, the
       table_name columns in the corresponding entries in the
       mysql.innodb_index_stats and mysql.innodb_table_stats
       system tables were truncated. To fix this issue, the
       length of the table_name column in each of these tables
       has been increased from 64 to 199 characters. In both
       cases, this is now the same as the lengths of these
       columns in MySQL 8.0.
       When upgrading to this release, use mysql_upgrade to
       effect these changes in your MySQL installation. In the
       event that you fail to do this, MySQL generates the
       warning Table mysql/innodb_table_stats has length
       mismatch in the column name table_name. Please run
       mysql_upgrade in the error log.
       Note
       Some platforms, such as Microsoft Windows, may restrict
       path lengths (MAX_PATH) to a maximum of 260, which can
       cause creation of partitioned tables with long names to
       fail. You can avoid this problem on Windows systems by
       enabling NTFS long path names; see your system
       documentation for information on how to do this.
       (Bug #86926, Bug #26390736)

     * InnoDB: The ngram full-text search parser permitted comma
       and period characters to be tokenized as words, which
       caused an inconsistency between boolean and natural
       language mode search results. Comma and period characters
       are no longer tokenized. (Bug #27847697)

     * InnoDB: An I/O error returned by an fsync() operation is
       now treated as a hard error. (Bug #27805553, Bug #90296)

     * InnoDB: A schema mismatch error reported during an import
       tablespace operation failed to print mismatched table
       flags in a readable format. (Bug #27542720)

     * InnoDB: A DDL operation failed to wait for a FULLTEXT
       index optimization operation to finish. (Bug #27326796)
       References: This issue is a regression of: Bug #24938374.

     * InnoDB: An unnecessary check for read-only transactions
       was removed from the trx_set_rw_mode() function. Thanks
       to Sandeep Sethia for the patch. (Bug #27211287, Bug
       #88739)

     * InnoDB: A DDL operation that added a foreign key
       constraint raised an assertion when it accessed a stale
       memory object that belonged to the parent table. (Bug
       #27208858)

     * InnoDB: A DDL operation on a table with a FULLTEXT index
       during full-text index cache synchronization caused an
       assertion failure. (Bug #27082268, Bug #27095935)

     * InnoDB: A failing assertion occurred after initiating a
       memcached get operation. (Bug #26876594)

     * InnoDB: A corrupt index ID encountered during a foreign
       key check raised an assertion. (Bug #26654685)

     * InnoDB: An internal deadlock during a DDL operation
       resulted in a long semaphore wait followed by a server
       exit. (Bug #26225783)

     * InnoDB: A DDL operation encountered a serious error due
       to an invalid lock upgrade. (Bug #26225783)

     * InnoDB: On a Windows 64-bit system, invalid buffer pool
       configuration values caused the server to exit on
       startup. (Bug #26100239, Bug #86370)

     * Partitioning: For a partitioned table, partition update
       time could be incorrect after rebuilding the table or
       restarting the server. (Bug #27073100)

     * Partitioning: An extraneous row lock was imposed by an
       update to a partitioned InnoDB table. (Bug #87253, Bug
       #26553164)

     * Replication: The log messages generated when a member
       fails to join the group have been improved, for example
       when group_replication_group_name on the member joining
       the group does not match the seed's
       group_replication_group_name this is now described in the
       log message. (Bug #27628695)

     * Replication: The
       ER_GRP_RPL_SQL_SERVICE_FAILED_TO_RUN_SQL_QUERY error was
       being logged incorrectly. (Bug #27590534)

     * Replication: The use of replication filters or binary log
       filters can cause issues when they are applied to tables
       that are updated with XA transactions. Filtering of
       tables could cause an XA transaction to be empty on a
       replication slave, and empty XA transactions are not
       supported. Also, with the settings
       master_info_repository=TABLE and
       relay_log_info_repository=TABLE on a replication slave,
       which became the defaults in MySQL 8.0, the internal
       state of the data engine transaction is changed following
       a filtered XA transaction, and can become inconsistent
       with the replication transaction context state.
       Due to these issues, the use of replication filters or
       binary log filters in combination with XA transactions is
       not supported. This fix adds the new error
       ER_XA_REPLICATION_FILTERS, which is logged whenever an XA
       transaction is impacted by a replication filter, whether
       or not the transaction was empty as a result. If the
       transaction is not empty, the replication slave is able
       to continue running, but you should take steps to
       discontinue the use of replication filters with XA
       transactions in order to avoid potential issues. If the
       transaction is empty, the replication slave stops. In
       that event, the replication slave might be in an
       undetermined state in which the consistency of the
       replication process might be compromised. In particular,
       the gtid_executed set on a slave of the slave might be
       inconsistent with that on the master. To resolve this
       situation, isolate the master and stop all replication,
       then check GTID consistency across the replication
       topology. Undo the XA transaction that generated the
       error message, then restart replication. (Bug #27442477)

     * Replication: When a transaction larger than the binary
       log transaction cache size (binlog_cache_size) was
       flushed to a temporary file during processing, and the
       flush failed due to a lack of space in the temporary
       directory, the flush error was not handled correctly. No
       message was written to the error log, and the binary log
       cache was not cleared after the transaction was rolled
       back. Now, in this situation, the server takes an
       appropriate action based on the binlog_error_action
       setting (shut down the server or halt logging), and
       writes a message to the error log. When the transaction
       is rolled back, the server checks for flush errors and
       clears the binary log cache if any occurred. (Bug
       #27399620, Bug #89272)

     * Replication: When GTIDs are in use for replication,
       replicated transactions that are filtered out on the
       slave are persisted. If binary logging is enabled on the
       slave, the filtered-out transaction is written to the
       binary log as a Gtid_log_event followed by an empty
       transaction containing only BEGIN and COMMIT statements.
       If binary logging is disabled, the GTID of the
       filtered-out transaction is written to the
       mysql.gtid_executed table. This process ensures that
       there are no gaps in the set of executed GTIDs, and that
       the filtered-out transactions are not retrieved again if
       the slave reconnects to the master. Previously, this
       process was not done for CREATE DATABASE, ALTER DATABASE,
       and DROP DATABASE statements, but it is now carried out
       for those statements as well as for others. (Bug
       #27308751, Bug #88891)

     * Replication: On a multithreaded slave, when a STOP SLAVE
       statement is executed on the slave, followed by a START
       SLAVE statement, the error log can report a different
       position in the binary log for the slave SQL thread when
       exiting, compared to the position reported for the slave
       SQL thread at the subsequent initialization.
       For a multithreaded slave, the position reported for the
       SQL thread on exit is a low water mark, up to which the
       replication stream is consistent and has no gaps.
       Transactions appearing before the position are guaranteed
       to have committed, but transactions after the position
       may have committed or not. However, this low water mark
       was being reported before the process to stop the worker
       threads was actually carried out, and the low water mark
       was subsequently updated by a checkpoint routine during
       that process. The timing of the log message has now been
       changed so that the final low water mark is reported as
       the position for the SQL thread on exit. (Bug #27300658)

     * Replication: In certain situations, such as during
       distributed recovery procedure, the certification info
       garbage collection was purging more data than it should,
       resulting in conflicts not being detected. The garbage
       collection procedure has been improved to take this case
       in consideration. (Bug #89938, Bug #27652526)

     * Replication: When the group_replication_applier channel's
       applier thread encountered an error, the master_log_name
       and end_log_pos in the error message were incorrect. In
       Group Replication, the events of a transaction are
       replicated before they are written to the binary log of
       the member where the transaction originated. The result
       is that the final master_log_name and the end_log_pos of
       those events are unknown at the time they are applied on
       the replica by group_replication_applier channel's
       applier thread. To avoid confusion, now any such error
       messages encountered by a group_replication_applier
       channel do not contain the binary log name and the binary
       log position. (Bug #89146, Bug #27368735)

     * A heap overflow vulnerability in the MySQL client library
       was fixed. (Bug #27980823)

     * For generated columns that used the INTERVAL() function,
       incorrect behavior could occur. (Bug #27881102)

     * The exec_in_background command for mysqltest is now
       available in MySQL 5.7. (Bug #27858055)

     * An unencrypted connection could result from a client
       connection attempt specifying that an encrypted
       connection was required, if the server was not configured
       to support SSL. (Bug #27759871)

     * A BETWEEN clause comparing negative values could lead to
       erroneous results. (Bug #27691347)

     * Audit log filter rules did not permit class names to be
       specified as an array of strings. That is now possible.
       Example:
                {
                  "filter": {
                    "class": [
                      { "name": [ "connection", "general", "table_access" ] }
                    ]
                  }
                }
       (Bug #27628325)


     * On Windows, if the Visual C++ Redistributable for Visual
       Studio had been removed, MySQL uninstallation using the
       MSI installer failed. (Bug #27621546)

     * The audit_log_read() user-defined function could
       deadlock. In consequence of the fix for this issue,
       audit_log_read() no longer uses a shared global buffer.
       Each call allocates its own buffer, which exists for the
       duration of the call. To control the buffer size, set the
       audit_log_read_buffer_size system variable. Previously,
       this variable existed only in global scope with a default
       of 1MB. Now, the variable also exists in session scope,
       has a smaller default of 32KB, and can be set at runtime.
       Each client should set its session value of
       audit_log_read_buffer_size appropriately for its use of
       audit_log_read(). (Bug #27545962)

     * Within stored procedures, it was not possible to write a
       condition handler to catch foreign key failures if the
       table involved used the FEDERATED storage engine. (Bug
       #27509959)

     * With the NO_ENGINE_SUBSTITUTION SQL mode disabled, an
       error (rather than substitution) occurred for CREATE
       TABLE and ALTER TABLE if the desired engine was disabled
       using the disabled_storage_engines system variable. (Bug
       #27502530)

     * If MySQL Enterprise Firewall was configured with a large
       number of rules, server shutdown could take a long time.
       (Bug #27492122)

     * A memory leak in the pfs-t unit test was fixed. Thanks to
       Yura Sorokin for the patch. (Bug #27440735, Bug #89384)

     * With automatic_sp_privileges enabled, the EXECUTE and
       ALTER ROUTINE privileges were not correctly granted to
       routine creators. (Bug #27407480)

     * Some queries that used ordering could access an
       uninitialized column during optimization and cause a
       server exit. (Bug #27389294)

     * For debug builds, an assertion was raised (rather than an
       error) for ALTER TABLE for an ARCHIVE table with a
       GEOMETRY NOT NULL column containing empty strings. (Bug
       #27330634, Bug #89088)

     * If system tables could not be read or initialized, the
       server wrote an incomplete error message. Thanks to
       Daniël van Eeden for a patch related to the fix. (Bug
       #27302337, Bug #89001)

     * The keyring_okv plugin did not always fail over to the
       standby OKV server when the primary server was
       unavailable. (Bug #27244099)

     * The Performance Schema could attempt to access invalid
       SOURCE column values. (Bug #27231036)

     * Mishandling of internal privilege structures could cause
       a server exit. (Bug #27230925)

     * The UNION of a user-defined variable and a DECIMAL column
       produced an incorrect result when using a UTF8 character
       set. (Bug #27197235)

     * Setting max_execution_time sometimes had no effect when
       used with full-text search. (Bug #27155294)

     * For attempts to increase the length of a VARCHAR column
       of an InnoDB table using ALTER TABLE with the INPLACE
       algorithm, the attempt failed if the column was indexed.
       If an index size exceeded the InnoDB limit of 767 bytes
       for COMPACT or REDUNDANT row format, CREATE TABLE and
       ALTER TABLE did not report an error (in strict SQL mode)
       or a warning (in nonstrict mode). (Bug #26848813)

     * In MySQL 5.7.19, the mysql.gtid_executed table was
       excluded from dumps. This table is no longer excluded but
       its data is not dumped. (Bug #26643180, Bug #87455)
       References: This issue is a regression of: Bug #82848,
       Bug #24590891.

     * The slave_rows_search_algorithms system variable controls
       how rows are searched for matches when preparing batches
       of rows for row-based logging and replication. Specifying
       INDEX_SCAN as one of the search algorithms performs an
       index scan if an index is present. In the situation where
       a different primary key is used on the master and the
       slave, and a unique key is present on the slave, a bug in
       the code meant that the index scan was not being
       performed as it should be, and a slower table scan was
       being performed instead. The issue has now been corrected
       so that an index scan is used. (Bug #26450129, Bug
       #81500)

     * Certain cases of subquery materialization could cause a
       server exit. These queries now produce an error
       suggesting that materialization be disabled. (Bug
       #26402045)

     * mysqldump exited abnormally for large --where option
       values. (Bug #26171967, Bug #86496, Bug #27510150)

     * For MyISAM tables, particular sequences of INSERT and
       DELETE statements could cause table corruption. (Bug
       #25541037)

     * The SHOW CREATE USER statement requires the SELECT
       privilege for the mysql database, except to see
       information for the current user. In addition, for the
       current user, the statement requires the SELECT privilege
       for the mysql.user system table for display of the
       password hash in the IDENTIFIED AS clause; otherwise, the
       hash displays as <secret>. (Bug #24911117)

     * CREATE FUNCTION produced an error if there was no default
       database and the function body called another function.
       (Bug #24357244, Bug #82350)

     * For debug builds, a SELECT statement executed within a
       stored program could raise an assertion if derived table
       resolution failed. (Bug #23221336)

     * If mysqldump or mysqlpump were used to dump binary data
       without the --hex-blob option, reloading the dump file
       could produce spurious warnings (values were inserted
       correctly regardless of the warnings). Such values are
       now written preceded by the _binary introducer to silence
       the warnings. (Bug #22601255, Bug #80150)

On Behalf of MySQL/ORACLE RE Team
Gipson Pulla

Dear MySQL users,

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

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

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

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

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:

https://wikis.oracle.com/display/mysql/Contributing

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

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

Enjoy!

Changes in MySQL 5.6.41 (2018-07-27, General Availability)


     * Security Notes

     * Functionality Added or Changed

     * Bugs Fixed

Security Notes


     * The linked OpenSSL library for the MySQL Commercial
       Server has been updated to version 1.0.2o. 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
       #28025379)

Functionality Added or Changed


     * Previously, for the --ssl-verify-server-cert option, the
       client checked whether the host name that it used for connecting
       matched the Common Name value in the certificate but not the
       Subject Alternative Name value.  Now, if MySQL was built using
       OpenSSL 1.0.2 or higher, the client checks whether the host name
       matches either the Subject Alternative Name value or the Common
       Name value in the server certificate. (Bug #16211011, Bug #68052,
       Bug #27511233, Bug #89578)

Bugs Fixed


     * InnoDB: A schema mismatch error reported during an import
       tablespace operation failed to print mismatched table flags in a
       readable format. (Bug #27542720)

     * InnoDB: A DDL operation failed to wait for a FULLTEXT
       index optimization operation to finish. (Bug #27326796)
       References: This issue is a regression of: Bug #24938374.

     * InnoDB: A failing assertion occurred after initiating a
       memcached get operation. (Bug #26876594)

     * InnoDB: A corrupt index ID encountered during a foreign
       key check raised an assertion. (Bug #26654685)

     * Replication: When a transaction larger than the binary
       log transaction cache size (binlog_cache_size) was flushed to a
       temporary file during processing, and the flush failed due to a
       lack of space in the temporary directory, the flush error was not
       handled correctly. No message was written to the error log, and
       the binary log cache was not cleared after the transaction was
       rolled back. Now, in this situation, the server takes an
       appropriate action based on the binlog_error_action setting (shut
       down the server or halt logging), and writes a message to the
       error log. When the transaction is rolled back, the server checks
       for flush errors and clears the binary log cache if any occurred.
       (Bug #27399620, Bug #89272)

     * Replication: When GTIDs are in use for replication,
       replicated transactions that are filtered out on the slave are
       persisted. If binary logging is enabled on the slave, the
       filtered-out transaction is written to the binary log as a
       Gtid_log_event followed by an empty transaction containing only
       BEGIN and COMMIT statements.  If binary logging is disabled, the
       GTID of the filtered-out transaction is written to the
       mysql.gtid_executed table. This process ensures that there are no
       gaps in the set of executed GTIDs, and that the filtered-out
       transactions are not retrieved again if the slave reconnects to
       the master. Previously, this process was not done for CREATE
       DATABASE, ALTER DATABASE, and DROP DATABASE statements, but it is
       now carried out for those statements as well as for others. (Bug
       #27308751, Bug #88891)

     * Replication: On a multithreaded slave, when a STOP SLAVE
       statement is executed on the slave, followed by a START SLAVE
       statement, the error log can report a different position in the
       binary log for the slave SQL thread when exiting, compared to the
       position reported for the slave SQL thread at the subsequent
       initialization.  For a multithreaded slave, the position reported
       for the SQL thread on exit is a low water mark, up to which the
       replication stream is consistent and has no gaps.  Transactions
       appearing before the position are guaranteed to have committed,
       but transactions after the position may have committed or not.
       However, this low water mark was being reported before the
       process to stop the worker threads was actually carried out, and
       the low water mark was subsequently updated by a checkpoint
       routine during that process. The timing of the log message has
       now been changed so that the final low water mark is reported as
       the position for the SQL thread on exit. (Bug #27300658)

     * A heap overflow vulnerability in the MySQL client library
       was fixed. (Bug #27980823)

     * An unencrypted connection could result from a client
       connection attempt specifying that an encrypted connection was
       required, if the server was not configured to support SSL. (Bug
       #27759871)

     * On Windows, if the Visual C++ Redistributable for Visual
       Studio had been removed, MySQL uninstallation using the MSI
       installer failed. (Bug #27621546)

     * A memory leak in the pfs-t unit test was fixed. Thanks to
       Yura Sorokin for the patch. (Bug #27440735, Bug #89384)

     * With automatic_sp_privileges enabled, the EXECUTE and
       ALTER ROUTINE privileges were not correctly granted to routine
       creators. (Bug #27407480)

     * Mishandling of internal privilege structures could cause
       a server exit. (Bug #27230925)

     * The UNION of a user-defined variable and a DECIMAL column
       produced an incorrect result when using a UTF8 character set.
       (Bug #27197235)

     * mysqldump exited abnormally for large --where option
       values. (Bug #26171967, Bug #86496, Bug #27510150)

     * For MyISAM tables, particular sequences of INSERT and
       DELETE statements could cause table corruption. (Bug #25541037)

     * FORCE INDEX had no effect on a query that used GROUP BY,
       ORDER BY, and LIMIT together. (Bug #90817, Bug #27998526)

On Behalf of MySQL Release Engineering Team,
Surabhi Bhat