Send output to the required file. This parameter may be omitted for file dependent output formats, in which situation the standard output is used.
In the case of a parallel dump, the snapshot identify outlined by this feature is applied rather than using a different snapshot.
Output SQL-regular SET SESSION AUTHORIZATION instructions in lieu of ALTER proprietor commands to determine object ownership. This can make the dump extra requirements-appropriate, but dependant upon the record of your objects in the dump, might not restore effectively.
Output a Listing-format archive suitable for enter into pg_restore. this tends to make a Listing with 1 file for each table and enormous object being dumped, as well as a so-identified as Table of Contents file describing the dumped objects within a equipment-readable structure that pg_restore can read through.
If no compression degree is specified, the default compression level might be utilized. If just a level is specified without mentioning an algorithm, gzip compression will probably be employed if the level is greater than 0, and no compression will be utilized if the level is 0.
When dumping reasonable replication subscriptions, pg_dump will generate develop membership commands that make use of the connect = Phony possibility, so that check here restoring the subscription will not make distant connections for creating a replication slot or for Preliminary table duplicate. like that, the dump can be restored with no demanding community use of the distant servers. It is then up into the person to reactivate the subscriptions in a suitable way.
parameter is interpreted being a pattern based on the exact regulations utilized by psql's \d instructions (see designs), so various schemas will also be selected by creating wildcard characters within the pattern.
. The pattern is interpreted according to the exact same policies as for -n. -N may be given in excess of at the time to exclude schemas matching any of quite a few designs.
For that reason every other usage of the table won't be granted either and may queue following the exceptional lock request. This includes the worker course of action endeavoring to dump the table. with none safety measures This might be considered a classic deadlock scenario. To detect this conflict, the pg_dump worker procedure requests Yet another shared lock utilizing the NOWAIT option. Should the employee process is not granted this shared lock, any individual else need to have asked for an unique lock in the meantime and there is no way to continue with the dump, so pg_dump has no alternative but to abort the dump.
With zstd compression, extended method may well Increase the compression ratio, at the price of improved memory use.
+ 1 connections towards the databases, so ensure that your max_connections setting is substantial adequate to accommodate all connections.
When the person does not have ample privileges to bypass row security, then an error is thrown. This parameter instructs pg_dump to set row_security to on as an alternative, allowing the user to dump the elements of the contents of the desk that they have got usage of.
If you see anything in the documentation that is not right, would not match your knowledge with the particular characteristic or requires more clarification, please use this form to report a documentation concern.
. The timeout could be laid out in any of your formats approved by established statement_timeout. (permitted formats change based on the server Model that you are dumping from, but an integer variety of milliseconds is accepted by all versions.)
That is the same as the -t/--table possibility, except that In addition it involves any partitions or inheritance little one tables in the desk(s) matching the sample
When working with wildcards, be careful to quote the pattern if desired to forestall the shell from expanding the wildcards; see Examples below.