5 September 2017: 2ndQuadrant is proud to announce the release of Barman version 2.3, a Backup and Recovery Manager for PostgreSQL.
This minor release introduces support for PostgreSQL 10. Following the change in naming conventions brought by PostgreSQL 10, Barman now uses the terms “WAL”, “location” instead of, respectively, “xlog” and “lsn”.
This release also adds a few additional options to the
barman recover command, in order to enable or disable network compression at run-time (
--no-network-compression) and to instruct PostgreSQL to exit recovery as soon as a consistent state is reached (
--target-immediate, available from PostgreSQL 9.4).
Barman 2.3 fixes an important bug for memory consumption of parallel copy introduced in 2.2, as well as some minor bugs.
With this release Barman has dropped the support for RHEL/CentOS 5 and Ubuntu Precise (12.04) which have both reached the official end of life.
For a complete list of changes, see the “Release Notes” section below.
- Man page, section 1
- Man page, section 5
- Client utilities for Barman
- pgespresso extension
Add support to PostgreSQL 10
Follow naming changes in PostgreSQL 10:
switch-xlogcommand has been renamed to
- In commands output, the
xlogword has been changed to
locationhas been changed to
barman recoverto enable or disable network compression at run-time
recovercommand, in order to exit recovery when a consistent state is reached (end of the backup, available from PostgreSQL 9.4)
Show cluster state (master or standby) with