| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Yurii Rashkovskii <yrashk(at)gmail(dot)com> |
| Cc: | 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 |
| Subject: | Re: [PATCH] Allow Postgres to pick an unused port to listen |
| Date: | 2023-04-13 02:17:47 |
| Message-ID: | 1215842.1681352267@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Yurii Rashkovskii <yrashk(at)gmail(dot)com> writes:
> Thank you all for the feedback. It's quite useful. I think it is important
> to separate this into two concerns:
> 1. Letting Postgres pick an unused port.
> 2. Retrieving the port it picked.
Yeah, those are distinguishable implementation concerns, but ...
> The bottom line is this decouples (1) from (2), and we can resolve them
> separately if there's too much (understandable) hesitation to commit to a
> particular approach to it (documenting postmaster.pid, changing its format,
> amending pg_ctl functionality, etc.)
... AFAICS, there is exactly zero value in committing a solution for (1)
without also committing a solution for (2). I don't think any of the
alternative methods you proposed are attractive or things we should
recommend.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2023-04-13 02:25:42 | Re: Clean up hba.c of code freeing regexps |
| Previous Message | Thomas Munro | 2023-04-13 02:04:59 | Re: Direct I/O |