Aurora MySQL database engine updates 2020-12-11 (version 2.09.1) (Deprecated)
Version: 2.09.1
Aurora MySQL 2.09.1 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.09.1. For clusters running Aurora MySQL version 1, you can upgrade an existing Aurora MySQL 1.23 or higher cluster directly to 2.09.1. You can also restore a snapshot from any currently supported Aurora MySQL release into Aurora MySQL 2.09.1.
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 RDS API.
If you have any questions or concerns, Amazon Support is available on the community forums and through
Amazon Support
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:
Incompatible changes:
This version introduces a permission change that affects the behavior of the mysqldump
command.
Users must have the PROCESS
privilege to access the INFORMATION_SCHEMA.FILES
table.
To run the mysqldump
command without any changes, grant the PROCESS
privilege to the database user
that the mysqldump
command connects to. You can also run the mysqldump
command with the
--no-tablespaces
option. With that option, the mysqldump
output doesn't include any
CREATE LOGFILE GROUP
or CREATE TABLESPACE
statements. In that case, the mysqldump
command doesn't access the INFORMATION_SCHEMA.FILES
table, and you don't need to grant
the PROCESS
permission.
Availability improvements:
-
Fixed an issue that might cause a client session to hang when the database engine encounters an error while reading from or writing to the network.
-
Fixed a memory leak in dynamic resizing feature, introduced in 2.09.0.
Global databases:
-
Fixed multiple issues where a global database secondary Region's replicas might restart when upgraded to release 2.09.0 while the primary Region writer was on an older release version.
Integration of MySQL community edition bug fixes
-
Replication: Interleaved transactions could sometimes deadlock the slave applier when the transaction isolation level was set to REPEATABLE READ
. (Bug #25040331) -
For a table having a TIMESTAMP
or DATETIME column having a default of CURRENT_TIMESTAMP , the column could be initialized to 0000-00-00 00:00:00
if the table had aBEFORE INSERT
trigger. (Bug #25209512, Bug #84077) -
For an INSERT
statement for which the VALUES
list produced values for the second or later row using a subquery containing a join, the server could exit after failing to resolve the required privileges. (Bug #23762382)
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).
-
Asynchronous key prefetch (AKP). For more information, see Optimizing Aurora indexed join queries with asynchronous key prefetch in the Amazon Aurora User Guide.
-
Hash joins. For more information, see Optimizing large Aurora MySQL join queries with hash joins in the Amazon Aurora User Guide.
-
Native functions for synchronously invoking Amazon Lambda functions. For more information, see Invoking a Lambda function with an Aurora MySQL native function 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.
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