We just found out that the problem was that our own ~/.psqlrc contained the SET
statement, overriding the global setting.
From: kong_mansatian...@hotmail.com
To: t...@sss.pgh.pa.us
CC: pgsql-general@postgresql.org
Subject: RE: [GENERAL] search_path not reloaded via unix socket connections
Date
other words the connection string and what client are you using?
> From: t...@sss.pgh.pa.us
> To: kong_mansatian...@hotmail.com
> CC: pgsql-general@postgresql.org
> Subject: Re: [GENERAL] search_path not reloaded via unix socket
connections
> Date: Thu, 17 Sep 2015 22:29:04 -0400
resql.org
> Subject: Re: [GENERAL] search_path not reloaded via unix socket connections
> Date: Thu, 17 Sep 2015 22:29:04 -0400
>
> Kong Man writes:
> > Can anybody explain why the search_path setting, with several config
> > reloads, would not change via local co
"David G. Johnston" writes:
> As an aside the alter user/database commands do end up requiring the user
> to disconnect and reconnect. Is there a hard limitation why an
> administrator can't send some kind of signal to cause a re-read of those by
> an active session?
If we wanted to redefine the
On Thursday, September 17, 2015, Tom Lane wrote:
> "David G. Johnston" > writes:
> > Or not, since it does appear that the reload signal is propagated to
> active
> > sessions and take effect after the most recent command finishes.
>
> Yeah. I had been wondering about long-lived open transaction
"David G. Johnston" writes:
> Or not, since it does appear that the reload signal is propagated to active
> sessions and take effect after the most recent command finishes.
Yeah. I had been wondering about long-lived open transactions, but AFAICS
from the code, backends should re-read the config
On Thursday, September 17, 2015, David G. Johnston <
david.g.johns...@gmail.com> wrote:
> On Thursday, September 17, 2015, Kong Man > wrote:
>
>> Can anybody explain why the search_path setting, with several config
>> reloads, would not change via local connections? We struggled with our
>> prod
On Thursday, September 17, 2015, Kong Man
wrote:
> Can anybody explain why the search_path setting, with several config
> reloads, would not change via local connections? We struggled with our
> production settings on Postgres 9.3 today, only to realize, after a while,
> that the search_path cha
Kong Man writes:
> Can anybody explain why the search_path setting, with several config reloads,
> would not change via local connections? We struggled with our production
> settings on Postgres 9.3 today, only to realize, after a while, that the
> search_path change actually took effect via T
