Horton

Re: Infinite loop in XLogPageRead() on standby

Michael Paquier <michael@paquier.xyz>

View thread
From: Michael Paquier <michael@paquier.xyz>
To: Alexander Kukushkin <cyberdemn@gmail.com>
Cc: Ants Aasma <ants.aasma@cybertec.at>, Kyotaro Horiguchi <horikyota.ntt@gmail.com>, pgsql-hackers@postgresql.org, thomas.munro@gmail.com
Date: 2024-12-25T03:00:59Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Fix header check for continuation records where standbys could be stuck

  2. Move routines to manipulate WAL into PostgreSQL::Test::Cluster

  3. Prevent archive recovery from scanning non-existent WAL files.

  4. Fix scenario where streaming standby gets stuck at a continuation record.

On Wed, Nov 13, 2024 at 02:18:06PM +0100, Alexander Kukushkin wrote:
> Now that v17 is released and before v18 feature freeze we have a few
> months, I hope you will find some time to look at it.

My apologies for taking a couple of weeks before coming back to this
thread.  I have been informed a couple of days ago about a report
which is showing the same symptoms as what you have reported.  Please
note that we have two other threads which refer to the same problem as
what you have here:
https://www.postgresql.org/message-id/15567-a9ff747c5e7c031c%40postgresql.org
https://www.postgresql.org/message-id/CAJ%2BDhQaf9ZMkqPPnapu06mvMFe-b_K4NGF%2B-MV%2Be%3DJB2edF4cQ%40mail.gmail.com

All of them refer to an infinite loop reachable in the startup process
when we read an incorrect incomplete record just after a failover or
when a WAL receiver restarts.  Not sure which way is best in order to
fix all of them in one shot, I am still considering what the possible
options at hand are here.
--
Michael