2.5.13

Upgraded pg_probackup to version 2.5.13, which provides optimizations and bugfixes. Notable changes are as follows:

Added support for PostgreSQL 16.
Improved catchup feature stability.
Improved documentation issues.
Centos Stream 9, Debian 12.2 (bookworm) and RedOS 7.3.2, packages have been added.
The package signing GPG key has been renewed so you may need to add the new key for APT repositories as described in the installation instructions.

2.5.12

Upgraded pg_probackup to version 2.5.12, which provides optimizations and bugfixes. Notable changes are as follows:

Added packages for Ubuntu 22.04.
Improved output of commands and hints for better user experience.

Download packages from the official repository: http://repo.postgrespro.ru/pg_probackup/

2.5.11

Upgraded pg_probackup to version 2.5.11, which provides optimizations and bugfixes. Notable changes are as follows:

• Improved pg_probackup stability when it is used with PostgreSQL 15.
• Optimized some tests and confirmed pg_probackup stability when it is used with PostgreSQL versions 10 - 14.
• Added packages for ALT 10 and removed outdated packages for ALT Linux 7, Oracle Linux 6, and openSUSE 15.1.

Download packages from the official repository: http://repo.postgrespro.ru/pg_probackup/

2.5.10

Upgraded pg_probackup to version 2.5.10, which provides optimizations and bugfixes. Notable changes are as follows:

• pg_probackup works with PostgresSQL 15
• Optimized CFM files backup by truncating them and storing the CRC computed before the truncation.
• Fixed an issue with checkdb --amcheck, which previously completed with an error when the checked database contained partitioned indexes.
• Fixed a backup failure on a replica that occurred because the version of the pg_probackup agent running there was different from that on the master.

2.5.8

Upgraded pg_probackup to version 2.5.8, which provides the following new features
and bugfixes:

• Enabled output of logs in the JSON format by adding new logging options.
• Added an option to explicitly specify the directory where the restore command should restore WAL records.
• Changed the level of detail of logging some messages of pg_probackup commands to add user convenience to reading logs.
• Fixed pg_probackup hanging that could occur when the ControlMaster option was specified in the SSH config file. Now the value of ControlMaster is explicitly set to no .

Download packages from the official repository: http://repo.postgrespro.ru/pg_probackup/

2.5.5

Improvements:

• New --checkunique option added to the checkdb command to work together with --amcheck and verify unique constraints during logical verification of indexes when the amcheck extension is installed in the database and its version supports the verification of unique constraints.

2.5.4

Major bugfixes:

• catchup: fix data corruption in delta and ptrack modes, before that, the source database could be damaged when using these modes (#459).

Bugfixes:

• archive-push: --wal-file-path option now works in accord with documentation. Now you can call arсhive-push not only from the postgres working directory, but also from an arbitrary directory (#437, #330, #265, fixed in 2.5.3)
• catchup: fix that catchup incorrectly checks the timeline history in some cases (#463).

Packaging:

• fix rhel-8 repo (#455).
• drop support of debian-8, ubuntu-14.04 and ubuntu-16.04 packages

Issues:

• https://github.com/postgrespro/pg_probackup/milestone/34?closed=1
• https://github.com/postgrespro/pg_probackup/milestone/31?closed=1

2.5.2

Bugfixes:

• Unlogged relations are correctly excluded from backup now. Reported by @Zergvl
• ENOSPC is now detected correctly when writing data. Reported by @slothfk
• wal directory in instance catalog can now be symlinked. Reported by @triwada
• CVE-2018-1058 is fixed

Improvements:

• New command catchup is implemented. With it you can now fast-forward fallen-behind standby using changed data from master. Developed by @kulaginm
• Important information and messages are now colored
• Added PG14 support
• Added RH8 support
• Added Debian11 support
• Ptrack 1.x support is dropped.
• Package support for 9.5 is dropped, but old packages are still available in repo
• Package support for Centos 6 and RHEL 6 is dropped, but old packages are still available in repo

Issues:
https://github.com/postgrespro/pg_probackup/milestone/19

Version 2.4.15

Bugfixes:

• Fix integer overflow of variable storing the offset of page header map. Reported by @sms1222
• Fix broken backward compatibility for backups of versions 2.0.22, 2.0.24 and 2.0.25. Affected version: 2.4.10. Reported by @shab2
• Do not delete invalid full backups within retention redundancy range. Reported by @triwada
• Correctly handle backups with empty backup.control. Reported by Mikhail Grigorev
• Empty WAL .history files are now handled correctly. Reported by Denis Podolsky
• Do no report meaningless timestamp when deleting backup without valid "recovery-time" attribute. Reported by Roman Zharkov
• Detect failure in WAL streaming correctly and report it as soon as possible. Reported by Yuri Kurenkov (#346)
• Do sync and rename when writing to configuration file pg_probackup.conf
• More robust parsing of tablespace_map content. Reported by Vasiliy Puchkov

Improvements:

• At the start of incremental backup the timeline switch of PostgreSQL instance is now detected automatically via replication protocol using TIMELINE_HISTORY command. Requested by Alex Ignatov
• Flags --no-validate and --no-sync are now can be used when running merge or retention merge operations.

Issues:
https://github.com/postgrespro/pg_probackup/milestone/28?closed=1

Version 2.4.10

Bugfixes:

• Due to false-positive crc match it was possible to erroneously reuse pg_filenode.map file during incremental restore, which could break pg_catalog relations relying on pg_filenode.map for filenode mapping if they were subject to VACUUM FULL or REINDEX operations before backup. This is fixed now.
• A race condition between reader and writer in acquiring the backup exclusive lock is removed.
• File descriptor leak in the backup shared lock is fixed.

Improvements:

• The remote agent API is now stable across the same minor version starting with 2.4.9, which makes pg_probackup installations more robust towards version drift. Requested by Alex Ignatov.
• It is now possible to restore and validate a backup from a read-only filesystem. Requested by Mikhail Kulagin.
• Backup shared locks are now released at the process exit.