Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vOLAC-003Uk3-27 for pgsql-general@arkaria.postgresql.org; Wed, 26 Nov 2025 19:26:52 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vOLAB-001Bt9-06 for pgsql-general@arkaria.postgresql.org; Wed, 26 Nov 2025 19:26:51 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vOLAA-001Bt1-0V for pgsql-general@lists.postgresql.org; Wed, 26 Nov 2025 19:26:50 +0000 Received: from fout-b3-smtp.messagingengine.com ([202.12.124.146]) by makus.postgresql.org with smtp (Exim 4.96) (envelope-from ) id 1vOLA7-001ch9-2Z for pgsql-general@lists.postgresql.org; Wed, 26 Nov 2025 19:26:49 +0000 Received: from phl-compute-02.internal (phl-compute-02.internal [10.202.2.42]) by mailfout.stl.internal (Postfix) with ESMTP id 37D551D00178; Wed, 26 Nov 2025 14:26:47 -0500 (EST) Received: from phl-mailfrontend-01 ([10.202.2.162]) by phl-compute-02.internal (MEProxy); Wed, 26 Nov 2025 14:26:47 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= cc:cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm2; t=1764185207; x=1764271607; bh=KnofhbkNf7ZlBBFfKqsfIgeVnYOVuHJtQL/wU7tUgeI=; b= KnOx5e+HuMOmCOrEvTNTGEzICyM0716YnT75WqRkKefcqGU3+sw6ey9g62XJtWhK RWcH1gJaQ3xc8DBqVwnHUgQZpW8ibSxTJoYEjU0rEjFiNPNjCei3Q/yotGcLFav9 2etAJ4K0tYFsAqGpS27yvkjK4kGqDFfZdDNknaFXAKPwUBg8AsH/EUaiaRHhrM3p 63umiyp/eUwWvvqQPIB7syQKOfdFGf8gdP2PhwMYs2pOxlkRjTv3qLlwstXwKGw+ Ecf7ODNmNXcUK+yIzmN/PAAnUuJjuz6m39AJFTGlqrsM/KF6AmIssX8d3jO0Dkna oGthiUtZcicJ4rQCtOjwEw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1764185207; x= 1764271607; bh=KnofhbkNf7ZlBBFfKqsfIgeVnYOVuHJtQL/wU7tUgeI=; b=k zs18A6LWa0hwOL4GEP+voePSAJBmonm6XmaFfQPR4XCE9zsKtXn7Sk6ERjkeNUim /rsyYEavtyRJ304QCpE4CvsLumLQiEvPR0vD+L2ONqPNGefjQFjQQ1EAxssYRxHA QPrqZEaOOaKn7Ghfith2CXAmaItA5aNdcaEG01siGb4LULGqvZuj9DIKsqq4KT/G yKLMaYMNtNkU0EVvBB6N2fjUKtlthzQaZlt9nD8XcQ1rzoKL+3mL4rEXdOV8zQt1 fuq+vXFBHpbEhDW8W3gMTBKvv/USeHQdRcgVXFVPI0b5Z2AXhzo3witsss9o75j1 HWlm7YU31vUoqeu43Ke5Q== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeeffedrtdeggddvgeehudelucetufdoteggodetrf dotffvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfurfetoffkrfgpnffqhgenuceu rghilhhouhhtmecufedttdenucenucfjughrpefkffggfgfuvfevfhfhjggtgfesthekre dttddvjeenucfhrhhomheptegurhhirghnucfmlhgrvhgvrhcuoegrughrihgrnhdrkhhl rghvvghrsegrkhhlrghvvghrrdgtohhmqeenucggtffrrghtthgvrhhnpeefgeefieeutd fggfetgefgheekjeehteeileeigfetieekjedvieeviefgheevtdenucevlhhushhtvghr ufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegrughrihgrnhdrkhhlrghvvg hrsegrkhhlrghvvghrrdgtohhmpdhnsggprhgtphhtthhopedvpdhmohguvgepshhmthhp ohhuthdprhgtphhtthhopegrughhvghnrhihrdelsehgmhgrihhlrdgtohhmpdhrtghpth htohepphhgshhqlhdqghgvnhgvrhgrlheslhhishhtshdrphhoshhtghhrvghsqhhlrdho rhhg X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 26 Nov 2025 14:26:46 -0500 (EST) Message-ID: <95c0ba97-f427-4a4b-8e18-67c1ba3a60fd@aklaver.com> Date: Wed, 26 Nov 2025 11:26:45 -0800 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Wal streaming To: Andrew Cc: pgsql-general@lists.postgresql.org References: <4b91a533-b2b7-42fe-bfb7-d92d56c6c1c1@aklaver.com> Content-Language: en-US From: Adrian Klaver In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 11/25/25 23:27, Andrew wrote: > 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? I am not going to straight up say you can disable the archive command as I will not be the one that has to bear the consequences. What I will say: 1) Have you tested that the Barman, repmgr setups work to do a recovery? 2) Are the two archive processes(streaming replication, barman-wal-archive) going to different locations? 3) There is also the question of whether the two archive methods are in sync. In other words would you get the same restore if used either at some point in time? My personal opinion is you would be best served by having only one tested process working. > > Regards > Andrew > Sent from my iPhone > -- Adrian Klaver adrian.klaver@aklaver.com