public inbox for [email protected]
help / color / mirror / Atom feedFrom: Adrian Klaver <[email protected]>
To: px shi <[email protected]>
Cc: [email protected]
Subject: Re: Questions about the continuity of WAL archiving
Date: Tue, 12 Aug 2025 09:14:19 -0700
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAAccyYJ-07SzCRAEkGJ2Qa8EAPCHQM4qcpB=OvD8P0zDbCJ0KQ@mail.gmail.com>
References: <CAAccyYKpNsQMD+S-A7a8YtDevFN0uRXkzg4tYWWBOFsv_jASNg@mail.gmail.com>
<[email protected]>
<CAAccyYLYZmwQiNMoJcQgo5t+E24rDtu1ZeBUrER7ZTKNAcZesw@mail.gmail.com>
<[email protected]>
<CAAccyYJ-07SzCRAEkGJ2Qa8EAPCHQM4qcpB=OvD8P0zDbCJ0KQ@mail.gmail.com>
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 <[email protected]
> <mailto:[email protected]>> 于2025年8月8日周五 23:23写道：
>
--
Adrian Klaver
[email protected]
view thread (12+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: Questions about the continuity of WAL archiving
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox