Re: [PATCH] Allow Postgres to pick an unused port to listen

From: Jacob Champion <jchampion(at)timescale(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Yurii Rashkovskii <yrashk(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: [PATCH] Allow Postgres to pick an unused port to listen
Date: 2023-04-12 16:45:01
Message-ID: CAAWbhmjC32eQad6kKAa0TPhBHLxDHAcnRD5XWPSjcbHJD20yKQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Apr 7, 2023 at 5:07 AM Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
> For TAP tests we have pretty much resolved the port collisions issue for TCP ports too. See commit 9b4eafcaf4

The Cirrus config still has the following for the Windows tests:

# Avoids port conflicts between concurrent tap test runs
PG_TEST_USE_UNIX_SOCKETS: 1

Is that comment out of date, or would this proposal improve the
Windows situation too?

--Jacob

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jacob Champion 2023-04-12 16:54:20 Re: [PATCH] Add `verify-system` sslmode to use system CA pool for server cert
Previous Message Tom Lane 2023-04-12 16:43:52 Allowing parallel-safe initplans