diff options
author | Jacob Anawalt <jlanawalt@gmail.com> | 2010-10-11 18:53:00 -0600 |
---|---|---|
committer | intrigeri <intrigeri@boum.org> | 2010-10-12 10:49:34 +0200 |
commit | 7355535ee18efc472f5a598b8474e8d05765d6f1 (patch) | |
tree | 8b7f48baa35b014974d2eaaf6f4d2e109264f2ce /examples/example.rsync | |
parent | cc35262c2a0a8153e7bbecef1af02ddf12869254 (diff) | |
download | backupninja-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.rsync')
0 files changed, 0 insertions, 0 deletions