Feature Request: Barman should preserve history files in the WAL archive indefinitely.
The way it is in 1.4.0:
Timeline history files, i.e. 0000000002.history, are subject to the same expiration rules as regular WAL files. This creates a problem if you try to use a Barman restore to restore to two different servers and set up a master-replica relationship, per this issue on Hackers:
http://www.postgresql.org/message-id/5579E7DE.6020109@agliodbs.com
This means that, once the history file has been expired and deleted, there is no way you can use Barman backup to restore both a master and a replica.
The way it should be:
While we hope that PostgreSQL will fix this bug, the fix may not be backported. As such, it would be useful if Barman preserved the history files:
.history files should not be subject to deletion when backup snapshots expire;
all .history files should be restored with the restored WAL.
Of course, if this is somehow already fixed in 2.0, please let me know and we'll upgrade. Thanks!
Ping?
Thanks Josh for posting. We will assess this issue and let you know ASAP.
Hi Josh,
this has been fixed with commit:4d19a9ba9f53c28dcc5836dbf4a7b4f0304c9e83
It will be included in the upcoming 1.5.0
Thanks,
Gabriele