| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Teja Jakkidi <teja(dot)jakkidi05(at)gmail(dot)com> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, pgsql-admin(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Postgres open source upgrades |
| Date: | 2022-06-28 20:26:11 |
| Message-ID: | 2748258.1656447971@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Teja Jakkidi <teja(dot)jakkidi05(at)gmail(dot)com> writes:
> Cluster started and I was able to connect remotely with no issues. However when I tried using psql, I got below error:
> Connection to server on socket “/var/run/postgresql/.s.PGSQL.5432” failed.
> But my postgres has been using socket file in /tmp location before upgrade. I am not sure why after upgrade psql is searching at a different allocation 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Teja Jakkidi | 2022-06-28 21:05:33 | Re: Postgres open source upgrades |
| Previous Message | David G. Johnston | 2022-06-28 20:24:43 | Re: Postgres open source upgrades |