Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update NEWS for 3.9.0 #853

Merged
merged 2 commits into from
Oct 3, 2023
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 25 additions & 0 deletions NEWS
Original file line number Diff line number Diff line change
@@ -1,5 +1,30 @@
Barman News - History of user-visible changes

Version 3.9.0 - 3 October 2023

- Allow `barman switch-wal --force` to be run against PG>=14 if the
user has the `pg_checkpoint` role (thanks to toydarian for this patch).

- Log the current check at `info` level when a check timeout occurs.

- The minimum size of an upload chunk when using `barman-cloud-backup`
with either S3 or Azure Blob Storage can now be specified using the
`--min-chunk-size` option.

- `backup_compression = none` is supported when using `pg_basebackup`.

- For PostgreSQL 15 and later: the allowed `backup_compression_level`
values for `zstd` and `lz4` have been updated to match those allowed by
`pg_basebackup`.

- For PostgreSQL versions earlier than 15: `backup_compression_level = 0`
didiermichel marked this conversation as resolved.
Show resolved Hide resolved
can now be used with `backup_compression = gzip`.

- Bug fixes:

- Fix `barman recover` on platforms where Multiprocessing uses spawn by
default when starting new processes.

Version 3.8.0 - 31 August 2023

- Clarify package installation. barman is packaged with default python version
Expand Down
Loading