2024
This topic describes the engine release notes for AnalyticDB for PostgreSQL in elastic storage mode in 2024 and provides links to the relevant references.
November 2024
V7.1.1.1
|
Category |
Feature |
Description |
References |
|
New feature |
Storage engine |
The data cache feature is supported for the Beam engine to accelerate nested-loop index joins. |
|
|
Automatic partitioning |
By default, the automatic partitioning feature is enabled for partitioned tables. |
||
|
Partition dump |
The dump_table_ddl() function can be used to export the schema of partitioned tables. |
None |
|
|
Optimized feature |
Planner |
The LIMIT query plans in the planner are optimized to improve the performance of index scans and LIMIT queries. |
None |
|
Optimizer |
The performance of the static partition pruning feature of the Orca optimizer is improved. |
None |
|
|
Fixed issue |
Optimizer |
The following issue is fixed: The Orca optimizer fails to generate execution plans that contain |
None |
|
Partitioned table |
The following issue is fixed: When the ANALYZE statement is executed on a partitioned table, the Not a Number (NaN) value is returned for the correlation parameter in specific scenarios. This may result in abnormal index scan costs. |
None |
|
|
Storage engine |
|
||
|
Stability |
|
||
|
Storage engine |
The following issue is fixed: The cache performance is degraded due to the reading of residual records. |
None |
V7.0.6.10
|
Category |
Feature |
Description |
References |
|
Optimized feature |
Planner |
The LIMIT query plans in the planner are optimized to improve the performance of index scans and LIMIT queries. |
None |
|
Fixed issue |
Optimizer |
The following issue is fixed: The Orca optimizer fails to generate execution plans that contain |
None |
|
Stability |
|
None |
|
|
Storage engine |
|
October 2024
V7.1.1.0
|
Category |
Feature |
Description |
References |
|
New feature |
Vector search |
The vector search engine is fully supported in AnalyticDB for PostgreSQL V7.0. |
None |
|
Synonym management |
The synonym search feature is supported. |
||
|
PostgresML |
An end-to-end platform that integrates AI/ML and Retrieval-Augmented Generation (RAG) is supported based on the AI/ML and RAG features of PostgreSQL. |
||
|
Asynchronous materialized view |
Asynchronous materialized views are fully supported in AnalyticDB for PostgreSQL V7.0. When data in a base table changes, the materialized view created based on the base table can be automatically updated. |
None |
|
|
Optimized feature |
Executor |
The performance of the Laser engine at the execution layer is improved. |
None |
|
Optimizer |
The performance of the static partition pruning feature of the Orca optimizer is improved. |
None |
|
|
Fixed issue |
Stability |
Issues related to the analyze and vacuum operations and sort keys of the Beam storage engine are fixed. |
None |
|
Dictionary encoding |
Dictionary encoding issues are fixed. |
V7.0.6.9
|
Category |
Feature |
Description |
References |
|
Optimized feature |
Data link |
The MaxCompute foreign data wrapper (FDW) feature is updated to improve stability. |
None |
|
Query acceleration |
The query cache feature is updated to improve stability. |
||
|
Fixed issue |
Stability |
Issues related to the analyze and vacuum operations and sort keys of the Beam storage engine are fixed. |
September 2024
V7.1.0.1
|
Category |
Feature |
Description |
References |
|
Fixed issue |
Minor version update |
The minor version update failure is fixed by modifying the installation logic of the minor version update extension. |
|
|
Scaling |
The redo xlog failure that occurs when added nodes are started is fixed. |
||
|
Data access |
The data access interruption issue caused by limits is fixed. |
None |
V7.1.0.0
|
Category |
Feature |
Description |
References |
|
New feature |
Multi-zone deployment |
The multi-zone deployment feature is supported to implement disaster recovery in the same region. This ensures a recovery point objective (RPO) of 0. |
None |
|
High-performance full-text search |
High-performance full-text search based on the Best Matching 25 (BM25) algorithm is supported. |
||
|
FIXDECIMAL |
The FIXDECIMAL type is supported to replace the DECIMAL or NUMERIC type to improve query speed. |
None |
|
|
High availability |
The hot mirror feature is supported. |
None |
|
|
Optimized feature |
Automatic partitioning |
Partitions can be automatically created based on inserted values. |
None |
|
Beam storage engine |
The performance of the bitmapscan feature is improved. |
||
|
Optimizer |
|
||
|
Fixed issue |
Scaling |
|
|
|
Logical backup |
The extension installation issue that occurs during an upgrade is fixed. |
None |
|
|
Storage engine |
The stability issue, such as a crash occurring when data is written to an append-only or Beam table that has generalized inverted index (GIN) indexes, is fixed. |
||
|
Optimizer |
The execution plan failure in specific partitioned tables is fixed for the Orca optimizer. |
||
|
Execution engine |
Specific executor stability issues are fixed. |
V7.0.6.8
|
Category |
Feature |
Description |
References |
|
New feature |
Query cache |
Query results can be cached to accelerate the response to repeated queries. |
|
|
Optimized feature |
Tiered storage |
Automatic data migration from hot storage to cold storage is optimized to adapt to the Beam storage engine. |
|
|
Minor version update |
The shared system table logic can be modified. |
||
|
Dump |
When the pg_dump tool is used to dump a partitioned table, all partitions of the table are dumped. |
None |
|
|
Stability |
The logic that is used to extend global transaction ID (GXIDs) from 32 bits to 64 bits is optimized. |
None |
|
|
Data masking |
The copy and equal functions can be used for data masking. |
||
|
Optimizer |
|
||
|
Fixed issue |
Storage engine |
|
|
|
Stability |
The issue about residual 2-phase commit transactions in the PostgreSQL community is fixed. |
None |
|
|
Optimizer |
|
||
|
Real-time materialized view |
The following issue is fixed: An error occurs on automatic nesting when an OUTER JOIN operation is performed on a real-time materialized view. |
August 2024 (V7.0.6.7)
|
Category |
Feature |
Description |
References |
|
New feature |
pgsearch extension |
The pgsearch extension is supported to perform full-text search in vector databases. |
None |
|
pg_buffercache extension |
The pg_buffercache extension is supported to check whether a table is cached. |
||
|
Vector algorithms in vector search |
The following distance metrics that can be used together with operator symbols are supported for vector search: L1, Hamming, and Jaccard. The Hierarchical Navigable Small World (HNSW) algorithm is supported. |
||
|
Fine ranking in vector search |
Fine ranking is supported for vector search. |
||
|
Optimized feature |
Vector indexes can be created based only on memory without being written to disks in vector search. |
||
|
More comprehensive logic is supported for modifying system tables if an AnalyticDB for PostgreSQL instance is updated to the latest version. |
|||
|
Subqueries can be pulled up by the optimizer for projection in queries. |
|||
|
A custom format for reading JSON data is supported. |
|||
|
Information about the table access method is included in the output DDL statements when the pg_dump tool is used to dump a table. |
|||
|
Features of resource groups are optimized. |
|||
|
Fixed issue |
Data can be moved from tables that contain column names enclosed in quotation marks ('') to cold storage. |
||
|
The performance and visibility issues of the Beam storage engine are fixed. |
|||
|
The issue that causes startup failures of secondary compute nodes when the gpstart tool is used is fixed. |
|||
|
The following issue is fixed: The iconv tool fails to convert the character set encoding format from GBK into UTF-8 in an Alinux3 environment. |
|||
|
The following issues are fixed: A scale-in operation times out. Data is lost when you perform concurrent rewrite and insert operations on partitioned tables. |
|||
|
The following issue is fixed: Core dumps occur when the Laser engine is executed. |
|||
July 2024 (V7.0.6.5)
|
Category |
Feature |
Description |
References |
|
Optimized feature |
Update of GanosBase to version 6.7 |
AnalyticDB for PostgreSQL GanosBase is updated to version 6.7. GanosBase provides a series of data types, functions, and stored procedures for AnalyticDB for PostgreSQL to store, index, query, analyze, and compute spatio-temporal data in a cost-effective manner. |
|
|
Fixed issue |
The following issue is fixed: After you extend a partitioned table, data errors occur on the table because the values of specific fields are excessively long in length. |
||
|
The following issue is fixed: Standard accounts do not have the permissions to use the auto_partition extension to configure automatic partition management. |
|||
|
The following issue is fixed: When you execute the ALTER TABLE RESET or ALTER TABLE SET statement by using the Beam storage engine, an error occurs on queries that involve table indexes created by using earlier versions of Beam. |
|||
|
The following issue is fixed: An error occurs when you attempt to add a column with a NOT NULL constraint to a Delta table by using the Beam storage engine. |
|||
|
The following issue is fixed: When you perform a query by using CTEs, the ERROR: could not find CTE error message is returned in the execution plan due to pull-up of an CTE. |
|||
|
The following issue is fixed: In scenarios that involve an external data source, core dumps occur when a single session sequentially accesses the two extensions, PostgreSQL FDW and Greenplum FDW. |
|||
June 2024 (V7.0.6.4)
|
Category |
Feature |
Description |
References |
|
New feature |
Security feature |
Row-level permission control on materialized views is supported. |
None |
|
Fixed issue |
The following issue is fixed: Residual fragments are reclaimed by the vacuum fragment auxiliary table of a Beam table after an AnalyticDB for PostgreSQL instance crashes. |
||
|
The following issue is fixed: WAL logs are lost when you use the pg_rewind tool to perform incremental data restoration. |
|||
|
The following issue is fixed: Database accounts that have the RDS_SUPERUSER permission cannot use the auto_partition extension. |
|||
May 2024 (V7.0.6.3)
|
Category |
Feature |
Description |
References |
|
New feature |
Real-time materialized view |
Real-time materialized views are supported. Compared with standard materialized views, real-time materialized views can be automatically refreshed when data changes without the need to execute REFRESH statements. |
|
|
Optimized feature |
Support for writes during the scale-out of the Beam storage engine |
Write operations, such as |
|
|
Fixed issue |
The following issue is fixed: |
||
|
The following issue is fixed: A database account that has the |
|||
|
The following issue is fixed: A mapping logic error occurs or core dumps occur when the CHAR type in the Optimized Row Columnar (ORC) format is mapped to the CHAR type in AnalyticDB for PostgreSQL in scenarios that involve Object Storage Service (OSS) foreign tables. |
|||
April 2024 (V7.0.6.1)
|
Category |
Feature |
Description |
References |
|
|
Fixed issue |
The following issue is fixed: Data loss occurs due to incorrect subtransaction visibility logic when you concurrently write transactions. |
|||
|
The following issue is fixed: Blocked files fail to be cleared when the backup archiving process unexpectedly fails. This issue may block subsequent xlog archiving and recycling processes and cause accumulated local log files. |
||||
|
The following issue is fixed: The |
||||
|
The following issue is fixed: The |
||||
|
The following issue is fixed: The monitoring query tool unexpectedly fails. The underlying implementation is optimized to improve error handling capabilities and stability and prevent failures. |
||||
April 2024 (V7.0.6.0)
|
Category |
Feature |
Description |
References |
|
Optimized feature |
Beam |
|
None |
|
Laser |
Stored procedures, cursors, and the following statements are supported: INSERT, UPDATE, DELETE, CTAS, REFRESH MATERIALIZED VIEW, and COPY. |
None |
|
|
Orca and planner optimizers |
|
None |
|
|
Slow queries |
The CPU utilization, memory usage, and disk file sizes of each query can be viewed at the instance and node levels. |
None |
|
|
Fixed issue |
The following issue is fixed: |
||
|
The following issue is fixed: Data fails to be moved to cold storage when no partitioned table name is specified or the NOT NULL constraint is specified for the parent table. |
|||
|
The following issue is fixed: The |
|||
|
The following issue is fixed: |
|||
|
The following issue is fixed: Temporary files remain in specific scenarios. |
|||
|
The following issue is fixed: DDL operations are blocked during a scale-in activity. |
|||
|
The following issue is fixed: The Query Monitor extension unexpectedly stops working. |
|||
|
The following issue is fixed: Data fails to be read and written when you rebuild indexes during a scale-out activity. |
|||
March 2024 (V7.0.5.2)
|
Category |
Feature |
Description |
References |
|
Fixed issue |
The following issue is fixed: The reloptions attribute of the parent partitioned table is incorrect after you add columns to Beam partitioned tables. |
||
|
The following issue is fixed: Auxiliary tables are inconsistent after you execute an ALTER statement that contains multiple substatements on a Beam partitioned table. |
|||
March 2024 (V7.0.5.1)
|
Category |
Feature |
Description |
References |
|
|
Fixed issue |
The following issue is fixed: An error occurs when you concurrently execute the INSERT ON CONFLICT and DROP TABLE statements. |
|||
|
The following issue is fixed: The |
||||
|
The pg_relation_size compatibility issue in earlier versions is fixed. |
||||
|
The following issue is fixed: |
||||
|
The following issue is fixed: |
||||
February 2024 (V7.0.5.0)
|
Category |
Feature |
Description |
References |
|
|
New feature |
Elastic scaling |
The elastic scaling feature for adding compute nodes is supported. When you add compute nodes, you can read, write, and update tables without business interruption. |
||
|
Fixed issue |
The following issue is fixed: Incorrect execution plans are generated by the Orca optimizer when the JOIN ON clause contains cross-level subqueries. |
|||
|
The following issue is fixed: Core dumps occur when you use the Orca optimizer to perform the UNION ALL and SORT operations. |
||||
|
The following issue is fixed: An error occurs when you execute the COPY ON CONFLICT DO NOTHING statement due to data conflicts. |
||||
|
The following issue is fixed: Beam flush operations are frequently canceled, which may cause performance degradation. |
||||
|
The dictionary memory issue of the Beam storage engine is fixed. |
||||
|
The following issue is fixed: The Query Monitor extension unexpectedly stops working. |
||||
|
The following issue is fixed: System tables may contain residual data when you execute the DROP FOREIGN SERVER statement on foreign tables. |
||||
|
The security issue is fixed. Security hardening is performed. |
||||
|
The compatibility issue that occurs when you execute the Laser Scan operator on ctid columns is fixed. |
||||