Do not output commands to select tablespaces. With this option, all objects will be created in whichever tablespace is the default during restore. --section= sectionname

Specify output file for generated script, or for the listing when used with -l. Use - for stdout. -F format

list-file is normally created by editing the output of a previous -l operation. Lines can be moved or removed, and can also be commented out by placing a semicolon ( ;) at the start of the line. See below for examples. -n schema Do not dump any tables matching pattern. The pattern is interpreted according to the same rules as for -t. -T can be given more than once to exclude tables matching any of several patterns. Semicolons start a comment, and the numbers at the start of lines refer to the internal archive ID assigned to each item. Do not output commands to select table access methods. With this option, all objects will be created with whichever table access method is the default during restore.

Only restore the named section. The section name can be pre-data, data, or post-data. This option can be specified more than once to select multiple sections. The default is to restore all sections. This option is ignored when emitting an archive (non-text) output file. For the archive formats, you can specify the option when you call pg_restore. -e patternSpecify the superuser user name to use when disabling triggers. This is relevant only if --disable-triggers is used. -t table Do not confuse this with the --schema option, which uses the word “ schema” in a different meaning.) Each job is one process or one thread, depending on the operating system, and uses a separate connection to the server. Specifies the location of the archive file (or directory, for a directory-format archive) to be restored. If not specified, the standard input is used. -a

Do not output commands to select table access methods. With this option, all objects will be created with whichever access method is the default during restore. --no-tablespaces Do not dump data for any tables matching pattern. The pattern is interpreted according to the same rules as for -t. --exclude-table-data can be given more than once to exclude tables matching any of several patterns. This option is useful when you need the definition of a particular table even though you do not need the data in it. Output a directory-format archive suitable for input into pg_restore. This will create a directory with one file for each table and large object being dumped, plus a so-called Table of Contents file describing the dumped objects in a machine-readable format that pg_restore can read. A directory format archive can be manipulated with standard Unix tools; for example, files in an uncompressed archive can be compressed with the gzip, lz4, or zstd tools. This format is compressed by default using gzip and also supports parallel dumps. t Output commands to DROP all the dumped database objects prior to outputting the commands for creating them. This option is useful when the restore is to overwrite an existing database. If any of the objects do not exist in the destination database, ignorable error messages will be reported during restore, unless --if-exists is also specified. pg_dump will open njobs + 1 connections to the database, so make sure your max_connections setting is high enough to accommodate all connections.By default, table data is restored even if the creation command for the table failed (e.g., because it already exists). With this option, data for such a table is skipped. This behavior is useful if the target database already contains the desired table contents. For example, auxiliary tables for PostgreSQL extensions such as PostGIS might already be loaded in the target database; specifying this option prevents duplicate or obsolete data from being loaded into them. When a data-only dump is chosen and the option --disable-triggers is used, pg_dump emits commands to disable triggers on user tables before inserting the data, and then commands to re-enable them after the data has been inserted. If the restore is stopped in the middle, the system catalogs might be left in the wrong state. For the custom and directory archive formats, this specifies compression of individual table-data segments, and the default is to compress using gzip at a moderate level. For plain text output, setting a nonzero compression level causes the entire output file to be compressed, as though it had been fed through gzip, lz4, or zstd; but the default is not to compress. With zstd compression, long mode may improve the compression ratio, at the cost of increased memory use. The database named in the -d switch can be any database existing in the cluster; pg_restore only uses it to issue the CREATE DATABASE command for mydb. With -C, data is always restored into the database name that appears in the dump file. Add ON CONFLICT DO NOTHING to INSERT commands. This option is not valid unless --inserts, --column-inserts or --rows-per-insert is also specified. --quote-all-identifiers

Specify the superuser user name to use when disabling triggers. This is relevant only if --disable-triggers is used. (Usually, it's better to leave this out, and instead start the resulting script as superuser.) -t pattern

This option is ignored when emitting an archive (non-text) output file. For the archive formats, you can specify the option when you call pg_restore. -R