Aurora MySQL database engine updates 2019-09-19 (version 1.19.5) (Deprecated) - Amazon Aurora
ImprovementsIntegration of MySQL community edition bug fixes
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Aurora MySQL database engine updates 2019-09-19 (version 1.19.5) (Deprecated)

Version: 1.19.5

Aurora MySQL 1.19.5 is generally available. Aurora MySQL 1.* versions are compatible with MySQL 5.6 and Aurora MySQL 2.* versions are compatible with MySQL 5.7.

This engine version is scheduled to be deprecated on February 28, 2023. For more information, see Preparing for Amazon Aurora MySQL-Compatible Edition version 1 end of life.

Currently supported Aurora MySQL releases are 1.19.5, 1.19.6, 1.22.*, 1.23.*, 2.04.*, 2.07.*, 2.08.*, 2.09.*, 2.10.*, 3.01.* and 3.02.*.

You have the option to upgrade existing database clusters to Aurora MySQL 1.19.5. You can restore snapshots of Aurora MySQL 1.14.*, 1.15.*, 1.16.*, 1.17.*, 1.18.*, 1.19.1, and 1.19.2 into Aurora MySQL 1.19.5.

To use an older version of Aurora MySQL, you can create new database clusters by specifying the engine version through the Amazon Web Services Management Console, the Amazon CLI, or the RDS API.

If you have any questions or concerns, Amazon Support is available on the community forums and through Amazon Support. For more information, see Maintaining an Amazon Aurora DB cluster in the Amazon Aurora User Guide.

Note

This version is currently not available in the following Amazon Regions: Europe (London) [eu-west-2], Amazon GovCloud (US-East) [us-gov-east-1], Amazon GovCloud (US-West) [us-gov-west-1], China (Ningxia) [cn-northwest-1], and Asia Pacific (Hong Kong) [ap-east-1]. There will be a separate announcement once it is made available.

Note

The procedure to upgrade your DB cluster has changed. For more information, see Upgrading the minor version or patch level of an Aurora MySQL DB cluster in the Amazon Aurora User Guide.

Improvements

  • Fixed an issue on Aurora reader instances that reduced free memory during long-running transactions while there is a heavy transaction commit traffic on the writer instance.

  • Fixed a parallel query abort error on Aurora reader instances while a heavy write workload is running on the Aurora writer instance.

  • The value of the parameter aurora_disable_hash_join is now persisted after database restart or host replacement.

  • Fixed an issue related to the Full Text Search cache that caused the Aurora instance to run out of memory.

  • Improved stability of the database when the volume size is close to the 64 tebibyte (TiB) volume limit by reserving 160 GB of space for the recovery workflow to complete without a failover.

  • Improved stability of the database when the hash join feature is enabled and the instance is low on memory.

  • Fixed the free memory calculation to include swap memory space on T2 instances that caused them to reboot prematurely.

  • Fixed an issue in the query cache where the "Too many connections" error could cause a reboot.

Integration of MySQL community edition bug fixes

  • CVE-2018-2696

  • CVE-2015-4737

  • Bug #19929406: HANDLE_FATAL_SIGNAL (SIG=11) IN __MEMMOVE_SSSE3_BACK FROM STRING::COPY

  • Bug #17059925: For UNION statements, the rows-examined value was calculated incorrectly. This was manifested as too-large values for the ROWS_EXAMINED column of Performance Schema statement tables (such as events_statements_current).

  • Bug #11827369: Some queries with SELECT ... FROM DUAL nested subqueries raised an assertion.

  • Bug #16311231: Incorrect results were returned if a query contained a subquery in an IN clause that contained an XOR operation in the WHERE clause.