Table of Contents
Create Dump [PostgreSQL] Dialog Help
On this page you can select the kind dump output.
- Custom – Create custom-format archive.
- Directory – Create a directory with one file for each table and blob being dumped, plus a so-called Table of Contents file describing the dumped objects in a machine-readable format.
- Excel – Create dump in Excel format.
- SQL – Create a plain-text SQL script file.
- Tar – Create a tar-format archive.
On this page you can select what need to dump.
- Structure Only – Dump only database objects (tables, triggers, functions etc) without data.
- Structure And Records – Dump database objects and stored data.
- Records Only – Dump only data.
- Dump Blobs – Dump blob records.
- Include CREATE DATABASE statement – If ON then the CREATE DATABASE statement will be added to the dump.
- Clean before restore – Clean (drop) database objects prior to outputting the commands for creating them.
- Use column inserts – Dump data as INSERT commands with explicit column names
(INSERT INTO TABLE_NAME (column_name, ...) VALUES ...)
- Use INSET commands – Dump data as INSERT commands (rather than COPY).
- Owner – Dump commands to set ownership of objects.
- Privilege – Dump of access privileges.
- Tablespace – Dump commands to select tablespaces.
- Unlogged table data – Dump the contents of unlogged tables.
- Disable triggers – Include commands to temporarily disable triggers on the target tables while the data is reloaded.
- Disable '$' quoting – Disable the use of dollar quoting for function bodies.
- Use SET SESSION AUTHORIZATION – USE SQL-standard SET SESSION AUTHORIZATION commands instead of ALTER OWNER commands to determine object ownership.
- With OID's – Dump object identifiers (OIDs) as part of the data for every table.
- Verbose – Output detailed object comments and start/stop times to the dump file, and progress messages to standard error.
- Force double quotes on identifiers – Force quoting of all identifiers.