[prev in list] [next in list] [prev in thread] [next in thread] 

List:       postgresql-general
Subject:    Re: pg_reload_conf()
From:       Marc Millas <marc.millas () mokadb ! com>
Date:       2023-02-20 20:36:53
Message-ID: CADX_1ab7t=hkeCLReqj-cD9D+d+_gJOn5CErt+A=zdq3i1EHmg () mail ! gmail ! com
[Download RAW message or body]

Thanks Adrian,

the fact that the changes are visible only by the new backend, and NOT by
the backend which did the changes was what I did missed.

Marc MILLAS
Senior Architect
+33607850334
www.mokadb.com



On Mon, Feb 20, 2023 at 6:01 PM Adrian Klaver <adrian.klaver@aklaver.com>
wrote:

> 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
>
>

[Attachment #3 (text/html)]

<div dir="ltr">Thanks Adrian,<div><br><div>the fact that the changes are visible only \
by the new backend, and NOT by the backend which did the changes was what I did \
missed.</div><div><br clear="all"><div><div dir="ltr" class="gmail_signature" \
data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr">Marc \
MILLAS<div>Senior Architect</div><div>+33607850334</div><div><a \
href="http://www.mokadb.com" \
target="_blank">www.mokadb.com</a></div><div><br></div></div></div></div></div></div><br></div></div></div><br><div \
class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Feb 20, 2023 at 6:01 PM \
Adrian Klaver &lt;<a \
href="mailto:adrian.klaver@aklaver.com">adrian.klaver@aklaver.com</a>&gt; \
wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 2/20/23 08:57, Marc \
Millas wrote:<br> &gt; select   setting, boot_val, reset_val from pg_settings where \
<br> &gt; name=&#39;log_connections&#39;;<br>
<br>
# select   setting, boot_val, reset_val, context from pg_settings where <br>
name=&#39;log_connections&#39;;<br>
   setting | boot_val | reset_val |         context<br>
---------+----------+-----------+-------------------<br>
   on         | off         | on            | superuser-backend<br>
<br>
<br>
<a href="https://www.postgresql.org/docs/15/view-pg-settings.html" rel="noreferrer" \
target="_blank">https://www.postgresql.org/docs/15/view-pg-settings.html</a><br> <br>
There are several possible values of context. In order of decreasing <br>
difficulty of changing the setting, they are:<br>
<br>
<br>
...<br>
<br>
superuser-backend<br>
<br>
        Changes to these settings can be made in postgresql.conf without <br>
restarting the server. They can also be set for a particular session in <br>
the connection request packet (for example, via libpq&#39;s PGOPTIONS <br>
environment variable), but only if the connecting user is a superuser or <br>
has been granted the appropriate SET privilege. However, these settings <br>
never change in a session after it is started. If you change them in <br>
postgresql.conf, send a SIGHUP signal to the postmaster to cause it to <br>
re-read postgresql.conf. The new values will only affect <br>
subsequently-launched sessions.<br>
<br>
...<br>
-- <br>
Adrian Klaver<br>
<a href="mailto:adrian.klaver@aklaver.com" \
target="_blank">adrian.klaver@aklaver.com</a><br> <br>
</blockquote></div>



[prev in list] [next in list] [prev in thread] [next in thread]