tencent cloud

All product documents
TencentDB for PostgreSQL
DocumentationTencentDB for PostgreSQLOperation GuideData MigrationDTS-Based Logical MigrationInstructions
Instructions
Download PDF
Last updated: 2024-11-04 10:04:48
Instructions
Last updated: 2024-11-04 10:04:48
Download PDF
Category
Description
Supported versions
1. Source database
Self-built databases PostgreSQL 10-16
Third-party cloud vendors 10-16
Alibaba Cloud RDS PostgreSQL
AWS RDS PostgreSQL
Huawei Cloud RDS for PostgreSQL
TencentDB for PostgreSQL 10-16 (Migration within the same root account/Migration between different root accounts)
2. Target database
TencentDB for PostgreSQL 10-16
Impact on the source database
1. During full data migration, Data Transfer Service (DTS) consumes certain source instance resources, which may increase the load and pressure of the source database. If your database configuration is low, we recommend you perform the migration during off-peak hours.
2. During the actual migration process, the rate can be influenced by factors such as the read performance of the source instance, network bandwidth between the source and target instances, and the specifications and performance of the target instance. The migration concurrency is determined by the number of cores of the target instance. For example, if the target instance has 2 cores, the concurrency will be 2.
Migration object
Interrelated data objects need to be migrated together; otherwise, the migration will fail. Common association relationships include: views referencing tables, views referencing views, storage procedures/functions/triggers referencing views/tables, and table association through primary and foreign keys.
Source database requirements
When Full + Incremental Migration is selected as the migration type, the tables in the source database must have primary keys; otherwise, data inconsistency between the source and target databases may occur. For tables without primary keys, it is recommended to select Full Migration.
Target database requirements
If the entire instance is to be migrated, the target database must not contain users and roles with the same names as those in the source database.
Network description
1. When a migration task is configured, the source database address must use the IP address and port that can directly connect to the PostgreSQL instance. Do not use the IP address and port of proxies like pgpool.
2. To ensure migration efficiency, cross-region migration is not supported for self-built instances on Cloud Virtual Machine (CVM). If cross-region migration is needed, choose the public network access method.
Operation limits
1. During the structural migration, full migration, and incremental migration, do not perform DDL operations or Large Object operations; otherwise, data inconsistency will occur.
2. Do not modify or delete user information (including the username, password, and permissions) and port numbers in the source and target databases during migration.
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No

Feedback

Contact Us

Contact our sales team or business advisors to help your business.

Contact Us
Technical Support

Open a ticket if you're looking for further assistance. Our Ticket is 7x24 avaliable.

Submit a Ticket
7x24 Phone Support
Hong Kong, China
+852 800 906 020 (Toll Free)
United States
+1 844 606 0804 (Toll Free)
United Kingdom
+44 808 196 4551 (Toll Free)
Canada
+1 888 605 7930 (Toll Free)
Australia
+61 1300 986 386 (Toll Free)
EdgeOne hotline
+852 300 80699
More local hotlines coming soon