pg_dump

Dump a database

$ pg_dump [database_name] > [backup.sql]

$ pg_dump -Fc [database_name] > [backup.dump]

$ pg_dump -t [table_name] [database_name] > [table.sql]

$ pg_dump -s [database_name] > [schema.sql]

$ pg_dump -a [database_name] > [data.sql]

$ pg_dump -h [host] -p [5432] -U [username] [database_name] > [backup.sql]

$ pg_dump -Fd -j [4] [database_name] -f [backup_dir]

$ pg_dump --exclude-table=[pattern] [database_name] > [backup.sql]

pg_dump [options] [dbname]

pg_dump is a utility for backing up PostgreSQL databases. It creates a consistent snapshot of the database at the time the dump begins, even while the database is being used.
The output can be in SQL script format (plain text) or custom archive formats that support compression and parallel restore. SQL scripts can be restored with psql, while archive formats use pg_restore.
pg_dump does not block readers or writers during the dump, making it suitable for production backups.

-F format

Output format (p=plain, c=custom, d=directory, t=tar).

Output file or directory.

Dump specific table(s).

Exclude table(s).

Dump specific schema(s).

Exclude schema(s).

Dump schema only, no data.

Dump data only, no schema.

Include DROP commands.

Include CREATE DATABASE command.

Parallel dump jobs (directory format).

Database server host.

Database server port.

Connect as user.

Force password prompt.

Compression level (0-9).

Does not dump roles and tablespaces (use pg_dumpall). Plain format cannot be restored in parallel. Custom format recommended for large databases. May require significant disk space for large databases.

pg_dump has been part of PostgreSQL since its earliest releases, evolving from the original POSTGRES project at UC Berkeley in the 1980s. It has gained features like parallel dump, custom archive format, and selective backup options as PostgreSQL evolved into a major database system.

pg_restore(1), pg_dumpall(1), psql(1), createdb(1)