# Aurora MySQL database engine updates 2020-09-02 (version 1.23.0) (Deprecated)
Aurora MySQL updates: 2020-09-02 (version 1.23.0) (Deprecated)Aurora MySQL version 1.23.0
Aurora MySQL version 1.23.0 is available.
**Version:** 1.23.0
Aurora MySQL 1.23.0 is generally available. Aurora MySQL 1.\$1 versions are compatible with MySQL 5.6 and Aurora MySQL 2.\$1 versions are compatible with MySQL 5.7.
This engine version is scheduled to be deprecated on February 28, 2023. For more information, see [ Preparing for Amazon Aurora MySQL-Compatible Edition version 1 end of life](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.MySQL56.EOL.html).
Currently supported Aurora MySQL releases are 1.19.5, 1.19.6, 1.22.\$1, 1.23.\$1, 2.04.\$1, 2.07.\$1, 2.08.\$1, 2.09.\$1, 2.10.\$1, 3.01.\$1 and 3.02.\$1.
You can restore the snapshot of an Aurora MySQL 1.\$1 database into Aurora MySQL 1.23.0.
**Important**
The improvements to Aurora storage in this version limit the available upgrade paths from Aurora MySQL 1.23 to Aurora MySQL 2.\$1. When you upgrade an Aurora MySQL 1.23 cluster to 2.\$1, you must upgrade to Aurora MySQL 2.09.0 or later.
To create a cluster with an older version of Aurora MySQL, please specify the engine version through the RDS Console, the AWS CLI, or the Amazon RDS API.
**Note**
This version is currently not available in the following regions: AWS GovCloud (US-East) [us-gov-east-1], AWS GovCloud (US-West) [us-gov-west-1]. There will be a separate announcement once it is made available.
If you have any questions or concerns, AWS Support is available on the community forums and through [AWS Support](https://aws.amazon.com/support). For more information, see [ Maintaining an Amazon Aurora DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.Maintenance.html) in the *Amazon Aurora User Guide*.
## Improvements
**New features:**
+ You can now turn parallel query on or off for an existing cluster by changing the value of the DB cluster parameter `aurora_parallel_query`. You don't need to use the `parallelquery` setting for the `--engine-mode` parameter when creating the cluster.
Parallel query is now expanded to be available in all regions where Aurora MySQL is available.
There are a number of other functionality enhancements and changes to the procedures for upgrading and enabling parallel query in an Aurora cluster. For more information, see [ Working with parallel query for Amazon Aurora MySQL](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/aurora-mysql-parallel-query.html) in the *Amazon Aurora User Guide*.
+ With this release, you can create Amazon Aurora MySQL database instances with up to 128 tebibytes (TiB) of storage. The new storage limit is an increase from the prior 64 TiB. The 128 TiB storage size supports larger databases. This capability is not supported on small instances sizes (db.t2 or db.t3). A single tablespace cannot grow beyond 64 TiB due to [InnoDB limitations with 16 KB page size](https://dev.mysql.com/doc/refman/5.7/en/innodb-limits.html).
Aurora alerts you when the cluster volume size is near 128 TiB, so that you can take action prior to hitting the size limit. The alerts appear in the mysql log and RDS Events in the AWS Management Console.
+ Improved binary log (binlog) processing to reduce crash recovery time and commit time latency when very large transactions are involved.
+ Aurora dynamically resizes your cluster storage space. With dynamic resizing, the storage space for your Aurora DB cluster automatically decreases when you remove data from the DB cluster. For more information, see [ Storage scaling](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.Managing.Performance.html#Aurora.Managing.Performance.StorageScaling) in the *Amazon Aurora User Guide*.
**Note**
The dynamic resizing feature is being deployed in phases to the AWS Regions where Aurora is available. Depending on the Region where your cluster is, this feature might not be available yet. For more information, see [the What's New announcement](https://aws.amazon.com/about-aws/whats-new/2020/10/amazon-aurora-enables-dynamic-resizing-database-storage-space/).
**High priority fixes:**
+ [CVE-2019-2911](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2911)
+ [CVE-2019-2537](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2537)
+ [CVE-2018-2787](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-2787)
+ [CVE-2018-2784](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-2784)
+ [CVE-2018-2645](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-2645)
+ [CVE-2018-2640](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-2640)
**Availability improvements:**
+ Fixed an issue in the lock manager where a race condition can cause a lock to be shared by two transactions, causing the database to restart.
+ Fixed an issue related to transaction lock memory management with long-running write transactions resulting in a database restart.
+ Fixed a race condition in the lock manager that resulted in a database restart or failover during transaction rollback.
+ Fixed an issue during upgrade from 5.6 to 5.7 when the `innodb_file_format` changed on a table that had Fast DDL enabled.
+ Fixed multiple issues where the engine might restart during zero-downtime patching while checking for a quiesced point in database activity for patching.
+ Fixed an issue related to DDL recovery that impacts restart of the DB instance while recovering an interrupted `DROP TRIGGER` operation.
+ Fixed a bug that might cause unavailability of the database if a crash occurs during the execution of certain partitioning operations. Specifically, an interrupted `ALTER TABLE` operation that modifies the type of partitioning or the number of partitions in a table.
+ Fix default value of `table_open_cache` on 16XL and 24XL instances which could cause repeated failovers and high CPU utilization on large instances classes (R4/R5-16XL, R5-12XL, R5-24XL). This impacted 1.21.x and 1.22.x.
**Global databases:**
+ Populate missing data in the MySQL `INFORMATION_SCHEMA.REPLICA_HOST_STATUS` view on primary and secondary AWS Regions in an Aurora global database.
+ Fixed unexpected query failures that could occur in a Global DB secondary Region due to garbage collection of UNDO records in the primary Region, after temporary network connectivity issues between the primary and secondary Regions.
**Parallel query:**
+ Fixed an issue where parallel query might cause a long-running query to return an empty result.
+ Fixed an issue where a query on a small table on the Aurora read replica might take more than one second.
+ Fixed an issue that might cause a restart when a parallel query and a DML statement are executing concurrently under a heavy workload.
**General improvements:**
+ Fixed an issue where queries using spatial index might return partial results if spatial index was created on tables with already existing large spatial values.
+ Increased maximum allowable length for audit system variables `server_audit_incl_users` and `server_audit_excl_users` from 1024 bytes to 2000 bytes.
+ Fixed an issue where a binlog replica connected to an Aurora MySQL binlog primary might show incomplete data when the Aurora MySQL binlog primary loads data from S3 under `statement` `binlog_format`.
+ Comply with community behavior to map `mixed` binlog\$1format to `row` instead of `statement` for loading data.
+ Fixed an issue causing binlog replication to stop working when the user closes the connection and the session is using temporary tables.
+ Improved response time of a query involving MyISAM temporary tables.
+ Fix permission issue when binlog worker runs a native lambda function.
+ Fixed an issue on Aurora read replicas when trying to query or rotate the slow log or general log.
+ Fixed an issue that broke logical replication when the `binlog_checksum` parameter is set to different values on the master and the replica.
+ Fixed an issue where the read replica might transiently see partial results of a recently committed transaction on the writer.
+ Include transaction info of the rolled-back transaction in `show engine innodb status` when a deadlock is resolved.
## Integration of MySQL community edition bug fixes
+ Binlog events with `ALTER TABLE ADD COLUMN ALGORITHM=QUICK` will be rewritten as `ALGORITHM=DEFAULT` to be compatible with the community edition.
+ BUG \$122350047: IF CLIENT KILLED AFTER ROLLBACK TO SAVEPOINT PREVIOUS STMTS COMMITTED
+ Bug \$129915479: RUNNING COM\$1REGISTER\$1SLAVE WITHOUT COM\$1BINLOG\$1DUMP CAN RESULTS IN SERVER EXIT
+ Bug \$130441969: BUG \$129723340: MYSQL SERVER CRASH AFTER SQL QUERY WITH DATA ?AST
+ Bug \$130628268: OUT OF MEMORY CRASH
+ Bug \$127081349: UNEXPECTED BEHAVIOUR WHEN DELETE WITH SPATIAL FUNCTION
+ Bug \$127230859: UNEXPECTED BEHAVIOUR WHILE HANDLING INVALID POLYGON"
+ Bug \$127081349: UNEXPECTED BEHAVIOUR WHEN DELETE WITH SPATIAL"
+ Bug \$126935001: ALTER TABLE AUTO\$1INCREMENT TRIES TO READ INDEX FROM DISCARDED TABLESPACE
+ Bug \$129770705: SERVER CRASHED WHILE EXECUTING SELECT WITH SPECIFIC WHERE CLAUSE
+ Bug \$127659490: SELECT USING DYNAMIC RANGE AND INDEX MERGE USE TOO MUCH MEMORY(OOM)
+ Bug \$124786290: REPLICATION BREAKS AFTER BUG \$174145 HAPPENS IN MASTER
+ Bug \$127703912: EXCESSIVE MEMORY USAGE WITH MANY PREPARE
+ Bug \$120527363: TRUNCATE TEMPORARY TABLE CRASH: \$1DICT\$1TF2\$1FLAG\$1IS\$1SET(TABLE, DICT\$1TF2\$1TEMPORARY)
+ Bug\$123103937 PS\$1TRUNCATE\$1ALL\$1TABLES() DOES NOT WORK IN SUPER\$1READ\$1ONLY MODE
+ Bug \$125053286: USE VIEW WITH CONDITION IN PROCEDURE CAUSES INCORRECT BEHAVIOR (fixed in 5.6.36)
+ Bug \$125586773: INCORRECT BEHAVIOR FOR CREATE TABLE SELECT IN A LOOP IN SP (fixed in 5.6.39)
+ Bug \$127407480: AUTOMATIC\$1SP\$1PRIVILEGES REQUIRES NEED THE INSERT PRIVILEGES FOR MYSQL.USER TABLE
+ Bug \$126997096: `relay_log_space` value is not updated in a synchronized manner so that its value is sometimes much higher than the actual disk space used by relay logs.
+ Bug\$115831300 SLAVE\$1TYPE\$1CONVERSIONS=ALL\$1NON\$1LOSSY NOT WORKING AS EXPECTED
+ SSL Bug backport Bug \$117087862, Bug \$120551271
+ Bug \$116894092: PERFORMANCE REGRESSION IN 5.6.6\$1 FOR INSERT INTO ... SELECT ... FROM (fixed in 5.6.15).
+ Port a bug fix related to `SLAVE_TYPE_CONVERSIONS`.