Re: error on connecting port 5432

From: Atul Kumar <akumar14871(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, Postgres General <pgsql-general(at)postgresql(dot)org>
Subject: Re: error on connecting port 5432
Date: 2020-12-02 07:02:11
Message-ID: CA+ONtZ7jTGdw4HGxnOT_8oHyS7koGCBCMQw5g1QER+vo9EJJAw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Thanks a lot Tom, I appended the -h /tmp and it worked.

I need just one more help from you.

Could you tell me that why & how that socket file existed in /tmp directory.

What is the practice to make sure that this file (.s.PGSQL.5432)
should be inside /var/run directory ? so that it will not throw such
error.

Please help me.

Regards,
Atul

On 12/1/20, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Atul Kumar <akumar14871(at)gmail(dot)com> writes:
>> Just to clarify that I am at root OS user, trying to create a test user
>> using postgres user(-u) with create user command.
>
> Given the reference to /var/run/postgresql, I'm suspecting that you
> are running a server that thinks it should put its socket in /tmp,
> but you have some copies of libpq on the machine that were built with
> default socket location /var/run/postgresql. When you are root, you
> are very likely using a different PATH that is finding a different
> createuser program linked to a different libpq.so than when you are
> not root.
>
> A possible workaround is to add "-h /tmp" to your command when
> running as root. Eventually you'd want to try to not have
> multiple postgres installations on the machine.
>
> regards, tom lane
>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Andreas Schmitz 2020-12-02 07:09:29 Re: error on connecting port 5432
Previous Message Hemil Ruparel 2020-12-02 06:44:03 Re: How to debug authentication issues in Postgres