Release Notes of Minor AliSQL Versions

ApsaraDB RDS for MySQL 8.0

20200630

• New features:
  • The faster DDL feature provides an optimized buffer pool management mechanism. This mechanism reduces the impact of data definition language (DDL) operations and increases the number of concurrent DDL operations that are allowed. For more information, see Faster DDL.
  • The maximum number of connections that are allowed is increased to 500,000.
• Performance optimization:
  • Thread pools are optimized.
  • The memory allocation mechanism is optimized. You can specify the maximum number of memory resources that are allowed for Performance Schema based on the instance type.
  • SQL log files are no longer detected.
  • Transparent Data Encryption (TDE) caches the keys that are provided by Key Management Service (KMS).
  • The status of threads that are running under concurrency control (CCL) can be modified. For more information, see Statement concurrency control.
• Bugs fixed:
  • The bug that causes the system to consider a semicolon (;) to be a part of the command used to create an outline is fixed.
  • The bug that causes the server to unexpectedly exit in the event of table changes is fixed.
  • The bug that causes earlier versions to disallow the memory and array keywords supported in later versions is fixed.
  • The bug that causes the system to incorrectly count the number of waits when commands are read from a client is fixed.
  • The bug that causes failures in minor engine version updates is fixed.

20200430

• New features:
  • The Binlog in Redo feature is introduced. This feature writes binary logs to the redo log file before the binary logs are written to disks. This reduces I/O consumption and improves database performance. For more information, see Binlog in Redo.
  • The Data Protect feature is introduced. This feature supports the customization of security policies that are used to manage the permissions on DROP and TRUNCATE statements. This allows you to avoid data losses caused by the unintentional execution of these statements. For more information, see Data Protect.
  • The code for row caching in X-Engine is restructured.
  • The XA_RECOVER_ADMIN permission is provided.
• Performance optimization:
  • The code that is used to scan data when operations are performed on a temporary InnoDB table is optimized. This allows the system to scan only dirty pages instead of the entire buffer pool.
  • The global parameter opt_readonly_trans_implicit_commit is renamed to rds_disable_explicit_trans. This ensures compatibility with MySQL 5.6.
  • The SQL Explorer (SQL audit) feature is optimized, so it does not log the upgrade of an RDS instance.
  • Memory resources that are consumed by DDL operations on X-Engine tables are reduced.
• Bugs fixed:
  • The bug that causes the sizes of X-Engine tables stored on disks to be inconsistent with the statistical information in the information_schema table is fixed.
  • The bug that causes the system to initialize X-Engine logs when the error log file is re-opened is fixed.

20200331

• New feature:

  The TRUNCATE TABLE statement is supported. After you execute this statement on a table, this statement moves the table to a dedicated directory used for the recycle bin. Then, this statement creates a table by using the schema of the table that you truncate. For more information, see Recycle Bin.

• Performance optimization:
  • The output of Transmission Control Protocol (TCP) errors is disabled by default.
  • The performance of thread pools with the default configuration is improved.
• Bugs fixed:
  • The bug that databases and tables become invalid because the names of partitioned tables are separated with a pound key and a letter p (#p) is fixed.
  • The bug that statements running under CCL are case-sensitive is fixed.
• Changes incorporated: Changes in MySQL 8.0.17 and MySQL 8.0.18 are incorporated. For more information, see Changes in MySQL 8.0.17 and Changes in MySQL 8.0.18.

20200229

• New features:
  • The performance agent feature is introduced. For more information, see Performance Agent. This feature is provided as a MySQL plug-in. It allows you to collect and analyze the performance metrics of an RDS instance in an efficient manner.
  • Network round-trip time is introduced to the semi-synchronous mode. This allows you to better understand the performance of an RDS instance.
• Performance optimization:
  • Statement-level CCL is allowed on read-only RDS instances.
  • Outlines are supported for secondary RDS instances.
  • The optimization of short-lived connections with database proxies is supported.
  • The time required to execute the PAUSE statement is reduced in various CPU architectures.
  • A memory table is introduced. This allows you to view the running status of a thread pool.
• Bugs fixed:
  • The bug that causes the system to forbid the ppoll function and replace the ppoll function with the poll function in Linux kernels earlier than 4.9 is fixed.
  • The bug that causes errors when the system calls the wrap_sm4_encrypt function is fixed.
  • The bug that causes the system to lock global variables when SQL logs are scrolled is fixed.
  • The bug that causes errors in restoration inconsistency checks is fixed.
  • The bug that causes incorrect time values in the io_statistics table is fixed.
  • The bug that causes the system to unexpectedly exit when invalid compression algorithms are invoked is fixed.
  • The bug that causes user columns in MySQL 8.0 and MySQL 5.6 to be incompatible is fixed.

20200110

• New feature:

  Three hints are introduced. These hints can be used in the SELECT, UPDATE, INSERT, and DELETE statements to commit and roll back transactions at faster speeds. For more information, see Inventory Hint.

• Performance optimization:
  • CCL is optimized. When an RDS instance is started, CCL queue structures are initialized before CCL rules.
  • The file deletion mechanism is optimized. When you asynchronously delete small files, links to the small files are canceled.
  • The performance of thread pools is optimized. For more information, see Thread Pool.
  • Restoration inconsistency checks are disabled by default.
  • The permissions required to configure variables are changed.
    • The user role that is authorized to configure the following variables is changed to standard user:
      • auto_increment_increment
      • auto_increment_offset
      • bulk_insert_buffer_size
      • binlog_rows_query_log_events
    • The user role that is authorized to configure the following variables is changed to superuser or system variable administrator:
      • binlog_format
      • binlog_row_image
      • binlog_direct
      • sql_log_off
      • sql_log_bin

20191225

• New feature:

  Deleted tables are transferred to the recycle bin. These tables can be retrieved from the recycle bin before the specified retention period elapses. For more information, see Recycle Bin.

• Performance optimization:
  • The mechanism that is used to process short-lived connections is optimized.
  • A dedicated thread is used to serve the maintain user. This allows you to avoid high availability (HA) failures.
  • The locking mechanism is optimized. If an error occurs when binary logs are updated by using redo logs, the lock triggered by file synchronization is explicitly released.
  • The deletion of unnecessary TCP error logs is supported.
  • Thread pools are enabled by default.
• Bugs fixed:
  • The bug that causes errors in updates to slow query logs is fixed.
  • The bug that causes an incorrect lock scope is fixed.
  • The bug that causes errors in core dumps when the system invokes the select function of TDE is fixed.

20191115

New feature:

Bucket-level queuing is supported. Statements that request the same resources are queued in one bucket to reduce overheads. For more information, see Statement Queue.

20191101

• New features:
  • The SM4 encryption algorithm is supported for TDE.
  • Data protection for secondary RDS instances is supported. Only the accounts with the SUPER or REPLICATION_SLAVE_ADMIN role have the permissions to insert, delete, and modify data in the slave_master_info, slave_relay_log_info, and slave_worker_info tables.
  • A mechanism is introduced to increase the priorities of auto-increment keys. If a table does not have a primary key or it does not have a unique key without a null value, the auto-increment key without a null value has the highest priority.
  • A mechanism is introduced to prevent the automatic conversion of tables from the MEMORY to MyISAM storage engines. These tables include system tables and the tables that are invoked by threads in the initializing state.
  • A mechanism is introduced to flush binary log files to disks before the redo log file.
  • A mechanism is introduced to stop the creation of temporary tables on an RDS instance when the RDS instance is locked.
  • X-Engine is provided to store transactions based on a log-structured merge (LSM) tree.
• Performance optimization:
  • The thread pool feature is optimized to reduce mutexes. For more information, see Thread Pool.
  • The returning feature is optimized to monitor thread pools. For more information, see Performance Insight.
  • Parameter adjustment:
    • primary_fast_lookup: a session parameter. Default value: true.
    • thread_pool_enabled: a global parameter. Default value: true.

20191015

• New features:
  • The TDE feature is introduced. This feature supports real-time I/O encryption and decryption on data files. Data is encrypted before it is written to disks and decrypted before it is read from disks to the memory. For more information, see TDE.
  • The returning feature allows data manipulation language (DML) statements to return result sets. In addition, the DBMS_TRANS package is provided for you to use this feature. For more information, see Returning.
  • The forced conversion from the MyISAM or MEMORY storage engine to the InnoDB storage engine is supported. If the global variable force_mysiam_to_innodb or force_memory_to_innodb is set to ON, a table is converted from the MyISAM or MEMORY storage engine to the InnoDB storage engine when the table is created or modified.
  • The permissions that allow standard accounts to switch over services between primary and secondary RDS instances are disabled. Only privileged accounts have these permissions.
  • A performance proxy plug-in is provided. This plug-in obtains performance data and saves the data as TXT files to your computer. These files are deleted by using a round-robin algorithm. Only the latest second-level files are retained.
  • A configurable timeout period is introduced for mutexes in InnoDB: This timeout period can be changed by setting the global variable innodb_fatal_semaphore_wait_threshold. The default value of the global variable is 600.
  • Index hint errors can be ignored by setting the global variable ignore_index_hint_error. The default value of the global variable is false.
  • SSL encryption can be disabled. For more information, see Configure SSL encryption for an ApsaraDB RDS for MySQL instance.
  • The output of TCP errors is supported. TCP errors in read, read-wait, and write-wait events along with their error codes are returned by using end_connection events. In addition, logs with information about the errors are generated.
• Bugs fixed:
  • The bug that prevents a Linux operating system from merging local asynchronous I/O (AIO) requests before linear Read Ahead is triggered is fixed.
  • The bug that prevents the proper collection of table and index statistics is fixed.
  • The bug that prevents the system direct access to the primary index of a table that has a primary key is fixed.

20190915

Bug fixed:

The bug that causes memory leaks when the Cmd_set_current_connection process runs is fixed.

20190816

• New features:
  • The thread pool feature is introduced to separate threads from sessions. If a large number of sessions exist, the system can run a small number of threads to complete the tasks in active sessions. For more information, see Thread Pool.
  • The CCL feature allows you to specify the maximum number of concurrent requests that are allowed. This enables the system to handle traffic bursts, process statements that consume excessive resources, and adapt to changes of SQL models. This also ensures the continuity and stability of your database service. For more information, see Statement concurrency control.
  • The statement outline feature supports optimizer hints and index hints. These hints are used to stabilize the execution of query plans on an RDS instance. For more information, see Statement outline.
  • The Sequence engine is introduced to simplify the acquisition of sequence values. For more information, see Sequence Engine.
  • The Purge Large File Asynchronously feature is introduced to asynchronously delete files. Before you delete a tablespace, the system renames the files in the tablespace as temporary files. Then, a background thread is started to asynchronously delete the temporary files. For more information, see Purge Large File Asynchronously.
  • The performance insight feature is introduced to support load monitoring, association analysis, and performance optimization at the instance level. This allows you to evaluate the loads of an RDS instance. This also allows you to locate performance issues to improve your database stability. For more information, see Performance Insight.
  • An optimized instance locking mechanism is introduced. This mechanism allows you to drop and truncate tables on an RDS instance even if the RDS instance is locked.
• Bugs fixed:
  • The bug that causes the system to incorrectly calculate file sizes is fixed.
  • The bug that allows irrelevant processes to reuse released memory resources is fixed.
  • The bug that causes a host to exit unexpectedly when the available cache size on the host is 0 is fixed.
  • The bug that causes conflicts between implicit primary keys and CTS statements is fixed.
  • The bug that causes the system to incorrectly log slow queries is fixed.

20190601

• Performance optimization:
  • Metadata locking on logging tables is reduced.
  • The code for termination options is restructured.
• Bugs fixed:
  • The bug that prevents the SQL Explorer (SQL audit) feature from logging precompiled statements is fixed.
  • The bug that prevents the system from filtering out error logs in logging tables with invalid names is fixed.

ApsaraDB RDS for MySQL 5.7 on RDS Basic or High-availability Edition

20200630

• New features:
  • Three hints are introduced to the inventory hint feature. These hints are used in SELECT, UPDATE, INSERT, and DELETE statements to commit and roll back transactions at faster speeds. This allows you to increase the throughput of your application. For more information, see Inventory Hint.
  • The CCL feature allows you to specify the maximum number of concurrent requests that are allowed. This enables the system to handle traffic bursts, process statements that consume excessive resources, and adapt to changes of SQL models. This also ensures the continuity and stability of your database service. For more information, see Statement concurrency control.
  • The statement queue feature supports bucket-level queuing. Statements that request the same resources are queued in one bucket to reduce overheads. For more information, see Statement Queue.
  • The statement outline feature supports optimizer hints and index hints. These hints are used to stabilize the execution of query plans on an RDS instance. For more information, see Statement outline.
  • The faster DDL feature provides an optimized buffer pool management mechanism. This mechanism reduces the impact of DDL operations and increases the number of concurrent DDL operations that are allowed. For more information, seeFaster DDL.
  • The maximum number of connections that are allowed is increased to 500,000.
• Performance optimization:
  • The call dbms_admin.show_native_procedure(); command is provided to view all of the procedures on an RDS instance.
  • A new function is provided to delete orphan tables.
  • Thread pools are optimized.
  • Query caching is optimized.
  • The memory allocation mechanism is optimized. You can specify the maximum number of memory resources that are allowed for Performance Schema based on the instance type.
• Bug fixed:

  The bug that causes an audit update thread to enter an infinite loop is fixed.

20200430

• New feature:

  The Data Protect feature is introduced. This feature supports the customization of security policies that are used to manage the permissions on DROP and TRUNCATE statements. This allows you to avoid data losses caused by the unintentional execution of these statements. For more information, see Data Protect.

• Performance optimization:

  Read-write locks are no longer supported in the query cache. The default hash function is changed from LF_hash to murmur3 hash.

• Bugs fixed:

  Two bugs that occur after the system hits the query cache during the execution of transactions at the REPEATABLE_READ isolation level are fixed.

20200331

• New features:
  • The fast query cache is introduced. It is developed by Alibaba Cloud based on the native MySQL query cache. It uses a new design and implementation mechanism to improve query performance. For more information, see A new version is available..
  • Two metadata locks are introduced from Percona Server 5.7: LOCK TABLES FOR BACKUP (LTFB) and LOCK BINLOG FOR BACKUP (LBFB).
• Performance optimization:
  • Thread pools are optimized to ensure compatibility with earlier MySQL versions.
  • The output of TCP errors is disabled by default.
  • The performance of thread pools with the default configuration is improved.
• Bugs fixed:
  • The bug that causes the system to delete temporary files when you delete large files is fixed.
  • The bug that causes dump threads to time out in thread pools is fixed.
  • The bug that the counter of the IPK field in the process context is incorrect is fixed.
  • The bug that rds_change_user causes pfs thread leakage and release is fixed.
• Changes incorporated: Changes in MySQL 5.7.28 are incorporated. For more information, visit GitHub.

20200229

• New features:
  • The performance agent feature is introduced. For more information, see Performance Agent. This feature is provided as a MySQL plug-in. It allows you to collect and analyze the performance metrics of an RDS instance in an efficient manner.
  • Network round-trip time is introduced to the semi-synchronous mode. This allows you to better understand the performance of an RDS instance.
• Performance optimization:
  • The time required to execute the PAUSE statement is reduced in various CPU architectures.
  • The optimization of short-lived connections with database proxies is supported.
  • A memory table is introduced. This allows you to view the running status of a thread pool.
• Bugs fixed:
  • The bug that causes DDL redo logs that are not secure is fixed.
  • The bug that causes incorrect time values in the io_statistics table is fixed.
  • The bug that causes the server to unexpectedly exit in the event of table changes is fixed.
  • The bugs in MySQL test cases are fixed.

20200110

Performance optimization:

• The file deletion mechanism is optimized. When you asynchronously delete small files, links to the small files are canceled.
• The performance of thread pools is optimized. For more information, see Thread Pool.
• The default value of the thread_pool_enabled parameter is changed to OFF.

20191225

• New feature:

  The management of internal accounts is supported. This allows you to manage user permissions and protect the security of your data.

• Performance optimization:
  • The mechanism that is used to process short-lived connections is optimized.
  • A dedicated thread is used to serve the maintain user. This allows you to avoid HA failures.
  • The deletion of unnecessary TCP error logs is supported.
  • Thread pools are optimized.
• Bugs fixed:
  • The bug that causes the mysqld process to unexpectedly exit when the read/write splitting function is enabled is fixed.
  • The bug that causes errors in core dumps when the system uses a KeyRing is fixed.

20191115

Bug fixed:

The bug that causes the system to display variables in SQL logs that are generated from primary/secondary switchovers is fixed.

20191101

• New features:
  • The SM4 encryption algorithm is supported for TDE. For more information, see TDE.
  • A mechanism is introduced to allow the system to access the primary index of a table with a primary key.
  • A mechanism is introduced to prevent the automatic conversion of tables from the MEMORY to MyISAM storage engines. These tables include system tables and the tables that are invoked by threads in the initializing state.
• Performance optimization:
  • The thread pool feature is optimized to reduce mutexes. For more information, see Thread Pool.
  • An SQL log caching mechanism is introduced to increase SQL logging performance.
  • The performance insight feature is optimized to monitor thread pools. For more information, see Performance Insight.
  • The thread pool feature is enabled by default. For more information, see Thread Pool.
• Bugs fixed:
  • The bug that prevents the release of locks on user tables when these tables are being managed or maintained is fixed.
  • More TCP errors are added.

20191015

• New features:
  • The rotation of slow query logs is supported. Every CSV slow query log file is assigned a unique name and a new file. This prevents data losses during the collection of slow query logs. You can run the show variables like '%rotate_log_table%'; command to check whether the rotation of slow query logs is enabled.
  • A performance proxy plug-in is provided. This plug-in obtains performance data and saves the data as TXT files to your computer. These files are deleted by using a round-robin algorithm. Only the latest second-level files are retained.
  • The forced conversion from the MEMORY to InnoDB storage engines is supported. If the global variable rds_force_memory_to_innodb is set to ON, a table is converted from the MEMORY to InnoDB storage engines when the table is created or modified.
  • The keyring-rds plug-in is introduced to TDE. This plug-in allows ApsaraDB for RDS to communicate with the administration system or Alibaba Cloud Key Management Service (KMS).
  • The output of TCP errors is supported. TCP errors in read, read-wait, and write-wait events along with their error codes are returned by using end_connection events. In addition, logs with information about the errors are generated.
• Bug fixed:

  The bug that causes error 1290 in DDL operations is fixed.

20190925

Parameter adjustment:

• The default value of the system variable auto_generate_certs is changed from true to false.
• The global read-only variable auto_detact_certs is introduced. Valid values: true and false. Default value: false. This variable is supported only when code is compiled by using OpenSSL on the server. This variable specifies whether the server automatically searches for SSL certificate and key files in the data directory.

20190915

New feature:

The thread pool feature is introduced to separate threads from sessions. If a large number of sessions exist, the system can run a small number of threads to complete the tasks in active sessions. For more information, see Thread Pool.

20190815

• New features:
  • The Purge Large File Asynchronously feature is introduced to asynchronously delete files. Before you delete a tablespace, the system renames the files in the tablespace as temporary files. Then, a background thread is started to asynchronously delete the temporary files. For more information, see Purge Large File Asynchronously.
  • The performance insight feature is introduced to support load monitoring, association analysis, and performance optimization at the instance level. This feature allows you to evaluate the loads of an RDS instance. This feature also allows you to locate performance issues to ensure the stability of your database service. For more information, see Performance Insight.
  • An optimized instance locking mechanism is introduced. This mechanism allows you to drop and truncate tables on an RDS instance even if the RDS instance is locked.
• Bugs fixed:
  • The bug that allows you to set the rds_prepare_begin_id option in the set rds_current_connection command is fixed.
  • The bug that prevents the system from updating information about locked accounts is fixed.
  • The bug that allows you to use actual as a keyword in table names is fixed.
  • The bug that causes the overflow of timestamps in slow query logs is fixed.

20190510

New feature: Temporary tables can be created during transactions.

20190319

New feature: Thread IDs can be configured in handshake packets.

20190131

• The upgrade to MySQL 5.7.25 is supported.
• JeMalloc used for memory management is disabled.
• The bug that causes the system to incorrectly calculate the internal variable net_lenth_size is fixed.

20181226

• New feature: Dynamic modifications to the system variable binlog-row-event-max-size are supported. This allows you to expedite the replication of tables that do not have a primary key.
• Bug fixed: The bug that prevents the proxy instance of an RDS instance from applying for memory resources is fixed.

20181010

• Implicit primary keys are supported.
• The replication of tables that do not have a primary key between primary and secondary RDS instances is accelerated.
• Native AIO is provided to improve I/O performance.

20180431

New features:

• The RDS High-availability Edition is supported.
• The SQL audit feature is supported. For more information, see SQL audit.
• The protection for RDS instances that allow snapshot backups is enhanced.

ApsaraDB RDS for MySQL 5.7 on RDS Enterprise Edition

20191128

• New feature:

  The read/write splitting function is supported.

• Bugs fixed:
  • The bug that causes the system to incorrectly calculate the value of the Second_Behind_Master metric for a follower is fixed.
  • The bug that causes dead locks during the re-execution of table-level parallel replication transactions is fixed.
  • XA-related bugs are fixed.

20191016

• New features:
  • The upgrade from the RDS High-availability Edition to the RDS Enterprise Edition is supported for RDS instances that use local SSDs.
  • The GTID function that is provided by native MySQL is supported. This function is disabled by default.
  • All of the AliSQL functions that are developed by Alibaba Cloud and released before the minor version 20190915 in the RDS Basic and High-availability Editions are incorporated.
• Bug fixed:

  The bug that causes the system to disable binary logs for reset secondary RDS instances is fixed.

20190909

• New features:
  • The execution of large transactions is accelerated. This applies when the synchronous mode is used to replicate data between primary and secondary RDS instances that run the RDS Enterprise Edition.
  • Binary logs can be dumped from a leader or a follower.
  • The creation of read-only RDS instances is supported.
  • The InnoDB storage engine is used for system tables by default.
• Bugs fixed:
  • The bug that invalidates the commands that are run by a follower to delete logs is fixed.
  • The bug that causes slave threads to unexpectedly exit when the slave_sql_verify_checksum parameter is set to OFF and the binlog_checksum parameter is set to crc32 is fixed.

20190709

New features:

• The RDS Enterprise Edition is supported.
• The semi-sync plug-in is disabled.
• Table-level parallel replication and write set-level parallel replication are supported.
• The pk_access module is provided to expedite queries that are based on primary keys.
• Thread pools are supported.
• All of the AliSQL functions that are developed by Alibaba Cloud and released before the minor version 20190510 in the RDS Basic and High-availability Editions are incorporated.

ApsaraDB RDS for MySQL 5.6

20200630

• New features:
  • The performance agent feature is introduced. For more information, see Performance Agent. This feature is provided as a MySQL plug-in. It allows you to collect and analyze the performance metrics of an RDS instance in an efficient manner.
  • The maximum number of connections that are allowed is increased to 500,000.
  • The faster DDL feature is introduced. This feature provides an optimized buffer pool management mechanism. This mechanism reduces the impact of DDL operations and increases the number of concurrent DDL operations that are allowed. For more information, see Faster DDL.
• Performance optimization:
  • The global parameter max_execution_time is introduced. If the execution duration of an SQL statement exceeds the value of this parameter, the execution is paused.
  • Thread pools are optimized.
• Bug fixed:

  The bug that causes the system to incorrectly count the number of waits when commands are read from a client is fixed.

20200430

• The Data Protect feature is introduced. This feature supports the customization of security policies that are used to manage the permissions on DROP and TRUNCATE statements. This allows you to avoid data losses caused by the unintentional execution of these statements. For more information, see Data Protect.
• The mdl_info table is provided to store information about metadata locks.
• The bug that a conflict occurs when the thread pool and ic_reduce features are both enabled is fixed.

20200331

Performance optimization:

• The performance of thread pools with the default configuration is improved.
• The output of TCP errors is disabled by default.

20200229

• New feature:

  The read/write splitting function is supported for database proxies.

• Performance optimization:
  • Thread pools are optimized.
  • The time required to execute the PAUSE statement is reduced in various CPU architectures.
• Bug fixed:

  The bug that causes the system to partially commit XA transactions is fixed.

20200110

• New feature:

  The thread pool feature is introduced to separate threads from sessions. If a large number of sessions exist, the system can run a small number of threads to complete the tasks in active sessions. For more information, see Thread Pool.

• Performance optimization:

  The file deletion mechanism is optimized. When you asynchronously delete small files, links to the small files are canceled.

• Bugs fixed:
  • The bug that cause the system to incorrectly calculate the sleep time of the page cleaner is fixed.
  • The bug that causes the SELECT @@global.gtid_executed statement to incur a failover failure is fixed.
  • The bug that causes the IF CLIENT KILLED AFTER ROLLBACK TO SAVEPOINT PREVIOUS STMTS COMMITTED error is fixed.

20191212

Performance optimization:

The deletion of unnecessary TCP error logs is supported.

20191115

Bug fixed:

The bug that causes the overflow of timestamps in slow query logs is fixed.

20191101

Bugs fixed:

• The bug that causes the system to rotate slow query logs when you update common logs is fixed.
• Some display-related bugs are fixed.

20191015

• New features:
  • The rotation of slow query logs is supported. Every CSV slow query log file is assigned a unique name and a new file. This prevents data losses during the collection of slow query logs. You can run the show variables like '%rotate_log_table%'; command to check whether the rotation of slow query logs is enabled.
  • A new SM4 encryption algorithm is introduced to replace the original SM4 encryption algorithm.
  • The Purge Large File Asynchronously feature is introduced to asynchronously delete files. Before you delete a tablespace, the system renames the files in the tablespace as temporary files. Then, a background thread is started to asynchronously delete the temporary files. For more information, see Purge Large File Asynchronously.
  • The output of TCP errors is supported. TCP errors in read, read-wait, and write-wait events along with their error codes are returned by using end_connection events. In addition, logs with information about the errors are generated.
  • An SQL log caching mechanism is introduced to increase SQL logging performance.
• Bugs fixed:
  • The bug that prevents responses to the pstack command when a large number of connections are established is fixed. This is implemented by disabling the pstack command.
  • The bug that causes conflicts between implicit primary keys and CREATE TABLE AS SELECT statements is fixed.
  • The bug that prevents the system from automatically deleting the temporary files that are created from binary log files is fixed.

20190815

An optimized instance locking mechanism is introduced. This mechanism allows you to drop and truncate tables on an RDS instance even if the RDS instance is locked.

20190130

Bugs that compromise database stability are fixed.

20181010

The rocksdb_ddl_commit_in_the_middle parameter is introduced to MyRocks. If this parameter is set to on, some DDL statements call the COMMIT operation when they are executed.

201806** (ApsaraDB RDS for MySQL 5.6.16)

New feature: Microsecond-level time precision is supported for slow query logs.

20180426 (ApsaraDB RDS for MySQL 5.6.16)

• Invisible indexes are supported. For more information, see AliSQL.
• The bug that causes the system to apply threads on secondary RDS instances is fixed.
• The bug that compromises database performance when updates to partitioned tables are applied on secondary RDS instances is fixed.
• The bug that causes TokuDB to rebuild tables on which ALTER TABLE COMMENT statements are executed is fixed. For more information, see AliSQL.
• The bug that triggers deadlocks when SHOW SLAVE STATUS or SHOW STATUS statements are executed is fixed.

20171205 (ApsaraDB RDS for MySQL 5.6.16)

• The bug that triggers deadlocks when OPTIMIZE TABLE and ONLINE ALTER TABLE statements are executed at the same time is fixed.
• The bug that triggers conflicts between sequences and implicit primary keys is fixed.
• The bug that prevents the proper execution of SHOW CREATE SEQUENCE statements is fixed.
• The bug that causes the system to incorrectly collect statistics on TokuDB tables is fixed.
• The bug that triggers deadlocks when OPTIMIZE statements are executed in parallel on tables is fixed.
• The bug that causes the system to incorrectly record character sets in QUERY_LOG_EVENT is fixed.
• The bug that prevents an RDS instance from stopping due to signal processing issues is fixed. For more information, see AliSQL.
• The bug that is caused by the execution of RESET MASTER statements is fixed.
• The bug that causes secondary RDS instances to be in a constant waiting state is fixed.
• The bug that prevents the system from updating the status of primary and secondary RDS instances after primary/secondary switchovers is fixed in the RDS Enterprise Edition.
• The bug that causes the database process to unexpectedly exit due to the execution of SHOW CREATE TABLE statements is fixed.

20170927 (ApsaraDB RDS for MySQL 5.6.16)

The bug that causes the system to query tables from TokuDB based on incorrect indexes is fixed.

20170901 (ApsaraDB RDS for MySQL 5.6.16)

• New features:
  • The upgrade of SSL encryption to TLS 1.2 is supported. For more information, see AliSQL.
  • Sequences are supported.
• Bug fixed: The bug that causes the system to return an incorrect result set for the NOT IN operator is fixed.

20170530 (ApsaraDB RDS for MySQL 5.6.16)

New feature: The privileged account of an RDS instance is provided with the permissions to close the connections that are established by all standard accounts on the RDS instance.

20170221 (ApsaraDB RDS for MySQL 5.6.16)

ApsaraDB RDS for MySQL 5.5

20181212

The bug that causes the gettimeofday(2) function to return an incorrect time value is fixed. The returned time value is used to calculate the timeout period. If the returned time value is incorrect, some operations never time out.