Package: barman Version: 1.4.1-1 Severity: normal Hi,
I've just upgraded two 9.1 clusters to 9.4.2. The new cluster continued with the same archive_command as before, but until I did the *second* new basebackup, barman would just discard all archived WAL segments (including the .backup labels). My retention setting is 1, so it might be that it simply started working once the last old backup was expired. I'm not sure if it's related to the fact that 9.4.2 actually *restarts* the timeline at 1 (see 4c5e060049a3714dd27b7f4732fe922090edea69 in PG master), or if it's a general problem with pg_upgrade. (The WAL position is preserved, but the timeline id 2 is now again 1.) A related bug is that I still had files in wals/00002..., while all my base backups (well actually the single backup) only needed files in wals/00001.... I've now manually removed these and rebuilt the wal db. Christoph -- c...@df7cb.de | http://www.df7cb.de/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
