Specifies various behavioral properties of the TPSQLDump.

Syntax:

TDumpOption = (doDataOnly, doIncludeBLOBs, doClean, doCreate, doInserts,
              doColumnInserts, doIgnoreVersion, doOIDs, doNoOwner,
              doSchemaOnly, doVerbose, doNoPrivileges, doDisableDollarQuoting,
              doDisableTriggers, doUseSetSessionAuthorization);
TDumpOptions = set of TDumpOption;
property Options: TDumpOptions;

Description:

Set Options to include the desired properties for the dump. Options is a set drawn from the following values:

doDataOnly

Dump only the data, not the object definitions (schema). This option is only meaningful for the plain-text format.

doIncludeBLOBs

Include large objects in dump.

doClean

Output commands to clean (drop) database objects prior to (the commands for) creating them. This option is only meaningful for the plain-text format.

doCreate

Begin the output with a command to create the database itself and reconnect to the created database. (With a script of this form, it doesn't matter which database you connect to before running the script.) This option is only meaningful for the plain-text format.

doInserts

Dump data as INSERT commands (rather than COPY). This will make restoration very slow; it is mainly useful for making dumps that can be loaded into non-PostgreSQL databases. Note that the restore may fail altogether if you have rearranged column order. The doColumnInserts option is safer, though even slower.

doColumnInserts

Dump data as INSERT commands with explicit column names (INSERT INTO table (column, ...) VALUES ...). This will make restoration very slow; it is mainly useful for making dumps that can be loaded into non-PostgreSQL databases.

doIgnoreVersion

Ignore version mismatch between dump and the database server. TPSQLDump can handle databases from previous releases of PostgreSQL, but very old versions are not supported anymore (currently prior to 7.0). Use this option if you need to override the version check.

doOIDs

Dump object identifiers (OIDs) for every table. Use this option if your application references the OID columns in some way (e.g., in a foreign key constraint). Otherwise, this option should not be used.

doNoOwner

Do not output commands to set ownership of objects to match the original database. By default, TPSQLDump issues SET SESSION AUTHORIZATION statements to set ownership of created database objects.

These statements will fail when the script is run unless it is started by a superuser (or the same user that owns all of the objects in the script). To make a script that can be restored by any user, but will give that user ownership of all the objects, specify doNoOwner.

This option is only meaningful for the plain-text format.

doSchemaOnly

Dump only the object definitions (schema), not data.

doVerbose

Specifies verbose mode. This will cause TPSQLDump to output detailed object comments and start/stop times to the dump file, and progress messages.

doNoPrivileges

Prevent dumping of access privileges (grant/revoke commands).

doDisableDollarQuoting

This option disables the use of dollar quoting for function bodies, and forces them to be quoted using SQL standard string syntax.

doDisableTriggers

This option is only relevant when creating a data-only dump. It instructs TPSQLDump to include 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 doDisableTriggers must be done as superuser. So, you should also specify a SuperUserName property, or preferably be careful to start the resulting script as a superuser.

This option is only meaningful for the plain-text format.

doUseSetSessionAuthorization

Output SQL standard SET SESSION AUTHORIZATION commands instead of OWNER TO commands. This makes the dump more standards compatible, but depending on the history of the objects in the dump, may not restore properly.