Hi, I’m using Postgres 17 and the latest versions of repmgr and barman
1. I’m replicating my database to another node using streaming replication. wal_level=replica, hot_standby=on. 2. I’ve got barman running on the primary node locally and have setup the barman config for streaming replication using streaming archiver and backup method Postgres. Previous to this I was using the archive and restore commands in postgresql.conf to use barman-wal-archive|restore to copy the wal files to barman’s wal folder. 3. Barman is on node 1 where the primary is running. The replica database used by repmgr is on node 2. 4. My archive command is still configured to use barman-wal-archive despite having moved to a streaming replication method in barman. So my question is, can I disable the archive command now that I am using streaming? Regards Andrew Sent from my iPhone > On 25 Nov 2025, at 16:54, Adrian Klaver <[email protected]> wrote: > > On 11/25/25 05:46, Andrew wrote: >> Hi, >> New to the list. If I’m Using streaming archiving with repmgr, and streaming >> archiving with barman, do I still need to maintain my archive command, and >> have processes in place to delete archived wals periodically? Or are they >> in effect defunct due to wal retention policies within Postgres? > > You are going to need to expand on this as it is unclear to me what your > processes are. > > 1) What is the repmgr setup for streaming? > > 2) What is the Barman setup for streaming? > > 3) What locations are 1 & 2 streaming to? > > 4) What is the process you have in place now to prune the archives? > > 5) What are the Postgres version you are working with? > >> Regards >> Andrew >> Sent from my iPhone > > > -- > Adrian Klaver > [email protected]
