Re: REPACK (CONCURRENTLY) backend waits indefinitely when decoding worker fails to start

From: Alvaro Herrera <alvherre(at)kurilemu(dot)de>
To: shihao zhong <zhong950419(at)gmail(dot)com>
Cc: Antonin Houska <ah(at)cybertec(dot)at>, Nikolay Samokhvalov <nik(at)postgres(dot)ai>, Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Nathan Bossart <nathandbossart(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: REPACK (CONCURRENTLY) backend waits indefinitely when decoding worker fails to start
Date: 2026-09-17 09:53:23
Message-ID: aqu3Pt_j33fnPmfU@alvherre.pgsql
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hello,

I have pushed these fixes, with some editorialization of my own.

I decided not to push the test case, because it has some nontrivial
additions to the injection point infrastructure that I'm not so sure
about. The part of the test that doesn't require those changes could
perhaps be considered for 19, and we can discuss adding the rest in 20.

Thanks!

--
Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Zhijie Hou (Fujitsu) 2026-09-17 09:55:16 RE: Distinguish publication exclusions in object addresses
Previous Message Antonin Houska 2026-09-17 09:52:42 Re: Race conditions in logical decoding