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

Bertrand Drouvot <bertranddrouvot.pg@gmail.com>

From: Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
To: Xuneng Zhou <xunengzhou@gmail.com>
Cc: "Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>, Alexander Lakhin <exclusion@gmail.com>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2026-06-10T17:28:00Z
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



Commits

  1. Fix second race with timeline selection during promotion

  2. Remove TAP test for timeline lookup race with logical decoding on standbys

  3. Fix race with timeline selection in logical decoding during promotion

  4. Backport GetWALInsertionTimeLineIfSet()

  5. TAP test for logical decoding on standby