A.1. pg_probackup 3.4.0 #
Release date: 2026-06-18
This release is based on pg_probackup 3.3.0 and provides new features, optimizations and bug fixes. Major changes are as follows:
New features:
Implemented remote incremental restore via the
send-backupcommand with the-I/--incremental-modeoption. For more details, refer to the Remote Restore section.Changed the default buffer size (the
--buffer-sizeoption) to128KB, improving performance when working with SFTP and remote storage.
Critical bug fixes:
Fixed TDE support for backup to a remote server. Page validation is now correctly skipped for encrypted data.
Fixed a buffer overflow detection issue that occurred during backup creation.
Fixed incorrect thread termination on error in
DIRECTmode.Fixed performance degradation during
PTRACKbackup creation inPROandDIRECTmodes.Fixed position tracking of replication slots to ensure timely removal of archived WAL files.
Fixed incorrect handling of the
zstdcompression algorithm during WAL archiving by adding a customzstd iostreamsfilter.Fixed the “Attempt to write more than uint32_t::max” error which occurred when using the
--with-file-mapoption with large amounts of data in mapping files.Fixed recovery with excluded tablespaces. The
pg_tblspcdirectory is no longer restored when excluded, which also resolves WAL validation errors.Added support for Shardman on s390x, including the following fixes and improvements:
Added full support for backup, incremental restore, and instance synchronization via the
catchupcommand for all Postgres Pro editions.Implemented WAL validation for the Shardman edition.
Fixed critical byte order issues in CRC checksums,
PGDATAcomparison with*.cfmfiles, and WAL validation.
Network:
Improved S3 integration:
Removed redundant warnings when checking object existence in S3.
Reduced log verbosity for routine S3 operations.
Improved error handling for connection failures and timeouts.
Fixed an issue where an SFTP session could remain open on file write errors. The session is now properly closed at the end of the operation.
Improved SFTP error messages for better diagnostics of remote operation issues.
CFS:
Added support for the
pglzcompression algorithm to extend compatibility with various Postgres Pro configurations. pg_probackup3 now correctly handles CFS files inlz4,zstd,zlib, andpglzformats.Fixed compression application for CFS backups. The utility now derives the compression algorithm for each tablespace from its
*.cfmfiles, independent of the backup compression algorithm. Different compression algorithms can now coexist across tablespaces.Fixed
PGDATAcomparison logic for CFS tablespaces —*.cfmfiles are now handled correctly when comparing pages, which ensures a proper validation check during synchronization (catchup) and incremental restore.
Other improvements:
Fixed error handling when reading instance configuration — errors are now logged along with descriptions.
Improved the error message that occurred when attempting to unmount a FUSE filesystem with a running Postgres Pro instance.
Added logging of current retention policy parameters during the
retentionoperation.Fixed the
CORRUPTbackup status behavior. It is no longer set when backup validation is interrupted.Added protection against infinite loops triggered by backup corruption detection.
Refined the
archive-getcommand to correctly handle cases wherezstdor any other compression algorithm is unavailable.Fixed recovery with
--recovery-target-timelineset tolatest— it now works correctly on replicas after promotion.Removed redundant cancellation token warnings that occurred when using
--with-file-mapinDIRECTmode. The metadata object is now initialized only when necessary.
A.1.1. Migration to Version 3.4.0 #
Important
Starting from pg_probackup 3.3.0, the libpgprobackup.so and libpb3_encoder.so libraries are contained in a single libpb3-encoder package instead of two separate ones — libpgprobackup3 and libpb3-encoder — in lower versions.
If the libpgprobackup3 package was installed to enable PRO mode in version 3.2.X or lower, remove it before upgrading.
To migrate to pg_probackup 3.4.0 from lower versions, refer to the Upgrading pg_probackup3 section.