| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| 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:45:10 |
| Message-ID: | CAKFQuwbsyouFeX4HeO=RFpnfaQoCdk0-hrfVc9PCGhUYkHyoyQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thursday, September 17, 2015, Kong Man <kong_mansatiansin(at)hotmail(dot)com>
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 change actually took effect via TCP/IP, but not unix
> socket, connections ever since the first reload.
>
>
What Tom said...
Alternatively maybe your Unix socket sessions are long lived but your
TCP/IP ones are not - potentially going through a pooler that refreshes
sessions. You need to describe more or provide repeatable evidence if we
are to conclude that this is anything other than operator error.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2015-09-18 02:50:51 | Re: search_path not reloaded via unix socket connections |
| Previous Message | Tom Lane | 2015-09-18 02:29:04 | Re: search_path not reloaded via unix socket connections |