Aurora MySQL database engine updates 2019-11-22 (version 2.06.0) (Deprecated)

Aurora MySQL clusters now support the instance types db.r5.8xlarge, db.r5.16xlarge, and db.r5.24xlarge. For more information about instance types for Aurora MySQL clusters, see Aurora DB instance classes in the Amazon Aurora User Guide.

The hash join feature is now generally available and does not require the Aurora lab mode setting to be ON. This feature can improve query performance when you need to join a large amount of data by using an equi-join. For more information about using this feature, see Using the Data API for Aurora Serverless in the Amazon Aurora User Guide.

The hot row contention feature is now generally available and does not require the Aurora lab mode setting to be ON. This feature substantially improves throughput for workloads with many transactions contending for rows on the same page.

Aurora MySQL 2.06 and higher support "rewinding" a DB cluster to a specific time, without restoring data from a backup. This feature, known as Backtrack, provides a quick way to recover from user errors, such as dropping the wrong table or deleting the wrong row. Backtrack completes within seconds, even for large databases. Read the Amazon blog for an overview, and refer to Backtracking an Aurora DB cluster in the Amazon Aurora User Guide for more details.

Aurora 2.06 and higher support synchronous Amazon Lambda invocations through the native function lambda_sync(). Also available is native function lambda_async(), which can be used as an alternative to the existing stored procedure for asynchronous Lambda invocation. For information about calling Lambda functions, see Invoking a Lambda function with an Aurora MySQL native function in the Amazon Aurora User Guide.

CVE-2019-2805

CVE-2019-2791

CVE-2019-2778

CVE-2019-2758

CVE-2019-2739

CVE-2019-2730

CVE-2018-3064

CVE-2018-3058

CVE-2018-2786

CVE-2017-3653

CVE-2017-3465

CVE-2017-3455

CVE-2017-3244

CVE-2016-5612

Database availability has been improved to better service a surge in client connections while executing one or more DDLs. It is handled by temporarily creating additional threads when needed. You are advised to upgrade if the database becomes unresponsive following a surge in connections while processing DDL.

Fixed an issue of prolonged unavailability while restarting the engine. This addresses an issue in the buffer pool initialization. This issue occurs rarely but can potentially impact any supported release.

Fixed an issue that causes a database configured as a binary log (binlog) master to restart while a heavy write workload is running.

Made improvements where queries accessing uncached data could be slower than usual. Customers experiencing unexplained elevated read latency while accessing uncached data are encouraged to upgrade as they may be experiencing this issue.

Fixed an issue that failed to restore partitioned tables from a database snapshot. Customers who encounter errors when accessing partitioned tables in a database that has been restored from the snapshot of an Aurora MySQL 1.* database are advised to use this version.

Improved stability of the Aurora Replicas by fixing lock contention between threads serving read queries and the one applying schema changes while a DDL query is in progress on the writer DB instance.

Fixed a stability issue related to mysql.innodb_table_stats table update triggered by DDL operations.

Fixed an issue that incorrectly reported ERROR 1836 when a nested query is executed against a temporary table on the Aurora Replica.

Improved performance of binlog replication by preventing unnecessary API calls to the cache if the query cache has been disabled on the binlog worker.

Asynchronous key prefetch (AKP). For more information, see Optimizing Aurora indexed join queries with asynchronous key prefetch in the Amazon Aurora User Guide.

Scan batching. For more information, see Aurora MySQL database engine updates 2017-12-11 (version 1.16) (Deprecated).

Migrating data from MySQL using an Amazon S3 bucket. For more information, see Migrating data from MySQL by using an Amazon S3 bucket in the Amazon Aurora User Guide.

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