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. --no-toast-compression pg_dump will open njobs + 1 connections to the database, so make sure your max_connections setting is high enough to accommodate all connections. Specify output file for generated script, or for the listing when used with -l. Use - for stdout. -F format Run the most time-consuming steps of pg_restore — those that load data, create indexes, or create constraints — concurrently, using up to number-of-jobs concurrent sessions. This option can dramatically reduce the time to restore a large database to a server running on a multiprocessor machine. This option is ignored when emitting a script rather than connecting directly to a database server. 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.

Do not output commands to set TOAST compression methods. With this option, all columns will be restored with the default compression setting. --no-unlogged-table-data 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. --disable-triggers This option is similar to, but for historical reasons not identical to, specifying --section=data. -b

pg_restore can operate in two modes. If a database name is specified, pg_restore connects to that database and restores archive contents directly into the database. Otherwise, a script containing the SQL commands necessary to rebuild the database is created and written to a file or standard output. This script output is equivalent to the plain text output format of pg_dump. Some of the options controlling the output are therefore analogous to pg_dump options. This option is useful when needing to synchronize the dump with a logical replication slot (see Chapter49) or with a concurrent session. 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. -R

Do not output commands to restore comments, even if the archive contains them. --no-data-for-failed-tables Send output to the specified file. This parameter can be omitted for file based output formats, in which case the standard output is used. It must be given for the directory output format however, where it specifies the target directory instead of a file. In this case the directory is created by pg_dump and must not exist before. -F format Each job is one process or one thread, depending on the operating system, and uses a separate connection to the server.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

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. -d dbname 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. Thaw the vial by gentle agitation in a 37°C water bath. To reduce the possibility of contamination, keep the O-ring and cap out of the water. Thawing should be rapid (approximately 2 minutes).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. Do not output commands to select tablespaces. With this option, all objects will be created in whichever tablespace is the default during restore. Restore only the data, not the schema (data definitions). Table data, large objects, and sequence values are restored, if present in the archive. The dump file produced by pg_dump does not contain the statistics used by the optimizer to make query planning decisions. Therefore, it is wise to run ANALYZE after restoring from a dump file to ensure optimal performance; see Section25.1.3 and Section25.1.6 for more information.