Migrating data from PostgreSQL to YDB
A Managed Service for YDB cluster can get data from PostgreSQL databases in real time. This data is automatically added to YDB tables with names of source schemas and tables.
To run data delivery:
If you no longer need the resources you created, delete them.
Required paid resources
The support cost for this solution includes:
-
Managed Service for PostgreSQL cluster fee: Using computing resources allocated to hosts and disk space (see Managed Service for PostgreSQL pricing).
-
Fee for using public IP addresses for cluster hosts (see Virtual Private Cloud pricing).
-
Fee for the Managed Service for YDB database. The charge depends on the usage mode:
- For the serverless mode, you pay for data operations and the amount of stored data.
- For the dedicated instance mode, you pay for the use of computing resources, dedicated DBs, and disk space.
Learn more about the Managed Service for YDB pricing plans.
Getting started
Set up your data pipeline infrastructure:
- Create a Managed Service for PostgreSQL source cluster with any applicable configuration, ensuring its hosts are publicly accessible.
- Create a Managed Service for YDB database in any suitable configuration.
- In the source cluster, create a user and assign them the
mdb_replicationrole.
-
If you do not have Terraform yet, install it.
-
Get the authentication credentials. You can add them to environment variables or specify them later in the provider configuration file.
-
Configure and initialize a provider. There is no need to create a provider configuration file manually, you can download it
. -
Place the configuration file in a separate working directory and specify the parameter values. If you did not add the authentication credentials to environment variables, specify them in the configuration file.
-
Download the data-transfer-mpg-ydb.tf
configuration file to the same working directory.This file describes:
- Network.
- Subnet.
- Security group and the rule permitting access to the Managed Service for PostgreSQL cluster.
- Managed Service for PostgreSQL source cluster.
- PostgreSQL database.
- Managed Service for PostgreSQL user.
- Managed Service for YDB database.
- Source endpoint.
- Transfer.
-
In the
data-transfer-mpg-ydb.tffile, specify the following settings:source_pg_version: PostgreSQL version in the source cluster.source_db_name: DB name in the source cluster.source_user_name: Username for connecting to the source cluster.source_user_password: User password.target_db_name: Managed Service for YDB database name.transfer_enabled: Set0to ensure that no transfer and source endpoint is created before you manually create a target endpoint.
-
Validate your Terraform configuration files using this command:
terraform validateTerraform will display any configuration errors detected in your files.
-
Create the required infrastructure:
-
Run this command to view the planned changes:
terraform planIf you described the configuration correctly, the terminal will display a list of the resources to update and their parameters. This is a verification step that does not apply changes to your resources.
-
If everything looks correct, apply the changes:
-
Run this command:
terraform apply -
Confirm updating the resources.
-
Wait for the operation to complete.
-
All the required resources will be created in the specified folder. You can check resource availability and their settings in the management console
. -
Prepare the source cluster
-
Connect to the database of the source cluster on behalf of the new user.
-
Add test data to the database. In this example, a simple table with information from car sensors is used.
Create a table:
CREATE TABLE public.sensors ( "device_id" text PRIMARY KEY NOT NULL, "datetime" timestamp NOT NULL, "latitude" real NOT NULL, "longitude" real NOT NULL, "altitude" real NOT NULL, "speed" real NOT NULL, "battery_voltage" real, "cabin_temperature" real NOT NULL, "fuel_level" real );Populate the table with data:
INSERT INTO public.sensors VALUES ('iv9a94th6rzt********', '2020-06-05 17:27:00', 55.70329032, 37.65472196, 427.5, 0, 23.5, 17, NULL), ('rhibbh3y08qm********', '2020-06-06 09:49:54', 55.71294467, 37.66542005, 429.13, 55.5, NULL, 18, 32), ('iv9a94th678t********', '2020-06-07 15:00:10', 55.70985913, 37.62141918, 417.0, 15.7, 10.3, 17, NULL);
Set up and activate the transfer
-
-
Database type:
YDB. -
Endpoint parameters:
- Connection settings:
-
Database: Select the Managed Service for YDB database from the list.
-
Service account ID: Select or create a service account with the
ydb.editorrole.
-
- Connection settings:
-
-
Create a source endpoint and transfer:
ManuallyTerraform-
Create an endpoint for the previously created PostgreSQL source with the following settings:
- Database type:
PostgreSQL. - Endpoint parameters:
- Installation type:
Managed Service for PostgreSQL cluster. - Managed Service for PostgreSQL cluster: Created Managed Service for PostgreSQL cluster.
- Database: Name of the DB created in the cluster Managed Service for PostgreSQL.
- User: Name of the user created in the Managed Service for PostgreSQL cluster.
- Password: User password.
- Included tables:
<DB_name>.sensors.
- Installation type:
- Database type:
-
Create a Snapshot and replication-type transfer and configure it to use the previously created endpoints.
-
Activate the transfer.
-
In the
data-transfer-mpg-ydb.tffile, specify the following settings:target_endpoint_id: ID of the target endpoint.transfer_enabled:1to create a source endpoint and a transfer.
-
Validate your Terraform configuration files using this command:
terraform validateTerraform will display any configuration errors detected in your files.
-
Create the required infrastructure:
-
Run this command to view the planned changes:
terraform planIf you described the configuration correctly, the terminal will display a list of the resources to update and their parameters. This is a verification step that does not apply changes to your resources.
-
If everything looks correct, apply the changes:
-
Run this command:
terraform apply -
Confirm updating the resources.
-
Wait for the operation to complete.
-
The transfer will activate automatically upon creation.
-
-
Test the transfer
-
Wait for the transfer status to change to Replicating.
-
Verify that the data has been transferred from the source Managed Service for PostgreSQL cluster to the Managed Service for YDB database:
Management console- In the management console
, select the folder with the DB you need. - From the list of services, select Managed Service for YDB.
- Select the database from the list.
- Navigate to the Navigation tab.
- Make sure the Managed Service for YDB database contains a table named
public_sensorswith the test data.
- In the management console
-
Connect to the Managed Service for PostgreSQL source cluster and populate the
sensorstable with data:INSERT INTO public.sensors VALUES ('iv7b74th678t********', '2020-06-08 17:45:00', 53.70987913, 36.62549834, 378.0, 20.5, 5.3, 20, NULL); -
Check that the Managed Service for YDB database shows information about the added row:
Management consoleYDB CLI- In the management console
, select the folder with the DB you need. - From the list of services, select Managed Service for YDB.
- Select the database from the list.
- Navigate to the Navigation tab.
- Make sure
public_sensorsnow contains the new data.
-
Check that
public_sensorsnow contains the new data:ydb table query execute \ --query "SELECT * \ FROM public_sensors"
- In the management console
Delete the resources you created
Some resources incur charges. To avoid unnecessary expenses, delete the resources you no longer need:
-
Deactivate and delete the transfer.
-
Delete endpoints for the source and target.
-
If you created a service account when creating the target endpoint, delete it.
-
In the terminal window, go to the directory containing the infrastructure plan.
Warning
Make sure the directory has no Terraform manifests with the resources you want to keep. Terraform deletes all resources that were created using the manifests in the current directory.
-
Delete resources:
-
Run this command:
terraform destroy -
Confirm deleting the resources and wait for the operation to complete.
All the resources described in the Terraform manifests will be deleted.
-