Re: t/035_standby_logical_decoding.pl might fail on attempt to read wrong timeline - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: t/035_standby_logical_decoding.pl might fail on attempt to read wrong timeline
Date
Msg-id aiqFjzGHpnYFP-Gm@paquier.xyz
Whole thread
In response to Re: t/035_standby_logical_decoding.pl might fail on attempt to read wrong timeline  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
On Thu, Jun 11, 2026 at 10:15:01AM +0900, Michael Paquier wrote:
> The backpatch of PG16 is straight-forward and adding
> GetWALInsertionTimeLineIfSet() down there does not look like an issue.
> Not having any tests in v16 feels sad, but that's life.  It does not
> prevent addressing the availability issue on this branch.

Backpatch of GetWALInsertionTimeLineIfSet() done in v16.

> I'll go take it up from here.

I have spent some time on the first part of this patch series,
focusing on the noisiest path for logical replication, and applied it
down to v17.  I have been able to reproduce the problem using
Alexander's sleep trick, and let 035 run with the same trick and the
patch applied for a few hundred runs.

Note that REL_17_STABLE has currently 4 failures in the buildfarm, due
to me messing up with the existence of injection_points.  I'll
probably just remove the test on this branch, 105b2cb33617 adding the
requirement on the module only in v18~.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Junwang Zhao
Date:
Subject: Re: PG19 FK fast path: OOB write and missed FK checks during batched
Next
From: Ewan Young
Date:
Subject: Re: Make SPI_prepare argtypes argument const