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.94.2) (envelope-from ) id 1ulrdq-006YIu-LY for pgsql-general@arkaria.postgresql.org; Tue, 12 Aug 2025 16:14:26 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1ulrdn-008Neu-Mg for pgsql-general@arkaria.postgresql.org; Tue, 12 Aug 2025 16:14:23 +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.94.2) (envelope-from ) id 1ulrdn-008Ndu-BZ for pgsql-general@lists.postgresql.org; Tue, 12 Aug 2025 16:14:23 +0000 Received: from fout-a4-smtp.messagingengine.com ([103.168.172.147]) by makus.postgresql.org with smtp (Exim 4.96) (envelope-from ) id 1ulrdk-000DHh-2h for pgsql-general@lists.postgresql.org; Tue, 12 Aug 2025 16:14:22 +0000 Received: from phl-compute-08.internal (phl-compute-08.internal [10.202.2.48]) by mailfout.phl.internal (Postfix) with ESMTP id A73B8EC00D8; Tue, 12 Aug 2025 12:14:20 -0400 (EDT) Received: from phl-mailfrontend-01 ([10.202.2.162]) by phl-compute-08.internal (MEProxy); Tue, 12 Aug 2025 12:14:20 -0400 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=1755015260; x=1755101660; bh=QYaSLZwanhLqNC47e+SFcsTGms8p79eGWS4EkszsyFc=; b= NggBo1FjEAzRijvyTMhCjR0vAfbV3q8mooiR+1+Kg3tbqwuqYyVCHXXpssY4xQyw R0iMWn8qZA4DtsJm8tD6TtLMksdbj7rXFfmGcWx6KtaZNM6NzX7gslc+pm40TyQ9 lsr/GIp2tYwURqqmV6EL34ek8OuODA6JSthPH1gD1LJVuU2NP+AEWz5EVSZLPg4M NGcuCfdzeKsI6ScR2bHH6rLGQP9Ls4DpQcO0a3pIopjVmM9h6hQHJn3wL7e6XUD7 PPx+ABB8WtKZ70n1IiIZdCp1VCi7IaEeQl/6Wg4KJiEhDRjTK5Ra8dy96l3xBGP/ M1OQ1WSweQv0Ymdvpn2kpQ== 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=1755015260; x= 1755101660; bh=QYaSLZwanhLqNC47e+SFcsTGms8p79eGWS4EkszsyFc=; b=g POXkUawEDGvrOLlSFfFOg8lz3ViSRe6N2/1WEjYuaiWI2Fn2ugGJyHi8rfrgtCI7 gCTvBGr1dZb3MrJbmgHspR/ih5OKGtHYd65G39D9rosQGj4h8c5+qcF7Tjhi3YJg 3+lmyKbuSVeRsEEb6yxLF/4EAMVq4CrwomtVtxcN10jF0GkRS1RcZA4Zc1vMBCRh lHAiVQL+lKSgxPIK8xa4MOWbVtgDlWYM8csoD64Zlmke9p2oDDehYUrkF9PXwht2 M47lKTbGlDY0z7TYMgT/5LitOPVA1GNsrq9U1uxGBJ6g4vxXrBzDl2RZCysJlke4 sg7F7ymR7y7GcaGwOoLhg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeeffedrtdefgddufeehjeekucetufdoteggodetrf dotffvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfurfetoffkrfgpnffqhgenuceu rghilhhouhhtmecufedttdenucenucfjughrpefkffggfgfuvfevfhfhjggtgfesthekre dttddvjeenucfhrhhomheptegurhhirghnucfmlhgrvhgvrhcuoegrughrihgrnhdrkhhl rghvvghrsegrkhhlrghvvghrrdgtohhmqeenucggtffrrghtthgvrhhnpeefgeefieeutd fggfetgefgheekjeehteeileeigfetieekjedvieeviefgheevtdenucevlhhushhtvghr ufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegrughrihgrnhdrkhhlrghvvg hrsegrkhhlrghvvghrrdgtohhmpdhnsggprhgtphhtthhopedvpdhmohguvgepshhmthhp ohhuthdprhgtphhtthhopehsphiglhihhiduvdefsehgmhgrihhlrdgtohhmpdhrtghpth htohepphhgshhqlhdqghgvnhgvrhgrlheslhhishhtshdrphhoshhtghhrvghsqhhlrdho rhhg X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 12 Aug 2025 12:14:19 -0400 (EDT) Message-ID: <73f3723b-f279-43c6-884d-d12b3151ec9e@aklaver.com> Date: Tue, 12 Aug 2025 09:14:19 -0700 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Questions about the continuity of WAL archiving To: px shi Cc: pgsql-general@lists.postgresql.org References: 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 8/12/25 01:24, px shi wrote: > > 1) What is the current archiving setup on the primary and why is > lagging? > >  The archive command uses pgBackRest to archive to S3. Because it is > uploaded to S3, the archiving speed is slow, which has caused lagging. > > 2) Have you looked at archiving off the standby node while it is in > standby per: > > Yes, archiving on the standby node is disabled. Is it recommended to > share the WAL archive between the primary and standby nodes to avoid > interruptions in archiving? Given that you are using a less then capable storage solution(S3) why do you think pushing the WAL from the standby to S3 would perform any better then what is happening with the primary WAL? The solution is to use a more capable storage platform. > > Adrian Klaver > 于2025年8月8日周五 23:23写道: > -- Adrian Klaver adrian.klaver@aklaver.com