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

From: Greg Stark <stark(at)mit(dot)edu>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Yurii Rashkovskii <yrashk(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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:31:09
Message-ID: CAM-w4HNO6d9Egr1JX+wGRFSJDOFVN6wMFxajfqdpgdx=eH20zQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, 12 Apr 2023 at 11:02, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>
> I mostly just wanted to say that I disagreed with Tom about the
> particular point on postmaster.pid, without really expressing an
> opinion about anything else.

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`

--
greg

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2023-04-12 17:51:40 Re: [PATCH] Allow Postgres to pick an unused port to listen
Previous Message Jacob Champion 2023-04-12 16:54:20 Re: [PATCH] Add `verify-system` sslmode to use system CA pool for server cert