public inbox for [email protected]  

help / color / mirror / Atom feed

From: Tom Lane <[email protected]>
To: Balkrishna Pandey <[email protected]>
Cc: [email protected]
Subject: Re: Docs: Clarify that SIGHUP/reload does not update all GUCs for existing sessions
Date: Wed, 14 Jan 2026 01:47:11 -0500
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAEdRop3fo784VmdeEWc3HXn-_x-tTx6AFXgNh78WGrhKkqvgtw@mail.gmail.com>
References: <CAEdRop3fo784VmdeEWc3HXn-_x-tTx6AFXgNh78WGrhKkqvgtw@mail.gmail.com>

Balkrishna Pandey <[email protected]> writes:
> *Proposed wording (illustrative diff):*

> *+ The main server process also propagates this signal to all currently
> running server processes.+ Existing sessions will adopt new values for
> parameters whose context allows changes at reload+ time (for example,
> sighup). Parameters whose context is backend or superuser-backend do not+
> change within an already-started session; changes to those only affect
> subsequently-launched+ sessions.*

This seems to me to be getting way too far into the implementation weeds,
while still failing to cover everything.  For example, it's also true
that a SET within the session will override postgresql.conf.

The main intent of the code is that SIGHUP will propagate a
postgresql.conf change into an existing session if that session
had been using the previous value from postgresql.conf.  If its
source for the active value was something else, nothing changes.
You can argue about whether "backend"-context GUCs are an exception
to that rule, but I think our statement in the docs should be
about at that level of complexity.

			regards, tom lane

view thread (4+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: Docs: Clarify that SIGHUP/reload does not update all GUCs for existing sessions
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox