| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com> |
| Cc: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, Atul Kumar <akumar14871(at)gmail(dot)com>, pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: permission denied on socket |
| Date: | 2024-01-25 21:30:20 |
| Message-ID: | 455826.1706218220@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Ron Johnson <ronljohnsonjr(at)gmail(dot)com> writes:
> On Thu, Jan 25, 2024 at 3:32 PM Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
> wrote:
>> Best guess is you are using a version of psql that is expecting the
>> socket to be somewhere else then where it actually is.
> Is "permission denied" really the error you get when the socket does not
> exist?
Nope, that should mean either that /tmp is not readable, or that the
socket file is there but has restrictive permissions.
That doesn't necessarily make Adrian's answer wrong though.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2024-01-25 21:32:11 | Re: field error on refreshed materialized view |
| Previous Message | Michael Nolan | 2024-01-25 21:29:08 | field error on refreshed materialized view |