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: <AA0098DA-EB2F-4092-AF82-922E1A54A7EF@gmail.com>
References: <5C6C7AA2-88FF-4F15-B7AC-92B2C2584877@gmail.com>
 <1435901.1656899131@sss.pgh.pa.us>
 <AA0098DA-EB2F-4092-AF82-922E1A54A7EF@gmail.com>
Comments: In-reply-to BeeRich Lists <bee.lists@gmail.com>
	message dated "Sun, 03 Jul 2022 23:21:28 -0400"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1450606.1656906357.1@sss.pgh.pa.us>
Date: Sun, 03 Jul 2022 23:45:57 -0400
Message-ID: <1450607.1656906357@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/1450607.1656906357%40sss.pgh.pa.us>
Precedence: bulk

BeeRich Lists <bee.lists@gmail.com> writes:
> It worked!  It was the firewall that needed a port hole poked in it.

Huh, interesting.  What I'd have expected from a firewall problem
is that the postmaster thinks it's listening on the port (and says
so at startup), but then no traffic actually reaches it.  The fact
that you didn't see any log entry about "listening on IPv4 address
so-and-so" suggests that your machine's version of a firewall is
interfering with even binding to the address.  Not impossible
I guess, but it's a new one on me.

			regards, tom lane