Re: Docs: Clarify that SIGHUP/reload does not update all GUCs for existing sessions

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Balkrishna Pandey <balkrishna(dot)pandey(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-docs(at)lists(dot)postgresql(dot)org" <pgsql-docs(at)lists(dot)postgresql(dot)org>
Subject: Re: Docs: Clarify that SIGHUP/reload does not update all GUCs for existing sessions
Date: 2026-01-14 14:10:03
Message-ID: CAKFQuwasYhypiu6UpL3=YTkMef1JXRokwpQbnx9U5GgsQPb0WQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-docs

Please follow our example and avoid top-posting.

On Tuesday, January 13, 2026, Balkrishna Pandey <balkrishna(dot)pandey(at)gmail(dot)com>
wrote:

> What I was trying to address is the impression a reader may get from “so
> that existing sessions also adopt the new values,” namely that *all*
> changed settings automatically take effect everywhere.
>

Yeah, getting rid of the somewhat unclear word “adopt” might be good.
Maybe say: “update their internal setting value hierarchy”.

David J.

In response to

Browse pgsql-docs by date

  From Date Subject
Previous Message Balkrishna Pandey 2026-01-14 06:57:54 Re: Docs: Clarify that SIGHUP/reload does not update all GUCs for existing sessions