Re: [PATCH] Allow Postgres to pick an unused port to listen - Mailing list pgsql-hackers

From Yurii Rashkovskii
Subject Re: [PATCH] Allow Postgres to pick an unused port to listen
Date
Msg-id CA+RLCQzPhJT88+AbziMDDw+kCTPCMd5Do76uwqgjUxMT0hg_aw@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] Allow Postgres to pick an unused port to listen  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Responses Re: [PATCH] Allow Postgres to pick an unused port to listen
Re: [PATCH] Allow Postgres to pick an unused port to listen
List pgsql-hackers
On Thu, May 11, 2023 at 10:36 AM Alvaro Herrera <alvherre@alvh.no-ip.org> wrote:
On 2023-May-11, Yurii Rashkovskii wrote:

> ```
> 127.0.0.1=5432 ::1=54321
> ```
>
> Basically, a space-delimited set of address/port pairs (delimited by `=` to
> allow IPv6 addresses to use a colon).

This seems a bit too creative.  I'd rather have the IPv6 address in
square brackets, which clues the parser immediately as to the address
family and use colons to separate the port number.  If we do go with a
separate file, which to me sounds easier than cramming it into the PID
file, then one per line is likely better, if only because line-oriented
Unix text tooling has an easier time that way.

Just a general caution here that using square brackets to denote IPv6 addresses will make it (unnecessarily?) harder to process this with a shell script.

--
Y.

pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Order changes in PG16 since ICU introduction
Next
From: Amit Kapila
Date:
Subject: Re: running logical replication as the subscription owner