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

From: Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com>
To: Xuneng Zhou <xunengzhou(at)gmail(dot)com>
Cc: "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>, Alexander Lakhin <exclusion(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-10 17:28:00
Message-ID: aimeoNYE93VLiQHt@bdtpg
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On Wed, Jun 10, 2026 at 04:36:14PM +0800, Xuneng Zhou wrote:
> On Tue, Jun 9, 2026 at 7:01 PM Bertrand Drouvot
> > 0002 does that by starting the new walsender and doing the decoding while the
> > startup is paused
> > 0004 does that by ensuring the pre-connected session triggers the decoding while
> > the startup is paused
>
> The
> essential thing is just to ensure that the startup remains paused
> until decoding output is observed.

Right, thanks for confirming. That's exactly what v2 is doing.

Regards,

--
Bertrand Drouvot
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Previous Message Tom Lane 2026-06-10 17:03:52 Re: Fix missing semicolon in pl_gram.y for option_value rule