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

From Tom Lane
Subject Re: [PATCH] Allow Postgres to pick an unused port to listen
Date
Msg-id 1161673.1681322178@sss.pgh.pa.us
Whole thread Raw
In response to Re: [PATCH] Allow Postgres to pick an unused port to listen  (Robert Haas <robertmhaas@gmail.com>)
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
Robert Haas <robertmhaas@gmail.com> writes:
> On Wed, Apr 12, 2023 at 1:31 PM Greg Stark <stark@mit.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



pgsql-hackers by date:

Previous
From: Dagfinn Ilmari Mannsåker
Date:
Subject: Re: Adding argument names to aggregate functions
Next
From: Robert Haas
Date:
Subject: Re: Allowing parallel-safe initplans