From: Tom Lane <tgl@sss.pgh.pa.us>
To: SAMMY CRISWELL <Sammy_R_Criswell@raytheon.com>
cc: pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: Psql: could not connect to server: No such file or directory
In-reply-to: 
 <363d3b8ca13a408c81d584a28d29da8e@BN1F00802MB0033.008f.mgd2.msft.net>
References: 
 <363d3b8ca13a408c81d584a28d29da8e@BN1F00802MB0033.008f.mgd2.msft.net>
Comments: In-reply-to SAMMY CRISWELL <Sammy_R_Criswell@raytheon.com>
	message dated "Thu, 02 May 2019 15:50:18 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2605.1556816864.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Thu, 02 May 2019 13:07:44 -0400
Message-ID: <2606.1556816864@sss.pgh.pa.us>
Precedence: bulk

SAMMY CRISWELL <Sammy_R_Criswell@raytheon.com> writes:
> I am preparing to upgrade my pqsl server from 9.3.5 to 9.6.12. I have in=
stalled the 9.6 rpm onto the server that has 9.3.5 running. Postgres is st=
ill running 9.3.5 on that server, but when I try to run psql I get the fol=
lowing message.

> "psql: 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"?"
> The database is still running and working I just can't use any of the cl=
ient commands like psql, pg_dump....
> And there is no "/var/run/postgresql/.s.PGSQL.5432" file.

What you've probably run into here is that some packagers build Postgres
to put the server's socket file into /tmp, while others build it to put
the socket into /var/run/postgresql/ or some similar path.  Likely,
you are now using a new version of libpq.so that expects the latter
while your server is still doing the former.  You can override libpq's
default with "-h /tmp" or equivalent in order to connect.

			regards, tom lane