Backup

Top  Previous  Next

The backup and restore dialog can be launched from several locations and can be used to
backup the entire database, a schema or a table.

 

LA uses the pg_dump program to implement it's backups.

 

 

The plain option outputs plain-text SQL script file

The tar option outputs a tar archive suitable for input into pg_restore.

The compressed option outputs a compressed file suitabl for input into pg_restore.

 

Blobs


Include large objects in the dump. A non-text output format must be selected.

 

Insert Commands


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.

 

Column Insert Commands


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. Also, while this option generates errors for invalid data, it allows other INSERTs to continue loading data into the table.

 

With OIDs


Dump object identifiers (OIDs) as part of the data 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.

 

Disable $ Quoting


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

 

Verbose Messages


Specifies verbose mode.

This will cause pg_dump to output detailed object comments and start/stop times to the dump file, and progress messages to standard error.

 

Only Data


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

For the archive formats, you may specify the option when you call pg_restore.

 

Only Schema


Dump the contents of schema only. If this option  is  not  specified,  all  non-system schemas in the target database will be dumped. Note:  In  this mode, pg_dump makes no attempt to dump any other database objects that objects in the selected schema may depend upon. Therefore, there is no guarantee  that the results of a single-schema dump can be successfully

restored by themselves into a clean database.

 

No Owner


Do not output commands to set ownership of objects to match the original database.  By default,  pg_dump  issues  ALTER  OWNER or 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 -O.

This option is only meaningful for the plain-text format. For the archive formats, you may specify the option when you call pg_restore.

 

Disable Trigger


This option is only relevant when creating a data-only dump.  It instructs  pg_dump  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 --disable-triggers must be

done as superuser. So, you should also specify a superuser  name with  -S, or preferably be careful to start the resulting script

as a superuser.  This option is only meaningful for the  plain-text  format.  For

the  archive  formats,  you may specify the option when you call pg_restore.

 

See also:


PG_DUMP