AliSQL kernel release notes

Minor version

Community version

Description

Expiration date

8.4.7

8.4.7

• New features

  • Incorporates changes from MySQL 8.4.7.

20260331

AliSQL version

Community MySQL version

Description

Expiration date

20260228

8.0.36

• New features

  • Added support for real-time application of large transactions.

• Performance optimizations

  • Optimized lock contention for MySQL replication in high-concurrency scenarios to reduce replication latency.

• Bug fixes

  • Fixed a 1-second replication latency issue caused by inconsistent system time settings between the primary and replica instances.

  • Fixed an issue where the real-time transmission of large transactions caused replication latency spikes on the replica instance.

  • Fixed an issue in native replication scenarios where granting the SUPER privilege caused replication to be interrupted. After the fix, only privileges held by the replication thread are granted.

  • Fixed an issue where the binary log cache free flush feature caused replication latency spikes.

—

20251231

8.0.36

• New features

  • Added support for creating vector indexes on nullable vector columns.

• Performance optimizations

  • Optimized lock release performance during the transaction commit phase.

• Bug fixes

  • Fixed an issue where the real-time DDL application feature was incorrectly applied to ALTER operations on temporary tables.

  • Fixed an out-of-bounds access issue during real-time DDL application logging.

  • Fixed a performance issue caused by trx_sys lock waits under high concurrency.

20251130

8.0.36

• New features

  • Upgraded jemalloc to version 5.3.

  • Added a CPU time consumption metric to the audit log.

• Performance optimizations

  • Optimized I/O thread transmission to improve semi-synchronous replication performance and replica instance efficiency under high-concurrency workloads.

  • Optimized SQL thread application to improve replication efficiency on replica instances with a mix of medium and small transactions.

• Bug fixes

  • Fixed issues in vector indexes, including memory leaks and DDL deadlocks.

  • Fixed a crash that occurred during data archiving operations.

—

20251031

8.0.36

• New features

  • Added support for vector capabilities, including a new vector column type, vector operation functions, and the ability to create vector indexes on vector columns.

  • Added support for instant extension of INT, VARCHAR, and CHAR column lengths.

  • Added support for DDL rate limiting.

  • The real-time DDL application now supports OPTIMIZE TABLE.

  • Real-time data transmission now supports setting require_row_format.

  • Added the cost_threshold_for_duckdb parameter. An error is reported if the optimizer's cost estimate for an SQL command exceeds this threshold.

• Performance optimizations

  • Optimized I/O thread transmission to improve semi-synchronous replication performance and replica instance efficiency under high-concurrency workloads.

  • Added support for redo log compression for BLOB fields to improve BLOB write performance.

• Bug fixes

  • Fixed performance spikes in single-statement transaction SBM.

  • Fixed an issue where purging relay logs caused slow acknowledgments in semi-synchronous replication.

  • Fixed a potential crash that occurred when a DDL operation was executed concurrently with an UPDATE operation on a table with a foreign key.

  • Fixed an issue in native replication scenarios where granting the SUPER privilege caused replication to be interrupted. After the fix, only privileges held by the replication thread are granted.

  • Fixed an issue where NULL values in JSON columns caused unexpected errors in prepared statements.

  • Fixed a performance issue caused by clearing the writeset.

—

20250731

8.0.36

• New features

  • Added the real-time DDL application feature.

  • Added support for online extension of INT, VARCHAR, and CHAR column lengths.

• Performance optimizations

  • Optimized write performance for large object (LOB) fields.

• Bug fixes

  • Fixed an issue where implicit primary keys could not be queried from information_schema.columns after an upgrade from an earlier version.

  • Fixed unexpected logging when innodb_log_optimize_ddl is set to OFF during index creation.

  • Fixed Community Bug #118476, resolving an issue where partitions could not be created with certain identifiers.

  • Fixed Community Bug #118872, resolving inaccurate statistics for Innodb_data_written.

  • Fixed Community Bug #105652, resolving an exception during crash recovery for tables that exceed 32 TB.

  • Fixed Community Bug #117275, which caused incorrect query results when index_merge used a descending primary key index.

—

20250531

8.0.36

• New features

  • Upgraded cURL to version 8.14.1.

  • Added support for real-time transmission of large transactions to replica instances during execution to prevent performance jitters caused by committing large transactions on semi-synchronous replication instances.

  • Added WAIT N and NO_WAIT hint syntaxes to let DML and DDL statements set the metadata lock (MDL) wait time.

  • Added support for non-blocking DDL to prevent DML statements from being blocked due to a metadata lock (MDL) acquisition timeout during DDL execution.

  • Added support for viewing the execution status of DDL statements and the status of metadata locks (MDLs) through a lightweight performance_schema implementation.

  • Added support for fast parsing of row records for tables that have not undergone INSTANT DDL operations.

  • Added support for enabling Binary Log in Redo and Binary Log Parallel Flush in semi-synchronous replication mode.

  • Added support for recording the end time of SQL statements in the start_time field of the slow query log.

  • Added a performance optimization feature for hot-row updates.

  • Optimized the DDL execution process to handle failures caused by unique key conflicts.

  • Added the number of active transactions and the average transaction execution time to the InnoDB status output.

• Performance optimizations

  • Improved the performance of primary key scanning, sorting, and index building during DDL execution.

  • Improved the parsing performance for the utf8mb3 character set.

• Bug fixes

  • Fixed an issue where reset slave all executed slowly.

  • Fixed an issue where the binlog_transaction_compression_level_zstd parameter did not take effect.

  • Fixed an issue where updating instant drop tables caused a crash.

  • Fixed a potential replication interruption when using writeset with foreign keys. This occurred when an INSERT statement did not specify a value for an auto-increment column.

  • Fixed an issue where version upgrades took a long time when the general log was enabled.

  • Fixed an issue where Hash Anti Join might produce incorrect results when join_buffer_size is small.

  • Fixed an issue where optimize table did not update the table status.

  • Fixed a statement ID overflow issue.

  • Fixed a crash issue in the Sequence Engine.

—

20241231

8.0.36

• New features

  • Upgraded cURL to version 8.11.1.

  • Added Key Management Service (KMS) support to the column encryption feature.

  • Added AES-256 algorithm support to the column encryption feature.

• Performance optimizations

  • Added support for multi-threaded parallel replay of the redo log during crash recovery to accelerate instance startup.

• Bug fixes

  • Fixed a table status error caused by the rename operation.

  • Fixed an incorrect server ID in the error log.

  • Fixed an issue where the start_time field was inaccurate for stored procedure calls recorded in the slow query log (slow log).

  • Resolving the issue of inaccurate undo tablespace information in information_schema.files after a MySQL restart.

  • Fixed an issue where automatic truncation of the undo tablespace failed during a MySQL restart.

  • Fixed missing error logs for stored procedures, events, and triggers during major version upgrades.

  • Fixed a memory leak during major version upgrades.

  • Fixed an issue where garbled characters were not checked when creating or modifying events and triggers.

—

20241130

8.0.36

• New features

  • Upgraded OpenSSL to version 3.0.15.

  • Upgraded cURL to version 8.9.1.

• Performance optimizations

  • Optimized the slow automatic repair process for the general log to reduce the instance Recovery Time Objective (RTO).

  • Optimized the double-write recovery process to reduce the instance Recovery Time Objective (RTO). For more information, see Community Bug #116209.

• Bug fixes

  • Fixed a crash caused by tables archived to object storage.

  • Fixed a ciphertext collision issue in EncDB column encryption.

  • Fixed an issue where the binary log was recorded even if an OPTIMIZE operation failed.

  • Fixed Community Bug #96236, which caused instance unavailability due to buffer pool exhaustion by internal temporary tables.

  • Fixed a potential crash when canceling a buffer pool shrink operation.

  • Fixed a crash or incorrect query result caused by referencing a CTE column in multiple query blocks and materializing the CTE table.

  • Fixed a crash caused by a subquery in a view definition where the definer does not exist or has insufficient permissions.

  • Fixed a potential crash when using multi-value indexes.

  • Fixed a crash during ranking calculation in full-text search (FTS).

—

20241031

8.0.36

• Bug fixes

  • Fixed Community Bug #115608, which resolved a data loss issue that could occur during an INPLACE DDL operation.

—

20240930

8.0.36

• New features

  • Added the innodb_instant_ddl_enabled parameter to control whether to enable instant DDL.

• Bug fixes

  • Fixed a crash that occurred when performing an UPDATE operation on a column added by an instant DDL operation.

  • Fixed a crash that occurred when performing a DELETE or UPDATE operation on a column dropped by an instant DDL operation.

—

20240731

8.0.36

• New features

  • The binary log dump thread can now skip empty events generated by the Binary Log Cache Free Flush feature.

• Performance optimizations

  • Optimized the Global Transaction Identifier (GTID) allocation process to improve performance in high-concurrency scenarios.

  • Fixed a performance issue with MD5 calculation in high-concurrency scenarios.

  • Optimized the automatic repair of the general log to resolve an issue that could prevent instance connections.

  • Optimized the retrieval and validation of tablespace metadata during instance startup to accelerate the startup of instances with a large number of tables.

  • Reduced lock holding time for DROP TABLE and TRUNCATE TABLE. When the new innodb_rds_drop_ahi_ahead parameter is enabled, the adaptive hash index for an InnoDB table is dropped before the DROP TABLE or TRUNCATE TABLE operation. This shortens the duration for which the InnoDB metadata lock is held and prevents other SQL statements from being blocked.

• Bug fixes

  • Fixed a crash when creating a full-text index with a parser.

  • Fixed a crash that occurred when a plugin received a NULL parameter after EncDB was enabled.

  • Fixed a crash related to tables archived in object storage.

  • Fixed an issue where DDL processes consumed the page cache.

  • Fixed inaccurate updated row counts in the audit log when INSERT or UPDATE statements failed.

  • Fixed a crash caused by using ALTER TABLE to add an auto-increment column as a primary key in descending order.

  • Fixed an issue where a binary log was recorded even if an OPTIMIZE TABLE operation failed.

—

20240630

8.0.36

• Bug fixes

  • Fixed unexpected behavior in the internal permission management of system tables. This fix allows user accounts to perform TRUNCATE operations on tables in Performance Schema.

  • Fixed a potential memory leak that occurred when recording redo logs for a table that has undergone an INSTANT DDL operation.

—

20240615

8.0.36

• Bug fixes

  • Fixed a crash during redo log writing caused by changing the order of non-instant columns within an Instant DDL operation.

—

20240531

8.0.36

• New features

  • Incorporated changes from the official Community MySQL versions 8.0.35 and 8.0.36.

  • Added support for automatically releasing NET::buff memory on long-lived connections to reduce memory usage and lower the risk of out-of-memory (OOM) errors.

• Performance optimizations

  • The Buffer Pool Extension now supports asynchronous I/O reads.

  • Optimized the scanning and validation of data files during instance startup to accelerate the startup of instances with a large number of tables.

• Bug fixes

  • Fixed an incorrect timestamp in the GTID Log Event generated by Binlog Cache Free Flush.

  • Fixed a major version upgrade failure from MySQL 5.7 to 8.0, which was caused by explicitly creating a column named FTS_DOC_ID in an InnoDB table.

  • Fixed an issue where EncDB returned incorrect data types.

  • Fixed an issue where table reclamation was still triggered on read-only replica instances after the recycle_bin parameter was disabled.

  • Fixed an issue where innodb_activity_count could be negative. For more information, see Community Bug #114180.

  • Fixed an issue where parallel reads on partitioned tables caused a parallel thread count leak, which in turn disabled parallel reads. For more information, see Community Bug #114154.

—

20240522

8.0.34

• Bug fixes

  • Fixed a redo log corruption issue caused by changing the order of non-instant columns in an instant DDL operation.

—

20240229

8.0.34

• New features

  • Upgraded OpenSSL to version 3.0.12.

  • Added a feature to record DDL operations in fault diagnosis logs.

  • Added the always-confidential database (in public preview) feature to implement end-to-end data encryption and protect data security.

• Bug fixes

  • Fixed an issue where semi-synchronous replication failed due to an error in comparing binary log filenames.

  • Fixed a backup set compatibility issue caused by implicit primary keys (IPK).

—

20240131

8.0.34

• New features

  Statement Outline now supports the ps-protocol.

• Bug fixes

  • Fixed an issue where the memory count in the performance_schema.memory_summary_by_thread_by_event_name table was over-reported when the thread pool was enabled.

  • Fixed an issue where auto-increment columns frequently reported duplicate entry errors after an X-Engine instance was restarted.

  • Fixed an issue where the "ERROR 1878 (HY000): Temporary file write failure." error was reported when creating a full-text index with innodb_disable_sort_file_cache=ON.

  • Fixed an issue where the parser for a full-text index rebuilt by using an INPLACE DDL statement in a single statement did not take effect. For more information, see Community Bug #110976.

  • Fixed an issue where the automatic cleanup logic on read-only replica instances did not work as expected after the recycle_bin parameter was modified.

  • Fixed a crash caused by executing CREATE SEQUENCE in a prepared statement.

—

20230930

8.0.34

• New features

  • Incorporated changes from the official Community MySQL versions 8.0.32, 8.0.33, and 8.0.34.

  • Upgraded OpenSSL from version 1.1.1u to 3.0.10.

  • Added the built-in function SM3().

  • The Buffer Pool Extension feature now supports online resizing.

  • Changed the default value of the ssl_cipher parameter to "ALL:@SECLEVEL=0".

• Performance optimizations

  • Added support for the binary log cache free flush feature.

    During the transaction commit phase, this feature directly converts the temporary binary log cache files of large transactions into binary log files. This reduces the time that a global binary log lock is held during the commit of large transactions and alleviates I/O pressure on the instance. This prevents a high availability (HA) switchover that can be caused by the instance being unable to write binary logs for an extended period or by I/O hangs.

  • Fixed a 1-second replication latency issue.

  • Optimized the memory usage of the Buffer Pool Extension.

  • Optimized the I/O efficiency of parallel reads when innodb_use_native_aio is set to off. For more information, see Community Bug #112137.

• Bug fixes

  • Fixed an issue where the Performance Schema memory monitoring items did not collect statistics for the buffer pool and Buffer Pool Extension.

  • Fixed a major version upgrade failure caused by case-sensitive inconsistencies of field names in an index between the server layer and the InnoDB layer.

—

20230914

8.0.31

• Bug fixes

  • The INPLACE algorithm is used by default instead of the INSTANT algorithm when you add or drop columns to avoid stability issues caused by the INSTANT algorithm.

—

20230630

8.0.31

• New features

  • Incorporated changes from the official Community MySQL version 8.0.31.

  • Added support for canceling an in-progress online resize of the buffer pool.

  • Statement Concurrency Control now supports template-level control, limiting the execution of SQL statements that use the same template. For more information, see Statement Concurrency Control.

  • Upgraded zlib to version 1.2.13.

  • Upgraded OpenSSL to version 1.1.1u.

  • Added the Innodb_redo_file_used_ratio status variable to show the usage ratio of redo log files.

  • X-Engine now supports deployment in ARM environments.

• Performance optimizations

  • Optimized mysqld_safe.sh to accelerate instance startup.

• Bug fixes

  • Fixed an issue where XA transactions could not be correctly recovered after an instance restart. For more information, see Community Bug #110533.

  • Fixed an abnormal instance restart caused by an incorrect sql_type in the thread pool.

  • Fixed an issue where debug information was missing from the installation package. For more information, see Community Bug #109560.

  • Fixed an issue where an upgrade from MySQL 5.7 to MySQL 8.0 failed due to temporary tables created in MySQL 5.6.

  • Fixed an issue where X-Engine transactions were occasionally lost in deadlock scenarios.

  • Fixed an issue where transactions could not be committed when Binary Log in Redo and Binary Log Parallel Flush were running under high loads for an extended period.

—

20230620

8.0.28

• Bug fixes

  • Introduced a delayed start for group replication to prevent cluster operations from failing when an instance is quickly restarted and reconnected to the cluster.

  • Fixed an issue where transactions could not be committed on an instance when Binary Log in Redo and Binary Log Parallel Flush were running under high loads for an extended period.

—

20230610

8.0.28

• Bug fixes

  • Fixed a deadlock that occurred when executing COM_STATISTICS, COM_CHANGE_USER, and SHOW PROCESSLIST statements, which made the instance unreachable. For more information, see Community Bug #110494.

  • Fixed an issue where backup tasks failed because the background cleanup task of the X-Engine engine exited unexpectedly.

—

20230324

8.0.28

• Bug fixes

  • Fixed an issue where the Binary Log in Redo feature was unexpectedly enabled in semi-synchronous replication mode.

—

20221231

8.0.28

• New features

  • Added support for enabling parallel writing of binary logs when sync_binlog is not set to 1. This improves the write performance of binary logs in high-concurrency workloads and significantly boosts the write performance of the instance.

  • Added a feature to MySQL Group Replication (MGR) to forcefully clear authentication information in single-primary mode. This default-enabled feature resolves issues such as periodic performance jitters, high memory usage, and performance degradation to zero when new nodes join the cluster in high-pressure, high-latency scenarios.

  • When an MGR primary election command is initiated, if a transaction exceeds the timeout specified in the SQL statement, the transaction is forcefully rolled back. This prevents the election from being blocked and improves the success rate of the election.

  • Upgraded OpenSSL to version 1.1.1s.

• Performance optimizations

  • Enhanced the asynchronous data file purge feature. For tables with a large number of dirty pages, this improves the execution speed of DROP TABLE and TRUNCATE TABLE statements.

  • Added purge statistics to Performance Agent, including:

    • INNODB_UNDO_SIZE_USED: The size of the used undo log.

    • INNODB_PURGE_LIMIT_TRX_NO: The purge position, which is the maximum transaction number that has been purged.

    • INNODB_PURGE_ITER_TRX_NO: The maximum transaction number that can be purged.

• Bug fixes

  • Fixed an issue where an EXPLAIN UPDATE statement involving a subquery with a derived table could cause an instance to crash. For more information, see Community Bug #31884434.

  • Fixed an issue where SELECT COUNT(*) returned inaccurate results when multi-value indexes were used. For more information, see Community Bug #104898.

  • Fixed an issue where a query returned only a partial result set after a multi-value index was added to a table with a JSON column. For more information, see Community Bug #106621.

  • Fixed a memory leak in the Clone_persist_gtid thread. For more information, see Community Bug #107991.

  • Fixed inaccurate updated row counts in the audit log when UPDATE and INSERT statements were executed with the CLIENT_FOUND_ROWS capability bit enabled (disabled by default).

  • Fixed a major version upgrade failure from MySQL 5.7 to MySQL 8.0 caused by a case mismatch of column names between the server layer and the InnoDB layer.

  • Fixed a major version upgrade failure from MySQL 5.7 to MySQL 8.0 caused by invalid strings in table, column, and index comments.

—

20221121

8.0.28

• Bug fixes

  • Fixed an issue where a reference to a temporary table was not correctly assigned to a Common Table Expression (CTE) when a query was performed by using the CTE syntax in certain scenarios.

—

20220830

8.0.28

• New features

  • Incorporated changes from the official Community MySQL versions 8.0.26, 8.0.27, and 8.0.28.

  • Added the json_document_max_depth parameter to allow you to configure the nesting depth for JSON data.

• Performance optimizations

  • Optimized the parallel initialization performance of the buffer pool.

• Bug fixes

  • Fixed an issue where redo logs were recorded for temporary tablespaces.

—

20220730

8.0.25

• Performance optimizations

  • Optimized the performance of Buffer Pool Free Resize.

—

20220530

8.0.25

• New features

  • For single-node instances that use cloud disks, this version added support for incremental backups and point-in-time recovery (PITR) using redo logs.

  • Added the Persist Binary Log Into Redo V2 feature, which is optimized for high concurrency and provides better performance under high concurrency.

  • Optimized the SSL encryption feature and fixed some internal errors.

  • Revoked the permissions of standard accounts to operate on the sys and performance_schema databases.

  • Added log records for FLUSH TABLES WITH READ LOCK and UNLOCK TABLES to the error log to facilitate online troubleshooting.

• Performance optimizations

  • Improved the performance of buffer pool initialization.

  • Optimized crash recovery by making the rollback of pending transactions asynchronous, which improves the Recovery Time Objective (RTO).

  • Optimized the memory usage and update speed of the adaptive hash index (AHI).

  • Optimized bidirectional circular replication. When a replica instance sends a binary log to the primary instance, it skips transactions that belong to the primary instance, reducing network traffic for circular replication.

  • Accelerated the instance restart speed after a crash.

• Bug fixes

  • Fixed an issue where the mysql.events table failed to migrate during a major version upgrade from MySQL 5.7 to MySQL 8.0.

  • Fixed a potential crash when deleting a full-text index table during a multi-step major version upgrade from a MySQL 5.6 instance to MySQL 8.0.

  • Fixed a potential instance crash in business scenarios with high metadata lock (MDL) contention.

  • Fixed a parsing error in xengine_record.

  • Fixed a compression failure when X-Engine builds an index.

  • Corrected the data in the start_time column of the slow_log table.

  • Optimized compilation speed and fixed compilation warnings.

—

20220523

8.0.25

• Bug fixes

  • Fixed an issue where a SELECT COUNT(*) statement without a WHERE clause executed slowly.

  • Fixed a crash caused by multiple calls to a stored procedure that uses the WITH ROLLUP syntax.

—

20220331

8.0.25

• New features

  • Removed the restriction that innodb_buffer_pool_instances cannot be greater than 1 when innodb_buffer_pool_size is less than 1 GB.

  • Reduced the performance impact of enabling the Native Flashback feature.

• Bug fixes

  • Fixed an issue where the Unknown thread id error was reported when a session was killed.

  • Fixed an issue where the rds_expose_priv_list parameter setting did not take effect after a restart.

  • Fixed an issue where the Binary Log in Redo feature blocked the advancement of the checkpoint position.

  • Incorporated bug fixes from the official Community MySQL version 8.0.25 (Bug#33341080, Bug#32962511).

—

20210930

8.0.25

• New features

  • Incorporated changes from the official Community MySQL version 8.0.25.

  • Introduced the recovery_apply_binlog mechanism to make XA transactions crash-safe.

  • The audit log now supports V3. It adds a separate column for the transaction ID and an ext field to indicate whether an SQL statement was truncated.

  • Allowed a new SEQUENCE type to be defined as TIMESTAMP SEQUENCE, which has a different format compared to the original DIGITAL SEQUENCE.

    Syntax: CREATE SEQUENCE seq CACHE [cache_size] TIMESTAMP;

  • Granted TRUNCATE permissions on the mysql.slow_log and mysql.general_log tables to privileged accounts.

  • Added the Native Flashback Query feature, which supports rollback queries and data recovery directly through SQL statements.

  • Added the self-developed X-Tree as an index for X-Engine MemTable, which supports high-performance writes, point queries, and range queries.

  • Added support for freely adjusting the buffer pool size and optimized the adjustment process to avoid impacting instance performance.

  • Added support for the Multi-Block Read feature. You can add the HINT /*+ MULTI_BLOCKS(n) */ in an SQL statement to pre-read multiple data pages.

  • Optimized the logic for scanning the buffer pool LRU list to get free pages.

  • Added support for UPDATE and DELETE statements with a primary key or unique key to automatically enter the Statement Concurrency Control queue.

  • Added TCP write wait duration to the performance_schema.events_statements_summary_by_digest_supplement table.

  • Allowed DDL statements to record redo logs when executed in INPLACE mode.

  • Added MyISAM to the disabled_storage_engines parameter by default, which disables the creation of MyISAM tables.

• Bug fixes

  • Fixed an issue where the execution result of SHOW GLOBAL STATUS was abnormal.

  • Fixed an issue where enabling Jemalloc Profiling prevented the instance from starting.

  • Fixed a crash when using SEQUENCE in an INSERT INTO SELECT statement.

  • Revoked the dbms_recycle.restore_table permission.

  • Added the number of index scans to the I_S.INDEX_STATISTICS table.

  • Added more performance metrics to the I_S.PERF_STATISTICS table.

  • Optimized the call performance when user-defined functions (nextval and currval) conflicted with the SEQUENCE system function.

  • X-Engine now instantly responds to user-initiated KILL SESSION requests.

  • Fixed an issue in X-Engine where some DDL operations were left in an inconsistent state after failing in extreme scenarios.

  • Added a stack overflow protection mechanism.

  • Fixed an issue where mysqld failed to start when persist_binlog_to_redo and X-Engine were enabled at the same time.

  • Fixed a memory leak caused by pthread_getattr_np.

  • Automatically cleaned up the page cache generated by Performance Agent files.

  • Fixed internal errors in the Statement Outline feature.

  • Fixed an issue where the session tracker was reset when a statement execution failed.

  • Adjusted the name of the ccl_wait_timeout variable.

    Note

    ccl_wait_timeout refers to the maximum wait time (in seconds) for a throttled statement.

  • Fixed a restart failure caused by not cleaning up socket files when a process exited.

  • Adjusted the priority of user-defined functions (nextval or currval).

  • Fixed the 251 error returned by net_length_size.

—

20201031

8.0.18

• New features

  • Added support for restoring tables from the recycle bin.

  • Automatically restored slow query log files during instance initialization.

• Performance optimizations

  • The Binary Log in Redo feature is disabled when the X-Engine engine is used.

• Bug fixes

  • Fixed an ASSERT exception caused by an excessively large unique key value.

  • Fixed an issue where the COM_DAEMON daemon process could not be terminated.

  • Fixed a cache overflow issue caused by FTS queries.

  • Fixed a rollback error after an Instant DDL crash.

20240601

20200831

8.0.18

• New features

  • Added an option to control whether the COUNT(*) function is allowed to perform parallel scans. You can set the innodb_parallel_read_threads parameter to 0 to disable parallel scans for this function. For more information, see Set instance parameters.

  • Added start gtid and stop gtid options to the mysqlbinlog utility.

  • Added support for outputting various LSN values of the redo log:

    • innodb_lsn: the LSN of the redo log.

    • innodb_log_checkpoint_lsn: the LSN of the last checkpoint.

    • innodb_log_write_lsn: the LSN of the log write.

    • innodb_log_ready_for_write_lsn: the LSN when the log buffer is complete.

    • innodb_log_flush_lsn: the LSN of the redo log flushed to disk.

    • innodb_log_dirty_pages_added_up_to_lsn: the LSN up to which dirty pages have been added.

    • innodb_log_oldest_lsn: the LSN of the oldest page flush.

• Performance optimizations

  • Optimized the wait and concurrency mechanism of Statement Concurrency Control (CCL).

  • Adjusted the execution priority of Statement Concurrency Control in stored procedures.

• Bug fixes

  • Fixed an issue where the heap memory size was not checked during parser recursion.

  • Fixed an issue where table definitions could not be modified when TDE was enabled.

  • Fixed a memory leak in the event scheduler.

20240601

20200630

8.0.18

• New features

  • Faster DDL: Optimized the buffer pool management mechanism during DDL operations to reduce the performance impact of DDL operations and increase the concurrency of online DDL operations.

  • Increased the maximum number of connections to 500,000.

• Performance optimizations

  • Internal optimization of the thread pool.

  • Set an upper limit on the memory occupied by Performance Schema based on instance specifications.

  • No longer checked audit log files.

  • TDE now caches keys provided by the KMS service.

  • Modified the status of threads running in Statement Concurrency Control.

• Bug fixes

  • Fixed an issue where Statement Outline considered a semicolon (;) as part of the input query when calculating the digest.

  • Fixed a server crash caused by altering a table.

  • Fixed a compatibility issue with the keywords MEMBER and ARRAY in older versions.

  • Fixed an issue where the wait count was incorrect when reading client commands.

  • Fixed an AliSQL version upgrade failure.

20240601

20200430

8.0.18

• New features

  • Binary Log in Redo: Optimized the transaction commit mechanism by writing the binary log to the redo log, which improves database performance.

  • Refactored the row cache code for the X-Engine engine.

  • Opened the XA_RECOVER_ADMIN permission.

• Performance optimizations

  • When operating on InnoDB temporary tables, only the dirty page list is scanned instead of the entire buffer pool list.

  • For compatibility with MySQL 5.6, the global parameter opt_readonly_trans_implicit_commit is renamed to rds_disable_explicit_trans.

  • During instance upgrades, upgrade-related logs are not recorded in the audit log.

  • Reduced memory consumption when performing DDL operations on tables that use the X-Engine engine.

• Bug fixes

  • Fixed an issue where the actual size of X-Engine tables on disk was inconsistent with the statistics in information_schema.

  • Fixed an issue where reopening the error log caused the X-Engine log to be re-initialized.

20240601

20200331

8.0.18

• New features

  • Incorporated changes from the official Community MySQL versions 8.0.17 and 8.0.18.

  • Recycle Bin: Added support for the TRUNCATE TABLE command. When executed, the original table is moved to a dedicated recycle bin directory, and a new table with the same structure is created.

• Performance optimizations

  • Disabled the output of TCP errors by default.

  • Improved the performance of the thread pool with default configurations.

• Bug fixes

  • Fixed an issue where invalid databases and tables were caused by partitioning filenames with #p.

  • Made Statement Concurrency Control matching case-insensitive.

20240601

20200229

8.0.16

• New features

  • Performance Agent: A more convenient performance data statistics solution. It collects and counts various internal performance data of a MySQL instance through a MySQL plugin.

  • Added network round-trip time in semi-synchronous mode and recorded it in performance data.

  • The X-Engine engine now supports online DDL.

• Performance optimizations

  • Allowed Statement Concurrency Control (CCL) operations on read-only instances.

  • Replica instances now support Statement Outline.

  • Optimized proxy short-lived connections.

  • Optimized the execution time of the PAUSE instruction on different CPU architectures.

  • Added a memory table to view the running status of the thread pool.

  • Optimized thread pool performance.

• Bug fixes

  • Disabled ppoll and used poll instead in Linux kernels earlier than 4.9.

  • Fixed a wrap_sm4_encrypt function call error.

  • Fixed an issue where a global variable lock was held when rolling audit logs.

  • Fixed a recovery inconsistency check issue.

  • Fixed an issue where the io_statistics table had incorrect time values.

  • Fixed a crash caused by an invalid compression algorithm.

  • Fixed a user column incompatibility with version 5.6.

  • Fixed a buffer count leak issue.

20240601

20200110

8.0.16

• New features

  • Inventory Hint: Added three hints that support SELECT, UPDATE, INSERT, and DELETE statements to quickly commit or roll back transactions and improve business throughput.

• Performance optimizations

  • When an instance starts, the Statement Concurrency Control queue structure is initialized before the Statement Concurrency Control rules.

  • Canceled links to small files during asynchronous file cleanup.

  • Optimized Thread Pool performance.

  • Disabled recovery inconsistency checks by default.

  • Changed the permissions required to set variables:

    • The permission required to set the following variables has been changed to standard user privileges:

      • auto_increment_increment

      • auto_increment_offset

      • bulk_insert_buffer_size

      • binlog_rows_query_log_events

    • The permission required to set the following variables has been changed to superuser or system variable administrator privileges:

      • binlog_format

      • binlog_row_image

      • binlog_direct

      • sql_log_off

      • sql_log_bin

20240601

20191225

8.0.16

• New features

  • Recycle Bin: Temporarily moves deleted tables to the recycle bin and allows you to set a retention period to facilitate data recovery.

• Performance optimizations

  • Improved the handling performance of short-lived connections.

  • Used a dedicated thread to serve maintain user to avoid high availability failures.

  • Explicitly released the file synchronization lock when an error occurs while flushing the binary log through the redo log.

  • Removed unnecessary TCP error logs.

  • Enabled the thread pool by default.

• Bug fixes

  • Fixed a slow query log flush issue.

  • Fixed an incorrect lock scope issue.

  • Fixed a core dump issue caused by the TDE SELECT function.

20240601

20191115

8.0.16

• New features

  • Statement Queue: A queuing mechanism for statements that groups statements into buckets. It tries to place statements with potential conflicts into the same bucket to reduce conflict overhead.

20240601

20191101

8.0.16

• New features

  • Added the SM4 encryption algorithm for TDE.

  • Protected replica instance information: Only users with SUPER or REPLICATION_SLAVE_ADMIN privileges can insert, delete, or modify the tables slave_master_info, slave_relay_log_info, and slave_worker_info.

  • Increased the priority of auto-increment keys: If a table has no primary key or non-null unique key, a non-null key with auto-increment becomes the first candidate.

  • Disabled the automatic conversion from the MEMORY engine to the MyISAM engine for system tables and tables used by threads in an initialization state.

  • Flushed the binary log file to disk before flushing the redo log.

  • Temporary tables are now also affected when an instance is locked.

  • Added X-Engine, a new transaction storage engine based on LSM-tree.

• Performance optimizations

  • Thread Pool: Mutex optimization.

  • Performance Insight: Performance points now support the thread pool.

  • Parameter adjustments:

    • primary_fast_lookup: A session parameter with a default value of true.

    • thread_pool_enabled: A global parameter with a default value of true.

20240601

20191015

8.0.16

• New features

  • Transparent Data Encryption (TDE): Added support for TDE, which performs real-time I/O encryption and decryption of data files. Data is encrypted before being written to disk and decrypted when read from disk into memory.

  • Returning: The Returning feature supports DML statements returning a ResultSet and provides the DBMS_TRANS toolkit for convenient use.

  • Added support for forcing engine conversion to InnoDB. If the global variable force_myisam_to_innodb or force_memory_to_innodb is set to ON, tables created with the MyISAM or MEMORY engine are automatically converted to InnoDB.

  • Prohibited non-privileged accounts from switching between primary and replica instances.

  • Performance agent plugin: Collects performance data and saves it to a local formatted text file. It uses file rotation to retain the most recent per-second performance data.

  • Configurable InnoDB mutex timeout: The global variable innodb_fatal_semaphore_wait_threshold is now configurable, with a default value of 600.

  • Ignore index hint errors: The global variable ignore_index_hint_error is now configurable, with a default value of false.

  • The SSL encryption feature can be disabled.

  • TCP error information: Returns TCP direction (read, read wait, write wait) errors and error codes to the end_connection event and outputs error information to the error log.

• Bug fixes

  • On Linux systems that support native AIO, AIO requests are merged before a linear read-ahead is triggered.

  • Optimized table and index statistics.

  • If a primary key is specified, the primary index is accessed directly.

20240601

20190915

8.0.16

• Bug fixes

  • Fixed a memory leak in Cmd_set_current_connection.

20240601

20190816

8.0.16

• New features

  • Thread Pool: Separates threads from sessions. Even with a large number of sessions, only a small number of threads are needed to complete the tasks of active sessions.

  • Statement Concurrency Control: Manages sudden database request traffic, high-resource-consuming statement access, and changes in SQL access models by controlling concurrency to ensure the continuous and stable operation of the MySQL instance.

  • Statement Outline: Uses optimizer hints and index hints to stabilize MySQL execution plans.

  • Sequence Engine: Simplifies the complexity of obtaining sequence values.

  • Purge Large File Asynchronously: When a single tablespace is deleted, the tablespace file is renamed to a temporary file, and an asynchronous process cleans up the temporary file.

  • Performance Insight: A powerful tool for instance load monitoring, correlation analysis, and performance tuning that helps you quickly assess database load, find the source of performance issues, and improve database stability.

  • Optimized instance lock status: DROP or TRUNCATE operations are allowed on tables even when the instance is locked.

• Bug fixes

  • Fixed a file size calculation error.

  • Fixed an issue where idle memory was occasionally reused.

  • Fixed a crash when the host cache size was 0.

  • Fixed a conflict between implicit primary keys and CTS statements.

  • Fixed an slog error caused by a slow query.

20240601

20190601

8.0.16

• Performance optimizations

  • Reduced the metadata lock (MDL) scope for log tables to decrease the possibility of MDL blocking.

  • Refactored the code for termination options.

• Bug fixes

  • Fixed an issue where prepared statements were not recorded in the audit log.

  • Masked error logs for invalid table names.

20240601

Version

Description

20230415

• Bug fixes

  • Fixed a stability issue in large transaction scenarios.

  • Fixed an issue where the Seconds_Behind_Master value was not 0 on the secondary instance when there was no traffic.

20230406

• Performance optimizations

  • Improved the performance of Faster DDL. When a session that generates temporary tables exits, the page eviction process is optimized to scan only pages related to those tables, not the entire buffer pool. This reduces wait times for temporary table eviction, minimizes contention, and improves overall performance.

20210305

• Bug fixes

  • Fixed a memory leak in Performance Schema.

20200918

• New features

  • You can now enable SSL encryption on a dedicated proxy.

20200805

• Bug fixes

  • Fixed a metadata issue.

20200608

• New features

  • Merged changes from the official MySQL Community Edition 8.0.17 and 8.0.18 releases.

  • Recycle Bin: Now supports the TRUNCATE TABLE statement. When you run this statement, the original table is moved to a dedicated recycle bin directory, and a new table with the same schema is created.

• Performance optimizations

  • Disabled TCP error output by default.

  • Improved the performance of the thread pool when using its default settings.

• Bug fixes

  • Fixed an issue that caused databases and tables to be invalidated when partition filenames were split by #p.

  • Fixed an issue where CCL matching was case-sensitive. Matching is now case-insensitive.

20200317

• New features

  • Performance Agent: Introduced the Performance Agent. This feature is a MySQL plugin that collects and analyzes internal performance data from a MySQL instance, providing a more convenient way to gather performance statistics.

  • Faster DDL: Introduced Faster DDL. This feature optimizes buffer pool management during DDL operations to reduce performance impact and increase online DDL concurrency.

  • Added network round-trip time (RTT) metrics for semi-synchronous mode to the performance data.

• Performance optimizations

  • Enabled statement-level Concurrency Control (CCL) on read-only instances.

  • Secondary instances now support Outline.

  • Optimized proxy short-lived connections.

  • Optimized pause instruction execution time across CPU architectures.

  • Added in-memory tables to view thread pool status.

  • Optimized thread pool performance.

• Bug fixes

  • Replaced ppoll with poll on Linux kernels earlier than 4.9.

  • Fixed incorrect calls to wrap_sm4_encrypt.

  • Fixed an issue where a global variable lock was held during audit log rotation.

  • Fixed an issue with recovery inconsistency checks.

  • Fixed incorrect time values in the io_statistics table.

  • Fixed a crash caused by an invalid compression algorithm.

  • Fixed a user column incompatibility with MySQL 5.6.

  • Fixed buffer reference count leaks.

AliSQL version

Community MySQL version

Description

Expiration date

20260228

5.7.44

New features

• Added support for SET_VAR optimizer hints.

• Added the rds_cost_threshold_for_duckdb parameter.

—

20251220

5.7.44

• New features

  • Added a CPU time metric to the audit log.

• Bug fixes

  1. Fixed an issue where the Sequence Engine caused an instance to restart when recording and rotating the binary log.

  2. Fixed an issue where version upgrades took a long time when the general log was enabled.

  3. Fixed a performance issue caused by trx_sys lock waits under high concurrency.

20251031

5.7.44

• New features

  • Added support for online length extension for INT, VARCHAR, and CHAR data types.

  • Added support for instant modification of column character sets.

  • Supports the automatic release of NET::buff memory on long connections, reducing memory resource usage and lowering the risk of OOM.

  • Added the built-in functions statement_digest and statement_digest_text.

• Bug fixes

  • Fixed an issue in native replication scenarios where granting the SUPER privilege caused replication to be interrupted. After the fix, only the privileges owned by the replication thread are granted.

  • Fixed Community Bug #105652, resolving an exception during crash recovery for tables that exceed 32 TB.

  • Fixed a potential crash that could occur when a DDL operation was run concurrently with an UPDATE statement on a table with a foreign key.

  • Fixed an issue with performance spikes in single-statement transaction processing.

  • Fixed an issue where purging relay logs caused slow acknowledgments in semi-synchronous replication.

  • Fixed a performance issue caused by clearing the writeset.

  • Fixed Community Bug #118476, which prevented partitions from being created with certain identifiers.

—

20250831

5.7.44

• Bug fixes

  • Fixed an issue where the innodb_max_mtr_records_for_tmp_table parameter caused query exceptions.

—

20250430

5.7.44

• New features

  • Added support for Visible Index and Invisible Index.

  • You can record the end time of an SQL query in the start_time field of the slow query log.

• Performance improvements

  • Improved the execution efficiency of the REPLACE function.

  • Enabled GTID auto-positioning, which allows a replica to automatically skip gap transactions when replication starts.

• Bug fixes

  • Fixed an issue where the start_time field was incorrect in the slow query log for CALL PROCEDURE.

—

20250331

5.7.44

• New features

  • Added support for the instant add column feature. For details, see Instant Add Column.

• Performance improvements

  • Fixed an issue where Writeset-based replication was interrupted in scenarios that involved unique indexes on string prefixes.

—

20241231

5.7.44

• New features

  • Added template-level statement concurrency control to limit the execution of SQL statements that use the same template.

  • The column-based data encryption feature supports key management by using Key Management Service (KMS).

  • The column-based data encryption feature now supports the AES-256 algorithm.

—

20241130

5.7.44

• New features

  • Upgraded OpenSSL to version 3.0.15.

• Performance improvements

  • Optimized the automatic repair process for the general log during crash recovery to reduce repair time.

• Bug fixes

  • Fixed Community Bug #96236, which caused an instance to become unavailable due to buffer pool exhaustion from internal temporary tables.

  • Fixed a potential instance crash when a buffer pool scale-in operation was canceled.

  • Fixed Community Bug #99643, which resolves an issue where transactions hang and cannot be killed due to an invalid value for trx->in_innodb.

  • Fixed an issue where the binary log was recorded even if an OPTIMIZE TABLE operation failed.

  • Fixed a ciphertext collision issue in EncDB column-based data encryption.

—

20240930

5.7.44

• New features

  • RDS instances that run MySQL 5.7 on Basic Edition now support native replication.

—

20240731

5.7.44

• New features

  • The binary log dump thread can now skip ignorable log events generated by the binlog cache free flush feature.

  • Added support for dynamically modifying encdb parameters.

• Performance improvements

  • Removed unnecessary server hooks to reduce lock contention during DML operations.

  • This feature optimizes the lock holding time for TRUNCATE TABLE operations. When you enable the innodb_rds_drop_ahi_ahead parameter, the adaptive hash index (AHI) for a table is dropped before the InnoDB table is truncated. This process shortens the holding time of the InnoDB metadata lock (MDL) during statement execution and prevents other SQL statements from being blocked.

  • Optimized the automatic repair process for the general log during crash recovery to reduce repair time.

• Bug fixes

  • Fixed an issue where the crash recovery process was stuck at 99%.

  • Fixed an issue where ANALYZE TABLE could cause a large number of SQL statements to get stuck in the "Waiting for table flush" state.

  • Fixed an issue where end_log_pos was incorrect for the binlog cache free flush feature.

  • Fixed a page validation error during crash recovery writes.

  • Fixed an issue where memory information was not collected by performance_schema when the buffer pool was initialized with multiple threads.

  • Fixed a crash caused by encdb timestamp processing.

  • Fixed an issue where the binary log was recorded even if an OPTIMIZE TABLE operation failed.

  • Fixed an issue where UPDATE statements unnecessarily acquired AUTO_INC locks.

—

20240430

5.7.44

• Performance improvements

  • Optimized the lock holding time for DROP TABLE. A new parameter, innodb_rds_drop_ahi_ahead, is introduced. When this parameter is enabled, the adaptive hash index for a table is deleted before the InnoDB table is dropped. This shortens the holding time of the InnoDB metadata lock during a DROP TABLE operation and prevents other SQL statements from being blocked.

  • Added support for the binlog cache free flush feature. During the transaction commit phase, this feature directly converts the temporary binary log cache files of large transactions into binary log files. This reduces the time that a global lock is held on binary logs when large transactions are committed, alleviates the I/O pressure on the instance, and prevents high availability (HA) switchovers caused by the instance being unable to write binary logs for an extended period or by I/O hangs.

• Bug fixes

  • Fixed an issue where the AUTO_INCREMENT value of an InnoDB table on a replica became inconsistent with the actual data due to a REPLACE INTO statement.

  • Fixed an issue where INSERT ... SELECT statements allowed the insertion of incompatible GEOMETRY type data.

  • Fixed an issue where data types returned by EncDB were inconsistent.

  • Fixed an issue where an "error 1305: savepoint does not exist." error could occur when you perform a backup by using Percona mysqldump with the --lock-for-backup option.

—

20240229

5.7.44

• New features

  • Incorporated changes from the official Community MySQL version 5.7.44.

  • Statement Outline supports the ps-protocol.

  • Upgraded OpenSSL to version 3.0.12.

  • EncDB now supports querying encryption rules and users.

• Performance improvements

  • Addressed an issue that caused a 1-second replication latency.

• Bug fixes

  • Fixed an issue where irrelevant errors were reported after a tablespace was discarded.

  • Fixed an issue where table reclamation was still triggered on replica instances after the recycle_bin parameter was disabled.

  • Fixed a potential crash when concurrently querying common tables and the information_schema.PARAMETERS or information_schema.ROUTINES system tables.

  • Fixed a slow query log write failure caused by a missing slow_log.CSV file.

  • Fixed a null pointer access issue that occasionally occurred when the query cache plugin was quickly unloaded after being loaded.

  • Fixed an issue where the truncation position of multiple statements recorded in audit log V3 was inaccurate when the statements were merged into a single query.

  • Fixed an issue where DROP TABLE FORCE was ineffective on tables with foreign key dependencies.

  • Fixed an issue where the more_result field in an OK packet was abnormal in multi-statement scenarios. This fix allows MaxScale to restore the session state by using multiple statements.

  • Fixed an issue where semi-synchronous replication failed due to an error in comparing binary log filenames.

  • Fixed an issue where EncDB wrote a NULL value as the timestamp when the explicit_defaults_for_timestamp parameter was set.

—

20240115

5.7.43

• Bug fixes

  • Fixed an issue where EncDB could not identify sensitive columns when a SQL query contained a table alias.

  • Fixed a system crash that occurred when the constructor of the internal DesensitizationAlgo class in EncDB received invalid input.

  • Fixed an issue where EncDB always output logs when no sensitive rules were configured, which could lead to disk exhaustion.

  • Fixed an issue where EncDB returned an error when handling users of the noneAccess type if the calculated ciphertext size and the actually generated ciphertext size were inconsistent.

—

20231215

5.7.43

• Bug fixes

  • Fixed an issue where clients could not connect to the server by using TLSv1.0 or TLSv1.1 after MySQL was upgraded with OpenSSL 3.0.9.

—

20231031

5.7.43

• Bug fixes

  • Fixed an issue where EncDB parameter settings did not take effect.

—

20230831

5.7.43

• New features

  • Incorporated changes from the official Community MySQL version 5.7.43.

  • Upgraded OpenSSL to version 3.0.9.

  • Accelerated MySQL startup through mysqld_safe by using built-in shell functions to parse parameters.

  • Added the always-confidential database feature to implement end-to-end data encryption and ensure data security.

• Bug fixes

  • Fixed an abnormal instance restart caused by an incorrect sql_type in the thread pool.

  • Fixed an infinite loop caused by an incorrect fil_addr pointer during the recovery of the undo table lock.

  • Fixed an issue where the audit log did not record multi-statement queries.

—

20230531

5.7.42

• New features

  • Incorporated changes from the official Community MySQL version 5.7.41 and Community MySQL version 5.7.42.

  • Upgraded OpenSSL to version 1.1.1u.

  • Accelerated the recovery of the undo tablespace lock during instance crash recovery.

  • Added support for canceling an online buffer pool resize to avoid excessively long resizing processes.

• Performance improvements

  • Used multiple threads to initialize buffer pool instances simultaneously during instance startup to accelerate the process.

  • Optimized the rollback of pending transactions from synchronous to asynchronous during instance crash recovery to improve the Recovery Time Objective (RTO).

  • Improved the performance of buffer pool initialization to accelerate startup.

• Bug fixes

  • Fixed an initialization failure caused by an out-of-bounds access to a parameter array when buffer pool instances are initialized with multiple threads.

—

20230228

5.7.40

• Bug fixes

  • Fixed an issue where memory usage could slowly increase in certain scenarios after recycle_scheduler was enabled.

  • Fixed an issue where a purge_table operation could not be executed due to a conflict between the recycle_scheduler background thread and an active purge_table operation.

—

20221231

5.7.40

• New features

  • Incorporated changes from the official Community MySQL version 5.7.40.

  • Upgraded OpenSSL to version 1.1.1s.

• Performance improvements

  • Optimized the adaptive hash index (AHI) feature:

    • Clears the memory occupied by AHI when AHI is disabled.

    • Improved the update speed of AHI.

  • When applying a transaction on a replica that modifies a table with no primary or non-null unique key, the system prioritizes a non-null key with an auto-increment field as the first candidate to find the target column. This improves the table playback efficiency on the replica and reduces replication latency.

    Note

    The non-null key with an auto-increment field can be a user-defined key or an implicit primary key created by ApsaraDB for RDS.

• Bug fixes

  • Fixed an issue where the number of rows updated by UPDATE and INSERT statements in the audit log was inaccurate.

  • Fixed an issue where a replica reported error 13146 because the character set of a temporary table was missing in the binary log when a standard table was created from the temporary table. This fix includes the temporary table's character set in the binary log, preventing the error.

—

20221031

5.7.39

• New features

  Incorporated changes from the official Community MySQL version 5.7.39.

• Bug fixes

  Removed the primary fast lookup feature.

—

20220731

5.7.38

• New features

  Incorporated changes from the official Community MySQL version 5.7.38.

• Bug fixes

  • Fixed a deadlock issue between a Rename Tablespace operation and other incomplete I/O operations during a DDL process.

  • Fixed an issue where the Memory/sql/String::value statistic in the performance_schema.memory_summary_global_by_event_name table was inaccurate.

  • Fixed a deadlock issue for XA transactions on a replica, which was caused by improper locking on a secondary index when data was inserted into the index.

  • Removed the restriction that innodb_buffer_pool_size cannot be less than 1 GB when innodb_buffer_pool_instances is greater than 1.

• Performance improvements

  Optimized the strategy for adjusting the buffer pool size to make the process smoother.

—

20220430

5.7.37

• New features

  • Incorporated changes from the official Community MySQL version 5.7.37.

  • Optimized the SSL encryption feature and fixed some internal errors.

  • Revoked the permissions of standard accounts to operate on the sys and performance_schema databases.

• Bug fixes

  Change the FLUSH TABLES WITH READ LOCK and UNLOCK TABLES log records in the error log to the warning level to facilitate online troubleshooting.

—

20211231

5.7.35

• New features

  • Incorporated changes from the official Community MySQL version 5.7.35.

  • Added support for Free Resize of the InnoDB buffer pool, which reduces the performance impact during buffer pool resizing and improves user experience.

  • Optimized bidirectional replication to stop sending unnecessary binary logs and to prevent the generation of heartbeat events when an EVENT is skipped.

  • You no longer need to restart an instance after you modify the log_slave_updates parameter.

  • The error log now includes FLUSH TABLES WITH READ LOCK and UNLOCK TABLES log entries.

  • Added the innodb_control_index_page_reserve parameter. Setting it to OFF reduces page splitting and lowers storage usage.

• Bug fixes

  • Fixed an issue where CPU usage statistics collected by Performance Agent were incorrect in the new Docker architecture.

  • Fixed an issue where the session tracker type number reserved by ApsaraDB for RDS was incorrect.

  • Fixed a crash recovery failure that occurred when the MTR log size exceeded the log parsing buffer size.

  • Added support for marking memory pages as MADV_DONTDUMP. If the innodb_buffer_pool_in_core_file parameter is disabled, the generated core dump does not include the InnoDB buffer pool, which reduces the size of the core dump.

  • Fixed an issue where the start_time in the mysql.slow_log table was incorrect. It now records the start time of an SQL statement, not the end time.

  • Granted the Show_db_priv permission to standard users.

  • Fixed a potential memory leak when LF_HASH_INSERT is executed.

  • Fixed an issue where the Recycle Bin did not support tables that contain virtual columns.

—

20210630

5.7.32

• New features

  • The audit log now supports the MYSQL_V3 format.

  • Users can now perform TRUNCATE operations on slow query logs and general logs.

  • Added a check for thread stack memory overflow.

  • Added the thread_pool_strict_mode parameter to control the maximum number of worker threads.

• Bug fixes

  • The mysqld_safe script now deletes old socket lock files on startup.

  • Fixed a memory leak issue in the Recycle Bin.

—

20210430

5.7.32

• New features

  • Added support for the Recycle Bin feature.

  • Added support for the Sequence Engine.

• Performance improvements

  • More performance data metrics are added to the I_S.PERF_STATISTICS table.

  • I_S.INDEX_STATISTICS table now includes the index scan count.

  • Optimized Transparent Data Encryption (TDE) performance.

• Bug fixes

  Fixed a community bug related to the abnormal handling of generated columns during a rollback.

—

20201031

5.7.30

• Bug fixes

  • Fixed a ROW_SEARCH_MVCC crash caused by concurrent updates.

  • Fixed a startup failure caused by changing innodb_undo_tablespaces.

  • Fixed a cache overflow issue caused by Full-Text Search (FTS) queries.

20240601

20200831

5.7.30

• New features

  • Incorporated changes from the official Community MySQL version 5.7.30.

  • Optimized the wait and concurrency mechanism of statement concurrency control (CCL).

  • Added start gtid and stop gtid features to the MySQL Binlog tool.

  • Added support for outputting various LSN values of the redo log:

    • innodb_lsn: the LSN of the redo log.

    • innodb_log_write_lsn: the LSN of the log write.

    • innodb_log_checkpoint_lsn: the LSN of the last checkpoint.

    • innodb_log_flushed_lsn: the LSN of the redo log flushed to disk.

    • innodb_log_Pages_flushed: the LSN of the page flush.

• Performance improvements

  • Adjusted the execution priority of statement concurrency control in stored procedures.

• Bug fixes

  • Fixed a reference count leak for temporary table pages used during SQL execution. This leak caused inefficient flushing of dirty blocks, exhausted free pages in the buffer pool, and severely affected database performance. For more information, see the official documentation.

20240601

20200630

5.7.28

• New features

  • Inventory Hint: Added three hints that support SELECT, UPDATE, INSERT, and DELETE statements to quickly commit or roll back transactions and improve business throughput.

  • statement concurrency control: Manages sudden database request traffic, high-resource-consuming statement access, and changes in SQL access models by controlling concurrency to ensure stable instance operation.

  • Statement Queue: A queuing mechanism for statements that groups statements into buckets. It tries to place statements with potential conflicts into the same bucket to reduce conflict overhead.

  • Statement Outline: Uses Optimizer Hints and Index Hints to stabilize MySQL execution plans.

  • Faster DDL: Optimized the buffer pool management mechanism during DDL operations to reduce the performance impact and increase the concurrency of online DDL operations.

  • Increased the maximum number of connections to 500,000.

• Performance improvements

  • You can view all native procedures by running the call dbms_admin.show_native_procedure(); command.

  • Added a function to delete orphan tables.

  • Internal optimization of the thread pool.

  • Optimized the query cache.

  • Capped Performance Schema memory usage based on instance specifications.

• Bug fixes

  • Fixed an issue where the audit refresh thread entered an infinite loop.

20240601

20200430

5.7.28

• Performance improvements

  • Removed rwlock from the query cache and changed the default hash function from LF_hash to murmur3 hash.

• Bug fixes

  • Fixed two errors that occurred when hitting the query cache at the REPEATABLE READ transaction isolation level.

20240601

20200331

5.7.28

• New features

  • Incorporated changes from the official Community MySQL version 5.7.28.

  • fast query cache: To address the shortcomings of the native MySQL query cache, Alibaba Cloud has redesigned and re-implemented it as the ApsaraDB for RDS query cache, which effectively improves database query performance.

  • Ported two MDLs from Percona Server 5.7: LOCK TABLES FOR BACKUP (LTFB) and LOCK BINLOG FOR BACKUP (LBFB).

• Performance improvements

  • Added thread pool compatibility for earlier versions.

  • Disabled the output of TCP errors by default.

  • Improved the performance of the thread pool with default configurations.

• Bug fixes

  • Fixed an issue where temporary files were included when large files were cleaned up.

  • Fixed a thread pool dump thread timeout issue.

  • Fixed an IPK field count error in the process context.

  • Fixed a PFS thread leak and release issue caused by rds_change_user.

20240601

20200229

5.7.26

• New features

  • Performance Agent: A more convenient performance data statistics solution. It works as a MySQL plugin to collect and analyze various internal performance data of a MySQL instance.

  • Added network round-trip time in semi-synchronous replication mode and recorded it in performance data.

• Performance improvements

  • Optimized the execution time of the PAUSE instruction on different CPU architectures.

  • Optimized proxy short-lived connections.

  • Added a memory table to view the running status of the thread pool.

• Bug fixes

  • Fixed a DDL redo log insecurity issue.

  • Fixed an issue where the io_statistics table had incorrect time values.

  • Fixed a server crash caused by altering a table.

  • Fixed MySQL test cases.

20240601

20200110

5.7.26

• Performance improvements

  • Removed links to small files during asynchronous file cleanup.

  • Optimized thread pool performance.

  • Changed the default value of the thread_pool_enabled parameter to OFF.

20240601

20191225

5.7.26

• New features

  • Internal account management and protection: Adjusted user permissions to protect data security.

• Performance improvements

  • Improved the handling performance of short-lived connections.

  • Used a dedicated thread to serve maintenance users to avoid HA failures.

  • Removed unnecessary TCP error logs.

  • Optimized the thread pool.

• Bug fixes

  • Fixed a mysqld process crash issue during read/write splitting.

  • Fixed a core dump issue caused by the keyring.

20240601

20191115

5.7.26

• Bug fixes

  • Fixed an issue where variables were displayed in the audit log after a primary/secondary switchover.

20240601

20191101

5.7.26

• New features

  • Added the SM4 encryption algorithm for Transparent Data Encryption (TDE).

  • If a primary key is specified, the primary index is accessed directly.

  • Disabled the automatic conversion from the Memory engine to the MyISAM engine for system tables and tables used by threads in an initialization state.

• Performance improvements

  • thread pool: Optimized mutex behavior.

  • Introduced an audit log buffering mechanism to improve audit log performance.

  • Performance Insight: Performance metrics now support the thread pool.

  • The thread pool is enabled by default.

• Bug fixes

  • Released locks when processing the maintenance user list.

  • Added more TCP error information.

20240601

20191015

5.7.26

• New features

  • Slow log rotation: To ensure zero data loss when collecting slow query logs, the log rotation process renames the CSV data file of the slow log table to a unique name and creates a new file. You can use show variables like '%rotate_log_table%'; to check if slow log rotation is enabled.

  • Performance Agent plugin: Collects performance data and saves it to a local formatted text file. It uses file rotation to retain the most recent performance data with second-level granularity.

  • Forced engine conversion from MEMORY to InnoDB: If the global variable rds_force_memory_to_innodb is set to ON, the table engine is converted from MEMORY to InnoDB when you create or modify a table.

  • TDE mechanism optimization: Added the keyring-rds plugin for interaction with the management system and Key Management Service (KMS).

  • TCP error information: Returns TCP direction (read, read wait, write wait) errors and error codes to the end_connection event and outputs error information to the error log.

• Bug fixes

  • Fixed the unexpected Error 1290 in DDL operations.

20240601

20190925

5.7.26

• Parameter modification

  • Changed the default value of the auto_generate_certs system variable from true to false.

  • Added the global read-only variable auto_detect_certs with a default value of false. Valid values are true and false. This system variable is available when the server side is compiled with OpenSSL and controls whether the server automatically searches for SSL certificate and key files in the data directory upon startup.

20240601

20190915

5.7.26

• New features

  • thread pool: Separates threads from sessions, allowing a small pool of threads to handle tasks for a large number of active sessions.

20240601

20190815

5.7.26

• New features

  • Purge Large File Asynchronously: When a single tablespace is deleted, the tablespace file is renamed to a temporary file, and an asynchronous cleanup process waits to clean up the temporary file.

  • Performance Insight: A powerful tool for instance load monitoring, correlation analysis, and performance tuning to help you quickly assess database load, find the source of performance issues, and improve database stability.

  • Optimized instance lock status: DROP or TRUNCATE operations are allowed on tables even when the instance is locked.

• Bug fixes

  • Do not set rds_prepare_begin_id in the set rds_current_connection command.

  • Allowed changing the information of a locked user.

  • Prohibited using the keyword actual as a table name.

  • Fixed a timestamp field overflow issue caused by the slow query log.

20240601

20190510

5.7.26

• New features

  • Allowed creating temporary tables within a transaction.

20240601

20190319

5.7.26

• New features

  • Added support for setting the thread ID for a proxy in handshake packets.

20240601

20190131

5.7.25

• Performance improvements

  • Upgraded to the official Community MySQL version 5.7.25.

  • Disabled the jemalloc memory management feature.

• Bug fixes

  • Fixed an issue where the internal variable net_lenth_size was calculated incorrectly.

20240601

20181226

—

• New features

  • Added support for dynamically modifying binlog-row-event-max-size to accelerate the replication of tables without a primary key.

• Bug fixes

  • Fixed an abnormal memory allocation issue for proxy instances.

20240601

20181010

—

• Performance improvements

  • Added support for implicit primary keys.

  • Accelerated primary-replica replication for tables without a primary key.

  • Added support for Native AIO to improve I/O performance.

20240601

20180431

—

• New features

  • Added support for RDS High-availability Edition.

  • Added support for SQL Audit.

  • Enhanced protection for instances during snapshot backups.

20240601

AliSQL version

Description

20230101

• Bug fixes

  • Fixed an issue that caused INSERT ON DUPLICATE KEY UPDATE (IODKU) to fail with a unique key conflict on tables with an auto-increment column. This failure occurred when multiple sessions performed the operation without providing an explicit value for the column. With this fix, when the insert part of an IODKU fails, the operation is correctly converted to an update, and the auto-increment value is not consumed.

20201229

• Bug fixes

  • Fixed a bug that could cause unexpected database crashes or hangs.

  • Fixed an issue where a prefix index was incorrectly identified as an invisible index.

  • Fixed an issue that caused the logger instance to report an abnormal status in the consensus protocol. This issue could prevent the cluster from correctly electing a primary instance.

20191128

• New features

  • Added support for read/write splitting.

• Bug fixes

  • Fixed an issue where the Seconds_Behind_Master metric for a follower was calculated incorrectly in some scenarios.

  • Fixed a deadlock that could occur when transactions were retried in table-level parallel replication.

  • Fixed XA-related bugs.

20191016

• New features

  • Added support for upgrading RDS instances from MySQL 5.7 on RDS High-availability Edition with local SSDs to RDS Enterprise Edition.

  • Added compatibility with the native MySQL GTID feature, which is disabled by default.

  • This version includes proprietary features from the 20190915 and earlier AliSQL versions for RDS Basic Edition and RDS High-availability Edition.

• Bug fixes

  • Fixed an issue where binary logging was disabled after a secondary instance was reset.

20190909

• New features

  • Improved the execution efficiency of large transactions in strong consistency mode.

  • Added support for binary log dumps from leader and follower instances.

  • Added support for creating read-only instances.

  • System tables now use the InnoDB storage engine by default.

• Bug fixes

  • Fixed an issue where log cleanup commands on a follower instance did not take effect.

  • Fixed an issue where the slave thread would exit unexpectedly when slave_sql_verify_checksum was set to OFF and binlog_checksum was set to crc32.

20190709

• New features

  • Added support for RDS Enterprise Edition.

  • Disabled the semi-sync plugin.

  • Added support for table-level parallel replication and writeset-based parallel replication.

  • Added support for pk_access to accelerate primary key queries.

  • Added support for the thread pool.

  • This version includes proprietary features from the 20190510 and earlier AliSQL versions for RDS Basic Edition and RDS High-availability Edition.

Minor version

Community version

Description

Expiration date

20260430

5.6.16

• Bug fixes

  • Fixed an issue in Event Scheduler where most events failed to execute due to an incorrect priority queue comparison function.

  • Fixed community Bug #105652, resolving an exception during crash recovery for tables larger than 32 TB.

• Performance improvements

  • Made DDL processes more responsive to KILL commands, which improves control over DDL operations.

—

20250531

5.6.16

• Bug fixes

  • Fixed a memory leak on the primary instance caused by an incorrect position comparison in semisynchronous replication.

—

20241231

5.6.16

• Bug fixes

  • Fixed an unexpected instance restart caused by an sql_type error in the Thread Pool feature.

  • Fixed a semisynchronous replication failure caused by an error in comparing binary log filenames.

—

20221130

5.6.16

• New features

  Added support for recording GLOBAL READ LOCK locking and unlocking events in the error log.

• Bug fixes

  • Fixed excessive memory consumption when opening a large number of InnoDB partitioned tables.

  • Fixed an issue where the InnoDB data dictionary was not updated when the case of a column name was changed.

  • Fixed a deadlock on the MySQL instance when renaming a tablespace.

  • Fixed a crash recovery failure caused by an undersized recovery parsing buffer.

  • Fixed an issue where the SHOW GLOBAL STATUS; statement returned inaccurate results.

  • Fixed an issue where the start_time field in the mysql.slow_log table was inaccurate.

—

20221126

5.6.16

• Bug fixes

  • Fixed duplicate values in an InnoDB AUTO_INCREMENT column.

—

20210630

5.6.16

• New features

  Added a check for thread stack overflow.

• Bug fixes

  • Fixed bugs from the MySQL 5.6 community version.

  • Removed operational restrictions on the SHOW CREATE statement in the mysql database.

—

20210430

5.6.16

• Performance improvements

  Added more performance metrics to the I_S.PERF_STATISTICS table.

• Bug fixes

  Fixed several memory leak bugs from the community version.

—

20201031

5.6.16

• Bug fixes

  • Fixed an issue where subqueries within an IN clause were invalid.

  • Fixed an issue with incorrect process permissions.

  • Fixed a user authorization issue in the kill_user_list table.

  • Fixed an error in the DROP DATABASE statement.

  • Fixed an incorrect calculation of SECONDS_BEHIND_MASTER caused by a PREVIOUS_GTID event.

20240601

20200831

5.6.16

• New features

  Added support for outputting various redo log LSN values:

  • innodb_lsn: The redo log LSN.

  • innodb_log_write_lsn: The log write LSN.

  • innodb_log_checkpoint_lsn: The last checkpoint LSN.

  • innodb_log_flushed_lsn: the LSN of the redo log flushed to disk.

  • innodb_log_Pages_flushed: The page flush LSN.

• Bug fixes

  • Fixed a type error with SHOW_HA_ROWS.

  • Fixed an IPK field count error in the procedure context.

  • Fixed a server crash caused by querying INFORMATION_SCHEMA.

  • Fixed an infinite loop in the audit log flush thread.

  • Fixed an issue where a secondary instance did not report replication latency.

20240601

20200630

5.6.16

• New features

  • Introduced Performance Agent, a MySQL plugin that collects and analyzes performance metrics from within a MySQL instance.

  • Increased the maximum number of connections to 500,000.

  • Introduced Faster DDL. This feature optimizes buffer pool management during DDL operations to reduce performance impact and increase online DDL concurrency.

• Performance improvements

  • Added the global parameter max_execution_time, which interrupts SQL statements that exceed the specified execution time.

  • Made internal optimizations to the Thread Pool.

• Bug fixes

  • Fixed an issue where the wait count was incorrect when reading client commands.

  • Fixed an issue where standard accounts did not have permission to execute the DROP DATABASE command.

20240601

20200430

5.6.16

• New features

  • Added the mdl_info table to store metadata lock (MDL) information.

• Bug fixes

  • Resolved a conflict that occurred when the Thread Pool and ic_reduce (instant kill) features were enabled simultaneously.

20240601

20200331

5.6.16

• Performance improvements

  • Improved the performance of the Thread Pool with default configurations.

  • Disabled the output of TCP errors by default.

• Bug fixes

  • Fixed an issue where temporary files were included when cleaning up large files.

20240601

20200229

5.6.16

• New features

  • Added support for proxy-based read/write splitting.

• Performance improvements

  • Optimized the Thread Pool feature.

  • Optimized the execution time of the PAUSE instruction on different CPU architectures.

• Bug fixes

  • Fixed an issue where XA transactions were partially committed.

20240601

20200110

5.6.16

• New features

  • Introduced Thread Pool. This feature separates threads from sessions, allowing a small number of threads to handle tasks for a large number of active sessions.

• Performance improvements

  • Unlinked small files during asynchronous file cleanup.

• Bug fixes

  • Fixed an issue where the sleep time of the page cleaner was calculated incorrectly.

  • Fixed a failover failure caused by the SELECT @@global.gtid_executed statement.

  • Fixed the IF CLIENT KILLED AFTER ROLLBACK TO SAVEPOINT PREVIOUS STMTS COMMITTED issue.

20240601

20191212

5.6.16

• Performance improvements

  • Removed unnecessary TCP error logs.

20240601

20191115

5.6.16

• Bug fixes

  • Fixed a timestamp overflow issue in the slow query log.

20240601

20191101

5.6.16

• Bug fixes

  • Fixed an issue where the slow query log was rotated when flushing all logs. The slow query log is now rotated only when it is explicitly flushed.

  • Corrected some display errors.

20240601

20191015

5.6.16

• New features

  • Slow query log rotation: To prevent data loss when collecting slow query logs, this feature rotates logs by renaming the current CSV data file to a unique name and creating a new file. You can run show variables like '%rotate_log_table%'; to check whether slow query log rotation is enabled.

  • SM4 encryption algorithm: Added the new SM4 encryption algorithm to replace the old SM encryption algorithm.

  • Introduced Purge Large File Asynchronously. When you delete a single tablespace, the system renames its file to a temporary file and an asynchronous process then cleans it up.

  • TCP error information: Returns TCP direction (read, read wait, or write wait) errors and error codes to the end_connection event and outputs error information to the error log.

  • Introduced an audit log buffering mechanism to improve audit log performance.

• Bug fixes

  • Disabled pstack to prevent it from becoming unresponsive with a large number of connections.

  • Fixed a conflict between implicit primary keys and the CREATE TABLE ... AS SELECT statement.

  • The system now automatically cleans up temporary files created by the binary log.

20240601

20190815

5.6.16

• Performance improvements

  • Optimized instance locking: DROP TABLE or TRUNCATE TABLE operations are now allowed on tables even when the instance is locked.

20240601

20190130

5.6.16

• Bug fixes

  • Fixed bugs that could cause system instability.

20240601

20181010

5.6.16

• Performance improvements

  • Added the rocksdb_ddl_commit_in_the_middle parameter for MyRocks. If this parameter is enabled, some DDL operations perform a COMMIT during execution.

20240601

201806**

5.6.16

• New features

  • Increased the precision of the slow query log to microseconds.

20240601

20180426

5.6.16

• New features

  • Introduced the invisible index feature, which allows you to set an index as invisible. For more information, see Invisible Indexes.

• Bug fixes

  • Fixed a bug in the apply thread of a secondary instance.

  • Fixed a performance degradation issue when a secondary instance applied updates to partitioned tables.

  • Fixed an issue where ALTER TABLE COMMENT rebuilt the entire table in TokuDB. For more information, see TokuDB documentation.

  • Fixed a potential deadlock triggered by SHOW SLAVE STATUS or SHOW STATUS.

20240601

20171205

5.6.16

• Bug fixes

  • Fixed a deadlock that occurred when running OPTIMIZE TABLE and ONLINE ALTER TABLE concurrently.

  • Fixed a conflict between SEQUENCE and implicit primary keys.

  • Fixed an issue with SHOW CREATE SEQUENCE.

  • Fixed incorrect table statistics for the TokuDB engine.

  • Fixed a deadlock introduced by parallel OPTIMIZE TABLE operations.

  • Fixed an issue with the character set recorded in QUERY_LOG_EVENT.

  • Fixed a signal handling issue that prevented the database from stopping. For more information, see MySQL documentation.

  • Fixed an issue introduced by RESET MASTER.

  • Fixed an issue where a secondary instance became stuck in a waiting state.

  • Fixed a potential process crash triggered by SHOW CREATE TABLE.

20240601

20170927

5.6.16

• Bug fixes

  • Fixed an issue where queries on TokuDB tables used incorrect indexes.

20240601

20170901

5.6.16

• New features

  • Upgraded SSL encryption to TLS 1.2. For more information, see Configuring SSL Encryption.

  • Added support for SEQUENCE.

• Bug fixes

  • Fixed an issue where NOT IN queries returned incorrect result sets in specific scenarios.

20240601

20170530

5.6.16

• New features

  • Allowed privileged accounts to terminate connections from other accounts.

20240601

20170221

5.6.16

• New features

  • Added support for enabling the proxy terminal.

20240601

AliSQL version

Description

20181212

• bug fix

  • Fixed a bug where the gettimeofday(2) system function returned an inaccurate value, leading to incorrect timeout calculations.