ApsaraDB RDS:Create an ApsaraDB RDS for PostgreSQL instance

• Select a zone.

  • No significant differences exist between the zones in the same region.

  • If the RDS instance resides in the same zone as the ECS instance on which your application is deployed, these instances can deliver optimal performance. If the RDS instance and the ECS instance reside in different zones in the same region, the performance of the RDS instance and the ECS instance is slightly lower than the performance of the RDS instance and the ECS instance that reside in the same zone.

• Configure the Deployment Method parameter.

  • Multi-zone Deployment: This is the recommended deployment method. The primary RDS instance and the secondary RDS instance reside in different zones of a region to provide cross-zone disaster recovery.

    If you set the Deployment Method parameter to Multi-zone Deployment, you must configure the Zone of Primary Node and Zone of Secondary Node parameters.

  • Single-zone Deployment: The RDS instance and its secondary RDS instance reside in the same zone.

    If you set the Edition parameter to Basic, only the Single-zone Deployment method is available.

  Note

  • If you use an RDS edition in which primary and secondary RDS instances are provisioned, such as RDS High-availability Edition, we recommend that you select Multi-zone Deployment to implement cross-zone disaster recovery.

  • If Sold Out appears in the upper-right corner of a zone name, this zone does not have sufficient resources. In this case, you must switch to another zone.

1. Configure the Category parameter. You can select General-purpose or Dedicated.

   Category	Description	Benefit
   General-purpose	A general-purpose RDS instance exclusively occupies the allocated memory and I/O resources. A general-purpose RDS instance shares CPU and storage resources with the other general-purpose RDS instances that are deployed on the same host.	General-purpose RDS instances are cost-effective.
   Dedicated	A dedicated RDS instance exclusively occupies the allocated CPU, memory, storage, and I/O resources. Note The dedicated host instance family is the highest configuration of the dedicated instance family. A dedicated host RDS instance exclusively occupies all the CPU, memory, storage, and I/O resources of the host on which the RDS instance is deployed.	A dedicated RDS instance delivers higher performance and higher stability. Note An RDS instance that runs RDS Basic Edition does not support the dedicated instance family.

2. Configure detailed specifications, such as the number of CPU cores, memory capacity, maximum number of connections, and maximum IOPS.

   • For a test environment, we recommend that you select an instance type that provides two or more CPU cores.

   • For a production environment, we recommend that you select an instance type that provides four or more CPU cores.

   Note

   For more information, see Primary ApsaraDB RDS instance types.

The value range of the storage capacity varies based on the instance type and storage type that you select. You can adjust the storage capacity at a step size of 5 GB.

If you set the Storage Type parameter to ESSD PL1, ESSD PL2, ESSD PL3, or General ESSD, you can specify a parameter template when you create the RDS instance. If you do not specify a parameter template, the default system parameter template is used. You can select a custom parameter template. For more information about how to create a custom parameter template, see Use a parameter template to configure the parameters of ApsaraDB RDS for PostgreSQL instances.

• If you set the Storage Type parameter to ESSD PL1, ESSD PL2, ESSD PL3, or General ESSD, you can specify a policy to update the minor engine version of the RDS instance when you create the RDS instance. The default value of the Minor Version Upgrade Policy parameter is Automatic Upgrade. If the minor engine version of your RDS instance is outdated, the system automatically delivers active O&M tasks to update the minor engine version from time to time. The system notifies you of the tasks by using methods such as emails and internal messages. The system automatically updates the minor engine version of your RDS instance within the maintenance window that you specified. For more information, see Set the maintenance window of an ApsaraDB RDS for PostgreSQL instance.

  Note

  After the RDS instance is created, you can go to the Basic Information page of the RDS instance to modify the value of the Minor Version Upgrade Policy parameter. For more information, see Update the minor engine version of an ApsaraDB RDS for PostgreSQL instance.

• ApsaraDB RDS for PostgreSQL allows you to specify a minor engine version when you create the RDS instance. If you do not specify a minor engine version, the latest version of AliPG is used by default.

  Example:

  rds_postgres_1400_20220830_14.4

  The following list describes the fields in the preceding example:

  • rds: the RDS instance

  • postgres: the PostgreSQL database

  • 1400: the major version of PostgreSQL, which is 14 in this example

  • 20220830: the version of AliPG, which can be specified. The available minor engine versions are displayed on the ApsaraDB RDS buy page. For more information, see Release notes for AliPG.

  • 14.4: the minor version of PostgreSQL

  Note

  If you select Enable Babelfish in the Basic Configurations step, the minor engine version of the RDS instance is displayed in the following format:

  rds_postgres_1400_20220630_babelfish_14.4

  • If your RDS instance runs PostgreSQL 13, you can select the AliPG version of 20220228 or later.

  • If your RDS instance runs PostgreSQL 14, you can select the AliPG version of 20220630 or later.

The resource group to which the RDS instance belongs. You can retain the default resource group or select a custom resource group based on your business requirements.

The following parameters take effect only when you select Enable Babelfish in the Basic Configurations step.

• Babelfish Migration Mode: the migration mode for the RDS instance for which Babelfish is enabled

  • single-db: You can create only one SQL Server database on an RDS instance for which Babelfish is enabled and create a standard PostgreSQL schema for the database.

  • multi-db: You can create multiple SQL Server databases and create different PostgreSQL schemas for the databases. You must name the schemas in the <Database name>_<Schema name> format to prevent name conflicts.

  Note

  For more information, see Migration modes.

• Initial Account: the username of the Babelfish management account that is used to connect to the RDS instance over the TDS port

  Important

  This account is a privileged account and cannot be deleted after it is created.

• Password: the password of the Babelfish management account

  Note

  You can change the password after the RDS instance is created. For more information, see Reset the password of an account on an ApsaraDB RDS for PostgreSQL instance.

• You can configure the time zone when you create a primary RDS instance. You cannot configure the time zone when you create a read-only RDS instance. A read-only RDS instance inherits the time zone of its primary RDS instance.

• You can configure this parameter only when the RDS instance uses cloud disks.

• The time zone is not in UTC. For more information, see Common time zones for ApsaraDB RDS for MySQL instances and ApsaraDB RDS for PostgreSQL instances.

• If you do not specify this parameter, the system assigns the default time zone of the region in which the RDS instance resides to the RDS instance. For more information, see Default time zones for ApsaraDB RDS for PostgreSQL instances.

If this is the first time you create an RDS instance after October 10, 2022, you must create the AliyunServiceRoleForRdsPgsqlOnEcs service-linked role (SLR) for ApsaraDB RDS for PostgreSQL. This way, your RDS instance can mount Elastic Network Interfaces (ENIs) and establish network connections.

You can create a privileged account when you create an RDS instance. If you select Later, you can create a privileged account after the RDS instance is created.

Go to the Instances page. In the top navigation bar, select the region in which the RDS instance resides. Then, find the RDS instance based on the Creation Time parameter.