aboutsummaryrefslogtreecommitdiff
path: root/examples/example.pgsql
diff options
context:
space:
mode:
authorJacob Anawalt <jlanawalt@gmail.com>2010-10-11 18:53:00 -0600
committerintrigeri <intrigeri@boum.org>2010-10-12 10:49:34 +0200
commit7355535ee18efc472f5a598b8474e8d05765d6f1 (patch)
tree8b7f48baa35b014974d2eaaf6f4d2e109264f2ce /examples/example.pgsql
parentcc35262c2a0a8153e7bbecef1af02ddf12869254 (diff)
downloadbackupninja-7355535ee18efc472f5a598b8474e8d05765d6f1.tar.gz
backupninja-7355535ee18efc472f5a598b8474e8d05765d6f1.tar.bz2
Enable pg_dump format option.
The format option of pg_dump enables tar and custom archive file formats in addition to the default plain-text file containing SQL commands. When either the tar or custom format are selected the behaviour of database=all is changed to no longer dump a single file via pg_dumpall. Instead pg_dumpall is called once to export the "global" data (roles & tablespaces) and then pg_dump is called once for each non-template table in the database. To support the GZIP and GZIP_OPTS variables in backupninja and to give the default --rsyncable gzip compression flag a chance at working on a PostgreSQL backup, the custom output is forced to not use compression. Instead compression is done via a pipe to gzip. Hopefully this benefits rsync and rdiff-backup style backups for reduced backup and storage costs that outweigh the restoration ones.
Diffstat (limited to 'examples/example.pgsql')
-rw-r--r--examples/example.pgsql13
1 files changed, 13 insertions, 0 deletions
diff --git a/examples/example.pgsql b/examples/example.pgsql
index 42f045e..5a4e02f 100644
--- a/examples/example.pgsql
+++ b/examples/example.pgsql
@@ -17,6 +17,19 @@
# compress = < yes | no > (default = yes)
# if yes, compress the pg_dump/pg_dumpall output.
+# format = < plain | tar | custom > (default = plain)
+# plain - Output a plain-text SQL script file with the extension .sql.
+# When dumping all databases, a single file is created via pg_dumpall.
+# tar - Output a tar archive suitable for input into pg_restore. More
+# flexible than plain and can be manipulated by standard Unix tools
+# such as tar. Creates a globals.sql file and an archive per database.
+# custom - Output a custom PostgreSQL pg_restore archive. This is the most
+# flexible format allowing selective import and reordering of database
+# objects at the time the database is restored via pg_restore. This
+# option creates a globals.sql file containing the cluster role and
+# other information dumped by pg_dumpall -g and a pg_restore file
+# per selected database. See the pg_dump and pg_restore man pages.
+
### You can also set the following variables in /etc/backupninja.conf:
# PGSQLDUMP: pg_dump path (default: /usr/bin/pg_dump)
# PGSQLDUMPALL: pg_dumpall path (default: /usr/bin/pg_dumpall)