Postgres Professional are proud to announce the release of pg_probackup
2.1.3.
pg_probackup is a utility to manage backup and recovery of PostgreSQL
database cluster. It is designed to perform periodic full and
incremental page-level backups of the PostgreSQL instance that enable
you to restore the server in case of a failure.
Changes since 2.1.2:
Bugfixes:
* 'validate' was giving a false-positive alarm for files disappeared
during backup. Reported by Nikitin Alexander.
* 'validate' was reporting incorrect latest possible recovery target
after WAL validation.
* 'backup' command was returning positive exit code even if
after-backup validation found corruption. Now in this case backup will
exit with an error.
* 'backup' on Windows had a risk of ending with failure if deleted
but pinned files were encountered. Fixed in pg_probackup and patch
submitted to PostgreSQL community:
https://www.postgresql.org/message-id/flat/a9c76882-27c7-9c92-7843-21d5521b70a9%40postgrespro.ru.
Reported by Yuri Kurenkov.
* 'restore' used with '--no-validate' could lead to data loss because
of lax behavior in case of file been missing. Now missing file is always
considered as an error condition for restore.
* 'merge' crash safety improved. Now the MERGING state is preserved
until the FULL backup successfully receives a new ID during the merge
operation.
* 'merge' of PAGE backup with an external directory had a risk of
data loss.
* Previously permission mask of restored files was not preserved and
default PostgreSQL permission mask (0700) was enforced, which
potentially could lead to inability to backup an instance, that was
restored with pg_probackup (for PostgreSQL version >= 11). Reported by
Mikhail Kulagin.
Improvements:
* Previously restore of incremental chain was inefficient in case of
deleted files: such files were copied and then deleted. Now they are
just not copied at all.
Download
--------
https://github.com/postgrespro/pg_probackup
--
Grigory Smolkin
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company