These are the 2026 release notes for the PolarDB-X compute nodes.
Release date: 2026-06-10
Product version: V2.6.0
Component version: 5.4.21
Category | Description |
New features and optimizations | Added support for AI Function. |
Added support for the AES_256 encryption algorithm. | |
Added performance monitoring for Binlog Dump connections on compute nodes (CNs). This feature supports three-stage timing for bottleneck analysis and heartbeat-based idle detection. | |
Optimized the output of | |
Subqueries can now be used in the | |
Fixes | Fixed a startup issue where compute nodes could block new connections for up to two hours. This was caused by the synchronous fetching of OSS file metadata for cold data archiving tables. |
Fixed an issue where the adaptive global secondary index (GSI) optimization was incompatible with MPP execution plans, causing query errors. | |
Fixed an issue where forbidPushDmlWithHint did not read the | |
Disabled the multi-stage DDL feature by default. | |
Fixed an issue where a | |
Fixed an | |
Fixed an issue where QPS statistics on compute nodes (CNs) did not include transaction control statements such as | |
Fixed an issue where querying a non-existent logical table in PARTITION_HINT mode did not correctly throw the | |
Fixed a |
Release date: 2026-05-21
Product version: V2.6.0
Component version: 5.4.21
Category | Description |
New features and optimizations | Added support for random dispatch of |
Added support for CTE reuse. | |
You can now disable writes to specified storage nodes (DNs). | |
Optimized the purge mechanism. | |
Expanded the scope of subqueries to support | |
Fixes | Fixed an issue where |
Fixed an issue where | |
Fixed an issue where statements that contained newline characters and resulted in an error were not automatically rolled back. | |
Fixed an MDL lock leak that occurred in some concurrent scenarios that involved DML and KILL statements. | |
Fixed an issue where the | |
Fixed an issue where executing | |
Fixed a | |
Fixes an unsupported syntax error caused by incorrectly pushing down | |
Fixed a primary key conflict in | |
Fixed incorrect handling of the | |
Fixes an issue where | |
Fixed a concurrency safety issue in | |
Fixed an issue where |
Release date: 2026-05-13
Product version: V2.5.0
Component version: 5.4.20
Category | Description |
New features and optimizations | |
Added support for the | |
Added support for the | |
Added support for sending the | |
Optimized the synchronization performance of the columnstore index (CCI). | |
Optimized the lock-free column type change capability, provided a logic-free multi-write execution strategy, and supported more | |
Fixes | Fixes an issue where |
Release date: 2026-04-14
Product version: V2.5.0
Component version: 5.4.21
Category | Description |
New features and optimizations | Added support for the |
Introduced Table Partition Splitting 2.0, which provides an in-place splitting execution strategy without logical multi-write operations. | |
Added support for hybrid row-based and columnar storage and queries for single tables. | |
Added support for baseline canary releases. | |
Added support for columnar sub-instances. | |
Added support for using | |
Collected Number of Distinct Values (NDV) information for all columns in the columnstore index. | |
Optimized GroupTopN by enabling two-phase GroupTopN by default for columnar storage. | |
Added support for the AES_256 encryption algorithm. | |
Optimized the synchronization performance of the columnstore index. | |
Enhanced the lock-free column type change capability by providing an execution strategy that does not require logical multi-write operations and by supporting more | |
Added support for the | |
Column encryption now supports external KMS keys. | |
Improved the compatibility of common error codes with native MySQL, such as "Table does not exist" or "Column does not exist". | |
Added support for pushing down subqueries in | |
Expanded the applicable scope of JOIN Reorder for columnar queries. | |
Optimized the performance of paginated queries that use OR conditions. | |
Optimized cardinality estimation for single-value JOINs. | |
Optimized the performance of columnar subqueries by supporting decorrelation for any subquery. | |
TTL (Time-to-Live) now supports cold data archiving for integer types based on specific date formats. | |
Optimized the performance of grouped Top-N queries. | |
Optimized the selection logic for columnar archive tables. Queries on TTL tables without a columnstore index are now automatically routed to the columnar archive table in read-only columnar instances. | |
Added the | |
Added support for the GB18030-2022 character set. | |
Optimized the index selection logic for queries where a global secondary index (GSI) is the only available index. | |
Fixes | Fixed an issue where logout log latency did not meet expectations. |
Fixed an issue where the | |
Fixed an SQL execution error that was caused by incorrect pushdown of correlated subqueries. | |
Fixed an issue where JOIN ROWCOUNT estimation failed for multi-table JOINs that were combined with column subqueries. | |
Fixed a physical SQL generation error that was caused by a subquery in a Correlate operation accessing an iterative CTE. | |
Fixed an occasional error in the RangeScan executor that occurred during dispatch planning. | |
Fixed an issue where a redundant ORDER BY clause prevented the generation of a BKA JOIN. | |
Fixed a data error in the columnstore index that was caused by case sensitivity issues in | |
Fixed an issue where a single-table DELETE with FORCE INDEX could cause a "database not found" error on storage nodes. | |
Fixed a scale-in failure that was caused by partition changes in a columnstore index. | |
Fixed an issue with database name replacement when pushing down cross-database CTE statements. | |
Fixed an issue where an archiving task for a TTL (Time-to-Live) table could fail with a null pointer exception (NPE) if the table had a columnstore index (CCI) but no archive table was configured. | |
Fixed an issue where the | |
Fixed an abnormal rollback of a Modify Column operation that was caused by a multi-stage DDL locking a table in a specific availability zone due to time zone issues. | |
Prevented the creation of a columnstore index on instances that do not have columnar nodes. | |
Fixed an error that occurred when executing | |
Fixed an error in | |
Fixed a rare logical database initialization failure that could occur during compute node startup. | |
Fixed an issue that prevented a columnstore index from being set to INVISIBLE. | |
Fixed an issue where MPP queries could return incorrect results due to shuffle operations. | |
Fixed a potential synchronization failure in the logging engine when processing CREATE TABLE statements for a specific table group, which was caused by specifying the collation before the charset. | |
Fixed an MDL deadlock detection failure. | |
Fixed a case sensitivity issue with columnstore index names. | |
Fixed the return value of | |
Fixed a table creation error that occurred when the boundary value definition of a range/list partitioned table contained escape characters. | |
Fixed a Range Scan query error within RC transactions. | |
Fixed a failure in the lock-free column type change feature that occurred when adding a new column before the primary key. | |
Fixed an error where the recycle bin feature failed to process tables that contained a global secondary index (GSI). | |
Fixed a CTE pushdown error for single tables in MySQL 5.7 storage nodes. | |
Fixed an error that was caused by using a CTE in an INSERT SELECT statement that involved only a single table. | |
Fixed a potential replication interruption on read-only row store instances when a DDL operation was interrupted or rolled back. | |
Fixed a potential optimization error in correlation queries that involved aggregate functions. |
Release date: 2026-03-25
Product version: V2.5.0
Component version: 5.4.21
Category | Description |
Fixes | Fixed an issue where the |
Release date: 2026-03-18
Product version: V2.5.0
Component version: 5.4.21
Category | Description |
Fixes | Fixed an upgrade error for some earlier versions of instances. |
Release date: 2026-03-12
Product version: V2.5.0
Component version: 5.4.20
Category | Description |
New features and optimizations | Improved error messages when a user does not exist. |
Enhanced the lock-free column type change capability by providing an execution strategy that does not require logical multi-write operations and by supporting more | |
Added support for expanding the number of partitions by using | |
| |
Optimized the distribution algorithm for subpartitions to resolve an issue where all subpartitions under a single primary partition were concentrated on a single storage node. | |
Optimized GroupTopN. Two-phase GroupTopN is now enabled by default for the columnstore index (CCI). | |
Introduced Table Partition Splitting 2.0, which provides an in-place splitting execution strategy without logical multi-write operations. | |
Added support for configuring account-based standby reads. | |
Column encryption now supports external KMS keys. | |
Fixes | Optimized the table group assignment for the columnstore index (CCI). |
Fixed an unexpected failure that occurred when adding a column to a table with a clustered index. | |
Fixed an issue where an EXIST subquery could return duplicate results. | |
Fixed incorrect results for reverse-broadcast SemiJoin on unique keys. | |
Fixed an issue where | |
Fixed errors that occurred in some subquery scenarios. | |
Fixed a potential interruption in the main link of the logging engine when executing an | |
Optimized the xplan index selection logic to prevent slow queries caused by the incorrect selection of a bit column index. | |
Fixed an issue with the set data type in columnar queries. |
Release date: 2026-01-27
Product version: V2.5.0
Component version: 5.4.21
Category | Description |
New features and optimizations | Added support for hybrid row-based and columnar storage and queries for single tables. |
Improved the compatibility of common error codes with native MySQL, such as "Table does not exist" or "Column does not exist". | |
Optimized the index selection logic in execution plans to prevent slow queries caused by the incorrect selection of a | |
Optimized the performance of table lookups for global secondary indexes (GSIs). | |
Optimized the distribution algorithm for subpartitions to resolve an issue where all subpartitions under a single primary partition were assigned to one storage node (DN) in specific scenarios. | |
Fixes | Fixed an issue where the |
Release date: 2026-01-26
Product version: V2.5.0
Component version: 5.4.20
Category | Description |
New features and optimizations | Added support for hybrid row-based and columnar storage and queries for single tables. |
Added support for directly loading incremental files from columnar nodes, which significantly reduces the overhead of cold loading for incremental data. | |
Added CSV file caching for columnstore indexes (CCIs). | |
Added the | |
Added support for the MySQL 8.0 | |
Optimized the performance of table lookups for global secondary indexes (GSIs). | |
Optimized the distribution algorithm for subpartitions to resolve an issue where all subpartitions under a single primary partition were assigned to one storage node (DN) in specific scenarios. | |
Optimized query performance for grouped Top-N scenarios. | |
Reduced transient disconnections and jitter in service traffic during maintenance on underlying storage nodes. | |
Optimized the idempotency check logic for migration tasks when the Locality property of a table group is modified. | |
Improved the compatibility of common error codes with native MySQL, such as "Table does not exist" or "Column does not exist". | |
Fixes | Fixed an error in |
Fixed a database creation failure that occurred if the name of the storage pool contained an uppercase letter. | |
Fixed an issue where execution plans failed to be updated correctly after DDL operations were performed on views that contained a window function. | |
Fixed an execution error in | |
Fixed unexpected query results when sending | |
Fixed incorrect metadata when multiple DNs were scaled in for logical databases that declare specific storage nodes in their Locality property. | |
Fixed an issue where assigning a NULL value to a | |
Fixed a potential lag in sequence values in statistics system tables. | |
Fixed inaccurate connection monitoring. | |
Fixed an issue where the connection metric for the | |
Fixed an error during | |
Fixed unexpected failures when performing |