Aurora MySQL database engine updates 2024-01-31 (version 3.05.2, compatible with MySQL 8.0.32) Default (original) (raw)

Version: 3.05.2

Aurora MySQL 3.05.2 is generally available. Aurora MySQL 3.05 versions are compatible with MySQL 8.0.32. For more information on the community changes that have occurred, see MySQL 8.0 Release Notes.

Version 3.05.2 is the current default version for Aurora MySQL version 3 when you create a DB cluster. For more information, see Default Amazon Aurora versions.

For details of the new features in Aurora MySQL version 3, see Aurora MySQL version 3 compatible with MySQL 8.0. For differences between Aurora MySQL version 3 and Aurora MySQL version 2, see Comparing Aurora MySQL version 2 and Aurora MySQL version 3. For a comparison of Aurora MySQL version 3 and MySQL 8.0 Community Edition, see Comparing Aurora MySQL version 3 and MySQL 8.0 Community Edition in the Amazon Aurora User Guide.

Currently supported Aurora MySQL releases are 2.07.9, 2.07.10, 2.11.*, 2.12.*, 3.03.*, 3.04.*, and 3.05.*.

You can perform an in-place upgrade, restore a snapshot, or initiate a managed blue/green upgrade using Amazon RDS Blue/Green Deployments from any currently supported Aurora MySQL version 2 cluster into an Aurora MySQL version 3.05.2 cluster.

For information on planning an upgrade to Aurora MySQL version 3, see Upgrade planning for Aurora MySQL version 3. For general information about Aurora MySQL upgrades, see Upgrading Amazon Aurora MySQL DB clusters in the_Amazon Aurora User Guide_.

For troubleshooting information, see Troubleshooting upgrade issues with Aurora MySQL version 3 in the Amazon Aurora User Guide.

If you have any questions or concerns, AWS Support is available on the community forums and through AWS Support. For more information, seeMaintaining an Amazon Aurora DB cluster in the Amazon Aurora User Guide.

Improvements

Fixed security issues and CVEs:

The following CVE fixes are included in this release:

Availability improvements:

Fixed an issue where processing INSERT queries on InnoDB partitioned tables can cause a gradual decline of free memory in the instance.
Fixed an issue that can cause a database instance restart when running SHOW STATUS and PURGE BINARY LOGS statements concurrently. PURGE BINARY LOGS is a managed statement that is run to honor the user-configured binlog retention period.
Fixed an issue that can cause the server to unexpectedly close after running Data Manipulation Language (DML) statements on a table whose nonvirtual columns were reordered with a MODIFY COLUMN or CHANGE COLUMN statement.
Fixed an issue that, during the restart of a database instance, can cause an additional restart.

General improvements:

Fixed an issue where the user is unable to interrupt any query or set session timeouts for performance_schema queries.
Fixed an issue where binary log (binlog) replication setup using custom SSL certificates (mysql.rds_import_binlog_ssl_material) could fail when the replication instance is undergoing a host replacement.
Fixed an issue related to audit log file management that can cause log files to be inaccessible for download or rotation, and in some cases increase CPU usage.
In Aurora MySQL versions lower than 3.05.2, users are unable to retrieve the output of SHOW ENGINE INNODB STATUS on Aurora MySQL reader DB instances. This is due to the default InnoDB behavior when innodb_read_only is enabled.
In Aurora MySQL version 3.05.2 and higher, when SHOW ENGINE INNODB STATUS is run on a reader instance, the output is written to the MySQL error log, allowing for easier troubleshooting.
For more information on working with MySQL error logs, see Aurora MySQL error logs. For more information on SHOW ENGINE INNODB STATUS, see SHOW ENGINE statement in the MySQL documentation.

Upgrades and migrations:

Fixed an issue that can cause upgrade failures from Aurora MySQL version 2 to Aurora MySQL version 3 when there is a user-defined FTS_DOC_ID column present in the table schema.
Fixed an issue that can cause upgrade failures from Aurora MySQL version 2 to Aurora MySQL version 3 due to a synchronization issue while processing InnoDB tablespaces.
Fixed an issue that can cause major version upgrades to Aurora MySQL version 3 to fail due to the presence of orphaned entries for already deleted tablespaces in InnoDB system tables in Aurora MySQL version 2.

Integration of MySQL Community Edition bug fixes

This release includes all community bug fixes up to and including 8.0.32, in addition to the following. For more information, see MySQL bugs fixed by Aurora MySQL 3.x database engine updates.

Fixed an issue where records_in_range performed an excessive number of disk reads for INSERT operations, leading to a gradual decline in performance. (Community Bug Fix #34976138)