MIME-Version: 1.0
From: px shi <spxlyy123@gmail.com>
Date: Fri, 8 Aug 2025 11:20:59 +0800
Message-ID: <CAAccyYKpNsQMD+S-A7a8YtDevFN0uRXkzg4tYWWBOFsv_jASNg@mail.gmail.com>
Subject: Questions about the continuity of WAL archiving
To: pgsql-general@lists.postgresql.org
Content-Type: multipart/alternative; boundary="000000000000d26cab063bd210fc"
Archived-At: <https://www.postgresql.org/message-id/CAAccyYKpNsQMD%2BS-A7a8YtDevFN0uRXkzg4tYWWBOFsv_jASNg%40mail.gmail.com>
Precedence: bulk

--000000000000d26cab063bd210fc
Content-Type: text/plain; charset="UTF-8"

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.
Is there a good solution to prevent this situation?

Regards,
Pixian Shi

--000000000000d26cab063bd210fc
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi,=C2=A0<div>There is a scenario: the current timeline of=
 the PostgreSQL primary node is 1, and the latest WAL file is 100. The stan=
dby 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 th=
e standby is promoted to the new primary, archiving will resume from file 1=
00 on timeline 2. As a result, WAL files from 81 to 100 on timeline 1 will =
be missing from the archive.<br>Is there a good solution to prevent this si=
tuation?</div><div><br></div><div>Regards,</div><div>Pixian Shi</div></div>

--000000000000d26cab063bd210fc--