pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Adrian Klaver <adrian.klaver@aklaver.com>
To: Marc Millas <marc.millas@mokadb.com>
To: pgsql-general@lists.postgresql.org <pgsql-general@lists.postgresql.org>
Subject: Re: pg_reload_conf()
Date: Mon, 20 Feb 2023 09:01:08 -0800
Message-ID: <b85352be-eb2f-85e0-3dc3-7d6a19b052e2@aklaver.com> (raw)
In-Reply-To: <CADX_1aaLOnPrCAi3xR1onuOfbtRwA25ORTsX+ZcLJc24SWs2bg@mail.gmail.com>
References: <CADX_1aaLOnPrCAi3xR1onuOfbtRwA25ORTsX+ZcLJc24SWs2bg@mail.gmail.com>

On 2/20/23 08:57, Marc Millas wrote:
> select  setting, boot_val, reset_val from pg_settings where 
> name='log_connections';

# select  setting, boot_val, reset_val, context from pg_settings where 
name='log_connections';
  setting | boot_val | reset_val |      context
---------+----------+-----------+-------------------
  on      | off      | on        | superuser-backend


https://www.postgresql.org/docs/15/view-pg-settings.html

There are several possible values of context. In order of decreasing 
difficulty of changing the setting, they are:


...

superuser-backend

     Changes to these settings can be made in postgresql.conf without 
restarting the server. They can also be set for a particular session in 
the connection request packet (for example, via libpq's PGOPTIONS 
environment variable), but only if the connecting user is a superuser or 
has been granted the appropriate SET privilege. However, these settings 
never change in a session after it is started. If you change them in 
postgresql.conf, send a SIGHUP signal to the postmaster to cause it to 
re-read postgresql.conf. The new values will only affect 
subsequently-launched sessions.

...
-- 
Adrian Klaver
adrian.klaver@aklaver.com






view thread (4+ messages)  latest in thread

Message-ID: <b85352be-eb2f-85e0-3dc3-7d6a19b052e2@aklaver.com>
Permalink:  ../b85352be-eb2f-85e0-3dc3-7d6a19b052e2@aklaver.com/
Also on:    postgresql.org/message-id/b85352be-eb2f-85e0-3dc3-7d6a19b052e2@aklaver.com

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-general@postgresql.org
  Cc: adrian.klaver@aklaver.com, marc.millas@mokadb.com
  Subject: Re: pg_reload_conf()
  In-Reply-To: <b85352be-eb2f-85e0-3dc3-7d6a19b052e2@aklaver.com>
  References: <CADX_1aaLOnPrCAi3xR1onuOfbtRwA25ORTsX+ZcLJc24SWs2bg@mail.gmail.com> <b85352be-eb2f-85e0-3dc3-7d6a19b052e2@aklaver.com>

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

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