Re: [PG19] Promotion hangs behind a backend blocked on a stuck client

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>
Cc: shveta malik <shveta(dot)malik(at)gmail(dot)com>, shihao zhong <zhong950419(at)gmail(dot)com>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Manu <manuelreyesbravo(at)gmail(dot)com>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Noah Misch <noah(at)leadboat(dot)com>, shveta malik <shvetamalik(at)gmail(dot)com>
Subject: Re: [PG19] Promotion hangs behind a backend blocked on a stuck client
Date: 2026-10-22 06:15:41
Message-ID: CAA4eK1KoyPqFMKfhQ0vR2UZnkPUiK7xUoGUXAq7pXxMUYNDjTA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Oct 22, 2026 at 10:42 AM Hayato Kuroda (Fujitsu)
<kuroda(dot)hayato(at)fujitsu(dot)com> wrote:
>
> Hi Amit, Shveta,
>
> > After a configuration reload, an existing session picks up the new
> > value when its client sends the next query.
>
> IIUC the description is correct: a backend process reloads the configuration in
> the main loop, and assign hook can be called there. But yours are also OK if you
> think it's too detail.
>

I am also okay with both but would prefer mine as that appears clear
and succinct.

--
With Regards,
Amit Kapila.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message shveta malik 2026-10-22 06:23:51 Re: [PG19] Promotion hangs behind a backend blocked on a stuck client
Previous Message Manu 2026-10-22 05:23:09 Re: [PG19] Promotion hangs behind a backend blocked on a stuck client