Re: [PATCH] Avoid a REPACK worker startup hang

From: Nikolay Samokhvalov <nik(at)postgres(dot)ai>
To: Alvaro Herrera <alvherre(at)kurilemu(dot)de>
Cc: pgsql-hackers mailing list <pgsql-hackers(at)postgresql(dot)org>, Antonin Houska <ah(at)cybertec(dot)at>, mihailnikalayeu(at)gmail(dot)com
Subject: Re: [PATCH] Avoid a REPACK worker startup hang
Date: 2026-09-13 18:39:39
Message-ID: CAM527d8xo=HLaT8JP+HNX4Cs_O7EeLaprqsfK4FPV-OnxsKK-g@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Sep 13, 2026 at 6:12 AM Alvaro Herrera
<alvherre(at)kurilemu(dot)de> wrote:
> I tried your isolation test against Bharath's patch, and I see that the
> error condition is reported correctly. I haven't reviewed that patch.
> I'll review that for push, maybe together with your proposed test
> addition.

I tested v4 further and followed up in that thread about the remaining
post-attachment waits:

https://www.postgresql.org/message-id/CAM527d8cF-6azsRWOPaOUCmsdgMG%3Dene7-st91_NM7v0q3uLLg%40mail.gmail.com

Nik

In response to

Browse pgsql-hackers by date

  From Date Subject
Previous Message Nikolay Samokhvalov 2026-09-13 18:37:49 Re: REPACK (CONCURRENTLY) backend waits indefinitely when decoding worker fails to start