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 1ulsz6-006qdZ-AX for pgsql-general@arkaria.postgresql.org; Tue, 12 Aug 2025 17:40:28 +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 1ulsz4-008soD-99 for pgsql-general@arkaria.postgresql.org; Tue, 12 Aug 2025 17:40:26 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1ulsz3-008so5-UX for pgsql-general@lists.postgresql.org; Tue, 12 Aug 2025 17:40:26 +0000 Received: from mail-yb1-xb2f.google.com ([2607:f8b0:4864:20::b2f]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1ulsz1-000F1O-1r for pgsql-general@lists.postgresql.org; Tue, 12 Aug 2025 17:40:25 +0000 Received: by mail-yb1-xb2f.google.com with SMTP id 3f1490d57ef6-e8ebd470b69so4276782276.1 for ; Tue, 12 Aug 2025 10:40:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1755020421; x=1755625221; darn=lists.postgresql.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=6FJ1yQegmZ6xeAqUqnId7HEgZm07k/IC/lttPqx0BFQ=; b=CTbu3qQaf9Zeh7jeY7U2CFNKjmRaOKKrisVMZsHGS8NgnvkiIYg6Br288GIQ87ZGTk PCtkh1rsB1OocoEaVB8Xr/Su9CI0m5JYSM5E3dWJ5Vp6HMAaEgHPHzD9cQxU1zMvBYIr 0lnhugBdaNqBI68DfggPujTLuxINNHVasx0N4RNoIg+mIxgf2I2/VtmT74Vru1JGYUkS H7eVQdTpp9s9YTM+aAeG43mIPYvkm9OTerfsb1ADHADJi1meD99oexspmjYLyhfRq6VN 5B6V71k6EvacPwzdr0G2UEVJPpjiRiCmr+faYR0ZNuGfNq3y0dKNGLFHTvEZuaJeE+7U 8AsA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1755020421; x=1755625221; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=6FJ1yQegmZ6xeAqUqnId7HEgZm07k/IC/lttPqx0BFQ=; b=r0eTCRDLggzYzgKzS99K8sNpg8yZXHByPfjcrUTB62e3G7BnWtXDGrXp2R91MQE7ZR W9yQUmKWy+TiIJZeFb/wsIzU78WXsHs3EC17SuEfIqGs1yHbh9q7ApFzcdu/TjwUkGW5 bigbYTBafDxxvpSSr0uTMM11eazDX6VfnNcWmsknXYhDcYyugLQxk0NBsIVjkEu3HCNE /vJu4qyqqA7hXbqKkHA9mw714nUcKr/3AFSikgTRz/WUSCKH7Xi8Y0KN+rfI04+BwaTD nsSqvpdFaugyMSTiCW/WRLJ0rsQf50itd9UNpPeFgemraFo1k8uWJ3VBKZB8V7AbM5Mw PbPA== X-Gm-Message-State: AOJu0Ywgp58Qi1vkPzo7OkXz2Ut1XxPoVZqvGVWIkgFj0EoGLheA1Rvm LAaRWvVlthUJ6hcjccnKRumEawIej0EyXZNlG8CwwcJ0mgxdgtb4v+dxaRZsaNdNRB2eBlRfzVn bfpqNQGqLvb7COD9rCkKM+xy773EvQ6+UKd6d X-Gm-Gg: ASbGncu02KpnyTo+e7STG/aC9GQSeD2iFIPBz83nFdpMrm9dw5gfAKP4G2v277Ofqkh 0Yh8qAJM0C/gf9EZCMMticAtp5QbioaeZIATPrqi+yWmVxBihekBI51+VHd895b9y7idr7E7G/e lJr/3roaVzFo4g3IsU9DoWiVutcDHvvDyJpc12ZjEIkIFdQCpMdargMbwCH6XN/x9ZsvXitryfx iDwpTE= X-Google-Smtp-Source: AGHT+IGneHLEGmKcqUdjm6GeY1TFfRFTEIJ4UiUD8/aVu4H6pM0oHxqMfwPVvo8+lsolIn4S+uDncMRrNuFTFbjpjqs= X-Received: by 2002:a05:6902:6c08:b0:e8e:2535:5ce with SMTP id 3f1490d57ef6-e930c0bcc16mr175596276.34.1755020420951; Tue, 12 Aug 2025 10:40:20 -0700 (PDT) MIME-Version: 1.0 References: <73f3723b-f279-43c6-884d-d12b3151ec9e@aklaver.com> In-Reply-To: <73f3723b-f279-43c6-884d-d12b3151ec9e@aklaver.com> From: Bob Jolliffe Date: Tue, 12 Aug 2025 18:40:08 +0100 X-Gm-Features: Ac12FXwkrJczYF-VriOiehp_rZN8DcO0ibMcXAzXBT369kgzGd2OozNp3kNuj_w Message-ID: Subject: Re: Questions about the continuity of WAL archiving To: pgsql-general@lists.postgresql.org Content-Type: multipart/alternative; boundary="000000000000c3c135063c2e8840" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000c3c135063c2e8840 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, 12 Aug 2025 at 17:14, Adrian Klaver wrote: > 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. > That is an interesting point you make Adrian. S3 seems quite popular for this type of archiving. What would you suggest as a more capable (and cost effective) storage platform? Regards Bob > > > > > Adrian Klaver > > =E4=BA=8E2025=E5=B9=B48=E6=9C=888= =E6=97=A5=E5=91=A8=E4=BA=94 23:23=E5=86=99=E9=81=93=EF=BC=9A > > > > -- > Adrian Klaver > adrian.klaver@aklaver.com > > > --000000000000c3c135063c2e8840 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Tue, 12 Aug 2025 at 17:14, Adrian Klav= er <adrian.klaver@aklaver.c= om> wrote:
On 8/12/25 01:24, px shi wro= te:
>
>=C2=A0 =C2=A0 =C2=A01) What is the current archiving setup on the prima= ry and why is
>=C2=A0 =C2=A0 =C2=A0lagging?
>
>=C2=A0 =C2=A0The archive command uses pgBackRest to archive to S3. Beca= use it is
> uploaded to S3, the archiving speed is slow, which has caused lagging.=
>
>=C2=A0 =C2=A0 =C2=A02) Have you looked at archiving off the standby nod= e while it is in
>=C2=A0 =C2=A0 =C2=A0standby per:
>
> Yes, archiving on the standby node is disabled. Is it recommended to <= br> > share the WAL archive between the primary and standby nodes to avoid <= br> > 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.

That is an interesting point you make Adrian.=C2=A0 S3 seems qu= ite popular for this type of archiving.=C2=A0 What would you suggest as a m= ore capable (and cost effective) storage platform?

Regar= ds
Bob=C2=A0

>
> Adrian Klaver <adrian.klaver@aklaver.com
> <mailto:adrian.klaver@aklaver.com>> =E4=BA=8E2025=E5=B9=B48=E6=9C=888= =E6=97=A5=E5=91=A8=E4=BA=94 23:23=E5=86=99=E9=81=93=EF=BC=9A
>

--
Adrian Klaver
adrian.klave= r@aklaver.com


--000000000000c3c135063c2e8840--