ApsaraDB RDS:[New features/New specifications] Zero-ETL is supported for ApsaraDB RDS for PostgreSQL

Introduction

ApsaraDB RDS provides the zero-ETL feature to synchronize data from an ApsaraDB RDS for PostgreSQL instance to an AnalyticDB for PostgreSQL instance. You do not need to create or maintain data synchronization tasks, and you are not charged for data synchronization tasks. This reduces data transmission costs and O&M costs.

Benefits

• Ease of use: You do not need to create or maintain complex data pipelines to perform extract, transform, and load (ETL) operations. You need to only select the source and destination instances to create real-time data synchronization tasks. This reduces the challenges of building and managing data pipelines and allows you to focus on application development.

• Zero cost: You can create zero-ETL tasks to synchronize data to a data warehouse free of charge for data analysis.

• Multi-source aggregation: You can create a zero-ETL task to synchronize data from multiple ApsaraDB RDS for PostgreSQL instances to an AnalyticDB for PostgreSQL instance in real time to build a global analysis perspective.

Prerequisites

• An AnalyticDB for PostgreSQL instance is created. For more information, see Create an instance.

• The ApsaraDB RDS for PostgreSQL instance and the AnalyticDB for PostgreSQL instance reside in the same region.

• A database is created in the AnalyticDB for PostgreSQL instance to receive data. For more information, see Manage databases.

• The privileged account of the ApsaraDB RDS for PostgreSQL instance is obtained and is specified as the owner of the destination database. The owner is an authorized account. For more information, see Create an account.

• The database account of the AnalyticDB for PostgreSQL instance is obtained. For more information, see Create a database account.

  Note

  You can also use the initial account or an account that has the SUPERUSER permission.

• The wal_level parameter of the ApsaraDB RDS for PostgreSQL instance is set to logical. For more information about how to modify parameters, see Modify the parameters of an ApsaraDB RDS for PostgreSQL instance.

• The logical replication failover slot feature is enabled for the ApsaraDB RDS for PostgreSQL instance. By default, the feature is enabled for the ApsaraDB RDS for PostgreSQL instance. For more information about how to check the status of the feature, see Logical Replication Slot Failover.

  Note

  The feature prevents interruptions to logical subscriptions during the primary/secondary switchover and ensures that the synchronization task runs as expected.

Effective date

June 30, 2024

Billing rules

You can use the zero-ETL feature to synchronize data free of charge.

Supported regions and synchronization links

• Regions: China (Beijing), China (Hangzhou), China (Shanghai), and China (Shenzhen)

  Note

  The feature is rolled out for RDS instances in regions in phases. The information in the ApsaraDB RDS console shall prevail.

• Synchronization links:

  ApsaraDB RDS for PostgreSQL to AnalyticDB for PostgreSQL

References

Use the zero-ETL feature