Re: search_path not reloaded via unix socket connections

Kong Man <kong_mansatiansin@hotmail.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
changeactually 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