Aurora MySQL database engine updates 2019-01-18 (version 2.03.3) (Deprecated) - Amazon Aurora
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.

Aurora MySQL database engine updates 2019-01-18 (version 2.03.3) (Deprecated)

Version: 2.03.3

Aurora MySQL 2.03.3 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.

When creating a new Aurora MySQL DB cluster (including restoring a snapshot), you can choose compatibility with either MySQL 5.7 or MySQL 5.6.

We don't allow in-place upgrade of Aurora MySQL 1.* clusters into Aurora MySQL 2.03.3 or restore to Aurora MySQL 2.03.3 from an Amazon S3 backup. We plan to remove these restrictions in a later Aurora MySQL 2.* release.

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 Amazon GovCloud (US-West) [us-gov-west-1] and China (Beijing) [cn-north-1] regions. 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

CVE fixes

Critical fixes:

  • Fixed an issue where an Aurora Replica might become dead-latched when running a backward scan on an index.

  • Fixed an issue where an Aurora Replica might restart when the Aurora primary instance runs in-place DDL operations on partitioned tables.

  • Fixed an issue where an Aurora Replica might restart during query cache invalidation after a DDL operation on the Aurora primary instance.

  • Fixed an issue where an Aurora Replica might restart during a SELECT query on a table while the Aurora primary instance runs truncation on that table.

  • Fixed a wrong result issue with MyISAM temporary tables where only indexed columns are accessed.

  • Fixed an issue in slow logs that generated incorrect large values for query_time and lock_time periodically after approximately 40,000 queries.

  • Fixed an issue where a schema named "tmp" could cause migration from RDS for MySQL to Aurora MySQL to become stuck.

  • Fixed an issue where the audit log might have missing events during log rotation.

  • Fixed an issue where the Aurora primary instance restored from an Aurora 5.6 snapshot might restart when the Fast DDL feature in the lab mode is enabled.

  • Fixed an issue where the CPU usage is 100% caused by the dictionary stats thread.

  • Fixed an issue where an Aurora Replica might restart when running a CHECK TABLE statement.

Integration of MySQL bug fixes

  • Bug #25361251: INCORRECT BEHAVIOR WITH INSERT ON DUPLICATE KEY IN SP

  • Bug #26734162: INCORRECT BEHAVIOR WITH INSERT OF BLOB + ON DUPLICATE KEY UPDATE

  • Bug #27460607: INCORRECT BEHAVIOR OF IODKU WHEN INSERT SELECT's SOURCE TABLE IS EMPTY

  • A query using a DISTINCT or GROUP BY clause could return incorrect results. (MySQL 5.7 Bug #79591, Bug #22343910)

  • A DELETE from joined tables using a derived table in the WHERE clause fails with error 1093 (Bug #23074801).

  • GCOLS: INCORRECT BEHAVIOR WITH CHARSET CHANGES (Bug #25287633).

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.03.3 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.03.3 does not currently support the following MySQL 5.7 features:

  • Global transaction identifiers (GTIDs). Aurora MySQL supports GTIDs in version 2.04 and higher.

  • 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

  • X Protocol