Skip to main content
pg_dump and pg_restore have to be on your Mac first. TablePro shells out to them and ships no copy of its own:
The lookup takes the first match from /usr/bin/which, then /opt/homebrew/bin, /usr/local/bin, and Postgres.app’s latest version. That path decides which client version does the work.
PostgreSQL and Redshift only. For any other engine, use a SQL export from Import & Export. Restore is disabled on a read-only Safe Mode connection; backup is not, because it writes nothing to the database.
Backup Dump sheet

The Backup Dump sheet with its format and scope options

​
Backup dump

1

Start the dump

Choose File > Backup Dump… on a connected session and pick the database.
2

Choose where to save it

The default filename is <database>-<yyyy-MM-dd-HHmmss>.dump. Dumps use the custom archive format (pg_dump -Fc), which is what pg_restore reads back.
3

Watch the byte counter

Cancel confirms, sends SIGTERM, and removes the partial file. On success the result sheet gives the size and Show in Finder.

​
Restore dump

1

Pick the dump file

Choose File > Restore Dump… and select a file pg_dump wrote in custom archive format.
2

Pick the target database

pg_restore runs with --no-owner --no-acl, so the connection user ends up owning the restored objects.
3

Wait it out

Restore shows no percentage. Cancel confirms and sends SIGTERM, and the target database is left as it stands: drop it and restore into a fresh one, or clean up the partial objects yourself.
No --clean is passed, so restoring on top of a schema that already holds conflicting objects produces errors instead of replacing them.

​
SSH tunnels and SSL

Both flows reuse the connection’s active SSH tunnel, with no second port forward. SSL connections pass their mode to the tools through PGSSLMODE, verify-ca and verify-full included.

​
Failures

A non-zero exit shows the last 64 KB of pg_dump or pg_restore stderr in a scrollable monospaced view. Three causes account for most of them.