RDS for MySQL Kernel Release History

This section describes the kernel version updates of RDS.

RDS for MySQL 8.0
RDS for MySQL 5.7
RDS for MySQL 5.6

RDS for MySQL 8.0

**Table 1** RDS for MySQL 8.0 version description
Date	Description
2024-10-28	Updates in RDS for MySQL 8.0.32: Issues resolved The statement outline was optimized to support the EXPLAIN ANALYZE statement. The deadlock problem in the 8.0.28.x community edition was resolved. Some bugs in SQL statement concurrency control were fixed.
2024-06-18	Updates in RDS for MySQL 8.0.28: Issues resolved The issue that a deadlock may occur during SHOW PROCESSLIST execution due to LOCK_thd_security_ctx introduced by sessions was resolved. For details, see Bug #32320541.
2024-05-23	The kernel version was upgraded to 8.0.32. New features and performance optimized Dynamic privileges of MySQL 8.0 allow the SUPER user to grant advanced administrative privileges, such as SESSION_VARIABLES_ADMIN and SYSTEM_VARIABLES_ADMIN, to other users. In RDS for MySQL 8.0.32, users are prevented from assigning risky permissions that may cause instance exceptions to themselves. When columns are added to or deleted from a table, the default algorithm can be changed from INSTANT to INPLACE or COPY. Issues resolved The issues resolved are the same as those of the community edition. For details, see Changes in MySQL 8.0.32. NOTE: To upgrade your instance version to 8.0.32, contact customer service. The performance of MySQL 8.0.32 deteriorates in some scenarios due to instant_col. For details, see Bug 111538. Security hardening The following security vulnerabilities were fixed: CVE-2018-25032, CVE-2021-22570, CVE-2022-21412, CVE-2022-21413, CVE-2022-21414, CVE-2022-21415, CVE-2022-21417, CVE-2022-21418, CVE-2022-21423, CVE-2022-21425, CVE-2022-21427, CVE-2022-21435, CVE-2022-21436, CVE-2022-21437, CVE-2022-21438, CVE-2022-21440, CVE-2022-21444, CVE-2022-21451, CVE-2022-21452, CVE-2022-21455, CVE-2022-21459, CVE-2022-21460, CVE-2022-21462, CVE-2022-21478, CVE-2022-21479, CVE-2022-21509, CVE-2022-21515, CVE-2022-21517, CVE-2022-21522, CVE-2022-21525, CVE-2022-21526, CVE-2022-21527, CVE-2022-21528, CVE-2022-21529, CVE-2022-21530, CVE-2022-21531, CVE-2022-21534, CVE-2022-21537, CVE-2022-21538, CVE-2022-21539, CVE-2022-21547, CVE-2022-21553, CVE-2022-21556, CVE-2022-21569, CVE-2022-21592, CVE-2022-21594, CVE-2022-21599, CVE-2022-21604, CVE-2022-21605, CVE-2022-21607, CVE-2022-21608, CVE-2022-21611, CVE-2022-21617, CVE-2022-21625, CVE-2022-21632, CVE-2022-21633, CVE-2022-21635, CVE-2022-21637, CVE-2022-21638, CVE-2022-21640, CVE-2022-21641, CVE-2022-27778, CVE-2022-32221, CVE-2022-39400, CVE-2022-39402, CVE-2022-39403, CVE-2022-39408, CVE-2022-39410, CVE-2023-21836, CVE-2023-21863, CVE-2023-21864, CVE-2023-21865, CVE-2023-21866, CVE-2023-21867, CVE-2023-21868, CVE-2023-21869, CVE-2023-21870, CVE-2023-21871, CVE-2023-21872, CVE-2023-21873, CVE-2023-21874, CVE-2023-21875, CVE-2023-21876, CVE-2023-21877, CVE-2023-21878, CVE-2023-21879, CVE-2023-21880, CVE-2023-21881, CVE-2023-21882, CVE-2023-21883, CVE-2023-21887, CVE-2023-21912, CVE-2023-21913, CVE-2023-21917, CVE-2023-21963, CVE-2023-22015, CVE-2023-22026, CVE-2023-22028, and CVE-2023-22084.
2023-12-01	Updates in RDS for MySQL 8.0.28: New features and performance optimized SQL statement concurrency control rules are applied to all users (the root user is excluded in the earlier version). To exclude certain users, contact customer service. The information_schema.rds_sql_filter_info system table is added, which allows you to view the current number of concurrent SQL statements and the number of historical SQL statements throttled by SQL statement concurrency control. Issues resolved The issue that the audit log plugin did not record prepared statements was resolved.
2023-09-01	The kernel version was upgraded to 8.0.28. New features and performance optimized SQL statement concurrency control was optimized. The asynchronous purge performance of large files was optimized. Issues resolved A bugfix of a later version was introduced. Data inconsistency caused by parallel DDL was resolved. The memory leakage and thread suspension issues of audit logs were resolved. Security hardening The following security vulnerabilities were fixed: CVE-2019-17543, CVE-2020-1971, CVE-2021-22901, CVE-2021-22922, CVE-2021-22923, CVE-2021-22924, CVE-2021-22925, CVE-2021-22926, CVE-2021-22945, CVE-2021-22946, CVE-2021-22947, CVE-2021-2339, CVE-2021-2340, CVE-2021-2342, CVE-2021-2352, CVE-2021-2354, CVE-2021-2356, CVE-2021-2357, CVE-2021-2367, CVE-2021-2370, CVE-2021-2372, CVE-2021-2374, CVE-2021-2383, CVE-2021-2384, CVE-2021-23841, CVE-2021-2385, CVE-2021-2387, CVE-2021-2389, CVE-2021-2390, CVE-2021-2399, CVE-2021-2402, CVE-2021-2410, CVE-2021-2412, CVE-2021-2417, CVE-2021-2418, CVE-2021-2422, CVE-2021-2424, CVE-2021-2425, CVE-2021-2426, CVE-2021-2427, CVE-2021-2429, CVE-2021-2437, CVE-2021-2440, CVE-2021-2441, CVE-2021-2478, CVE-2021-2479, CVE-2021-2481, CVE-2021-3449, CVE-2021-35537, CVE-2021-35546, CVE-2021-35575, CVE-2021-35577, CVE-2021-35583, CVE-2021-35591, CVE-2021-35596, CVE-2021-35602, CVE-2021-35604, CVE-2021-35607, CVE-2021-35610, CVE-2021-35612, CVE-2021-35622, CVE-2021-35623, CVE-2021-35624, CVE-2021-35625, CVE-2021-35626, CVE-2021-35627, CVE-2021-35628, CVE-2021-35629, CVE-2021-35630, CVE-2021-35631, CVE-2021-35632, CVE-2021-35633, CVE-2021-35634, CVE-2021-35635, CVE-2021-35636, CVE-2021-35637, CVE-2021-35638, CVE-2021-35639, CVE-2021-35640, CVE-2021-35641, CVE-2021-35642, CVE-2021-35643, CVE-2021-35644, CVE-2021-35645, CVE-2021-35646, CVE-2021-35647, CVE-2021-35648, CVE-2021-3711, CVE-2022-0778, CVE-2022-21245, CVE-2022-21249, CVE-2022-21253, CVE-2022-21254, CVE-2022-21264, CVE-2022-21265, CVE-2022-21278, CVE-2022-21297, CVE-2022-21301, CVE-2022-21302, CVE-2022-21303, CVE-2022-21304, CVE-2022-21339, CVE-2022-21342, CVE-2022-21344, CVE-2022-21348, CVE-2022-21351, CVE-2022-21352, CVE-2022-21358, CVE-2022-21362, CVE-2022-21367, CVE-2022-21368, CVE-2022-21370, CVE-2022-21372, CVE-2022-21374, CVE-2022-21378, CVE-2022-21595, CVE-2022-21600, and CVE-2023-21950.
2023-03-15	Updates in RDS for MySQL 8.0.25: New features and performance optimized Printing of oversized SQL audit logs was optimized. The security of kernel log printing was enhanced. Issues resolved Unexpected restarts due to concurrent DDL and DML operations on DB instances were resolved. Users can no longer be granted the connection_admin permission.
2022-09-09	Updates in RDS for MySQL 8.0.25: New features and performance optimized Connection per thread was supported for killing sessions. Constraints on memory were added for the Performance Schema. The performance of SQL Explorer was optimized based on specific scenarios. Database performance was optimized in specific scenarios when the value of internal_tmp_mem_storage_engine was set to MEMORY. The compiler was upgraded to GCC 10.3. Issues resolved Errors caused by writes to a temporary file were resolved. Unexpected responses to Common Table Expression (CTE) queries were resolved. Security hardening The following security vulnerabilities were fixed: CVE-2021-2417, CVE-2021-2339, CVE-2021-2425, CVE-2021-2426, CVE-2021-2427, CVE-2021-2424, CVE-2021-2383, CVE-2021-2384, and CVE-2021-2410.
2022-06-01	New features and performance optimized The kernel version was upgraded to 8.0.25. SQL statement concurrency control was supported. The compiler was upgraded to GCC 9.3. Issues resolved Replication interruption caused by a single oversized binlog was resolved. Inaccurate innodb_row_lock_current_waits statistics were fixed. Unexpected restarts due to the use of BLOB fields were resolved. Security hardening The following security vulnerabilities were fixed: CVE-2021-2307, CVE-2021-2180, and CVE-2021-2194.
2021-08-07	New features and performance optimized Static connection in the thread pool improved the performance. Profile-Guided Optimization (PGO) was enabled. The MySQL hash algorithm was optimized. Remarks can be added to a database. Protection from being modified by DDL was provided for the system database. The innodb_total_tablespaces parameter was added to calculate the number of InnoDB tablespaces. The InnoDB lock view was provided in information_schema. The OpenSSL, jemalloc, and curl open-source components were upgraded. Issues resolved The issue that XA transactions may restart abnormally after binlog rotation was resolved. The issue that precompiled SQL statement types were not recorded by SQL Explorer was resolved. Incorrect execution time statistics for FLUSH PRIVILEGES was resolved. The issue that audit logs were incorrectly written into other files was resolved.
2021-04-13	The issue that XA transactions may be lost after unexpected database restart was resolved. The adaptive hash segmentation algorithm was optimized. The kernel version was upgraded to 8.0.21. Security hardening The following security vulnerabilities were fixed: CVE-2020-14697, CVE-2020-14680, CVE-2020-14678, CVE-2020-14663, CVE-2021-2020, CVE-2020-14619, CVE-2020-14591, CVE-2020-14576, and CVE-2020-14539.
2021-01-26	SQL statement concurrency control was optimized. Full SQL collection was optimized.
2020-12-31	Performance optimized The compiler was upgraded to GCC 9.
2020-12-01	Performance optimized The efficiency of collecting additional information about slow query logs was improved. Issues resolved The issue that replication on the standby DB instance might be interrupted during the rollback of distributed transactions was resolved.
2020-11-06	Issues resolved Timing error caused by gettimeofday in multiple threads was fixed.
2020-09-21	Disconnection details were recorded in error logs. Index hints were supported.
2020-08-03	The execution time and waiting time of large transactions were displayed. Independent connection control was used to manage users. SQL filter was used to restrict the execution frequency of SQL statements during peak hours. Kernel performance was optimized.
2020-06-19	The kernel version was upgraded to 8.0.20. Kernel performance was optimized.
2020-02-15	RDS for MySQL 8.0 was put into commercial use. The Huawei Cloud Kunpeng-powered Arm kernel version was released.
2019-12-15	The kernel version was upgraded to 8.0.17. The parallel index creation was 2.5 times faster.
2019-10-15	The issue that the primary/standby replication was abnormal when SQL_MODE was set to PAD_CHAR_TO_FULL_LENGTH was resolved.
2019-09-15	Thread pools were supported. For details, see Connection Thread Pool. OpenSSL was upgraded to 1.1.1a. The Common Type System (CTS) syntax create table xx select was supported. The memory usage and CPU time usage of user threads can be queried through show full processlist.

RDS for MySQL 5.7

**Table 2** RDS for MySQL 5.7 version description
Date	Description
2024-10-28	Updates in RDS for MySQL 5.7.44: Issues resolved Some bugs in SQL statement concurrency control were fixed.
2024-04-11	The kernel version was upgraded to 5.7.44. The changes are the same as those of the community edition. For details, see Changes in MySQL 5.7.44. Security hardening The following security vulnerabilities were fixed: CVE-2023-22028, CVE-2023-22084, and CVE-2023-38545.
2023-12-01	New features and performance optimized The kernel version was upgraded to 5.7.43. SQL statement concurrency control rules are applied to all users (the root user is excluded in the earlier version). To exclude certain users, contact customer service. The information_schema.rds_sql_filter_info system table is added, which allows you to view the current number of concurrent SQL statements and the number of historical SQL statements throttled by SQL statement concurrency control. Issues resolved The issue that the audit log plugin did not record prepared statements was resolved. Security hardening The following security vulnerabilities were fixed: CVE-2022-43551, CVE-2023-21912, CVE-2023-21980, CVE-2023-22007, CVE-2023-22015, CVE-2023-22026, and CVE-2023-22053.
2023-09-01	Updates in RDS for MySQL 5.7.41: New features and performance optimized SQL statement concurrency control was optimized. Slow memory release of jemalloc, which causes out of memory (OOM) exceptions, was optimized. Issues resolved The memory leakage and thread suspension issues of audit logs were resolved. Too large gap lock ranges were resolved.
2023-06-28	New features and performance optimized The kernel version was upgraded to 5.7.41. Compiler security options were added. Issues resolved The replication exception that may occur when an index is added to a reference table and a foreign key is added to another table concurrently was rectified. The replication exception that may occur when a child table is deleted after a foreign key table is deleted was rectified. Security hardening The following security vulnerabilities were fixed: CVE-2023-21963, CVE-2022-32221, CVE-2023-21840, CVE-2022-2097, CVE-2022-21617, CVE-2022-21608, CVE-2022-21592, CVE-2022-21589, CVE-2022-1292, CVE-2022-27778, CVE-2018-25032, and CVE-2022-21515.
2022-09-09	New features and performance optimized The kernel version was upgraded to 5.7.38. The compiler was upgraded to GCC 10.3. Connection per thread was supported for killing sessions. The threshold for slow query logs can be set based on the lock wait duration. ALT security was hardened. Issues resolved Recovery security of crashed XA transactions on the primary instance was enhanced. Abnormal instance reboot when Database Proxy is enabled was resolved. Abnormal reboot caused by failed memory request for plugins was resolved. Security hardening The following security vulnerabilities were fixed: CVE-2022-21454, CVE-2022-21417, CVE-2022-21427, CVE-2022-21451, CVE-2022-21444, and CVE-2022-21460.
2022-06-01	New features and performance optimized The kernel version was upgraded to 5.7.37. The compiler was upgraded to GCC 9.3. The OpenSSL and curl open-source components were upgraded. Issues resolved Replication interruption caused by a single oversized binlog was resolved. Unexpected restarts caused by concurrent playback grants to the slave node were resolved. Replication interruptions caused by hidden auto-increment keys were resolved. Unexpected restarts during rollback of tables with virtual columns were resolved. Unexpected restarts during recovery of encrypted tables were resolved. Inaccurate Seconds Behind Master values in specific scenarios were resolved. Security hardening The following security vulnerabilities were fixed: CVE-2022-21367, CVE-2022-21304, and CVE-2022-21344.
2022-01-26	New features and performance optimized Hidden auto-increment keys were supported. Issues resolved Replication exceptions caused by repeated commitment of XA transactions were resolved. Inaccurate innodb_row_lock_current_waits statistics were fixed.
2021-11-26	New features and performance optimized Restrictions on the length of a single record for SQL Explorer were removed. Application Lossless and Transparent (ALT) Phase I was supported for RDS for MySQL. Issues resolved Memory problems of the thread pool in extreme scenarios were resolved. Occasional suspension of XA transaction playbacks on a standby node was resolved.
2021-08-07	New features and performance optimized Static connection in the thread pool improved the performance. Profile-Guided Optimization (PGO) was enabled. The MySQL hash algorithm was optimized. Remarks can be added to a database. Protection from being modified by DDL was provided for the system database. I/O latency information can be queried in error logs. Minidumps were supported. The kernel version was upgraded to 5.7.33. The OpenSSL, jemalloc, and curl open-source components were upgraded. Issues resolved The issue that the replication on the standby node may be interrupted due to playback order preserving was resolved. The issue that XA transactions may restart abnormally after binlog rotation was resolved. The issue that precompiled SQL statement types may not be recorded by SQL Explorer was resolved. Incorrect execution time statistics for FLUSH PRIVILEGES was resolved. The issue that audit logs were incorrectly written into other files was resolved. Security hardening The following security vulnerabilities were fixed: CVE-2021-2011, CVE-2021-2178, and CVE-2021-2202.
2021-04-13	The issue that XA transactions may be lost after unexpected database restart was resolved. The adaptive hash segmentation algorithm was optimized. The kernel version was upgraded to 5.7.32.
2021-01-26	New features The real client address can be displayed when proxy is used. Issues resolved Full SQL collection was optimized. The issue that revoking permissions might cause permission inconsistency between primary and standby DB instances was resolved. MySQL 8.0 optimizations on Instant Add Column was incorporated.
2020-12-31	Performance optimized The efficiency of collecting additional information about slow query logs was improved. The compiler was upgraded to GCC 9. Issues resolved The issue that replication on the standby DB instance might be interrupted during the rollback of distributed transactions was resolved.
2020-12-01	The conflict frequency between fil_sys mutual exclusions was reduced.
2020-11-06	New features The compiler was optimized. The UTF-8 encoding efficiency was improved on non-Arm platforms. Issues resolved Timing error caused by gettimeofday in multiple threads was fixed.
2020-09-21	The kernel version was upgraded to 5.7.31. SQL filter was used to restrict the execution frequency of SQL statements during peak hours.
2020-08-03	Kernel performance was optimized. The recycle bin was supported. Issues that may occur during local disk data cleanup were resolved.
2020-07-09	Kernel performance was optimized. Users' operation history can be recorded in error logs. Distributed transaction stability was improved.
2020-06-30	Kernel performance was optimized. Local disk logs whose size exceeds the local disk capacity were stored on cloud disks. The buffer pool memory initialization module was optimized to improve the initialization efficiency. The thread security of some operations on Arm was improved.
2020-05-30	New features Index hints were supported. Full SQL logs can be captured. Issues resolved Occasional database connection failures were resolved.
2020-04-30	Kernel performance was optimized.
2020-03-30	The kernel version was upgraded to 5.7.29. Kernel performance was optimized. Threshold pools supported statistics on I/O waits.
2020-02-15	Replication dual-channel: A replication status channel was added to accurately determine the replication status when the primary database crashes, ensuring that transactions are not lost. Optimized ROW_IMAGE mode: The binlog size was reduced, and migration and SQL flashback were supported.
2019-12-15	The progress of adding columns or indexes can be obtained through information_schema.innodb_alter_table_progress. For details, see DDL Progress Display. Long transactions: The transaction execution time Trx_Executed_Time can be obtained through show processlist. Online extension of the string field length: The VARCHAR field length was changed from COPY to INPLACE by default. For details, see Online Varchar Length Increase. Abundant InnoDB deadlock information: The complete onsite information when deadlock occurs at the InnoDB layer can be viewed through show engine innodb status.
2019-10-15	Performance optimized The Huawei Cloud Kunpeng-powered Arm kernel version was released. New features The kernel version was upgraded to 5.7.27. Instant Add Column was supported. Columns are quickly added to a table without copying data and without occupying disk space and disk I/Os. Data can be updated in real time during peak hours. Metadata lock (MDL) view was supported. The MDL information held or waited by the thread can be obtained through information_schema.metadata_lock_info. For details, see MDL Views.
2019-08-15	For Jemalloc memory management, the glibc memory management module was replaced to reduce memory usage and improve memory allocation efficiency.
2019-06-15	The kernel version was upgraded to 5.7.25.
2019-05-15	New features When sync_binlog and innodb_flush_log_at_trx_commit are set to values other than 1, the crash-safe replication of the standby database is guaranteed. In sysbench high-concurrent write-only request scenarios, the replication delay between primary and standby DB instances is almost zero. Issues resolved The issue that when relay_log_recovery was set to ON, the standby database could not be rebooted after being killed in certain scenarios was resolved. The issue that the primary/standby replication was abnormal when SQL_MODE was set to PAD_CHAR_TO_FULL_LENGTH was resolved. The issue that performance_schema statistics were repeatedly measured was resolved. The issue that when ORDER BY queries were performed on tables related to information replication in Performance_schema, the return value was empty was resolved.
2019-01-15	The issue that data was inconsistent and data replication was interrupted after the flush operation was performed on read replicas was resolved. The issue that the replication thread of the standby database was suspended due to statements like REPAIR or OPTIMIZE was resolved.
2018-11-15	The kernel version was upgraded to 5.7.23. Temporary tables can be created or deleted in transactions when GTID is enabled. Table-level multi-threaded slaves (MTS) parallel playback was supported.
2018-07-15	The kernel version was upgraded to 5.7.22. Thread pools were supported. For details, see Connection Thread Pool. The Common Type System (CTS) syntax create table xx select was supported. Operator pushdown: The aggregation operator is pushed down to the storage engine layer to improve the execution speed of count() and sum(). Kill idle transactions: Transactions that have been idled for a long time are automatically killed after the timeout threshold is reached. For details, see Ending Idle Transactions. The memory usage and CPU time usage of user threads can be queried through show full processlist.

RDS for MySQL 5.6

**Table 3** RDS for MySQL 5.6 version description
Date	Description
2024-10-28	Updates in RDS for MySQL 5.6.51: Issues resolved DB instance crashes due to the crash bug of the row_search_mvcc function in the open-source community were resolved by backporting. For details, see Bug #96610. The calculation of long-running transactions after XA transactions are committed was optimized.
2023-09-01	Updates in RDS for MySQL 5.6.51: New features and performance optimized SQL statement concurrency control was optimized. Issues resolved Thread suspension for audit logs was resolved.
2023-03-15	Updates in RDS for MySQL 5.6.51: New features and performance optimized Printing of oversized SQL audit logs was optimized. The security of log printing was enhanced. Issues resolved The replication exception that may occur when an index is added to a reference table and a foreign key is added to another table concurrently was rectified.
2022-09-09	New features and performance optimized Connection per thread was supported for killing sessions. Issues resolved Abnormal instance reboot when Database Proxy is enabled was resolved. main.proxy_connect buffer overflow issues were resolved. Abnormal reboot caused by failed memory request for plugins was resolved.
2022-06-01	Inaccurate innodb_row_lock_current_waits statistics were fixed.
2021-08-07	New features Remarks can be added to a database. Protection from being modified by DDL was provided for the system database. The OpenSSL and jemalloc open-source components were upgraded. Issues resolved The issue that the synchronization may be interrupted after password change was resolved. The issue that audit logs were incorrectly written into other files was resolved.
2021-04-13	The issue that the replication on the standby node may be interrupted due to playback order preserving was resolved. The kernel version was upgraded to 5.6.51. Security hardening The vulnerability patches for MySQL 5.6 Community Edition are no longer released because the patches for this version are not released anymore.
2021-01-26	New features The real client address can be displayed when proxy is used. Issues resolved The issue that a syntax error was reported during the select 1 for update execution was resolved. Full SQL collection was optimized.
2020-12-31	SQL filter was reconstructed to improve usability.
2020-11-06	The kernel version was upgraded to 5.6.50.
2020-09-23	SQL filter was used to restrict the execution frequency of SQL statements during peak hours.
2020-08-03	The kernel version was upgraded to 5.6.49.
2020-07-09	Local disk logs whose size exceeds the local disk capacity were stored on cloud disks. Users' operation history can be recorded in error logs.
2020-05-30	The buffer pool memory initialization module was optimized to improve the initialization efficiency.
2020-04-30	Occasional database connection failures were resolved.
2020-03-30	Full SQL collection was supported. The compiler was upgraded to 7.3. The kernel version was upgraded to 5.6.47.
2020-02-15	Replication dual-channel: A replication status channel was added to accurately determine the replication status when the primary database crashes, ensuring that transactions are not lost. Optimized ROW_IMAGE mode: The binlog size was reduced, and migration and SQL flashback were supported.
2019-12-15	Long transactions: The transaction execution time Trx_Executed_Time can be obtained through show processlist. Online extension of the string field length: The VARCHAR field length was changed from COPY to INPLACE by default. For details, see Online Varchar Length Increase. Abundant InnoDB deadlock information: The complete onsite information when deadlock occurs at the InnoDB layer can be viewed through show engine innodb status.
2019-10-15	The kernel version was upgraded to 5.6.45. The memory usage and CPU time usage of user threads can be queried through show full processlist. Kill idle transactions: Transactions that have been idled for a long time are automatically killed after the timeout threshold is reached. For details, see Ending Idle Transactions.
2019-08-15	For Jemalloc memory management, the glibc memory management module was replaced to reduce memory usage and improve memory allocation efficiency.
2019-06-15	The kernel version was upgraded to 5.6.43. The audit function was supported.
2019-05-15	The issue that the replication delay Seconds_Behind_Master was inaccurate in certain scenarios was resolved. The issue that the primary/standby replication was abnormal when SQL_MODE was set to PAD_CHAR_TO_FULL_LENGTH was resolved.
2019-01-15	The issue that data was inconsistent and data replication was interrupted after the flush operation was performed on read replicas was resolved. The issue that the replication thread of the standby database was suspended due to statements like REPAIR or OPTIMIZE was resolved. The issue that an error occurred on the grant select(column_name) statement replication threshold was resolved.
2018-11-15	The kernel version was upgraded to 5.6.41. Temporary tables can be created or deleted in transactions when GTID is enabled. Table-level multi-threaded slaves (MTS) parallel playback was supported.
2018-07-15	New features The kernel version was upgraded to 5.6.40. Thread pools were supported. For details, see Connection Thread Pool. The Common Type System (CTS) syntax create table xx select was supported. Issues resolved The issue that binlog and relay log names depended on the PID file names was resolved. The issue that the empty relay_log_basename parameter value resulted in primary/standby replication failures was resolved. The issue that the force index syntax became invalid in the group_by xx order_by xx limit n1,n2 scenario was resolved.