# changelog

author: - Marco Nenciarini <marco.nenciarini@2ndquadrant.it> 2.8-1
changelog:
  - New upstream version 2.8
  - Add python3-barman and barman-cli binaries
  - Build with python3 on FC>25 and RHEL>8


author: - Michael Wallace <michael.wallace@enterprisedb.com> 2.12.1-1
changelog:
  - Allow specifying target-tli with other target-* recovery options
  - Fix incorrect NAME in barman-cloud-backup-list manpage
  - Don't raise an error if SIGALRM is ignored
  - Fetch wal_keep_size, not wal_keep_segments, from Postgres 13


author: - Abhijit Menon-Sen <ams@2ndQuadrant.com> 2.13-2
changelog:
  - Add Azure blob storage support to barman-cloud
  - Support tablespace remapping in barman-cloud-restore via
    `--tablespace name:location`
  - Allow barman-cloud-backup and barman-cloud-wal-archive to run as
    Barman hook scripts, to allow data to be relayed to cloud storage
    from the Barman server
  - Stop backups failing due to idle_in_transaction_session_timeout
    (https://github.com/EnterpriseDB/barman/issues/333)
  - Fix a race condition between backup and archive-wal in updating
    xlog.db entries (#328)
  - Handle PGDATA being a symlink in barman-cloud-backup, which led to
    "seeking backwards is not allowed" errors on restore (#351)
  - Recreate pg_wal on restore if the original was a symlink (#327)
  - Recreate pg_tblspc symlinks for tablespaces on restore (#343)
  - Make barman-cloud-backup-list skip backups it cannot read, e.g.,
    because they are in Glacier storage (#332)
  - Add `-d database` option to barman-cloud-backup to specify which
    database to connect to initially (#307)
  - Fix "Backup failed uploading data" errors from barman-cloud-backup
    on Python 3.8 and above, caused by attempting to pickle the boto3
    client (#361)
  - Correctly enable server-side encryption in S3 for buckets that do
    not have encryption enabled by default.

    In Barman 2.12, barman-cloud-backup's `--encryption` option did
    not correctly enable encryption for the contents of the backup if
    the backup was stored in an S3 bucket that did not have encryption
    enabled. If this is the case for you, please consider deleting
    your old backups and taking new backups with Barman 2.13.

    If your S3 buckets already have encryption enabled by default
    (which we recommend), this does not affect you.


author: - Michael Wallace <michael.wallace@enterprisedb.com> 2.14-1
changelog:
  - Add the `barman-cloud-backup-delete` command which allows backups in
    cloud storage to be deleted by specifiying either a backup ID or a
    retention policy.
  - Allow backups to be retained beyond any retention policies in force by
    introducing the ability to tag existing backups as archival backups
    using `barman keep` and `barman-cloud-backup-keep`.
  - Allow the use of SAS authentication tokens created at the restricted
    blob container level (instead of the wider storage account level) for
    Azure blob storage
  - Significantly speed up `barman restore` into an empty directory for
    backups that contain hundreds of thousands of files.
  - The backup privileges check will no longer fail if the user lacks
    "userepl" permissions and will return better error messages if any
    required permissions are missing (#318 and #319).


author: - Michael Wallace <michael.wallace@enterprisedb.com> 2.15-1
changelog:
  - Add plural forms for the `list-backup`, `list-server` and
    `show-server` commands which are now `list-backups`, `list-servers`
    and `show-servers`. The singular forms are retained for backward
    compatibility.
  - Add the `last-failed` backup shortcut which references the newest
    failed backup in the catalog so that you can do:
    `barman delete <SERVER> last-failed`
  - Tablespaces will no longer be omitted from backups of EPAS
    versions 9.6 and 10 due to an issue detecting the correct version
    string on older versions of EPAS.


author: - Jane Threefoot <jane.threefoot@enterprisedb.com> 2.16-1
changelog:
  - Add the commands `barman-check-wal-archive` and `barman-cloud-check-wal-archive`
    to validate if a proposed archive location is safe to use for a new PostgreSQL
    server.
  - Allow Barman to identify WAL that's already compressed using a custom
    compression scheme to avoid compressing it again.
  - Add `last_backup_minimum_size` and `last_wal_maximum_age` options to
    `barman check`.
  - Use argparse for command line parsing instead of the unmaintained
    argh module.
  - Make timezones consistent for `begin_time` and `end_time`.
  - We thank chtitux, George Hansper, stratakis, Thoro, and vrms for their contributions to this release.


author: - Michael Wallace <michael.wallace@enterprisedb.com> 2.17-1
changelog:
  - Resolves a performance regression introduced in version 2.14 which
    increased copy times for `barman backup` or `barman recover` commands
    when using the `--jobs` flag.
  - Ignore rsync partial transfer errors for `sender` processes so that
    such errors do not cause the backup to fail (thanks to barthisrael).


author: - Michael Wallace <michael.wallace@enterprisedb.com> 2.18-1
changelog:
  - Add snappy compression algorithm support in barman cloud (requires the
    optional python-snappy dependency).
  - Allow Azure client concurrency parameters to be set when uploading
    WALs with barman-cloud-wal-archive.
  - Add `--tags` option in barman cloud so that backup files and archived
    WALs can be tagged in cloud storage (aws and azure).
  - Update the barman cloud exit status codes so that there is a dedicated
    code (2) for connectivity errors.
  - Add the commands `barman verify-backup` and `barman generate-manifest`
    to check if a backup is valid.
  - Add support for Azure Managed Identity auth in barman cloud which can
    be enabled with the `--credential` option.
  - Change `barman-cloud-check-wal-archive` behavior when bucket does not
    exist.
  - Ensure `list-files` output is always sorted regardless of the
    underlying filesystem.
  - Man pages for barman-cloud-backup-keep, barman-cloud-backup-delete
    and barman-cloud-check-wal-archive added to Python packaging.


author: - Didier Michel <didier.michel@enterprisedb.com> 2.19-1
changelog:
  - Change `barman diagnose` output date format to ISO8601.
  - Add Google Cloud Storage (GCS) support to barman cloud.
  - Support `current` and `latest` recovery targets for the `--target-tli`
    option of `barman recover`.
  - Add documentation for installation on SLES.
  - `barman-wal-archive --test` now returns a non-zero exit code when
    an error occurs.
  - Fix `barman-cloud-check-wal-archive` behaviour when `-t` option is
    used so that it exits after connectivity test.
  - `barman recover` now continues when `--no-get-wal` is used and
    `"get-wal"` is not set in `recovery_options`.
  - Fix `barman show-servers --format=json ${server}` output for inactive
    server.
  - Check for presence of `barman_home` in configuration file.
  - Passive barman servers will no longer store two copies of the
    tablespace data when syncing backups taken with
    `backup_method = postgres`.


author: Craig Ringer <craig.ringer@2ndquadrant.com> 1.2.0-1_2ndQuadrant
changelog:
  - The 1.2 update integrates the pglogical_output extension
  - First release targeting PostgreSQL 9.6rc1


author: Craig Ringer <craig.ringer@2ndquadrant.com> 1.2.1-1_2ndQuadrant
changelog:
  - Fix compatibility with 9.4 as downstream (GH #45)
  - Better error for 'snapshot is too large'
  - Ignore missing origin when cascading
  - Don't package hooks header anymore


author: Markus Wanner <markus.wanner@2ndquadrant.com> 2.2.0-2
changelog:
  - Rebuild against latest PostgreSQL point-releases to work around PostgreSQL
    ABI break in logical decoding
  - Require >= latest point release to prevent accidentally running on older
    versions with the old ABI


