The restore backup ParadeDB command re-creates a database from a ParadeDB-generated dump file using pg_restore or psql.
It rebuilds all tables, indexes, extensions, and data in a target database from a ParadeDB backup file (.dump or .sql). The operation is transaction-safe, letting you fully recover or clone environments.
Use pg_restore
for custom/tar backups and psql
for plain SQL files. Both honor ParadeDB objects because ParadeDB is extension-compatible with PostgreSQL.
Create the empty database and install ParadeDB before restoring.Example: CREATE DATABASE shop_clone;
then CREATE EXTENSION paradedb;
.
See the next section for the full command reference, including options for roles, schemas, and parallelism.
1. Copy shop.dump
to the server.
2. Run pg_restore
with the --clean
and --create
flags if you want a one-shot rebuild.
3.Verify counts with simple SELECTs on Customers
, Orders
, and Products
.
• Restore into a staging DB first.
• Use --jobs
to speed up large ecommerce datasets.
• Always enable --if-exists
to avoid errors if objects are missing.
Skipping the ParadeDB extension or forgetting to drop active connections will abort the restore. Details follow after the syntax block.
.
Yes. Use --create
to let pg_restore make the new database or manually create it before running the command.
No extra flags are needed. ParadeDB objects are standard PostgreSQL extension objects preserved in the dump.
Use --jobs
with a number equal to CPU cores and ensure your backup was made with -Fc
format.