000100AE). As a
result, while the new primary does not have any local WAL gaps, the archive
directory will contain a gap in that WAL range.
I’m not sure if I explained it clearly.
Justin 于2025年8月13日周三 10:51写道：
>
>
> On Tue, Aug 12, 2025 at 10:24 PM px shi wrote:
>
not existing?
>
> If it's _ever_ happened, you should _fix that_ instead of rolling your own
> WAL archival.process.
>
> On Tue, Aug 12, 2025 at 10:05 PM px shi wrote:
>
>> Hi, Adrian
>>
>> Given that you are using a less then capable storage solution(S3) why
eal time. As long as real-time
archiving cannot be achieved, there will always be some WAL files that are
not archived if the primary node crashes.
Adrian Klaver 于2025年8月13日周三 00:14写道：
> On 8/12/25 01:24, px shi wrote:
> >
> > 1) What is the current archiving setup on the primary
>
> Bog-standard PgBackRest retains all WAL files required for a full backup
> set and its associated differential/incremental backups.
Yes, WAL files are continuous under normal circumstances. However, if the
primary node crashes under high load, the archived WAL logs on S3 may be
discontinuous.
>
> I'm still not clear on what the problem here is, other than your archiving
> not keeping up.
In my scenario, archive_mode is not set to always on the replicas, it may
cause interruptions in the archived WAL logs.
You can set archive_mode=always on the replicas to help with this.
Yes, it can
dby
> 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?
Adrian Klaver 于2025年8月8日周五 23:23写道：
> On 8/7/25 22:50, px shi wrote:
> > Thank you for your reply.
> > T
ackup yet, these
WAL logs can still be used to recover to any point on timeline 2.
Regards,
Pixian Shi
Adrian Klaver 于2025年8月8日周五 12:25写道：
> On 8/7/25 20:20, px shi wrote:
> > Hi,
> > There is a scenario: the current timeline of the PostgreSQL primary node
> > is 1, and
Hi,
There is a scenario: the current timeline of the PostgreSQL primary node is
1, and the latest WAL file is 100. The standby node has also received up to
WAL file 100. However, the latest WAL file archived is only file 80. If the
primary node crashes at this point and the standby is promoted to t
