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

From: Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>
To: Alvaro Herrera <alvherre(at)kurilemu(dot)de>
Cc: shihao zhong <zhong950419(at)gmail(dot)com>, Antonin Houska <ah(at)cybertec(dot)at>, Nikolay Samokhvalov <nik(at)postgres(dot)ai>, 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 19:06:00
Message-ID: CALj2ACW=bGA7BAUi1w+iULd0UyVjFLEj7=vAn6F-+qhK4D9jNg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On Thu, Sep 17, 2026 at 2:53 AM Alvaro Herrera <alvherre(at)kurilemu(dot)de> wrote:
>
> 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 Alvaro for taking care of this. I think it is fine to not have
the tests in core and to have them here in the thread for reference.
My thinking is that the issues fixed here look rare in practice and
making them run reliably and deterministically would need more
developer cycles. Moreover, we haven't had such tests for parallel
query for a while, and testing resources are not free. Others may have
a different opinion.

And thanks Shihao for reviewing and identifying one of the problems
and proposing the fix for it.

--
Bharath Rupireddy
Amazon Web Services: https://aws.amazon.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Previous Message Bharath Rupireddy 2026-09-17 19:03:00 Re: Support for 8-byte TOAST values, round two