Request a Demo
Home   >   mailing lists

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

From Bertrand Drouvot
Subject Re: t/035_standby_logical_decoding.pl might fail on attempt to read wrong timeline
Date
Msg-id aimeoNYE93VLiQHt@bdtpg
Whole thread
In response to Re: t/035_standby_logical_decoding.pl might fail on attempt to read wrong timeline  (Xuneng Zhou <xunengzhou@gmail.com>)
Responses Re: t/035_standby_logical_decoding.pl might fail on attempt to read wrong timeline
List pgsql-hackers
Tree view 
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

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Fix missing semicolon in pl_gram.y for option_value rule
Next
From: "Pavlo Golub"
Date:
Subject: [PATCH v5] pg_stat_statements: Add last_execution_start column