||Query Profiling Statistics
||The query profiling statistics feature is supported to automatically collect and record
statistics of AnalyticDB for PostgreSQL during query execution. Query statistics can be displayed in system views.
||Query profiling statistics
|Dynamic Join Filter
||The dynamic join filter feature is supported. This feature can be used before a hash
join to filter out the data that does not match the hash join from the left table
by using the dynamically collected join key of the right table. This way, the disk
reading, networking, and CPU computing overheads are reduced to improve the hash join
||Dynamic join filter
|Data synchronization to data warehouses
||The data synchronization feature is supported to synchronize data from ApsaraDB RDS
for PostgreSQL to AnalyticDB for PostgreSQL.
|Support for Realtime Compute for Apache Flink
||Realtime Compute for Apache Flink can be used to write data to or read data from AnalyticDB for PostgreSQL based on the latest version of Flink AnalyticDB for PostgreSQL connector.
||Error message for overlong fields
||An error message can be returned if the length of a written field exceeds the specified
value when data is updated or inserted.
||The index scan tuple statistics feature is supported for bitmap scans. The number
of times for which indexes are used and the number of rows scanned can be returned
if the execution plan of an SQL statement contains bitmap indexes.
||The JIT cache feature is supported for partitioned tables to prevent repeated compilation.
If more than 100 partitioned tables are involved, a query can be implemented within
||Define table partitioning
|Laser computing engine
||The MergeAppend operator is supported for the Laser computing engine. If all subqueries
are ordered and the ultimate results need to be sorted based on the same sort key,
the MergeAppend operator can return a combination of ordered subquery results by using
the heapsort algorithm.
||Use the Laser computing engine
|Object Storage Service (OSS) foreign table
||Data of OSS foreign tables can be read and written in the Avro format.
||Use OSS foreign tables to access OSS data
|Backup and restoration
||The parallel archiving feature is supported for backup and restoration to speed up
||The issue that may cause redistribution in a table that has a distribution key of
the VARCHAR or TEXT type is fixed. Redistribution may be caused after operations such
as UNION ALL are performed because the distribution key is missing.
|The tuplestore backward scanning feature is supported to prevent
Backward scanning of tuplestores are not supported at this time errors.
|The issue that may cause DDL operation failures on secondary coordinator nodes during
a switchover between the primary and standby coordinator nodes is fixed.