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 certain 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 DML and DDL incremental data replication for all object types. By leveraging technologies such as row-level concurrency and hotspot merging, it delivers robust replication performance.
• 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 Source	Target Data Source
  Structure Replication	SELECT permission	SELECT, INSERT, UPDATE, DELETE permissions
  Full Replication	SELECT permission	SELECT, INSERT, UPDATE, DELETE permissions
  Incremental Replication	SELECT, REPLICATION CLIENT, REPLICATION SLAVE permissions	SELECT, 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 "Source & Target" 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 Incremental task, with a specification of Micro.

• Tasks with a status of Terminated 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 Spec 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. In the left navigation pane, click Replication > Data Replication.

3. On the Replication page, click Create Replication in the upper-right corner.

4. On the Source & Target tab, configure the parameters in the following table, and click Next.

   Parameter	Description
   Name	Enter a name for the data synchronization task. To make the task easier to find and manage later, use a meaningful name. Up to 64 characters are supported.
   Source	The data source that contains the objects to synchronize.
   Target	The data source that receives the synchronized objects.
   Target DB	Select the target database to which data is synchronized.
   Target Object Name	Select the case conversion rule for object names after they are migrated from the source to the target. Convert all to Lowercase: Regardless of the naming rule on the source, all target names are lowercase. Consistent with Source: Keep the naming rule of the source. Convert all to Uppercase: Regardless of the naming rule on the source, all target names are uppercase.
   Type	Select the replication type. Schema: Synchronize only the database and table schemas of the source data source, without synchronizing data. Full: Synchronize all objects and data from the source data source, namely full data replication. Incremental: After full synchronization is complete, perform incremental synchronization based on the logs of the source data source.The icon is used to configure incremental operation types. You can clear specific operation types as needed. Cleared operation types will be ignored during incremental synchronization.
   Incremental Started	Required only when Type is Incremental. From Started: Use the current replication task start time as the baseline for incremental replication. Customized Time: Select the point in time from which incremental replication starts. You can select a time zone based on the region of your business. If the configured time point is earlier than the current replication task start time and DDL operations occurred during that period, the replication task will fail.
   Spec	The specification of the replication task. A larger specification provides a higher replication rate. Hover over the icon to view the rate and configuration information of each specification. If you configure the data replication task before purchasing resources, you can select the required specification here. If you purchase resources before configuring the task, the system selects the specification chosen during resource purchase, and you cannot change it in the task configuration.
   If target table already exists (Required when Schema is selected)	Pre-Check Error and Stop Task: Stop the task when a table with the same name is detected during the precheck stage. Skip and Continue Task: When a table with the same name is detected during the precheck stage, display a prompt and continue the task. During schema replication, ignore the table with the same name. If you also perform data replication, data is appended to the table with the same name and existing data is not overwritten. Delete Objects and Rewrite: When a table with the same name is detected during the precheck stage, display a prompt and continue the task. During schema replication, delete the table with the same name in the target database and replicate the table schema again based on the source database. If you also perform data replication, data is written after schema replication is complete.
   Target Table Exists Data (Required when Full is selected)	Pre-Check Error and Stop Task: Stop the task when data is detected in the target table during the precheck stage. Ignore existing target data and append to it.: When data is detected in the target table during the precheck stage, ignore that data and append other data. Clear target existing data before write: When data is detected in the target table during the precheck stage, delete that data and write it again.
   Incremental data conflict handling strategy for target table (Required when Incremental is selected)	Runtime error: During incremental replication, report an error when target data already exists and wait for manual intervention. Do not update target data: During incremental replication, do not write data when target data already exists, and continue subsequent tasks. Update target data: During incremental replication, overwrite the target data when target data already exists.

5. On the Objects tab, configure the following parameters, and click Next.

   Parameter	Description
   Replication Objects	Select the content to replicate. You can select All Objects to replicate all content in the source database, or select Customized Object, select the content to replicate in the Source Object list, and click > to add it to the Target Object list on the right.

   If you need to create multiple replication links with the same replication objects, you can create a configuration file and import it when creating a task. Click Import Config in the upper-right corner, click Download Template to download the configuration file template, edit the file, and then click Upload to upload it for batch import. Configuration file description:

   Parameter	Description
   source_table_name	The source table name of the object to synchronize.
   destination_table_name	The target table name that receives the synchronized object.
   source_schema_name	The source schema name of the object to synchronize.
   destination_schema_name	The target schema name that receives the synchronized object.
   source_database_name	The source database name of the object to synchronize.
   target_database_name	The target database name that receives the synchronized object.
   column_list	The list of columns to synchronize.
   extra_configuration	Additional configuration information. You can configure the following information here: column_rules: Defines column mappings and value rules. Field descriptions: column_name: Original column name. destination_column_name: Specifies the target column name. column_value: Specifies the column value, which can be an SQL function or a constant value. filter_condition: Specifies row-level data filtering conditions. Only rows that meet the conditions are replicated.

   tip

   • The following is an example of extra_configuration:

     {
       "extra_config":{
         "column_rules":[
           {
             "column_name": "created_time", // Specifies the original column name to be mapped.
             "destination_column_name": "migrated_time", // Maps the target column name to "migrated_time".
             "column_value": "current_timestamp()" // Changes the column value to the current timestamp.
           }
         ],
         "filter_condition": "id != 0" // Only rows whose ID is not 0 are synchronized.
       }
     }

   • For a complete example of the configuration file, see the downloaded template.

6. On the "Mapping" tab, choose different operations based on the selected replication type, and click Save and Pre-Check. If the source and target data sources are updated during mapping configuration, click Refresh Metadata in the upper-right corner of the page to refresh the source and target data source information.

   • Includes Schema: Configure the table name after synchronization to the target data source.

   • Does not include Schema: The system selects the database with the same name in the target data source by default. If no such database exists, you need to manually select the target database. The table names and column names in the target database must match the synchronization objects. If they do not match, you can manually map the table names and column names.

   You can also perform the following operations:

   • Click Mapping & Filtering on the right side of the page to customize the column names after synchronization to the target data source.
   • On the Mapping & Filtering page, enter a comparison expression in the text box below Data Filter as the filtering condition. Only data that meets the filtering condition is synchronized to the target data source. For example, if the filtering condition is set to emp_no>=10005, data whose emp_no column value is less than 10005 is not synchronized to the target data source.
   • Click the icon to the right of "Target Table" to search for a table name and replace it with the target name.
   • Enter a table name in the Search Table text box in the upper-right corner to quickly locate the target table.
   • Click Batch Configuration in the upper-right corner to define common rules in batches, such as table name and column name case conversion, prefix or suffix addition, and replacement, so that mapping configuration can be applied uniformly to a large number of tables and columns.

• Click the drop-down menu to the right of Object Owner to specify the owner of the object. If you do not select an owner, An account with the same name as schema is used by default.

7. On the Pre-check tab, wait for the system to complete the precheck. After the precheck is passed, click Launch.

   • You can select Enable data consistency comparison. After the synchronization task is complete, a data consistency comparison task based on the source data source automatically starts to ensure data consistency between both ends. Based on the selected Type, Enable data consistency comparison starts at the following times:

     • Schema: Starts after schema replication is complete.
     • Schema+Full: Starts after full replication is complete.
     • Full: Starts after full replication is complete.
     • Schema+Full+Incremental, Incremental: Starts when incremental data is consistent with the source data source for the first time and Delay is 0 seconds. You can click View Details and view the synchronization delay on the Details page.

   • If the precheck fails, click Details in the Actions column on the right of the failed check item, troubleshoot the cause, manually fix the issue, and then click Check Again to run the precheck again until it passes.

   • Check items whose Result is Warning can be fixed or ignored depending on the situation.

8. On the Launch page, the Launch Successfully prompt appears, indicating that the synchronization task has started. You can then perform the following operations:

   • Click View Details to view the execution status of each stage of the synchronization task.

   • Click Back to list to return to the Replication task list page.

1. Log in to the NineData Console.

2. Click on Replication in the left navigation bar.

3. On the Replication page, click on Create Replication.

4. On the Source & Target tab, configure according to the table below and click on Next.

   Parameter	Description
   Name	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.
   Source	The data source where the synchronization object is located.
   Target	The data source that receives the synchronization object.
   Type	Choose the content to be replicated to the target data source. Schema: Only synchronize the database table structure of the source data source, without synchronizing data. Full: Synchronize all objects and data of the source data source, that is, full data replication. Incremental: After the full synchronization is completed, perform incremental synchronization based on the logs of the source data source.
   If target table already exists（Required when Schema is selected）	Pre-Check Error and Stop Task: Stop the task when the same name table is detected during the pre-inspection stage. Skip and Continue Task: 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. Delete Objects and Rewrite: 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. Keep Schema and Clear Data, then Rewrite（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.
   Target Table Exists Data（Required when Schema is not selected）	Pre-Check Error and Stop Task: Stop the task when data is detected in the target table during the pre-inspection stage. Ignore existing target data and append to it.: Ignore the data when it is detected in the target table during the pre-inspection stage, and append other data. Clear target existing data before write: Delete the data when it is detected in the target table during the pre-inspection stage, and rewrite it.

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

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

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

   • Including Schema: Configure the table name after the target table is synchronized to the target data source, and click Save and Pre-Check.

     tip

     You can click on Mapping & Filtering 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 Data Filter, 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 "Schema": 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 Pre-check tab, wait for the system to complete the pre-inspection, and after the pre-inspection is passed, click Launch.

   tip

   • You can check Enable data consistency comparison. 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 Type you selected, the timing for starting Enable data consistency comparison is as follows:
     • Schema: Start after the structural replication is completed.
     • Schema+Full, Full: Start after the full replication is completed.
     • Schema+Full+Incremental, Incremental: Start when the incremental data is consistent with the source data source for the first time and Delay is 0 seconds. You can click View Details to view the synchronization delay on the Details page.
   • If the pre-inspection does not pass, you need to click on Details in the Actions column on the right side of the target inspection item to investigate the cause of the failure, manually fix it, and then click Check Again to re-execute the pre-inspection until it passes.
   • If the Result is Warning, you can fix or ignore it according to the specific situation.

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

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

View Synchronization Results

1. Log in to the NineData Console.

2. Click on Replication > Data Replication in the left navigation bar.

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

   

   Number	Function	Description
   1	Sync Delay	The 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.
   2	Configure Alerts	After configuring alerts, the system will notify you in the way you choose when the task fails.
   3	More	Pause: Pause the task, only tasks with Running status are selectable. Duplicate: Create a new replication task with the same configuration as the current task. Terminate: 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: Delete the task. Once the task is deleted, it cannot be recovered, so please proceed with caution.
   4	Structure Replication (displayed in scenarios involving structure replication)	Displays the progress and detailed information of structure replication. Click on Log on the right side of the page: View the execution logs of structure replication. Click on on the right side of the page: View the latest information. Click on View DDL in the Actions column on the right side of the target object in the list: View SQL playback.
   5	Full Replication (displayed in scenarios involving full replication)	Displays the progress and detailed information of full replication. Click on Monitor on the right side of the page: View various monitoring indicators during full replication. During full replication, you can also click on Flow Control Settings 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 Log on the right side of the page: View the execution logs of full replication. Click on on the right side of the page: View the latest information.
   6	Incremental Replication (displayed in scenarios involving incremental replication)	Displays various monitoring indicators of incremental replication. Click on View Threads on the right side of the page: View the operations currently being executed by the current replication task, including: Thread ID: Replication tasks are executed in multiple threads, displaying the current thread number in progress. Execute SQL: Details of the SQL statement currently being executed by the current thread. Response Time: The response time of the current thread. If this value increases, it indicates that the current thread may be stuck for some reason. Event Time: The timestamp when the current thread was started. Status: The status of the current thread. Click on Flow Control Settings 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 Log on the right side of the page: View the execution logs of incremental replication. Click on on the right side of the page: View the latest information.
   7	Modify Object	Displays the modification records of synchronization objects. Click on Modify Objects on the right side of the page to configure the synchronization objects. Click on on the right side of the page: View the latest information.
   8	Data Comparison	Displays the comparison results between the source data source and the target data source. If you have not enabled data comparison, please click on Enable Comparison on the page. Click on Re-compare on the right side of the page: Re-initiate the comparison between the current source and target data sources. Click on Stop 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 Log on the right side of the page: View the execution logs of consistency comparison. Click on Monitor (displayed only in data comparison): View the trend chart of RPS (records per second) comparison. Click on Details to view earlier records. Click on in the Actions column on the right side of the comparison list (displayed under the Data tab only in the case of inconsistency): View details of the comparison between the source and target sides. Click on in the Actions 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.
   9	Expand	Display detailed information of the current replication task. Common Options: Export table configuration: 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. Alert Rules: 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.

Category	MySQL Data Type	PostgreSQL Data Type
Numeric	TINYINT	SMALLINT
	TINYINT UNSIGNED	SMALLINT
	SMALLINT	SMALLINT
	SMALLINT UNSIGNED	INTEGER
	MEDIUMINT	INTEGER
	MEDIUMINT UNSIGNED	INTEGER
	INT	INTEGER
	INT UNSIGNED	BIGINT
	BIGINT	BIGINT
	BIGINT UNSIGNED	BIGINT
	BIT(M)	BIT(N)
	DECIMAL()	DECIMAL
	NUMERIC	DECIMAL
	FLOAT	FLOAT
	DOUBLE	FLOAT8
	BOOL，BOOLEAN	SMALLINT
DATE AND TIME	DATE	DATE
	DATETIME[(fsp)]	TIMESTAMP[(p)]
	TIMESTAMP[(fsp)]	TIMESTAMP[(p)] with time zone
	TIME[(fsp)]	TEXT
	YEAR[(4)]	INTEGER
STRING	CHAR	CHAR[(n)]
	VARCHAR	VARCHAR
	BINARY/VARBINARY	BYTEA
	TINYTEXT/TEXT/MEDIUMTEXT/LONGTEXT	TEXT
	TINYBLOB/BLOB/MEDIUMBOLB/LONGBLOB	BYTEA
	ENUM	VARCHAR
	SET	VARCHAR
JSON	JSON	JSON

Appendix 2: Pre-inspection Item List

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

Related Documents

Introduction to Data Replication