Migrating data from PostgreSQL to YDB
Managed Service for YDB clusters support real-time data ingestion from PostgreSQL databases. The system will automatically insert this data into YDB tables named after the original schemas and tables.
To start data delivery:
If you no longer need the resources you created, delete them.
Required paid resources
-
Managed Service for PostgreSQL cluster: Computing resources allocated to hosts, storage and backup size (see Managed Service for PostgreSQL pricing).
-
Public IP addresses if public access is enabled for cluster hosts (see Virtual Private Cloud pricing).
-
Managed Service for YDB database (see Managed Service for YDB pricing). The cost depends on deployment mode:
- In serverless mode, you pay for data operations and storage volume, including stored backups.
- In dedicated instance mode, you pay for the use of computing resources allocated to the database, storage size, and backups.
Getting started
Set up your data delivery infrastructure:
- Create a Managed Service for PostgreSQL source cluster using any suitable configuration with publicly accessible hosts.
- Create a Managed Service for YDB database with your preferred 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 your current working directory.This file describes:
- Network.
- Subnet.
- Security group and the rule required for connecting 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: Database 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: Set to0to prevent the automatic creation of a source endpoint and transfer 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 source cluster’s database with your new user account.
-
Populate the database with test data. In this example, we will use a simple table with car sensor information.
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 your Managed Service for YDB database from the list.
-
Service account ID: Select an existing service account or create a new one 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: Managed Service for PostgreSQL cluster you created earlier.
- Database: Name of the database you created in the Managed Service for PostgreSQL cluster.
- User: Name of the user you 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 configured to use the new 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.
-
Make sure that the data from the source Managed Service for PostgreSQL cluster has been transferred to the Managed Service for YDB database:
Management console- In the management console
, select the folder containing your database. - From the list of services, select Managed Service for YDB.
- Select your database from the list.
- Navigate to the Navigation tab.
- Verify that the Managed Service for YDB database contains the
public_sensorstable with 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); -
Verify that the added row’s details have appeared in the Managed Service for YDB database:
Management consoleYDB CLI- In the management console
, select the folder containing your database. - From the list of services, select Managed Service for YDB.
- Select your database from the list.
- Navigate to the Navigation tab.
- Verify that the new data has been added to the
public_sensorstable.
-
Verify that the new data has been added to the
public_sensorstable.ydb table query execute \ --query "SELECT * \ FROM public_sensors"
- In the management console
Delete the resources you created
To reduce the consumption of resources you do not need, delete them:
-
Deactivate and delete the transfer.
-
If you created a service account when setting up 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.
-