public inbox for [email protected]
help / color / mirror / Atom feedFrom: px shi <[email protected]>
To: Greg Sabino Mullane <[email protected]>
Cc: [email protected]
Subject: Re: Questions about the continuity of WAL archiving
Date: Tue, 12 Aug 2025 16:33:48 +0800
Message-ID: <CAAccyYL1tE956RWaRrP-2a-Z+TBhsUi3QS+qO_BXjiHnNcFgog@mail.gmail.com> (raw)
In-Reply-To: <CAKAnmmJPGgEp2kKPomhq7P=GUA5HD1eOaP5X+7c68gm5f4YVqQ@mail.gmail.com>
References: <CAAccyYKpNsQMD+S-A7a8YtDevFN0uRXkzg4tYWWBOFsv_jASNg@mail.gmail.com>
<CAKAnmmJPGgEp2kKPomhq7P=GUA5HD1eOaP5X+7c68gm5f4YVqQ@mail.gmail.com>
>
> 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 work. And I would like to know if this is the recommended
configuration for production use?
Greg Sabino Mullane <[email protected]> 于2025年8月9日周六 02:25写道：
> 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 the
>> new primary, archiving will resume from file 100 on timeline 2. As a
>> result, WAL files from 81 to 100 on timeline 1 will be missing from the
>> archive.
>> Is there a good solution to prevent this situation?
>>
>
> I'm still not clear on what the problem here is, other than your archiving
> not keeping up. The best solution to that is:
>
>
> https://pgbackrest.org/1/configuration.html#section-archive/option-archive-async
>
> Yes, you would lost some ability for easy PITR for 80-100, but could still
> be done by resurrecting your crashed primary, or carefully grabbing from
> the replica before they get recycled. You can set archive_mode=always on
> the replicas to help with this.
>
> Cheers,
> Greg
>
> --
> Crunchy Data - https://www.crunchydata.com
> Enterprise Postgres Software Products & Tech Support
>
>
view thread (5+ 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: <CAAccyYL1tE956RWaRrP-2a-Z+TBhsUi3QS+qO_BXjiHnNcFgog@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