Aurora MySQL database engine updates 2019-07-08 (version 2.04.5) (Deprecated) - Amazon Aurora
ImprovementsComparison with Aurora MySQL version 1MySQL 5.7 compatibility
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-07-08 (version 2.04.5) (Deprecated)

Version: 2.04.5

Aurora MySQL 2.04.5 is generally available. Aurora MySQL 2.x versions are compatible with MySQL 5.7 and Aurora MySQL 1.x versions are compatible with MySQL 5.6.

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 Aurora MySQL 2.* database clusters to Aurora MySQL 2.04.5. We do not allow in-place upgrade of Aurora MySQL 1.* clusters. This restriction will be lifted in a later Aurora MySQL 2.* release. You can restore snapshots of Aurora MySQL 1.14.*, 1.15.*, 1.16.*, 1.17.*, 1.18.*, 1.19.*, 2.01.*, 2.02.*, 2.03.* and 2.04.* into Aurora MySQL 2.04.5.

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

For information on how to upgrade your Aurora MySQL database cluster, see Upgrading the minor version or patch level of an Aurora MySQL DB cluster in the Amazon Aurora User Guide.

Improvements

Security fixes:

General fixes:

  • Fixed a race condition during storage volume growth that caused the database to restart.

  • Fixed an internal communication failure during volume open that caused the database to restart.

  • Added DDL recovery support for ALTER TABLE ALGORITHM=INPLACE on partitioned tables.

  • Fixed an issue with DDL recovery of ALTER TABLE ALGORITHM=COPY that caused the database to restart.

  • Improved Aurora Replica stability under heavy delete workload on the writer.

  • Fixed a database restart caused by a deadlatch between the thread performing full-text search index sync and the thread performing eviction of full-text search table from dictionary cache.

  • Fixed a stability issue on the binlog worker during DDL replication while the connection to the binlog master is unstable.

  • Fixed an out-of-memory issue in the full-text search code that caused the database to restart.

  • Fixed an issue on the Aurora Writer that caused it to restart when the entire 64 tebibyte (TiB) volume is used.

  • Fixed a race condition in the Performance Schema feature that caused the database to restart.

  • Fixed an issue that caused aborted connections when handling an error in network protocol management.

Comparison with Aurora MySQL version 1

The following Amazon Aurora MySQL features are supported in Aurora MySQL Version 1 (compatible with MySQL 5.6), but these features are currently not supported in Aurora MySQL Version 2 (compatible with MySQL 5.7).

MySQL 5.7 compatibility

Aurora MySQL 2.04.5 is wire-compatible with MySQL 5.7 and includes features such as JSON support, spatial indexes, and generated columns. Aurora MySQL uses a native implementation of spatial indexing using z-order curves to deliver >20x better write performance and >10x better read performance than MySQL 5.7 for spatial datasets.

Aurora MySQL 2.04.5 does not currently support the following MySQL 5.7 features:

  • Group replication plugin

  • Increased page size

  • InnoDB buffer pool loading at startup

  • InnoDB full-text parser plugin

  • Multisource replication

  • Online buffer pool resizing

  • Password validation plugin

  • Query rewrite plugins

  • Replication filtering

  • The CREATE TABLESPACE SQL statement