Docs

Database Transmission Service

PostgreSQL connected over public network as the source

Migrating to PostgreSQL connected over public network

This topic introduces how to create a migration task from public network PostgreSQL to public network PostgreSQL in the Database Transmission Service (DTS) console.

Prerequisites

A self-managed instance and its database for PostgreSQL have been set up in the public network environment.

If you need to migrate data from the PostgreSQL engine instance managed in the AI native database management platform (AIDAP):

AIDAP-managed Supabase engine instance:

Create workspace. For detailed steps, refer to Create workspace.

Create database branch. For detailed steps, refer to Creating branch.

Obtain the connection information required by DTS, such as host address, port, account number, and password. refer to Obtaining the connection information of computing power for detailed steps.

AIDAP hosted standard PostgreSQL engine instance:

Create workspace. For detailed steps, refer to Create workspace.

Create database branch. For detailed steps, refer to Creating branch.

Obtain the connection information required by DTS, such as host address, port, account number, and password. refer to Obtaining the connection information of computing power for detailed steps.

Confirm the network connectivity and service availability of the source and target databases before creating a data migration task.

You can also prepare the migration objects in the source and target databases according to the instructions in the Pre-check items. For more information, refer to Pre-check items (PostgreSQL).

On the Create migration task page, locate the Configure source and target database wizard, and configure the following parameters.

Type	Name	Description
Basic information	Task name	Optional. Customize the task name. The length must be within 256 characters. tip If not set, the system generates a task named with dts- by default.
Basic information		Link specification	Select the link specification for the migration task. Compact, Medium and Standard are supported. tip The link specification can not be modified after the task is successfully created. For details on the link specifications, refer to Product specifications.
Source database configuration	Select an existing data source	You can choose whether to use an existing instance as needed: Use existing instances: Click Select an existing data source, then in the Select data source control panel, choose the target region from the Region drop-down list, and select the target data source. Supports selecting data sources by data source name and ID. For methods to create data sources, refer to Data source management. Do not use existing instances: If not using an existing instance, you need to configure the following database instance information.
		Instance type	Select PostgreSQL.
		Access method	Select PostgreSQL connected over public network. tip When migrating PostgreSQL connected over public network instances, add the DTS IP segment access permission in the source end's allowlist or security group policy in advance. Click View DTS CIDR blocks to view and copy the CIDR block.
		Region	Select the region where the target instance is located.
		Host address	Enter the host address of the target self-managed instance.
		Port	Enter the port number of the target self-managed instance.
		Database name	Enter the database name.
		Database account	Enter the database account of the target instance.
		Database password	Enter the password corresponding to the database account of the target instance.
		Connection method	Select whether to enable the encryption protocol as needed to establish a secure connection between the client and the database instance, preventing data interception, tampering, or forgery during transmission. Option: Unencrypted connection: suitable for self-built PostgreSQL instances deployed in public network environments. This method carries security risks and is recommended only for testing environments or controlled networks. SSL secure connection: Recommended for production environments, supports connections to PostgreSQL instances hosted on the AI native database management platform (AIDAP), and can also be used for self-built instances configured with SSL.
		Test connection	Click Test connection to verify the connection to the instance. If the test connection fails, modify the configuration based on the failure prompt, and then click Test connection again to verify the connection. The specific prompts are as follows: Connection authentication failed. Check the network: When this error prompt appears, confirm network connectivity. Connection authentication failed. Check the username and password: When this error prompt appears, verify your username and password. Invalid IP address: When this error prompt appears, verify the accuracy of the IP address.
Target database configuration	Select an existing data source	You can choose whether to use an existing instance as needed: Use existing instances: Click Select an existing data source, then in the Select data source control panel, choose the target region from the Region drop-down list, and select the target data source. Supports selecting data sources by data source name and ID. For methods to create data sources, refer to Data source management. Do not use existing instances: If not using an existing instance, you need to configure the following database instance information.
		Instance type	Select PostgreSQL.
		Access method	Select PostgreSQL connected over public network. tip When migrating PostgreSQL connected over public network instances, add the DTS IP segment access permission in the source end's allowlist or security group policy in advance. Click View DTS CIDR blocks to view and copy the CIDR block.
		Region	Select the region where the target instance is located.
		Host address	Enter the host address of the target self-managed instance.
		Port	Enter the port number of the target self-managed instance.
		Database name	Enter the database name.
		Database account	Enter the database account of the target instance.
		Database password	Enter the password corresponding to the database account of the target instance.
		Connection method	Select whether to enable the encryption protocol as needed to establish a secure connection between the client and the database instance, preventing data interception, tampering, or forgery during transmission. Option: Unencrypted connection: suitable for self-built PostgreSQL instances deployed in public network environments. This method carries security risks and is recommended only for testing environments or controlled networks. SSL secure connection: Recommended for production environments, supports connections to PostgreSQL instances hosted on the AI native database management platform (AIDAP), and can also be used for self-built instances configured with SSL.
		Test connection	Click Test connection to verify the connection to the instance. If the test connection fails, modify the configuration based on the failure prompt, and then click Test connection again to verify the connection. The specific prompts are as follows: Connection authentication failed. Check the network: When this error prompt appears, confirm network connectivity. Connection authentication failed. Check the username and password: When this error prompt appears, verify your username and password. Invalid IP address: When this error prompt appears, verify the accuracy of the IP address.
None	Project	Optional. Select the affiliated project for the task from the drop-down list. By default, it is under default (default project). You can also click Create new project to create a new project. For more information, refer to Creating a new project. tip To grant sub-user privileges to access resources in a specific project, refer to Modifying project privileges. After a task is created successfully, if you need to change its affiliated project, you can move the resource to another project. A project is a virtual concept that includes a set of resources, users, and roles. A project allows for a unified view and management of a set of resources, and controls the permissions of users and roles within the project for those resources.
		Tag	(Optional) Click Add tag to add a tag to the instance. Tags can help you categorize cloud resources, control access to them, and allocate bills and costs. A tag is a key-value pair that identifies a cloud resource. You can use tags to categorize resources with the same characteristics from different dimensions, such as purpose or owner, making it easier to filter, aggregate, and manage your cloud resources. For more details about tags, refer to Tag overview. The rules for tag key-value pairs are as follows: Key Supports any language, characters, numbers, spaces, or symbols (_.:/=+-@). Case-sensitive, and the length is 1 to 128 characters. In UTF-8 encoded Unicode format. Keys cannot start with any form of volc:, such as Volc: or VOLC:. (Optional) Value Supports any language, character, digit, space, or symbol (_.:/=+-@). Case-sensitive, and the length is 0 to 256 characters. In UTF-8 encoded Unicode format. tip Support fuzzy search for selecting existing tag keys and tag values. A maximum of 20 tags can be associated with a task in a single operation. A maximum of 50 tags can be associated with a single task. For a single resource, tag keys must be unique, and each tag key can have only one value.
		Billing method	Currently, only Pay-as-you-go is supported. No selection is required. tip For detailed billing information, refer to Billing instructions.

Click Next step: configure migration object.

On the Configure migration object wizard page, configure the related parameter information as shown in the table below.

tip

If you do not need to start the migration task immediately, click Save in the lower-right corner of the page after configuring the migration object.

After saving, you will be redirected to the Migration task list page. The task status will be To be started, and you can configure the migration task at a suitable time. For configuration methods, refer to Configuring a migration task.

Name			Description
Migration type			Select the migration type as needed. Currently supported types are Schema migration, Full migration, and Incremental migration. including: If only full migration is required, select both Schema migration and Full migration. If online migration is needed, select Schema migration, Full migration, and Incremental migration simultaneously. tip When Incremental migration is not selected, do not write new data to the source database instance during data migration to ensure data consistency. To ensure real-time data consistency, it is recommended to select schema migration, full data migration, and incremental data migration.
Migration object			In the Migration object area, check the objects to migrate. You can confirm the objects to migrate in the Selected object area. tip The migration object granularity can be either database or table. If tables are selected as the migration objects, other objects such as views, triggers, functions, or stored procedures will not be migrated to the target database. To ensure data migration performance and task stability, TRIGGER, RULE, FOREIGN KEY, SEQUENCE, and other objects of RDS for PostgreSQL will migrate only after the incremental migration completes. The search box in the Selected object area supports fuzzy search to batch delete unwanted targets.
Advanced configuration	Enable millisecond-level delay monitoring	When Migration type selects Incremental migration, millisecond-level latency monitoring is enabled by default. When enabled, it provides high-precision, full-link, proactive end-to-end latency measurement, effectively improving monitoring stability and sensitivity to abnormal conditions such as network interruptions and idle disconnections. When enabled, DTS writes heartbeat data to the source database, requiring the source end account to have SELECT, INSERT, and UPDATE permissions. For more information about the heartbeat table, refer to Manual creation of the heartbeat table.
		Skip post-schema migration	When selecting schema migration in migration type, DTS automatically migrates post-schema after the incremental migration ends. You may also skip post-schema migration, meaning DTS will not migrate post-schema objects. RDS for PostgreSQL database post-schema migration objects include ordinary trigger, event trigger, RULE, exclusive constraint, foreign key constraint, check constraint, Domain constraint, and Sequence value setting. Yes: Represent skipping post-schema migration, i.e., DTS does not migrate post-schema objects. No: Represent not skipping post-schema migration, i.e., DTS migrates post-schema objects. tip The configuration of whether to skip post-schema migration is only supported when the migration type includes Schema migration.
		Error retry time	If a migration task fails due to a disconnection between the source and target databases, the system immediately retries connecting to them multiple times within the specified time. Value range: 600 - 86400, in seconds (s). The default value is 600 seconds.
		Full migration rate	Set the full migration rate as needed. To prevent high migration rates from affecting the source database's performance, adjust the following parameters based on the read and write pressure of the source and target databases accordingly: Rows migrated per second: Enable and set the rows migrated per second as needed. The default value is 100,000, and the value range is 1 to 100,000. Data volume migrated per second: Enable and set the data volume migrated per second as needed. The default value is 25,000. The value range is 1 to 25,000, and the unit is KB. Migration task concurrency: Set the concurrency of migration tasks as needed. The default value is 8, the value range is 1-64. tip You can configure this parameter when selecting Migration type as Full migration. An excessively high migration rate may affect the performance of the source database. Adjust appropriately based on the read and write pressure of the source and target databases.

Last updated: 2026.09.02 16:10:47