aboutsummaryrefslogtreecommitdiff
path: root/etc
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 /etc
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 'etc')
-rw-r--r--etc/backupninja.conf.in1
1 files changed, 1 insertions, 0 deletions
diff --git a/etc/backupninja.conf.in b/etc/backupninja.conf.in
index dee9fff..7e3d347 100644
--- a/etc/backupninja.conf.in
+++ b/etc/backupninja.conf.in
@@ -83,6 +83,7 @@ vservers = no
# MYSQL=/usr/bin/mysql
# MYSQLHOTCOPY=/usr/bin/mysqlhotcopy
# MYSQLDUMP=/usr/bin/mysqldump
+# PSQL=/usr/bin/psql
# PGSQLDUMP=/usr/bin/pg_dump
# PGSQLDUMPALL=/usr/bin/pg_dumpall
# GZIP=/bin/gzip