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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Greg Stark <stark(at)mit(dot)edu>, Yurii Rashkovskii <yrashk(at)gmail(dot)com>, 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-12 17:56:18
Message-ID: 1161673.1681322178@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Wed, Apr 12, 2023 at 1:31 PM Greg Stark <stark(at)mit(dot)edu> wrote:
>> I don't object to using the pid file as the mechanism -- but it is a
>> bit of an awkward UI for shell scripting. I imagine it would be handy
>> if pg_ctl had an option to just print the port number so you could get
>> it with a simple port=`pg_ctl -D <dir> status-port`

> That's not a bad idea, and would provide some additional isolation to
> reduce direct dependency on the PID file format.

Yeah. My main concern here is with limiting our ability to change
the pidfile format in future. If we can keep the dependencies on that
localized to code we control, it'd be much better.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2023-04-12 18:06:05 Re: Allowing parallel-safe initplans
Previous Message Dagfinn Ilmari Mannsåker 2023-04-12 17:53:54 Re: Adding argument names to aggregate functions