From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
Cc: Thomas Munro <thomas.munro@gmail.com>
Cc: Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: Regression tests failures on Windows Server 2019 - on master at commit # d816f366b
Date: Fri, 04 Mar 2022 12:23:43 -0500
Message-ID: <3892341.1646414623@sss.pgh.pa.us> (raw)
In-Reply-To: <20220304171014.7rubwmslcvcqgcwv@alap3.anarazel.de>
References: <CALj2ACWMZKZELZEMfUTgg57ksmYtUXd-bNOwdNJ7=7iQ9Rt7sw@mail.gmail.com>
<CA+hUKG+54=sy=7pCJRb2Y_fiR1tSFE5_zx8PyfJONY7BCZuRmg@mail.gmail.com>
<3850536.1646405668@sss.pgh.pa.us>
<20220304171014.7rubwmslcvcqgcwv@alap3.anarazel.de>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, andres@anarazel.de, thomas.munro@gmail.com, bharath.rupireddyforpostgres@gmail.com, pgsql-hackers@lists.postgresql.org
Subject: Re: Regression tests failures on Windows Server 2019 - on master at commit # d816f366b
In-Reply-To: <3892341.1646414623@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox