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 |
|
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 |
- 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 |
|
2020-12-01 |
The conflict frequency between fil_sys mutual exclusions was reduced. |
2020-11-06 |
|
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 |
|
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.
- 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.
- 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.
|
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.
- 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.
- The memory usage and CPU time usage of user threads can be queried through show full processlist.
|