Barman

Bug fixes:

- Fix a bug which prevented `barman-cloud-backup-show` from
displaying the backup metadata for backups made with
`barman backup` and uploaded by `barman-cloud-backup` as a
post-backup hook script.

- Fix a bug where the PostgreSQL connection used to validate backup
compression settings was left open until termination of the
Barman command.

- Fix an issue which caused rsync-concurrent backups to fail when
running for a duration greater than `idle_session_timeout`.

- Fix a bug where the backup name was not saved in the backup
metadata if the `--wait` flag was used with `barman backup`.

Acknowledgements

We thank the following who contributed to this release:
- barthisrael
- epolkerman
- hzetters

Features

- This is the last release of Barman which will support Python 2 and
new features will henceforth require Python 3.6 or later.

- A new `backup_method` named `snapshot` is added. This will create
backups by taking snapshots of cloud storage volumes. Currently
only Google Cloud Platform is supported however support for AWS
and Azure will follow in future Barman releases. Note that this
feature requires a minimum Python version of 3.7. Please see the
Barman manual for more information.

- Support for snapshot backups is also added to `barman-cloud-backup`,
with minimal support for restoring a snapshot backup added to
`barman-cloud-restore`.

- A new command `barman-cloud-backup-show` is added which displays
backup metadata stored in cloud object storage and is analogous to
`barman show-backup`. This is provided so that snapshot metadata
can be easily retrieved at restore time however it is also a
convenient way of inspecting metadata for any backup made with
`barman-cloud-backup`.

Bug fixes

- The instructions for installing Barman from RPMs in the docs are
updated.

- The formatting of NFS requirements in the docs is fixed.

- Supported PostgreSQL versions are updated in the docs (this is a
documentation fix only - the minimum supported major version is
still 10).

Features

- A backup can now be given a name at backup time using the new `--name`
option supported by the `barman backup` and `barman-cloud-backup`
commands. The backup name can then be used in place of the backup ID
when running commands to interact with backups. Additionally, the
commands to list and show backups have been been updated to include
the backup name in the plain text and JSON output formats.

- Stricter checking of PostgreSQL version to verify that Barman is
running against a supported version of PostgreSQL.

Bug fixes

- Fix inconsistencies between the barman cloud command docs and the help
output for those commands.

- Use a new PostgreSQL connection when switching WALs on the primary
during the backup of a standby to avoid undefined behaviour such as
`SSL error` messages and failed connections.

- Reduce log volume by changing the default log level of stdout for
commands executed in child processes to `DEBUG` (with the exception
of `pg_basebackup` which is deliberately logged at `INFO` level due
to it being a long-running process where it is frequently useful to
see the output during the execution of the command).

Features

- `barman-cloud-backup-delete` now accepts a `--batch-size` option
which determines the maximum number of objects deleted in a single
request.
- All `barman-cloud-*` commands now accept a `--read-timeout` option
which, when used with the `aws-s3` cloud provider, determines the
read timeout used by the boto3 library when making requests to S3.

Bug fixes

- Fix the failure of `barman recover` in cases where
`backup_compression` is set in the Barman configuration but the
PostgreSQL server is unavailable.

Features

- Backups taken with `backup_method = postgres` can now be compressed
using lz4 and zstd compression by setting `backup_compression = lz4`
or `backup_compression = zstd` respectively. These options are only
supported with PostgreSQL 15 (beta) or later.
- A new option `backup_compression_workers` is available which sets
the number of threads used for parallel compression. This is
currently only available with `backup_method = postgres` and
`backup_compression = zstd`.
- A new option `primary_conninfo` can be set to avoid the need for
backups of standbys to wait for a WAL switch to occur on the primary
when finalizing the backup. Barman will use the connection string
in `primary_conninfo` to perform WAL switches on the primary when
stopping the backup.
- Support for certain Rsync versions patched for CVE-2022-29154 which
require a trailing newline in the `--files-from` argument.
- Allow `barman receive-wal` maintenance options (`--stop`, `--reset`,
`--drop-slot` and `--create-slot`) to run against inactive servers.
- Add `--port` option to `barman-wal-archive` and `barman-wal-restore`
commands so that a custom SSH port can be used without requiring any
SSH configuration.

- Various documentation improvements.

- Python 3.5 is no longer supported.

Bug fixes

- Ensure PostgreSQL connections are closed cleanly during the
execution of `barman cron`.
- `barman generate-manifest` now treats pre-existing
backup_manifest files as an error condition.
- backup_manifest files are renamed by appending the backup ID
during recovery operations to prevent future backups including
an old backup_manifest file.
- Fix epoch timestamps in json output which were not
timezone-aware.
- The output of `pg_basebackup` is now written to the Barman
log file while the backup is in progress.

Acknowledgements

We thank the following who contributed to this release:
- barthisrael
- elhananjair
- kraynopp
- lucianobotti
- mxey

Bug fixes

- Fix package signing issue in PyPI (same sources as 3.0.0)