Jacob Anawalt authored 14 years ago and intrigeri committed 14 years ago

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.

... so that this option can be disabled on systems that don't support it.
This also allows to use another compression program, such as pbzip2 on SMP
machines (closes Roundup bug #2405).

... for rdiff.helper, dup.helper, example.dup and example.rdiff.

... instead of previous /var/backups/duplicity.

This is the only way to securely transmit the FTP password from backupninja
to duplicity.

I'd love to use "dpkg --compare-versions" but we don't want backupninja to be
Debian-specific. Any similar tool?

Signed-off-by: intrigeri <intrigeri@boum.org>

This is necessary to get rid of unnecessary old cache files when cleaning up,
when using duplicity >=0.6.01 that depends on local caching.

Closes: #572721