Andres Freund <andres@anarazel.de> writes:
> On 2022-03-04 09:54:28 -0500, Tom Lane wrote:
>> I find it a little suspicious that startcreate is merrily starting
>> the postmaster on port 5432, without concern for the possibility
>> that that port is in use or blocked by a packet filter.
> It's a container that's just created for that run, so there shouldn't be
> anything else running. We also see that the server successfully starts:
True, so the port was free. The postmaster wouldn't know whether there's
a relevant packet filter though. The reason I'm harping on this is that
it's hard to see why this postmaster start would fail before anything
was actually done, when several previous starts on other ports behaved
just fine.
Actually ... looking closer at the failure log:
[09:41:50.589] Checking plpgsql
[09:41:50.608] (using postmaster on Unix socket, default port)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[09:41:50.608] ============== dropping database "pl_regression" ==============
[09:41:52.731] psql: error: connection to server at "localhost" (::1), port 5432 failed: Connection refused
(0x0000274D/10061)
[09:41:52.731] Is the server running on that host and accepting TCP/IP connections?
[09:41:52.731] connection to server at "localhost" (127.0.0.1), port 5432 failed: Connection refused (0x0000274D/10061)
[09:41:52.731] Is the server running on that host and accepting TCP/IP connections?
pg_regress thinks the postmaster is listening to a Unix socket.
Maybe it's *only* listening to a Unix socket. In any case,
psql has very clearly not been told to use a Unix socket.
Something is not wired up correctly there.
regards, tom lane