PostgreSQL

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. [.term]#-a

Restore only the data, not the schema (data definitions). Table data, large objects, and sequence values are restored, if present in the archive.
This option is similar to, but for historical reasons not identical to, specifying --section=data. [.term]#-c

Clean (drop) database objects before recreating them. (Unless --if-exists is used, this might generate some harmless error messages, if any objects were not present in the destination database.) [.term]#-C

Create the database before restoring into it. If --clean is also specified, drop and recreate the target database before connecting to it.
When this option is used, the database named with -d is used only to issue the initial DROP DATABASE and CREATE DATABASE commands. All data is restored into the database name that appears in the archive. [.term]#`-d +`_`+dbname`_

Connect to database `dbname and restore directly into the database. The dbname can be a connection string. If so, connection string parameters will override any conflicting command line options. [.term]#-e`

Exit if an error is encountered while sending SQL commands to the database. The default is to continue and to display a count of errors at the end of the restoration. [.term]#`-f +`_`+filename`_

Specify output file for generated script, or for the listing when used with -l. Use - for the standard output, which is also the default. [.term]#`-F +`_`+format`_

Specify format of the archive. It is not necessary to specify the format, since pg_restore will determine the format automatically. If specified, it can be one of the following: + [.term]#c

Restore definition of named index only. Multiple indexes may be specified with multiple -I switches. [.term]#`-j +`_`+number-of-jobs`_

Run the most time-consuming parts of pg_restore — those which load data, create indexes, or create constraints — using multiple concurrent jobs. This option can dramatically reduce the time to restore a large database to a server running on a multiprocessor machine.
Each job is one process or one thread, depending on the operating system, and uses a separate connection to the server.
The optimal value for this option depends on the hardware setup of the server, of the client, and of the network. Factors include the number of CPU cores and the disk setup. A good place to start is the number of CPU cores on the server, but values larger than that can also lead to faster restore times in many cases. Of course, values that are too high will lead to decreased performance because of thrashing.
Only the custom and directory archive formats are supported with this option. The input must be a regular file or directory (not, for example, a pipe). This option is ignored when emitting a script rather than connecting directly to a database server. Also, multiple jobs cannot be used together with the option --single-transaction. [.term]#-l

List the table of contents of the archive. The output of this operation can be used as input to the -L option. Note that if filtering switches such as -n or -t are used with -l, they will restrict the items listed. [.term]#`-L +`_`+list-file`_

Restore only those archive elements that are listed in `list-file, and restore them in the order they appear in the file. Note that if filtering switches such as `-n or -t are used with -L, they will further restrict the items restored.
`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. [.term]#`-n +`_`+schema`_

Restore only objects that are in the named schema. Multiple schemas may be specified with multiple -n switches. This can be combined with the -t option to restore just a specific table. [.term]#`-N +`_`+schema`_

Do not restore objects that are in the named schema. Multiple schemas to be excluded may be specified with multiple -N switches.
When both -n and -N are given for the same schema name, the -N switch wins and the schema is excluded. [.term]#-O

Do not output commands to set ownership of objects to match the original database. By default, pg_restore issues ALTER OWNER or SET SESSION AUTHORIZATION statements to set ownership of created schema elements. These statements will fail unless the initial connection to the database is made by a superuser (or the same user that owns all of the objects in the script). With -O, any user name can be used for the initial connection, and this user will own all the created objects. [.term]#`-P +`_`+function-name(argtype [, ...])`_

Restore the named function only. Be careful to spell the function name and arguments exactly as they appear in the dump file’s table of contents. Multiple functions may be specified with multiple -P switches. [.term]#-R

This option is obsolete but still accepted for backwards compatibility. [.term]#-s

Restore only the schema (data definitions), not data, to the extent that schema entries are present in the archive.
This option is the inverse of --data-only. It is similar to, but for historical reasons not identical to, specifying --section=pre-data --section=post-data.
(Do not confuse this with the --schema option, which uses the word “[.quote]#schema”# in a different meaning.) [.term]#`-S +`_`+username`_

Specify the superuser user name to use when disabling triggers. This is relevant only if --disable-triggers is used. [.term]#`-t +`_`+table`_

Restore definition and/or data of only the named table. For this purpose, “[.quote]#table”# includes views, materialized views, sequences, and foreign tables. Multiple tables can be selected by writing multiple -t switches. This option can be combined with the -n option to specify table(s) in a particular schema. + [NOTE] ==== ==== Note

When `+-t+` is specified, pg_restore makes no attempt to restore any other database objects that the selected table(s) might depend upon. Therefore, there is no guarantee that a specific-table restore into a clean database will succeed.
====
+
[NOTE]
====
==== Note

This flag does not behave identically to the `+-t+` flag of pg_dump. There is not currently any provision for wild-card matching in pg_restore, nor can you include a schema name within its `+-t+`.
====
+
[NOTE]
====
==== Note

  In versions prior to PostgreSQL 9.6, this flag matched only tables, not any other type of relation.
  ====
[.term]#`+-T +`_`+trigger+`_ +

Restore named trigger only. Multiple triggers may be specified with multiple -T switches. [.term]#-v

Specifies verbose mode. [.term]#-V

Print the pg_restore version and exit. -x
#[.term]--no-privileges

Prevent restoration of access privileges (grant/revoke commands). [.term]#-1

Execute the restore as a single transaction (that is, wrap the emitted commands in BEGIN/COMMIT). This ensures that either all the commands complete successfully, or no changes are applied. This option implies --exit-on-error.

This option is relevant only when performing a data-only restore. It instructs pg_restore to execute commands to temporarily disable triggers on the target tables while the data is reloaded. Use this if you have referential integrity checks or other triggers on the tables that you do not want to invoke during data reload. + Presently, the commands emitted for --disable-triggers must be done as superuser. So you should also specify a superuser name with -S or, preferably, run pg_restore as a PostgreSQL superuser.

This option is relevant only when restoring the contents of a table which has row security. By default, pg_restore will set row_security to off, to ensure that all data is restored in to the table. If the user does not have sufficient privileges to bypass row security, then an error is thrown. This parameter instructs pg_restore to set row_security to on instead, allowing the user to attempt to restore the contents of the table with row security enabled. This might still fail if the user does not have the right to insert the rows from the dump into the table. + Note that this option currently also requires the dump be in INSERT format, as COPY FROM does not support row security.

Use conditional commands (i.e., add an IF EXISTS clause) when cleaning database objects. This option is not valid unless --clean is also specified.

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. + This option is effective only when restoring directly into a database, not when producing SQL script output.

Do not output commands to restore publications, even if the archive contains them.

Do not output commands to restore security labels, even if the archive contains them.

Do not output commands to restore subscriptions, even if the archive contains them.

Do not output commands to select tablespaces. With this option, all objects will be created in whichever tablespace 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. + The data section contains actual table data as well as large-object definitions. Post-data items consist of definitions of indexes, triggers, rules and constraints other than validated check constraints. Pre-data items consist of all other data definition items.

Require that each schema (-n/--schema) and table (-t/--table) qualifier match at least one schema/table in the backup file.

Output SQL-standard SET SESSION AUTHORIZATION commands instead of ALTER OWNER commands to determine object ownership. This makes the dump more standards-compatible, but depending on the history of the objects in the dump, might not restore properly. [.term]#-?

Show help about pg_restore command line arguments, and exit.