Bugfixes:

• Delete of backups containing hidden files works correctly now. Reported by Alex Ignatov.
• Local logging into file for archive-push and archive-get commands works correctly now. Reported by @triwada.
• Support for extension ptrack 2.1

Major Bugfixes:

• Due to incorrect handling of ENOENT for remote files, It was possible to get silent data loss if more than 32 data files were dropped during remote backup. Reported by Mikhail Aksenov.

Bugfixes:

• Remote and local binaries version matching was done incorrectly. Reported by @tengilim.
• .deb packages from previous release 2.3.2 incorrectly contained binaries with suffix -dev. Reported by Alex Ignatov

Bugfixes:

• Previously backup control file was not always synced to disk during backup and merge. Reported by Mikhail Aksenov

Improvemts:

• New backup attribute content-crc is added to detect corruption of backup content control file.

Bugfixes:

• Multi-timeline incremental backup in PAGE mode now correctly extracts pagemap of changed blocks from multiple timelines.
• Full backup, produced by merge of multi-timeline chain, now inherits timeline ID of destination backup.

Improvements:

• Packages for Ubuntu 20.04 are now available in repository

New features:

• The --status option can be used with the delete command to remove all backups with the specified status. Requested by Stepan Santalov. Contributed by Victor Spirin.
• The --no-sync flag can be used with backup, restore, and archive-push commands to disable syncing of copied files to the underlying storage.
• The --note option allows to add a text note of size up to 1KB to the backup metadata when running backup and set-backup commands. Contributed by Victor Spirin.
• Multi-timeline incremental chains are now supported. The timeline number of an incremental backup can differ from the parent timeline number, but only if it is possible to determine (using WAL archive) that the child timeline descends from the parent timeline.
• You can now set PostgreSQL parameters primary_slot_name and primary_conninfo during restore using the -S | --primary-slot-name and --primary-conninfo options, respectively. Requested by Yuri Kurenkov.
• Major revamp of the archive-push command:
  • Multi-threading support is added via the -j | --threads option.
  • Batch processing is added via the --batch-size option.
  • In the remote mode, checksums are now computed on a remote agent.
• Major revamp of the archive-get command:
  • Multi-threading support is added via the -j | --threads option.
  • WAL prefetching is added via the --batch-size option. The default directory with prefetched WAL segments is PGDATA/pg_wal/pbk_prefetch. You can change this location using the --prefetch-dir option.
  • Partial WAL files produced by pg_receivewal program are now recognized and used if the corresponding full WAL segment is missing. Reported by Artem Dolgih.

Improvements:

• The speed of restore from incremental chain is greatly improved. In some cases, by an order of magnitude. Reported and tested by Alex Ignatov.
• The speed of merge, especially merge of several backups at a time, is greatly improved. Reported by Rostislav Pochevalov.
• The speed of remote backup in PAGE and PTRACK modes is greatly improved.
• You can now delete a backup even if there is no space left on device. Reported by Stepan Santalov.
• Hidden files are now ignored during backup.
• Now it is explicitly forbidden to restore a backup using an older pg_probackup version. Contributed by Dmitriy Kuzmin.

Bugfixes:

• Enabled logging info file should not break archiving anymore. Reported by Artem Dolgih.
• The add-instance command no longer implicitly sets the --remote-proto and --remote-host parameters in the instance configuration when adding a remote PostgreSQL instance into the backup catalog.
• When taking a backup in the ARCHIVE mode, pg_probackup now waits for the segment containing the START LSN, not the previous segment. Reported by Mikhail Kulagin.
• The expire-time attribute is now inherited during merge.
• Setting session parameters via the PGOPTIONS environment variable during backup now does not cause corruption of backup meta information.

Bugfixes

• fix stack limit segfault. Reported by Petr Karezin

Bugfixes

• Pinned backups are now ignored for the purpose of WAL archive retention policy fulfillment. Reported by Puchkov Vasily.
• attribute pgdata_bytes for FULL and DELTA backups in remote mode is calculated correctly now
• now full names of WAL segments are used in Max Segno, Min Segno and lost-segments fields of WAL Archive catalog. Reported by Nikolay Popov.
• multiple minor fixes

Improvements

• added support for ptrack 2.0
• packages for ALT Linux versions p7, p8 and p9 are available in the repository
• documentation is moved to https://postgrespro.github.io/pg_probackup

Bugfixes

• fix buffer overflow for old compilers. Reported by Leonid Kraubner
• wal_bytes attribute for ARCHIVE backups is calculated correctly now
• total size of WAL data and backup data to delete during retention purge are calculated correctly now
• the value for Zratio field in show --archive --format=plain output is calculated correctly now
• now the value of --restore-command option is always added to recovery config as restore_command setting when restoring STREAM backup

Improvements

• PostgreSQL 12 is supported, packages are available in the repository
• packages for Oracle Linux 8 are available in the repository

Bugfixes

• WAL segment number calculation was incorrect, which have resulted in preserving expired WAL segments in the archive, which in turn may results in WAL archive overflow. Also, because of this bug, WAL archive catalog may have reported incorrect values for some attributes, such as Min Segno and Max Segno. Affected versions: 2.2.1, 2.2.3.

Improvements

• function pgpro_edition() now called only during backup of PostgresPro Standart and PostgresPro Enterprise clusters.
• pg_probackup RPM and DEB packages for PostgresPro Standart and PostgresPro Enterprise are now available in the separate repository: https://github.com/postgrespro/pg_probackup#pg_probackup-for-postgrespro-standart-and-enterprise

Bugfixes:

• Major Bugfix: the writing of metadata file containing list of files belonging to a backup was bugged, which resulted in losing the information about one file per 4MB of metadata. Now the writing of metadata is done correctly. validate command can detect metadata corruption in backups produced by affected versions. Affected versions: 2.1.4, 2.1.5 and 2.2.1. Reported by Leonid Kraubner. More information can be found here: https://github.com/postgrespro/pg_probackup/issues/132

• previously WAL retention didn`t retained WAL segments entitled to protection from WAL purge, now WAL retention works correctly

Improvements:

• new flag --force for restore command can be used to restore invalid backups.
• validation running during backup merge now does only file checksum comparison without block validation. It should speed up merge of compressed backups