Skip to main content

MySQL Migration Synchronization to PostgreSQL

NineData replication supports data synchronization from MySQL to PostgreSQL data sources.

Feature Introduction​

NineData data replication supports high-performance replication of structure, full data, and incremental data between data sources. For MySQL data sources, it also provides bidirectional replication, enabling the quick construction of geo-distributed active-active business architectures.

  • Structure: Supports the replication of object structures between homogeneous and heterogeneous data sources, greatly reducing the barrier to data replication between two sources.
  • Full Data: Achieves row-level concurrent batch replication through intelligent data sharding, effectively ensuring replication performance. The independently developed novel breakpoint resume technology ensures the accuracy of data in tables without primary keys.
  • Incremental Data: Supports incremental data replication of full object types DML|DDL, combined with transaction-level concurrency, hotspot merging, and other technologies to provide robust replication performance while ensuring transaction consistency.
  • Bidirectional Real-time Data Replication (only between MySQL instances): Direct bidirectional replication of data between multiple nodes ensures that all node data remains up-to-date.

With the above features, it is easy and efficient to achieve scenarios such as full|incremental data replication, full|incremental data migration, full|incremental data synchronization, data integration, and seamless migration without downtime, providing enterprises with flexible and reliable data replication solutions.

Prerequisites​

  • The source and target data sources have been added to NineData. For instructions on how to add them, see Adding Data Sources.

  • The source database type is MySQL or a MySQL-compatible database, such as MySQL, MariaDB, PolarDB MySQL, TDSQL-C, GaussDB MySQL, Aurora, etc.

  • The target data source is PostgreSQL, with a version of 15, 14, 13, 12, 11, or 10.

  • You must have the following permissions for the source and target data sources:

    Replication Type
    		Source Data SourceTarget Data Source
    Structure ReplicationSELECT permissionSELECT, INSERT, UPDATE, DELETE permissions
    Full ReplicationSELECT permissionSELECT, INSERT, UPDATE, DELETE permissions
    Incremental ReplicationSELECT, REPLICATION CLIENT, REPLICATION SLAVE permissionsSELECT, INSERT, UPDATE, DELETE permissions

  • For incremental replication, the source data source must have Binlog enabled, and the Binlog-related parameters are set as follows:

    • binlog_format=ROW
    • binlog_row_image=FULL
    tip

    If the source data source is a replica, to ensure complete acquisition of Binlog logs, the log_slave_updates parameter also needs to be enabled.

  • If the source and target data sources are recorded in NineData with different regions, you also need to add the IP addresses of the respective NineData servers to each other's data source whitelist. You can view the IP addresses of both when creating a replication task, on the node page.

Usage Limitations​

  • The incremental replication process does not currently support synchronizing DDL operations from the source.
  • The data replication feature is only for user databases in the data source; system databases will not be replicated. For example, databases like information_schema, mysql, performance_schema, sys in MySQL-type data sources will not be replicated.
  • Before performing data synchronization, it is necessary to assess the performance of the source and target data sources, and it is recommended to perform data synchronization during off-peak business hours. Otherwise, the full data initialization will occupy a certain amount of read and write resources from the source and target data sources, leading to increased database load.
  • It is necessary to ensure that each table in the synchronization object has a primary key or unique constraint, and the column names are unique; otherwise, the same data may be synchronized repeatedly.

Operation Steps​

Commercialization Notice

NineData’s data replication product has been commercialized. You can still use 10 replication tasks for free, with the following considerations:

  • Among the 10 replication tasks, you can include 1 task, with a specification of Micro.

  • Tasks with a status of do not count towards the 10-task limit. If you have already created 10 replication tasks and want to create more, you can terminate previous replication tasks and then create new ones.

  • When creating replication tasks, you can only select the you have purchased. Specifications that have not been purchased will be grayed out and cannot be selected. If you need to purchase additional specifications, please contact us through the customer service icon at the bottom right of the page.

  1. Log in to the NineData Console.

  2. Click on in the left navigation bar.

  3. On the page, click on in the top right corner.

  4. On the tab, configure according to the table below and click on .

    Parameter
    		Description
    Enter the name of the data synchronization task. To facilitate subsequent search and management, please use meaningful names as much as possible. Up to 64 characters are supported.
    The data source where the synchronization object is located.
    The data source that receives the synchronization object.
    Select which database to synchronize the data to the target.
    Choose the content that needs to be replicated to the target data source.
    • : Only synchronize the database table structure of the source data source, without synchronizing the data.
    • : Synchronize all objects and data of the source data source, i.e., full data replication. The switch on the right is the switch for periodic full replication. For more information, please refer to Periodic Full Replication.
    • : After the full synchronization is completed, perform incremental synchronization based on the logs of the source data source.
    （Required when is selected）
    • : Stop the task when a table with the same name is detected during the pre-inspection phase.
    • : Send a prompt and continue the task when a table with the same name is detected during the pre-inspection phase. Ignore the table with the same name during structure replication. If you also perform data replication, the data will be appended to the table with the same name without overwriting the original data.
    • : Send a prompt and continue the task when a table with the same name is detected during the pre-inspection phase. Delete the table with the same name in the target database and re-replicate the table structure based on the source database during structure replication. If you also perform data replication, the data will be written after the table structure replication is completed.
    • （Optional when both structure and data replication are performed）: Send a prompt and continue the task when a table with the same name is detected during the pre-inspection phase. Retain the table structure in the target database during structure replication, and clear the data in the table with the same name at the beginning of data replication, then re-copy from the original table.
    （Required when is not selected）
    • : Stop the task when data is detected in the target table during the pre-inspection phase.
    • : Ignore the data when it is detected in the target table during the pre-inspection phase, and append other data.
    • : Delete the data when it is detected in the target table during the pre-inspection phase, and rewrite it.

  5. On the tab, configure the following parameters, and then click on .

    Parameter
    		Description
    Choose the content that needs to be replicated. You can choose to replicate all content from the source database, or you can choose , select the content that needs to be replicated in the list, and click > to add to the right list.

    If you need to create multiple replication chains with the same replication object, you can create a configuration file and import it when creating a new task. Click on in the top right corner, then click Download Template to download the configuration file template to your local machine, edit it, and then click to upload the configuration file to achieve batch import. Configuration file description:

    Parameter
    		Description
    source_table_nameThe source table name where the object to be synchronized is located.
    destination_table_nameThe target table name that receives the synchronized object.
    source_schema_nameThe source Schema name where the object to be synchronized is located.
    destination_schema_nameThe target Schema name that receives the synchronized object.
    source_database_nameThe source database name where the object to be synchronized is located.
    target_database_nameThe target database name that receives the synchronized object.
    column_listThe list of fields that need to be synchronized.
    extra_configurationAdditional configuration information, where you can configure the following information:
    • Field mapping: column_name, destination_column_name
    • Field value: column_value
    • Data filtering: filter_condition
    tip

    • An example of extra_configuration is as follows:

      {
          "column_name": "created_time", //Specify the original column name for column name mapping
          "destination_column_name": "migrated_time", //Map the target column name to "migrated_time"
          "column_value": "current_timestamp()", //Change the field value of the column to the current timestamp
          "filter_condition": "id != 0" //Only rows with ID not equal to 0 will be synchronized.
      }

    • For the overall example content of the configuration file, please refer to the downloaded template.

  6. On the tab, select different operations based on the selected replication type, and then click on . Click on the drop-down menu to the right of Object Owner to specify the owner of the object, if not selected, the default is . If there are updates in the source and target data sources during the configuration mapping phase, you can click on the button in the top right corner of the page to refresh the information of the source and target data sources.

    • Including : Configure the table name after the target table is synchronized to the target data source.

    • Not including : The system defaults to selecting the database with the same name in the target data source; if it does not exist, you need to manually select the target database. The table name and column name in the target database need to be consistent with the synchronization object. If they are not consistent, you can also manually map the table name and column name.

    You can click on on the right side of the page to customize the name of the column after it is synchronized to the target data source. In addition, you can set , configure filtering conditions through comparison expressions, and only data that meets the filtering conditions will be synchronized to the target data source. For example, if the filtering condition is set to emp_no>=10005, then data with emp_no less than 10005 in the column will not be synchronized to the target data source.

  7. On the tab, wait for the system to complete the pre-inspection, and after the pre-inspection is passed, click on .

    tip

    • You can check . After the synchronization task is completed, automatically start data consistency comparison based on the source data source to ensure data consistency on both ends. Depending on the you selected, the start time of is as follows:

      • : Start after the structure replication is completed.
      • +, : Start after the full replication is completed.

      • ++, : Start when the incremental data is first consistent with the source data source and is 0 seconds. You can click on to view the synchronization delay on the page.

        sync_delay

    • If the pre-inspection does not pass, you need to click on in the column to the right of the target inspection item, troubleshoot the cause of the failure, manually fix it, and then click on to re-execute the pre-inspection until it passes.

    • If the is for the inspection item, it can be repaired or ignored according to the specific situation.

  8. On the page, it prompts , and the synchronization task starts running. At this time, you can perform the following operations:

    • Click on to view the execution of each stage of the synchronization task.
    • Click on to return to the task list page.

  1. Log in to the NineData Console.

  2. Click on in the left navigation bar.

  3. On the page, click on .

  4. On the tab, configure according to the table below and click on .

    Parameter
    		Description
    Enter the name of the data synchronization task. To facilitate subsequent search and management, please use a meaningful name. Up to 64 characters are supported.
    The data source where the synchronization object is located.
    The data source that receives the synchronization object.
    Choose the content to be replicated to the target data source.
    • : Only synchronize the database table structure of the source data source, without synchronizing data.
    • : Synchronize all objects and data of the source data source, that is, full data replication.
    • : After the full synchronization is completed, perform incremental synchronization based on the logs of the source data source.
    （Required when is selected）
    • : Stop the task when the same name table is detected during the pre-inspection stage.
    • : Send a prompt and continue the task when the same name table is detected during the pre-inspection stage. During structural replication, ignore the table with the same name. If you also perform data replication, the data will be appended to the table with the same name instead of overwriting the existing data.
    • : Send a prompt and continue the task when the same name table is detected during the pre-inspection stage. During structural replication, delete the table with the same name in the target database and re-copy the table structure based on the source database. If you also perform data replication, the data will be written after the table structure is copied.
    • （Optional when both structure and data replication are performed）: Send a prompt and continue the task when the same name table is detected during the pre-inspection stage. During structural replication, retain the table structure in the target database, and clear the data in the table with the same name at the beginning of data replication, then re-copy from the original table.
    （Required when is not selected）
    • : Stop the task when data is detected in the target table during the pre-inspection stage.
    • : Ignore the data when it is detected in the target table during the pre-inspection stage, and append other data.
    • : Delete the data when it is detected in the target table during the pre-inspection stage, and rewrite it.

  5. On the tab, configure the following parameters, then click on .

    Parameter
    		Description
    Select the content to be replicated. You can choose to replicate all content from the source database, or you can choose , select the content to be replicated in the list, and click > to add it to the right list.

  6. On the tab, choose different operations based on the selected replication type.

    • Including : Configure the table name after the target table is synchronized to the target data source, and click .

      tip

      You can click on on the right side of the page to customize the name of the column name synchronized to the target data source. In addition, you can set , and configure filtering conditions through comparison expressions, only data that meets the filtering conditions will be synchronized to the target data source. For example, if the filtering condition is set to emp_no>=10005, data in the emp_no column less than 10005 will not be synchronized to the target data source.

    • Not including : The system defaults to selecting the database with the same name in the target data source. If it does not exist, you need to manually select the target library. The table name and column name in the target library need to be consistent with the synchronization object. If they are not consistent, you can also manually map the table name and column name.

  7. On the tab, wait for the system to complete the pre-inspection, and after the pre-inspection is passed, click .

    tip
    • You can check . After the synchronization task is completed, automatically start the data consistency comparison based on the source data source to ensure that the data on both sides is consistent. Depending on the you selected, the timing for starting is as follows:
      • : Start after the structural replication is completed.
      • +, : Start after the full replication is completed.
      • ++, : Start when the incremental data is consistent with the source data source for the first time and is 0 seconds. You can click to view the synchronization delay on the page. sync_delay
    • If the pre-inspection does not pass, you need to click on in the column on the right side of the target inspection item to investigate the cause of the failure, manually fix it, and then click to re-execute the pre-inspection until it passes.
    • If the is , you can fix or ignore it according to the specific situation.

  8. On the page, it prompts , and the synchronization task starts running. At this point, you can perform the following operations:

    • Click on to view the execution of each stage of the synchronization task.
    • Click on to return to the task list page.

View Synchronization Results​

  1. Log in to the NineData Console.

  2. Click on > in the left navigation bar.

  3. On the page, click on the of the target synchronization task, the page details are as follows.

    result

    Number
    		Function
    		Description
    1Sync DelayThe data synchronization delay between the source data source and the target data source. 0 seconds means there is no delay between the two ends, at which point you can choose to switch the business to the target data source for smooth migration.
    2Configure AlertsAfter configuring alerts, the system will notify you in the way you choose when the task fails. For more information, please refer to Operations Monitoring Introduction.
    3More
    • : Pause the task, only tasks with Running status are selectable.
    • : Create a new replication task with the same configuration as the current task.
    • : End tasks that are unfinished or listening (i.e., in incremental synchronization). Once the task is terminated, it cannot be restarted, so please proceed with caution. If the synchronization objects contain triggers, a trigger replication option will pop up, please select as needed.
    • : Delete the task. Once the task is deleted, it cannot be recovered, so please proceed with caution.
    4Structure Replication (displayed in scenarios involving structure replication)Displays the progress and detailed information of structure replication.
    • Click on on the right side of the page: View the execution logs of structure replication.
    • Click on refresh on the right side of the page: View the latest information.
    • Click on in the column on the right side of the target object in the list: View SQL playback.
    5Full Replication (displayed in scenarios involving full replication)Displays the progress and detailed information of full replication.
    • Click on on the right side of the page: View various monitoring indicators during full replication. During full replication, you can also click on on the right side of the monitoring indicator page to limit the rate of writing to the target data source per second. The unit is rows/second.
    • Click on on the right side of the page: View the execution logs of full replication.
    • Click on refresh on the right side of the page: View the latest information.
    6Incremental Replication (displayed in scenarios involving incremental replication)Displays various monitoring indicators of incremental replication.
    • Click on on the right side of the page: View the operations currently being executed by the current replication task, including:
      • : Replication tasks are executed in multiple threads, displaying the current thread number in progress.
      • : Details of the SQL statement currently being executed by the current thread.
      • : The response time of the current thread. If this value increases, it indicates that the current thread may be stuck for some reason.
      • : The timestamp when the current thread was started.
      • : The status of the current thread.
    • Click on on the right side of the page: Limit the rate of writing to the target data source per second. The unit is rows/second.
    • Click on on the right side of the page: View the execution logs of incremental replication.
    • Click on refresh on the right side of the page: View the latest information.
    7Modify ObjectDisplays the modification records of synchronization objects.
    • Click on on the right side of the page to configure the synchronization objects.
    • Click on refresh on the right side of the page: View the latest information.
    8Data ComparisonDisplays the comparison results between the source data source and the target data source. If you have not enabled data comparison, please click on on the page.
    • Click on on the right side of the page: Re-initiate the comparison between the current source and target data sources.
    • Click on on the right side of the page: After the comparison task starts, you can click this button to stop the comparison task immediately.
    • Click on on the right side of the page: View the execution logs of consistency comparison.
    • Click on (displayed only in data comparison): View the trend chart of RPS (records per second) comparison. Click on to view earlier records.
    • Click on details in the column on the right side of the comparison list (displayed under the tab only in the case of inconsistency): View details of the comparison between the source and target sides.
    • Click on sql in the column on the right side of the comparison list (displayed only in the case of inconsistency): Generate change SQL. You can directly copy this SQL to the target data source to execute and modify the inconsistent content.
    9ExpandDisplay detailed information of the current replication task. Common Options:
    • : Export the current task's database and table configuration, allowing for quick import when creating a new replication task. This helps rapidly establish multiple replication links with the same replication objects.
    • : Configure the alarm strategy for the current task.

Appendix 1: MySQL and PostgreSQL Data Type Mapping Table​

During the data replication process, MySQL data types are mapped to corresponding PostgreSQL data types.

CategoryMySQL Data TypePostgreSQL Data Type
NumericTINYINTSMALLINT
TINYINT UNSIGNEDSMALLINT
SMALLINTSMALLINT
SMALLINT UNSIGNEDINTEGER
MEDIUMINTINTEGER
MEDIUMINT UNSIGNEDINTEGER
INTINTEGER
INT UNSIGNEDBIGINT
BIGINTBIGINT
BIGINT UNSIGNEDBIGINT
BIT(M)BIT(N)
DECIMAL()DECIMAL
NUMERICDECIMAL
FLOATFLOAT
DOUBLEFLOAT8
BOOL，BOOLEANSMALLINT
DATE AND TIMEDATEDATE
DATETIME[(fsp)]TIMESTAMP[(p)]
TIMESTAMP[(fsp)]TIMESTAMP[(p)] with time zone
TIME[(fsp)]TEXT
YEAR[(4)]INTEGER
STRINGCHARCHAR[(n)]
VARCHARVARCHAR
BINARY/VARBINARYBYTEA
TINYTEXT/TEXT/MEDIUMTEXT/LONGTEXTTEXT
TINYBLOB/BLOB/MEDIUMBOLB/LONGBLOBBYTEA
ENUMVARCHAR
SETVARCHAR
JSONJSONJSON

Appendix 2: Pre-inspection Item List​

Inspection ItemInspection Content
Source Data Source Connection CheckCheck the gateway status of the source data source, whether the instance is reachable, and the accuracy of the username and password
Target Data Source Connection CheckCheck the gateway status of the target data source, whether the instance is reachable, and the accuracy of the username and password
Target Library Permission CheckCheck whether the account permissions of the target database meet the requirements
Source Library Permission CheckCheck whether the account permissions of the source database meet the requirements
Source Database log_slave_updates Support CheckWhen the source database is a replica, check whether log_slave_updates is ON
Source and Target Data Source Version CheckCheck whether the versions of the source and target databases are compatible
Source Database Binlog Enabled CheckCheck whether the Binlog is enabled in the source database
Source Database Binlog Format Support CheckCheck whether the binlog format of the source database is 'ROW'
Source Database binlog_row_image Support CheckCheck whether the binlog_row_image of the source database is 'FULL'
Target Library Data Existence CheckCheck whether there is data in the target database for the object to be replicated
Target Library Same Name Object Existence CheckCheck whether there is an object with the same name in the target database

Introduction to Data Replication

Last updated on