From: | ProPAAS DBA <dba(at)propaas(dot)com> |
---|---|
To: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: psql only works with -h (even localhost) |
Date: | 2017-01-25 20:30:11 |
Message-ID: | 37b469be-2a27-bb89-8fc9-11b4bb625c7d@propaas.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 01/25/2017 09:35 AM, Tom Lane wrote:
> Steve Crawford <scrawford(at)pinpointresearch(dot)com> writes:
>> Adrian asks the correct questions. Lacking the answers to those I'm going
>> to venture a guess that a Unix-domain socket exists but access via
>> Unix-domain sockets is somehow blocked, probably by pg_hba.conf.
> Actually, the more common case I've seen is that the server put the
> socket file in directory X but psql (or more specifically libpq)
> is looking in directory Y. Try "show unix_socket_directories"
> (or on older server versions "show unix_socket_directory") in a
> successful connection, and compare to the path that psql shows when
> bleating that it can't connect.
>
> Usually this isn't operator error per se, but inconsistent defaults
> between builds obtained from different sources.
>
> regards, tom lane
Thanks Tom;
This was the issue...
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Kellerer | 2017-01-25 20:59:25 | How does Postgres estimate the memory needed for sorting/aggregating |
Previous Message | Shailesh Singh | 2017-01-25 17:57:47 | Re: Fwd: I could not see any row in audit table |