A.1. pg_probackup 3.4.1 #
Release date: 2026-08-07
This release is based on pg_probackup 3.4.0 and provides the following bug fixes:
Critical bug fixes:
Fixed an issue where incomplete writes were retried using the original buffer size instead of the remaining size, which could, in rare cases, cause data corruption or a process crash.
Fixed the
mergecommand to check validation result of each backup in the chain and abort with an error if a backup is invalid.
CFS:
Fixed a server crash with SIGABRT during CFS backup on large tablespaces.
Fixed an issue with CFS garbage collector being blocked by the backup process in
PROmode, which could lead to data corruption. Now both processes lock only specific data files briefly, avoiding mutual blocking.Fixed a “could not stat file” error leading to a backup or restore process crash. Temporary files created by the CFS garbage collector are now skipped during backup and restore.
Other bug fixes:
Fixed backup failures in
DIRECTmode that occurred if a file disappeared between scanning a directory and attempting to access it, for example, if it was deleted by Postgres Pro.Fixed option reset during instance configuration parsing. Previously, option values, including
--slot,--no-color, and write thread count, were overwritten by default values.Fixed path normalization in the
--backup-pathoption when using relative paths or paths with redundant separators.Fixed a memory leak that occurred when processing external directories during restore.