Re: Docs: Clarify that SIGHUP/reload does not update all GUCs for existing sessions - Mailing list pgsql-docs

From David G. Johnston
Subject Re: Docs: Clarify that SIGHUP/reload does not update all GUCs for existing sessions
Date
Msg-id CAKFQuwasYhypiu6UpL3=YTkMef1JXRokwpQbnx9U5GgsQPb0WQ@mail.gmail.com
Whole thread Raw
In response to Re: Docs: Clarify that SIGHUP/reload does not update all GUCs for existing sessions  (Balkrishna Pandey <balkrishna.pandey@gmail.com>)
List pgsql-docs
Please follow our example and avoid top-posting.

On Tuesday, January 13, 2026, Balkrishna Pandey <balkrishna.pandey@gmail.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.

pgsql-docs by date:

Previous
From: Balkrishna Pandey
Date:
Subject: Re: Docs: Clarify that SIGHUP/reload does not update all GUCs for existing sessions
Next
From: PG Doc comments form
Date:
Subject: 3.5. Window Functions, example table