public inbox for [email protected]
help / color / mirror / Atom feedFrom: Bob Jolliffe <[email protected]>
To: [email protected]
Subject: Re: Questions about the continuity of WAL archiving
Date: Tue, 12 Aug 2025 18:40:08 +0100
Message-ID: <CACd=f9c9MZUhjGc9hKZL=7S18LkxwW_LDsiH15wmUAO-ERkXxg@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <CAAccyYKpNsQMD+S-A7a8YtDevFN0uRXkzg4tYWWBOFsv_jASNg@mail.gmail.com>
<[email protected]>
<CAAccyYLYZmwQiNMoJcQgo5t+E24rDtu1ZeBUrER7ZTKNAcZesw@mail.gmail.com>
<[email protected]>
<CAAccyYJ-07SzCRAEkGJ2Qa8EAPCHQM4qcpB=OvD8P0zDbCJ0KQ@mail.gmail.com>
<[email protected]>
On Tue, 12 Aug 2025 at 17:14, Adrian Klaver <[email protected]>
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 <[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]
Subject: Re: Questions about the continuity of WAL archiving
In-Reply-To: <CACd=f9c9MZUhjGc9hKZL=7S18LkxwW_LDsiH15wmUAO-ERkXxg@mail.gmail.com>
* 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