Re: Questions about the continuity of WAL archiving

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: px shi <spxlyy123(at)gmail(dot)com>
Cc: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Questions about the continuity of WAL archiving
Date: 2025-08-12 16:14:19
Message-ID: 73f3723b-f279-43c6-884d-d12b3151ec9e@aklaver.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-general

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 <adrian(dot)klaver(at)aklaver(dot)com
> <mailto:adrian(dot)klaver(at)aklaver(dot)com>> 于2025年8月8日周五 23:23写道:
>

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Bob Jolliffe 2025-08-12 17:40:08 Re: Questions about the continuity of WAL archiving
Previous Message Adrian Klaver 2025-08-12 16:04:16 Re: Inquiry: Using PostgreSQL as a Staging Database for SAP ERP Data Export