From: Tom Lane <tgl@sss.pgh.pa.us>
To: Teja Jakkidi <teja.jakkidi05@gmail.com>
cc: Bruce Momjian <bruce@momjian.us>, pgsql-admin@lists.postgresql.org
Subject: Re: Postgres open source upgrades
In-reply-to: <AAE7AA79-1C07-4365-BC0B-4282A518E6FB@gmail.com>
References: <YrtgFX7Zu04ctk3e@momjian.us>
 <AAE7AA79-1C07-4365-BC0B-4282A518E6FB@gmail.com>
Comments: In-reply-to Teja Jakkidi <teja.jakkidi05@gmail.com>
	message dated "Tue, 28 Jun 2022 13:14:08 -0700"
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-ID: <2748257.1656447971.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Tue, 28 Jun 2022 16:26:11 -0400
Message-ID: <2748258.1656447971@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/2748258.1656447971%40sss.pgh.pa.us>
Precedence: bulk

Teja Jakkidi <teja.jakkidi05@gmail.com> writes:
> Cluster started and I was able to connect remotely with no issues. Howev=
er when I tried using psql, I got below error:
>         Connection to server on socket =E2=80=9C/var/run/postgresql/.s.P=
GSQL.5432=E2=80=9D failed.
> But my postgres has been using socket file in /tmp location before upgra=
de. I am not sure why after upgrade psql is searching at a different alloc=
ation for socket. =

> Can someone help me here? =


Some distributions configure the code with a different default socket
location because they don't like putting the socket in /tmp.  It's
best to use a server and libraries all built by the same source so
that you don't have to fight with decisions like that.  If you have
to, though, it's possible to force the server to put its socket
where you want (see unix_socket_directories).

			regards, tom lane