RE: t/035_standby_logical_decoding.pl might fail on attempt to read wrong timeline

From: "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>
To: 'Bertrand Drouvot' <bertranddrouvot(dot)pg(at)gmail(dot)com>
Cc: Alexander Lakhin <exclusion(at)gmail(dot)com>, "xunengzhou(at)gmail(dot)com" <xunengzhou(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: RE: t/035_standby_logical_decoding.pl might fail on attempt to read wrong timeline
Date: 2026-06-09 04:04:20
Message-ID: TYRPR01MB12156677791D04E4E858F3FCCF51D2@TYRPR01MB12156.jpnprd01.prod.outlook.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Dear Bertrand, Xuneng,

Thanks for sharing the reproducer and opinion. I could now understand.

While seeing, I felt the same issue can happen even for the streaming case.
Please see attached reproducer and possible fix.

Can you also include that point? Or this thread discusses only for the logical case?
If separated, I can take initiative for the streaming part, after the logical decoding
case.

Best regards,
Hayato Kuroda
FUJITSU LIMITED

Attachment Content-Type Size
0001-Reproducer-for-the-streaming-replication.patch application/octet-stream 4.6 KB
0002-Fix-race-condition-in-streaming-replication-timeline.patch application/octet-stream 1.4 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message shveta malik 2026-06-09 04:13:40 Re: [PATCH] Preserve replication origin OIDs in pg_upgrade
Previous Message Dilip Kumar 2026-06-09 03:57:48 Re: Proposal: Conflict log history table for Logical Replication