PostgreSQL

A PostgreSQL schedule imports a SQL backup into the exact PostgreSQL version you select, then evaluates the configured gates.

Available versions

Configure the restore

Use a plain SQL dump, optionally wrapped in one of the supported artifact layouts. pg_dump custom (-Fc), directory (-Fd), and native tar (-Ft) formats are not supported. Automatic detection does not convert them to SQL.

1. 1

   Select PostgreSQL and a version

   In the schedule's database step, select PostgreSQL and the exact version that matches the backup producer.

2. 2

   Describe the backup layers

   The dump format is SQL. Choose automatic detection or enforce the container and compression. Supported containers are none, tar, and ZIP; supported compression options are listed in Database restores.

3. 3

   Add decryption settings

   If required, select a ZIP password or age secret metadata entry. The corresponding Kubernetes Secret must exist in the selected worker's job namespace.

4. 4

   Choose the target database

   Enter a target database name when the check must import into a specific name. If left empty, RestoreTrust uses restoretrust_restore.

5. 5

   Define success

   Require a successful import, then add SQL probes whose first result value can be compared as a boolean, integer, or string. Add download, restore, or probe duration gates where they represent your recovery objective.

Useful probes test facts that should remain stable enough to be meaningful: a minimum row count in a critical table, the presence of a migration marker, or a known invariant. Keep queries read-only and avoid returning secrets or personal data.

The import runs under a temporary role without superuser privileges. Dumps requiring superuser-only constructs, such as event triggers or extensions outside the validator's allowlist, are rejected. Client meta-commands are restricted as well. Review the restore log if an otherwise valid SQL dump depends on privileges or extensions unavailable in the validation environment.

Start a manual run, then review the restore log and probe results before enabling notifications or relying on recurring checks.