Specifies a role identify to be used to develop the dump. This option brings about pg_dump to concern a SET part rolename
parameter is interpreted like a pattern in accordance with the similar principles employed by psql's \d commands (see Patterns), so many international servers can also be selected by composing wildcard people inside the pattern.
Output a personalized-structure archive ideal for input into pg_restore. along with the directory output structure, this is among the most versatile output structure in that it makes it possible for guide collection and reordering of archived goods throughout restore. This format is likewise compressed by default.
With zstd compression, extensive mode could Enhance the compression ratio, at the expense of elevated memory use.
Observe that if you use this feature now, you most likely also want the dump be in INSERT structure, because the COPY FROM for the duration of restore doesn't support row protection.
Dump information as INSERT instructions (instead of duplicate). This will make restoration really sluggish; it is principally useful for creating dumps which might be loaded into non-PostgreSQL databases. Any error in the course of restoring will result in only rows which can be part of the problematic INSERT to be missing, rather than the entire desk contents.
tend not to wait around for good to amass shared desk locks firstly of the dump. rather fail if not able to lock a table within the specified timeout
To conduct a parallel dump, the databases server has to support synchronized snapshots, a element which was released in PostgreSQL 9.2 for Major servers and 10 for standbys. using this feature, database consumers can assure they see a similar data set Despite the fact that they use unique connections.
If the thing is anything in the documentation that isn't right, doesn't match your practical experience with the particular feature or calls for more clarification, make sure you use this manner to report a documentation problem.
pressure quoting of all identifiers. this feature is suggested when dumping a databases from the server whose PostgreSQL key version differs from pg_dump's, or when the output is intended to be loaded right into a server of a special key version.
mail output to the required file. This parameter might be omitted for file based mostly output formats, in which situation the normal output is used.
will not output commands to pick out table obtain techniques. With this selection, all objects will likely be produced with whichever table obtain method would be the default for the duration of restore.
Also, It's not at all guaranteed that pg_dump's output may be loaded into a server of an older big Edition — not whether or not the dump was taken from the server of that Model. Loading a dump file into an older server may well demand guide enhancing on the dump file to remove syntax not understood via the more สล็อตแตกง่าย mature server. Use from the --quotation-all-identifiers alternative is suggested in cross-Edition instances, as it could prevent complications arising from various reserved-phrase lists in various PostgreSQL versions.
Specify the compression approach and/or even the compression stage to work with. The compression approach is often established to gzip, lz4, zstd, or none for no compression. A compression detail string can optionally be specified.
for that personalized and directory archive formats, this specifies compression of specific desk-information segments, and the default is to compress working with gzip in a reasonable level. For basic textual content output, location a nonzero compression amount results in your complete output file to be compressed, as though it had been fed by gzip, lz4, or zstd; however the default is to not compress.
This option is suitable only when dumping the contents of a table which has row stability. By default, pg_dump will established row_security to off, in order that all knowledge is dumped from the table.