AnalyticDB for PostgreSQL V7.0
AnalyticDB for PostgreSQL V7.0 is a cloud-native data warehouse built on PostgreSQL 12. This version offers significant improvements in features, performance, enterprise-grade capabilities, and security.
Notes
V7.0 is available only for AnalyticDB for PostgreSQL instances in Elastic Storage Mode.
Performance test for V7.0
The following figure shows the performance test results for an AnalyticDB for PostgreSQL V7.0 instance, comparing the proprietary Laser engine with the native Greenplum compute engine. The test results demonstrate that the Laser engine delivers a significant performance improvement, with a total execution time approximately one-fifth that of the native engine. For more information, see AnalyticDB for PostgreSQL V7.0 TPC-H performance test.

New features in V7.0
|
Category |
Feature |
Description |
|
- |
Codebase |
The AnalyticDB for PostgreSQL kernel is based on PostgreSQL 12. |
|
Security |
You can use a row security policy to control which rows in a table a user can access. |
|
|
Supports the SCRAM-SHA-256 authentication method, which provides higher security than the MD5 method. |
||
|
You can set column-level data masking rules and assign masking policies to specific users. This feature protects sensitive data by dynamically masking it based on the user who is viewing it. |
||
|
Enterprise-grade capabilities |
Supports the |
|
|
Supports generated columns, which are special columns computed from other columns in a table. |
||
|
Features and performance |
Table partition |
Supports hash partitions in addition to range and list partitions. The syntax for hash partitions is compatible with PostgreSQL. |
|
Supports all SQL:2011 standard functions. |
||
|
You can specify the columns for which to collect statistics. This improves the accuracy of cost estimation and query performance. |
||
|
JSON |
More JSON functions are supported. |
|
|
Covering indexes |
You can include additional columns in an index to expand its coverage and improve query performance. |
|
|
Supports just-in-time (JIT) compilation to improve query performance. |
||
|
Supports aggregate function reuse. When multiple reusable aggregate functions are used on the same column, the aggregation is performed only once. |
||
|
Indexes |
Hash, BRIN, and Bloom indexes are added. B-tree, GIN, GiST, and Bitmap indexes are optimized. |
Kernel features
AnalyticDB for PostgreSQL V7.0 is compatible with most PostgreSQL features, so you can use standard PostgreSQL syntax in most cases. The following table describes the feature support in V7.0.
|
Category |
Feature |
Supported |
|
Basic features |
ALTER TABLE |
Yes |
|
Indexes |
Yes |
|
|
PRIMARY KEY |
Yes |
|
|
UNIQUE CONSTRAINT |
Yes |
|
|
INSERT ON CONFLICT (upsert) |
Yes |
|
|
Unlogged tables |
Yes |
|
|
Triggers |
No |
|
|
Heap, AO, and AOCS tables |
Yes |
|
|
Custom data types |
Yes |
|
|
Explicit cursors |
Yes |
|
|
Compute engines |
Orca optimizer |
Yes |
|
Laser engine |
Yes |
|
|
Transaction capabilities |
Subtransactions |
Yes |
|
Transaction isolation levels |
Supports Read Committed (RC) and Repeatable Read (RR) isolation levels. |
|
|
Advanced features |
Backup and restoration |
Yes |
|
Materialized view |
Yes |
|
|
AUTO VACUUM |
Partially supported (only for system tables) |
|
|
AUTO ANALYZE |
Yes |
|
|
Elastic scale-out |
Yes |
|
|
Elastic scale-in |
No |
|
|
GIS/Ganos |
Yes |
|
|
Data sharing |
No |
Console features
The following table describes the console features available in V7.0.
|
Category |
Feature |
Supported |
|
Instance management |
Basic instance information |
Yes |
|
Log on to databases by using DMS |
Yes |
|
|
Instance creation |
Yes |
|
|
Instance release |
Yes |
|
|
Instance restart |
Yes |
|
|
Instance configuration upgrade or downgrade |
Yes |
|
|
coordinator node scaling |
Not supported |
|
|
Instance scale-out |
Yes |
|
|
Instance scale-in |
Not supported |
|
|
Minor version update |
Yes |
|
|
Account management |
Account creation |
Yes |
|
Password reset |
Yes |
|
|
Database connection |
Basic connection information (such as endpoints and ports) |
Yes |
|
Public endpoint creation |
Yes |
|
|
Monitoring and alerting |
Monitoring |
Yes |
|
Alert rules |
Yes |
|
|
Data security |
Whitelists |
Yes |
|
SQL audit |
Yes |
|
|
SSL |
Yes |
|
|
Backup and restoration |
Yes |
|
|
Configuration |
Parameter settings |
Yes |
Data migration
The following table describes the data migration operations available in V7.0.
|
Migration type |
Documentation |
Supported |
|
Data writing |
Yes |
|
|
Yes |
||
|
Yes |
||
|
Table-level migration |
Yes |
|
|
Yes |
||
|
Yes |
||
|
Yes |
||
|
Yes |
||
|
Use external tables for federated queries of Hadoop data sources |
Yes |
|
|
Warehouse-level migration |
Migrate data from a self-managed Greenplum database to AnalyticDB for PostgreSQL |
Yes |
|
Not supported You can import data by using external tables. |
||
|
Manually migrate data from Amazon Redshift to AnalyticDB for PostgreSQL |
Not supported You can import data by using external tables. |
|
|
Migrate Oracle applications to the cloud-native data warehouse AnalyticDB for PostgreSQL |
Not supported You can import data by using external tables. |
|
|
Not supported You can import data by using external tables. |
Product edition selection
AnalyticDB for PostgreSQL V7.0 is available in Standard Edition and Economy Edition, with Standard Edition as the default. If your business has moderate performance requirements and you want a cost-effective solution, see V7.0 Economy Edition.
FAQ
Q: Can I upgrade an elastic storage mode instance from V6.0 to V7.0?
A: You cannot directly upgrade a V6.0 instance to V7.0. To perform the upgrade, Submit a ticket and contact technical support.