Moving and restoring a cluster PostgreSQL

• Can I restore a cluster backup to a running Managed Service for PostgreSQL instance in a different cloud network?

• Can I change the retention period of automatic backups?

• Do I need the wal2json plugin if there is only data replication and no copying?

• Can I make a local dump of a database backup?

• How do I move a local PostgreSQL database dump to Yandex Cloud?

• Why can a data transfer through creating and restoring a logical dump fail with an error?

• What should I do if I get the replication slot already exists error when performing logical replication?

Can I restore a cluster backup to a running Managed Service for PostgreSQL instance in a different cloud network?Can I restore a cluster backup to a running Managed Service for PostgreSQL instance in a different cloud network?

You can only recover a cluster from a backup within a single cloud network.

To migrate data between cloud networks, follow the migration guide.

Can I change the retention period of automatic backups?Can I change the retention period of automatic backups?

When creating or modifying a cluster, you can set the retention period for automatic backups.

Do I need the wal2json plugin if data is only replicated but not copied?Do I need the wal2json plugin if data is only replicated but not copied?

Yes, you need the plugin even if you do not copy data.

Can I make a local dump of a database backup?Can I make a local dump of a database backup?

You cannot use the service to make a local dump of a DB backup from Yandex Cloud but you can use the pg_dump utility.

How do I move a local PostgreSQL database dump to Yandex Cloud?How do I move a local PostgreSQL database dump to Yandex Cloud?

Follow the steps described in Migrating databases.

Why does a data transfer through creating and restoring a logical dump fail with an error?Why does a data transfer through creating and restoring a logical dump fail with an error?

Restoring a logical dump may fail with one of the following errors:

• ERROR: role "<source_username>" does not exist
• ERROR: must be member of role "<source_username>"

The errors occur because the target cluster does not have the user (or the privileges of the user) who created the logical dump in the source cluster.

To resolve the errors:

1. In the target cluster, add a user with access to the migrated database and the same name as the user who created the logical dump in the source cluster.
2. Use this user to restore the logical dump or grant their privileges to the user who is restoring the logical dump.

What should I do if I get the error when performing logical replication?What should I do if I get the replication slot already exists error when performing logical replication?

By default, when you create a subscription, a replication slot is also created. The replication slot already exists error means that a replication slot already exists.

You can fix this error by doing one of the following:

1. Link your subscription to an existing replication slot. To do this, add the create_slot = false parameter to the request to create a subscription.
2. Delete the existing replication slot and try creating the subscription again.