Help Center/ Data Replication Service/ Real-Time Synchronization/ To the Cloud/ From PostgreSQL to GaussDB Primary/Standby
Updated on 2023-04-26 GMT+08:00

From PostgreSQL to GaussDB Primary/Standby

Supported Source and Destination Databases

Table 1 Supported databases

Source DB

Destination DB

  • On-premises database (PostgreSQL 9.4, 9.5, 9.6, 10, 11, 12, 13 and 14)
  • ECS database (PostgreSQL 9.4, 9.5, 9.6, 10, 11, 12, 13 and 14)
  • Other cloud database (PostgreSQL 9.4, 9.5, 9.6, 10, 11, 12, 13 and 14)
  • RDS for PostgreSQL (9.5, 9.6, 10, 11, 12, 13, 14)

GaussDB primary/standby

Supported Synchronization Objects

Table 2 lists the objects that can be synchronized in different scenarios. DRS will automatically check the objects you selected before the synchronization.

Table 2 Supported synchronization objects

Type

Precautions

Objects

  • Instance-level synchronization is not supported.

    Only one database can be synchronized at a time. To synchronize multiple databases, create multiple DRS tasks.

  • Supported field types:
    • tinyint, smallint, int, bigint, numeric, decimal, char, bpchar, varchar, text, date, time, timetz, timestamp, timestamptz, and interval
    • XML, line, domain, and self-built data type synchronization is not supported.
  • Scope of full synchronization
    • Supported: schemas, tables, primary keys and unique constraints, table data, and sequences
    • Not supported: system schemas and system catalogs (The following schemas are system schemas in the destination database and cannot be synchronized: "pg_toast", "cstore", "snapshot", "sys", "dbms_job", "dbms_perf", "pg_catalog", "information_schema", "utl_file", "dbms_output", "dbms_random", "utl_raw", "dbms_sql", "dbms_lob", "dbe_perf", "pkg_service", "pkg_util", "dbe_file", "dbe_random", "dbe_output", "dbe_raw", "dbe_sql", "dbe_lob", "dbe_task", "blockchain", "db4ai", "dbe_pldebugger", "sqladvisor", "dbe_application_info", "dbe_match", "dbe_pldeveloper", "dbe_scheduler", "dbe_session", "dbe_utility", "dbe_sql_util").
    NOTE:

    The restrictions on the objects that can be synchronized are as follows:

    • Object name: The database name cannot contain +" %?\<>, the schema name and table name cannot contain ".'<>, and the column name cannot contain double quotation marks (") and single quotation marks (').
    • Table: Temporary tables are not synchronized. Only table-level synchronization is supported. Constraints on tables can be synchronized together. Common indexes, rules, and triggers of tables cannot be synchronized. Only objects in the primary table can be synchronized. All data in the partition table will be written to the primary table.
    • Schema: Permissions of the public schema are not synchronized. During table-level synchronization, the permissions of existing schemas in the destination database are synchronized.
  • Scope of incremental synchronization
    • Supported: some DML statements, including INSERT, UPDATE, and DELETE
    • Not supported: DDL statements, DML statements of unlogged tables and temporary tables

Database Account Permission Requirements

To start a synchronization task, the source and destination database users must meet the requirements in the following table. Different types of synchronization tasks require different permissions. For details, see Table 3. DRS automatically checks the database account permissions in the pre-check phase and provides handling suggestions.

  • You are advised to create an independent database account for DRS task connection to prevent task failures caused by database account password modification.
  • After changing the account passwords for the source or destination databases, modify the connection information in the DRS task as soon as possible to prevent automatic retry after a task failure. Automatic retry will lock the database accounts.
Table 3 Database account permission

Type

Full

Full+Incremental

Source database user

Database CONNECT permission, schema USAGE permission, table SELECT permission, and sequence SELECT permission

The CONNECT permission for databases, the USAGE permission for schemas, the SELECT permission for tables, the SELECT permissions for sequences, the UPDATE, DELETE, and TRUNCATE permissions for tables that do not have primary keys, and the permission to create replication connections

NOTE:
  • The UPDATE, DELETE, and TRUNCATE permissions for tables that do not have primary keys are only used to temporarily lock tables to ensure data consistency after the migration.
  • To add the permission to create replication connections, perform the following steps:
    1. Add host replication <src_user_name> <drs_instance_ip>/32 md5 before all configurations in the pg_hba.conf file of the source database.
    2. Run select pg_reload_conf(); in the source database as user SUPERUSER, or restart the DB instance to apply the changes.

Destination database user

  • Table-level:
    • To synchronize databases, the CREATEDB permission is required.
    • To synchronize a schema, the CONNECT and CREATE permissions for the database that contains the schema are required.
    • To synchronize objects in a schema, the CONNECT permission for the database that contains the schema, and the USAGE and CREATE permissions for the schema that contain the object are required.

Suggestions

  • When a task is being started or in the full synchronization phase, do not perform DDL operations on the source database. Otherwise, the task may be abnormal.
  • To keep data consistency before and after the synchronization, ensure that no data is written to the destination database during the synchronization.
  • The success of database synchronization depends on environment and manual operations. To ensure a smooth synchronization, perform a synchronization trial before you start the synchronization to help you detect and resolve problems in advance.
  • Start your synchronization task during off-peak hours. A less active database is easier to synchronize successfully. If the data is fairly static, there is less likely to be any severe performance impacts during the synchronization.
    • If network bandwidth is not limited, the query rate of the source database increases by about 50 MB/s during full synchronization, and two to four CPUs are occupied.
    • To ensure data consistency, tables to be synchronized without a primary key may be locked for 3s.
    • The data being synchronized may be locked by other transactions for a long period of time, resulting in read timeout.
    • When DRS concurrently reads data from a database, it will use about 6 to 10 sessions. The impact of the connections on services must be considered.
    • If you read a table, especially a large table, during the full migration, the exclusive lock on that table may be blocked.
    • For more information about the impact of DRS on databases, see What Is the Impact of DRS on Source and Destination Databases?
  • Data-Level Comparison

    To obtain accurate comparison results, start data comparison at a specified time point during off-peak hours. If it is needed, select Start at a specified time for Comparison Time. Due to slight time difference and continuous operations on data, data inconsistency may occur, reducing the reliability and validity of the comparison results.

Precautions

The full+incremental synchronization process consists of four phases: task startup, full synchronization, incremental synchronization, and task completion. A single full synchronization task contains three phases. To ensure smooth synchronization, read the following notes before creating a synchronization task.

Table 4 Precautions

Type

Constraints

Starting a task

  • Source database parameter requirements:
    • The partition table trigger of the source database cannot be set to disable.
    • For a full synchronization task, the source database can be a standby database, but hot_standby_feedback must be set to on. For an incremental synchronization task, the source database cannot be a standby database.
    • To perform incremental synchronization:
      The pg_hba.conf file of the source database contains the following configuration:
      host replication all 0.0.0.0/0 md5

      The wal_level value of the source database must be logical.

      The test_decoding plug-in must be installed on the source database in advance.

      The replica identity attribute of tables that do not have primary keys in the source database must be full.

      The max_replication_slots value of the source database must be greater than the number of used replication slots.

      The max_wal_senders value of the source database must be greater than or equal to the max_replication_slots value.

      If the toast attribute of the primary key column in the source database is main, external, or extended, the replica identity attribute must be full.

  • Source database object requirements:
    • The objects that have dependencies must be synchronized at the same time. Otherwise, the synchronization may fail.
      NOTE:

      Common dependencies: tables referenced by views, views referenced by views, tables referenced by primary and foreign keys, parent tables referenced by child tables, partitioned tables referenced by sub-partitioned tables, and sequences referenced by auto-increment columns.

  • Destination database parameter requirements:
    • The max_prepared_transactions value of the destination database must be greater than that of the source database.
    • The max_worker_processes value of the destination database must be greater than that of the source database.
    • The max_locks_per_transaction value of the destination database must be greater than that of the source database.
    • The max_connections value of the destination database must be greater than that of the source database.
    • The lc_monetary value of the destination database must be the same as that of the source database.
  • Destination database object requirements:
    • The character set of the destination database must be the same as that of the source database.
    • The time zone of the destination database must be the same as that of the source database.
    • Do not use foreign keys for tables during synchronization. Otherwise, the sequence of writing data to different tables may be inconsistent with that in the source database, which may trigger foreign key constraints and cause synchronization failures.
    • The destination table can contain more columns than the source table. However, the following failures must be avoided:

      Assume that extra columns on the destination cannot be null or have default values. If newly inserted data records are synchronized from the source to the destination, the extra columns will become null, which does not meet the requirements of the destination and will cause the task to fail.

      Assume that extra columns on the destination must be fixed at a default value and have a unique constraint. If newly inserted data records are synchronized from the source to the destination, the extra columns will contain multiple default values. That does not meet the unique constraint of the destination and will cause the task to fail.

  • Other notes:
    • If the DCC does not support instances with 4 vCPUs and 8 GB memory or higher instance specifications, the synchronization task cannot be created.
    • Cascading one-way synchronization is not supported. For example, data cannot be synchronized from instance A to instance B and then from instance B to instance C.
    • Only the primary table can be synchronized. The primary table will be converted into a common table and synchronized to the destination database. Data in the partition table will be written to the primary table.
    • When a schema name or table name is mapped, to prevent conflicts between indexes and constraint names, the original index name in the table is changed to the following format after synchronization: i_+hash value+original index name (which may be truncated)+_key The hash value is calculated based on the original schema name_original table name_original index name. Similarly, the original constraint name on the table is changed to c_ + hash value + original constraint name (which may be truncated) + _key.
    • Before starting a full+incremental or incremental synchronization task, ensure that no long transaction is started in the source database. If a long transaction is started in the source database, the creation of the logical replication slot will be blocked. As a result, the task fails.
    • In a full synchronization for the table structure, the length of the character and character varying types in the source database automatically increases by byte in the destination database (because the length of the destination database is in the unit of byte). By default, the length is increased by four times, and the maximum length is 10485760.

Full synchronization

  • Do not change the port of the source and destination databases, or change or delete the passwords and permissions of the source and destination database users. Otherwise, the task may fail.
  • Do not run any DDL statement in the source database. Otherwise, data may be inconsistent or the task may fail.
  • Do not write data to the destination database. Otherwise, data may be inconsistent.

Incremental synchronization

  • Do not change the port of the source and destination databases, or change or delete the passwords and permissions of the source and destination database users. Otherwise, the task may fail.
  • Do not change the primary key or unique key (if the primary key does not exist) of the source database table. Otherwise, incremental data may be inconsistent or the task may fail.
  • Do not modify the replica identity attribute of tables in the source database. Otherwise, incremental data may be inconsistent or the task may fail.
  • Do not write data to the destination database. Otherwise, data may be inconsistent.
  • During database-level synchronization, if a table without a primary key is added to the source database, you must set replica identity of the table to full before writing data. Otherwise, data may be inconsistent or the task may fail.
  • During database-level synchronization, if a primary key table is added to the source database and the toast attribute of the primary key column is main, external, or extended, the replica identity attribute of the table must be set to full before writing data. Otherwise, data may be inconsistent or the task may fail.

Synchronization comparison

  • You are advised to compare data in the source database during off-peak hours to prevent inconsistent data from being falsely reported and reduce the impact on the source database and DRS tasks.
  • During incremental synchronization, if data is written to the source database, the comparison results may be inconsistent.
  • Data cannot be compared during full synchronization.
  • Do not limit the synchronization speed during data comparison.

Stopping a task

  • Stop a task normally:
    • When a full+incremental synchronization task is complete, the streaming replication slot created by the task in the source database is automatically deleted.
  • Forcibly stop a task:

Prerequisites

  • You have logged in to the DRS console.
  • Your account balance is greater than or equal to $0 USD.
  • For details about the DB types and versions supported by real-time synchronization, see Supported Databases.
  • If a subaccount is used to create a DRS task, ensure that an agency has been added. To create an agency, see Agency Management.

Procedure

  1. On the Data Synchronization Management page, click Create Synchronization Task.
  2. On the Create Synchronization Instance page, select a region and project, specify the task name, description, and the synchronization instance details, and click Create Now.

    • Task information description
      Figure 1 Synchronization task information
      Table 5 Task and recipient description

      Parameter

      Description

      Region

      The region where the synchronization instance is deployed. You can change the region.

      Project

      The project corresponds to the current region and can be changed.

      Task Name

      The task name must start with a letter and consist of 4 to 50 characters. It can contain only letters, digits, hyphens (-), and underscores (_).

      Description

      The description consists of a maximum of 256 characters and cannot contain special characters !=<>'&"\

    • Synchronization instance details
      Figure 2 Synchronization instance details
      Table 6 Synchronization instance settings

      Parameter

      Description

      Data Flow

      Select To the cloud.

      Source DB Engine

      Select PostgreSQL.

      Destination DB Engine

      Select GaussDB Primary/Standby.

      Network Type

      Available options: VPC, Public network and VPN or Direct Connect. VPC is used as an example.

      Destination DB Instance

      An available GaussDB primary/standby instance.

      Synchronization Instance Subnet

      Select the subnet where the synchronization instance is located. You can also click View Subnet to go to the network console to view the subnet where the instance resides.

      By default, the DRS instance and the destination DB instance are in the same subnet. You need to select the subnet where the DRS instance resides and ensure that there are available IP addresses. To ensure that the synchronization instance is successfully created, only subnets with DHCP enabled are displayed.

      Synchronization Mode

      • Full+Incremental

        This synchronization mode allows you to synchronize data in real time. After a full synchronization initializes the destination database, an incremental synchronization parses logs to ensure data consistency between the source and destination databases.

      • Full

        This synchronization mode is suitable for scenarios where service interruption is acceptable. Database objects and data, including tables, views, and stored procedures, from non-system databases can be synchronized to the destination all at once.

      • Incremental

        In this mode, incremental data generated on the source database is continuously synchronized to the destination database through log parsing.

    • Enterprise Projects and Tags
      Figure 3 Enterprise projects and tags
      Table 7 Enterprise Projects and Tags

      Parameter

      Description

      Enterprise Project

      An enterprise project you would like to use to centrally manage your Global Accelerator resources. Select an enterprise project from the drop-down list. The default project is default. For more information about enterprise project, see Enterprise Management User Guide.

      To customize an enterprise project, click Enterprise in the upper right corner of the console. The Enterprise Management page is displayed. For details, see Creating an Enterprise Project in Enterprise Management User Guide.

      Tags

      • This setting is optional. Adding tags helps you better identify and manage your tasks. Each task can have up to 10 tags.
      • After a task is created, you can view its tag details on the Tags tab. For details, see Tag Management.

    If a task fails to be created, DRS retains the task for three days by default. After three days, the task automatically ends.

  3. On the Configure Source and Destination Databases page, wait until the synchronization instance is created. Then, specify source and destination database information and click Test Connection for both the source and destination databases to check whether they have been connected to the synchronization instance. After the connection tests are successful, select the check box before the agreement and click Next.

    Establish the connectivity between the DRS instance and the source and destination databases.

    • Network connectivity: Ensure that the source and destination databases accept connections from the IP address of the DRS instance. To access databases over a public network, configure the database to accept connections from the EIP of the DRS instance. To access databases over a VPC, VPN, or Direct Connect network, configure the database to accept connections from the private IP address of the DRS instance.For details, see Network Preparations.
    • Account connectivity: Ensure that the source and destination databases allows connections from the DRS instance using the username and password.

    The source database can be an ECS database or an RDS instance. Configure parameters based on different scenarios.

    • Scenario 1: Databases on an ECS - source database configuration
      Figure 4 Self-build on ECS - source database information
      Table 8 Self-build on ECS - source database information

      Parameter

      Description

      Source Database Type

      Select Self-built on ECS.

      VPC

      A dedicated virtual network in which the source database is located. It isolates networks for different services. You can select an existing VPC or create a VPC.

      Subnet

      A subnet provides dedicated network resources that are isolated from other networks, improving network security. The subnet must be in the AZ where the source database resides. You need to enable DHCP for creating the source database subnet.

      IP Address or Domain Name

      The IP address or domain name of the source database.

      Port

      The port of the source database. Range: 1 – 65535

      Database Name

      Indicates whether to specify a database. If this option is enabled, enter the database name.

      Database Username

      The username for accessing the source database.

      Database Password

      The password for the database username.

      SSL Connection

      SSL encrypts the connections between the source and destination databases.

      The IP address, domain name, username, and password of the source database are encrypted and stored in DRS, and will be cleared after the task is deleted.

    • Scenario 2: RDS DB instance - source database configuration
      Figure 5 RDS DB instance - source database information
      Table 9 RDS DB instance - source database information

      Parameter

      Description

      Source Database Type

      Select an RDS DB instance.

      DB Instance Name

      Select the RDS PostgreSQL instance to be synchronized as the source DB instance.

      Database Username

      The username for accessing the source database.

      Database Password

      The password for the database username.

    Figure 6 Destination database information
    Table 10 Destination database settings

    Parameter

    Description

    DB Instance Name

    The GaussDB primary/standby instance selected during synchronization task creation. This parameter cannot be changed.

    Database Username

    The username for accessing the destination database.

    Database Password

    The password for the database username.

    The username and password of the source and destination databases are encrypted and stored in the databases and the synchronization instance during the synchronization. After the task is deleted, the username and password are permanently deleted.

  4. On the Set Synchronization Task page, select the objects to be synchronized, and then click Next.

    Figure 7 Synchronization mode
    Table 11 Synchronization Object

    Parameter

    Description

    Synchronization Object

    The left pane displays the source database objects, and the right pane displays the selected objects. DRS supports table-level synchronization. You can select data for synchronization based on your service requirements.

    • If the synchronization objects in source and destination databases have different names, you can map the source object name to the destination one. For details, see Mapping Object Names.
    • When a schema name or table name is mapped, to prevent conflicts between indexes and constraint names, the original index name in the table is changed to the following format after synchronization: i_+hash value+original index name (which may be truncated)+_key The hash value is calculated based on the original schema name_original table name_original index name. Similarly, the original constraint name on the table is changed to c_ + hash value + original constraint name (which may be truncated) + _key.
    NOTE:
    • To quickly select the desired database objects, you can use the search function.
    • If there are changes made to the source databases or objects, click in the upper right corner to update the objects to be synchronized.
    • If the object name contains spaces, the spaces before and after the object name are not displayed. If there are multiple spaces between the object name and the object name, only one space is displayed.
    • The name of the selected synchronization object cannot contain spaces.

  5. On the Check Task page, check the synchronization task.

    • If any check fails, review the cause and rectify the fault. After the fault is rectified, click Check Again.

      For details about how to handle check failures, see Checking Whether the Source Database Is Connected in Data Replication Service User Guide.

    • If all check items are successful, click Next.
      Figure 8 Pre-check

      You can proceed to the next step only when all checks are successful. If there are any items that require confirmation, view and confirm the details first before proceeding to the next step.

  6. On the displayed page, specify Start Time, Send Notification, SMN Topic, Synchronization Delay Threshold, and Stop Abnormal Tasks After, confirm that the configured information is correct, select the check box before the agreement, and click Submit to submit the task.

    Figure 9 Task startup settings
    Table 12 Task startup settings

    Parameter

    Description

    Started Time

    Set Start Time to Start upon task creation or Start at a specified time based on site requirements.

    NOTE:

    After a synchronization task is started, the performance of the source and destination databases may be affected. You are advised to start a synchronization task during off-peak hours.

    Send Notifications

    SMN topic. This parameter is optional. If an exception occurs during synchronization, the system will send a notification to the specified recipients.

    SMN Topic

    This parameter is available only after you enable Send Notifications and create a topic on the SMN console and add a subscriber.

    For details, see Simple Message Notification User Guide.

    Synchronization Delay Threshold

    During an incremental synchronization, a synchronization delay indicates a time difference (in seconds) of synchronization between the source and destination database.

    If the synchronization delay exceeds the threshold you specify, DRS will send alarms to the specified recipients. The value ranges from 0 to 3,600. To avoid repeated alarms caused by the fluctuation of delay, an alarm is sent only after the delay has exceeded the threshold for six minutes.

    NOTE:
    • If the delay threshold is set to 0, no notifications will be sent to the recipient.
    • In the early stages of an incremental synchronization, the synchronization delay is long because a large quantity of data is awaiting synchronization. In this case, no notifications will be sent.
    • Before setting the delay threshold, enable Send Notification.

    Stop Abnormal Tasks After

    Number of days after which an abnormal task is automatically stopped. The value must range from 14 to 100. The default value is 14.

    NOTE:

    Tasks in the abnormal state are still charged. If tasks remain in the abnormal state for a long time, they cannot be resumed. Abnormal tasks run longer than the period you set (unit: day) will automatically stop to avoid unnecessary fees.

  7. After the task is submitted, you can view and manage it on the Data Synchronization Management page.

    • You can view the task status. For more information about task status, see Task Statuses.
    • You can click in the upper-right corner to view the latest task status.
    • By default, DRS retains a task in the Configuration state for three days. After three days, DRS automatically deletes background resources, and the task status remains unchanged. When you restart the task configuration, DRS applies for resources again.