From: | Atul Kumar <akumar14871(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com>, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: permission denied on socket |
Date: | 2024-01-26 02:40:38 |
Message-ID: | CA+ONtZ7wQNQMedQyecaLe4O+7ghHWmQy8Lk9gSvTLCHDhenGLQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I checked the permissions on /tmp directory and it shows "drwxrwxrwt."
already, do I need to check something else as well ?
Regards.
On Fri, Jan 26, 2024 at 3:00 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> 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 | Tom Lane | 2024-01-26 03:45:33 | Re: permission denied on socket |
Previous Message | Michael Nolan | 2024-01-25 21:51:24 | Re: field error on refreshed materialized view |