REDREDGROUP Document Hub
RDC CloudRelational Database

Import from PostgreSQL

Perform a one-time schema and data import into an empty database.

Before you begin

  • Use a PostgreSQL 12–17 source reachable by the import service through public IPv4. Private and reserved addresses are rejected.
  • Prepare source credentials with permission to read the schema and data.
  • Confirm the destination is empty and any required extensions are available there.
  • Stop application writes to both source and destination for the import window.

The importer copies schema and data, excluding source owners and permissions. It does not copy source roles or provide continuous replication.

Run the import

  1. Open the destination's Data Import section and choose Import from PostgreSQL.
  2. Enter the source hostname, port, database, username, and password.
  3. Configure TLS, an optional TLS server name, and certificate verification. Keep verification enabled for a verifiable source identity.
  4. Confirm that writes are stopped and the destination is empty.
  5. Select Test connection and import.
  6. Wait for the operation to finish, then connect to the destination and validate the schema, records, and application queries before resuming writes.

Limits and failure handling

The archive limit is 512 MiB. Each dump and restore step has a five-minute limit. Existing destination objects are never removed automatically.

A restore error rolls back its restore transaction, but interruption after commit or a later permission-update failure can leave imported data. Inspect the destination before retrying. Do not delete data merely to clear an error without confirming what was imported.

If the source cannot be reached or a required extension is unavailable, correct that condition before submitting another import.

On this page