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

From Hayato Kuroda (Fujitsu)
Subject RE: t/035_standby_logical_decoding.pl might fail on attempt to read wrong timeline
Date
Msg-id TYRPR01MB12156677791D04E4E858F3FCCF51D2@TYRPR01MB12156.jpnprd01.prod.outlook.com
Whole thread
In response to Re: t/035_standby_logical_decoding.pl might fail on attempt to read wrong timeline  (Bertrand Drouvot <bertranddrouvot.pg@gmail.com>)
Responses Re: t/035_standby_logical_decoding.pl might fail on attempt to read wrong timeline
List 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

pgsql-hackers by date:

Previous
From: Dilip Kumar
Date:
Subject: Re: Proposal: Conflict log history table for Logical Replication
Next
From: shveta malik
Date:
Subject: Re: [PATCH] Preserve replication origin OIDs in pg_upgrade