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

From: "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>
To: 'shveta malik' <shveta(dot)malik(at)gmail(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Cc: 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 05:12:09
Message-ID: OS7PR01MB18317138566060CDB5AE125B6F5652@OS7PR01MB18317.jpnprd01.prod.outlook.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

Best regards,
Hayato Kuroda
FUJITSU LIMITED

In response to

Responses

Browse pgsql-hackers by date

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