Re: BUG #16086: Cannot connect using psql, however I can connect using pgadmin

Hi Jeff, thanks for the reply, I have found where I went wrong.
I am very new in the PSQL world, I am an oracle dba by profession.

I wanted to change the port from default to 5437, initially it worked, but suddendly I had issues connecting.
I changed the port postgresql.conf back to 5432.

[root(at)zardplpsmasdev01 data]# su - postgres -c "psql"
psql (12.0)
Type "help" for help.

postgres=#

________________________________
From: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
Sent: Tuesday, 29 October 2019 13:27
To: PG Bug reporting form <noreply(at)postgresql(dot)org>
Cc: pgsql-bugs <pgsql-bugs(at)lists(dot)postgresql(dot)org>; mzwai99(at)outlook(dot)com <mzwai99(at)outlook(dot)com>
Subject: Re: BUG #16086: Cannot connect using psql, however I can connect using pgadmin

LOG: listening on Unix socket "/u01/postgresql/.s.PGSQL.5437"
LOG: listening on Unix socket "/tmp/.s.PGSQL.5437"

...

[root(at)zardplpsmasdev01 ~]# su - postgres -c "psql"
psql: error: could not connect to server: could not connect to server: No
such file or directory
Is the server running locally and accepting
connections on Unix domain socket
"/var/run/postgresql/.s.PGSQL.5432"?

You probably have multiple binaries installed coming from different packages or package managers. psql is searching for the socket in one place, which is not either of the two places the server is listening. You could explicitly tell it where to connect with either `-h /tmp`, or `-h 127.0.0.1`. Or you could find the correct "psql" to run (the one that came with the running server) so that it just knows where to look, possibly uninstalling the wrong psql to minimize future confusion.

Cheers,

Jeff