barthisrael
commented
3 months ago I run a test with the code and it seems to do what is required. I can see the summarize_wal with the correct value in both of my Postgres 17 servers (one with rsync, another with postgres method), and I can see None for the Postgres 16 server:
$ find ~/ -type f -name "backup.info" -print -exec bash -c "grep summarize_wal {}; echo" \;
/home/vagrant/barman_home/pg17-postgres-default/base/20240610T182147/backup.info
summarize_wal=on
/home/vagrant/barman_home/pg17-rsync/base/20240610T182149/backup.info
summarize_wal=on
/home/vagrant/barman_home/pg16-postgres-default/base/20240610T182145/backup.info
summarize_wal=NoneLet me check the code and commits as well.
With postgres major version >= 17, we have the possibility to do incremental backups with pg_basebackup.
A crucial element for enabling this functionality is the WAL summarizer process. This is a recent addition, designed to assist incremental backups by identifying the differences in the data directory since the previous backup.
A new field was added in configuration file
postgresql.confcalledsummarize_wal. This field handles the state of the process (on or off).This commit adds a new field called summarize_wal to the backup.info metadata.
For postgres versions prior to 17, this field will remain as
None.Unit tests updated accordingly.
References: BAR-172.
Signed-off-by: Andre Marchesini de Aguiar andre.marchesini@enterprisedb.com