Skip to content
Snippets Groups Projects
Select Git revision
  • fix/dont_save_partition_table_of_mapper_devices
  • fix_11285
  • master default protected
  • debian
  • pristine-tar
  • upstream
  • backupninja_debian/1.0.2-1
  • backupninja_upstream/1.0.2
  • backupninja-1.0.2
  • backupninja_debian/1.0.1-2
  • backupninja_debian/1.0.1-1
  • backupninja_upstream/1.0.1
  • backupninja-1.0.1
  • backupninja_debian/1.0-1
  • backupninja_upstream/1.0
  • backupninja-1.0
  • backupninja_debian/1.0_rc1-1
  • backupninja_upstream/1.0_rc1
  • backupninja-1.0-rc1
  • backupninja_debian/0.9.10-2
  • backupninja_debian/0.9.10-1
  • backupninja_upstream/0.9.10
  • backupninja-0.9.10
  • backupninja_debian/0.9.9-1
  • backupninja-0.9.9
  • backupninja-0.9.8.1
26 results

etc

  • Clone with SSH
  • Clone with HTTPS
  • Forked from Liberate / backupninja
    397 commits behind the upstream repository.
    Jacob Anawalt's avatar
    Jacob Anawalt authored
    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.
    7355535e
    History