2022

更新时间:
复制 MD 格式

This topic describes the 2022 engine release notes for AnalyticDB for PostgreSQL in Serverless mode.

To update your instances to the latest minor engine version, see Update the minor engine version.

July 5, 2022 (V1.0.2.0)

New features

Data sharing

Data sharing now supports replicated tables, random tables, and partitioned tables.

For setup and configuration details, see Enable or disable data sharing for instances.

New data types

The VARCHAR and TIMESTAMP data types are now supported. For details, see Serverless mode.

Fixed issues

  • Fixed an issue where 2PC transactions could not be performed while materialized views were being refreshed.

  • Fixed an issue where DataShare could not be created in Multi-Master mode.

  • Fixed an issue that could cause destroy_dadi_fs syntax errors.

  • Fixed an issue where ANALYZE statements on tables with large numbers of small Object Storage Service (OSS) objects could result in errors.

  • Fixed an issue where cross-database queries failed when a WHERE clause referenced a fully qualified column path in the format <share_name>.<schema_name>.<table_name>.<column_name>.

  • Fixed a false positive that incorrectly flagged subtransactions as unsupported after data sharing was enabled.

March 3, 2022 (V1.0.0.0)

New features

Data sharing

Data sharing lets you query data across instances without exporting or importing data, reducing the overhead of cross-instance access compared to traditional data warehouse approaches.

To enable data sharing and set up the required SQL operations, see Enable or disable data sharing for instances and SQL operations for data sharing.

Backup and restoration

Backup and restoration is now available to protect your data. By default, backup data is retained for seven days. For configuration details, see Backup and restoration (Serverless mode).

Optimized features

Laser computing engine

The Laser computing engine is now supported. The engine is disabled by default. For usage details, see Use the Laser computing engine.

Fixed issues

  • Optimized the limit on the amount of data merged during VACUUM operations to prevent out of memory (OOM) issues.