Re: search_path not reloaded via unix socket connections

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Kong Man <kong_mansatiansin(at)hotmail(dot)com>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: search_path not reloaded via unix socket connections
Date: 2015-09-18 02:29:04
Message-ID: 30630.1442543344@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Kong Man <kong_mansatiansin(at)hotmail(dot)com> 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 TCP/IP, but not unix socket, connections ever since the first reload.

That's, um, pretty hard to believe. Less magical interpretations would
involve something like a per-user or per-database setting overriding
what's in the config file in some sessions but not others. But I really
really doubt that TCP vs unix socket is the determining factor.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message David G. Johnston 2015-09-18 02:45:10 Re: search_path not reloaded via unix socket connections
Previous Message Quiroga, Damian 2015-09-18 02:25:20 Re: Hiding name and version