| From: | Yurii Rashkovskii <yrashk(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Stephen Frost <sfrost(at)snowman(dot)net>, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Greg Stark <stark(at)mit(dot)edu>, Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Cary Huang <cary(dot)huang(at)highgo(dot)ca> |
| Subject: | Re: [PATCH] Allow Postgres to pick an unused port to listen |
| Date: | 2023-05-11 11:24:23 |
| Message-ID: | CA+RLCQzPhJT88+AbziMDDw+kCTPCMd5Do76uwqgjUxMT0hg_aw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, May 11, 2023 at 10:36 AM Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2023-05-11 11:38:41 | Re: running logical replication as the subscription owner |
| Previous Message | Peter Eisentraut | 2023-05-11 11:09:26 | Re: Order changes in PG16 since ICU introduction |