Feedback-ID: i76984098:Fastmail
Message-ID: <4b91a533-b2b7-42fe-bfb7-d92d56c6c1c1@aklaver.com>
Date: Tue, 25 Nov 2025 07:54:17 -0800
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Wal streaming
To: Andrew <adhenry.9@gmail.com>, pgsql-general@lists.postgresql.org
References: <58B86368-DF2D-443D-A0EA-3F82831AE0C7@gmail.com>
Content-Language: en-US
From: Adrian Klaver <adrian.klaver@aklaver.com>
In-Reply-To: <58B86368-DF2D-443D-A0EA-3F82831AE0C7@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://www.postgresql.org/message-id/4b91a533-b2b7-42fe-bfb7-d92d56c6c1c1%40aklaver.com>
Precedence: bulk

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
adrian.klaver@aklaver.com