:[EOS/Discontinuation] ApsaraDB RDS for PPAS are no longer available for purchase from May 16, 2022

If you are using an ApsaraDB RDS for PPAS instance, you can go to the Data Transmission Service (DTS) console to migrate data from your ApsaraDB RDS for PPAS instance to a PolarDB for PostgreSQL (Compatible with Oracle) cluster. For more information, see Migrate data from an ApsaraDB RDS for PPAS instance to a PolarDB for PostgreSQL (Compatible with Oracle) cluster.

When you migrate data from an ApsaraDB RDS for PPAS instance to a PolarDB for PostgreSQL (Compatible with Oracle) cluster, take note of the following items:

• Make sure that the specifications of the PolarDB for PostgreSQL (Compatible with Oracle) cluster are higher than or equal to the specifications of your ApsaraDB RDS for PPAS instance. Otherwise, slow SQL queries or out of memory (OOM) error may occur because of insufficient CPU or memory resources after you migrate the data to the PolarDB for PostgreSQL (Compatible with Oracle) cluster. For more information about recommended specifications of PolarDB for PostgreSQL (Compatible with Oracle) clusters, see Mapping between specifications of ApsaraDB RDS for PPAS instances and recommended specifications of PolarDB for PostgreSQL (Compatible with Oracle) clusters.

• If you have special requirements for the number of connections and IOPS after migration, select specifications based on your business requirements. For more information, see Specifications of PolarDB for PostgreSQL (Compatible with Oracle) cluster.

• If you use a cluster endpoint to connect your application to a PolarDB for PostgreSQL (Compatible with Oracle) cluster, read/write splitting is enabled. Then, the system forwards read requests to read-only PolarDB for PostgreSQL (Compatible with Oracle) nodes. This reduces the loads on the primary PolarDB for PostgreSQL (Compatible with Oracle) node. For more information about how to obtain a cluster endpoint, see View or apply for an endpoint.