Aurora MySQL database engine updates 2021-11-12 (version 2.09.3) - 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 2021-11-12 (version 2.09.3)

Version: 2.09.3

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

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 can upgrade an existing Aurora MySQL 2.* database cluster to Aurora MySQL 2.10.0. For clusters running Aurora MySQL version 1, you can upgrade an existing Aurora MySQL 1.23 or higher cluster directly to 2.10.0. You can also restore a snapshot from any currently supported Aurora MySQL release into Aurora MySQL 2.10.0.

To create a cluster with an older version of Aurora MySQL, specify the engine version through the Amazon Web Services Management Console, the Amazon CLI, or the Amazon 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

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:

Fixes and other enhancements to fine-tune handling in a managed environment. Additional CVE fixes below:

Availability improvements:

  • Introduced an optimization which can reduce contention for queries that are executed on tables in information_schema.

  • Add support for ECDHE SSL ciphers.

General improvements:

  • Fixed an issue which, in rare conditions, can cause a writer instance to restart when an in-memory data-integrity check fails.

  • Fixed an issue which, in rare conditions, can cause the database instance to restart when the cluster volume is expanding while binary logging is enabled.

  • Fixed a rare race condition during a database instance restart, which can cause more than one restart.

  • Fixed an issue which can cause a database instance restart to fail when the database has a large number of user and privilege combinations.

  • Fixed an issue with parallel query which can cause the database to restart when executing SQL statements with LIMIT clause.

  • Fixed an issue with incorrect reporting of aurora replication lag.

  • Fixed an issue which can cause general_log and slow_log tables to become inaccessible after in-place major version upgrade from Aurora-MySQL 1.x (based on MySQL 5.6) to Aurora-MySQL 2.x (based on MySQL 5.7).

  • Fixed an issue which, in rare cases, can cause the database instance to restart when innodb_trx, innodb_locks or innodb_lockwaits tables are queried while the database is under heavy workload. Monitoring tools and features such as performance insights may query such tables.

  • Fixed an issue which can cause a database instance to restart when "FLUSH TABLES WITH READ LOCK" SQL statement is executed.

  • Fixed an issue where the InnoDB purge process pauses during the deletion of a reader instance leading to a temporary increase in history list length.

  • Fixed an issue with parallel query which can cause the database to restart when executing a SQL statement against a table containing a virtual column.

  • Fixed an issue with parallel query which can cause the database to return incorrect groupings or sort order when executing queries with GROUP BY clause and a WHERE clause containing a range predicate.

  • Fixed an issue in parallel query which, in rare conditions, can cause the database to restart when executing SQL statements with JSON functions.

  • Fixed an issue which, in rare conditions, can cause the writer instance in primary Global Database cluster to restart because of a race condition during Global Database Replication.

  • Fixed an issue that can cause a Binlog replica to stop with an HA_ERR_FOUND_DUPP_KEY error when replicating certain DDL and DCL statements. The issue occurs when the source instance is configured with MIXED binary logging format and READ COMMITTED or READ UNCOMMITTED isolation level.

  • Fixed an issue which, in rare conditions, can cause the database instance to restart when using XA transactions in READ COMMITTED isolation level.

  • Fixed an issue where the value of a TIMESTAMP column of an existing row is updated to the latest timestamp when all of the following conditions are satisfied: 1. a trigger exists for the table; 2. an INSERT is performed on the table that has an ON DUPLICATE KEY UPDATE clause; 3. the inserted row can cause a duplicate value violation in a UNIQUE index or PRIMARY KEY; and 4. one or more columns are of TIMESTAMP data type and have a default value of CURRENT_TIMESTAMP.

  • Fixed an issue which, in rare conditions, can cause a reader instance to restart due to an incorrect check processing.

  • Fixed an issue which can cause the reader instance to restart when the writer instance grows the database volume to cross specific volume size boundaries.

  • Fixed an issue which can cause longer restart times for database instances using cloned cluster volumes.

  • Fixed an issue where a database instance restart may fail one or more times after a TRUNCATE TABLE operation was performed on the writer instance.

  • Fixed an issue which, in rare conditions, can cause the database instance to restart.

  • Fixed an issue which, in rare conditions, can cause the writer instance to restart when the database volume grows to a multiple of 160GB.

Integration of MySQL community edition bug fixes

  • Bug #23533396 - When adding a new index, the server dropped an internally defined foreign key index and attempted to use a secondary index defined on a virtual generated column as the foreign key index, causing a server exit. InnoDB now permits a foreign key constraint to reference a secondary index defined on a virtual generated column.

  • Bug #29550513 - Replication: A locking issue in the WAIT_FOR_EXECUTED_GTID_SET() function can cause the server to hang in certain circumstances. The issue has now been corrected.

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

This Aurora MySQL version 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.

This Aurora MySQL version 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