| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | px shi <spxlyy123(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Questions about the continuity of WAL archiving |
| Date: | 2025-08-08 04:25:30 |
| Message-ID: | fd5c6708-3791-4339-83a2-e5fc389cd9cb@aklaver.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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 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.
What are you planning to do with the archived files?
Also is not the case that once the primary crashes you are in a split
brain case and can't really trust it's timeline anymore?
> Is there a good solution to prevent this situation?
>
> Regards,
> Pixian Shi
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | px shi | 2025-08-08 05:50:19 | Re: Questions about the continuity of WAL archiving |
| Previous Message | px shi | 2025-08-08 03:20:59 | Questions about the continuity of WAL archiving |