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
.historyfiles 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_mapcontent. 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_HISTORYcommand. Requested by Alex Ignatov - Flags
--no-validateand--no-syncare now can be used when running merge or retention merge operations.
Issues:
https://github.com/postgrespro/pg_probackup/milestone/28?closed=1