From: Tom Lane <tgl@sss.pgh.pa.us>
To: BeeRich Lists <bee.lists@gmail.com>
cc: Submit Postgresql Novice <pgsql-novice@postgresql.org>
Subject: Re: psql: error: could not connect to server: Connection refused
In-reply-to: <5C6C7AA2-88FF-4F15-B7AC-92B2C2584877@gmail.com>
References: <5C6C7AA2-88FF-4F15-B7AC-92B2C2584877@gmail.com>
Comments: In-reply-to BeeRich Lists <bee.lists@gmail.com>
	message dated "Sun, 03 Jul 2022 21:06:33 -0400"
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-ID: <1435900.1656899131.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Sun, 03 Jul 2022 21:45:31 -0400
Message-ID: <1435901.1656899131@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/1435901.1656899131%40sss.pgh.pa.us>
Precedence: bulk

BeeRich Lists <bee.lists@gmail.com> writes:
> Hi folks.  I cannot connect to my postgres server.  I=E2=80=99ve run thr=
ough all the directives and I still can=E2=80=99t understand why this isn=E2=
=80=99t showing up.  =


It sure looks like the postmaster doesn't think you told it to
listen on any TCP sockets, because if it did they'd have been
listed in the initial log output.  Are you sure that this setting
is really the active one?

> listen_addresses =3D '*'

It could also be that there is something weird about your system
environment that is causing '*' to expand to nothing.  Try
explicitly specifying '127.0.0.1, ::1' instead.

			regards, tom lane