Re: Starting a PostgreSQL server on a dynamic port (parameter port=0) - Mailing list pgsql-bugs

From David G. Johnston
Subject Re: Starting a PostgreSQL server on a dynamic port (parameter port=0)
Date
Msg-id CAKFQuwbO6frSLj3w+UYV9reoML=3UFkXbvH5+QJsCNMdaQAxxA@mail.gmail.com
Whole thread Raw
In response to Re: Starting a PostgreSQL server on a dynamic port (parameter port=0)  (a.mitrokhin@postgrespro.ru)
Responses Re: Starting a PostgreSQL server on a dynamic port (parameter port=0)
List pgsql-bugs
On Thursday, July 10, 2025, <a.mitrokhin@postgrespro.ru> wrote:

If you're not interested in this behavior, you'll never use it. But
there are cases where it can be very convenient. Why artificially
restrict functionality that is simple, doesn't conflict with anything,
and has no negative side effects?

Then figure out how to do it on all the OSes we support and propose a patch.  Maybe it’s simple enough to include.  Maybe not.  If it is simple e on an OS one cares about a shell script around pg_ctl is a simple way to leverage it so it’s still a fairly low priority to add into core.

David J.

pgsql-bugs by date:

Previous
From: Laurenz Albe
Date:
Subject: Re: Unexpected behavior when setting "idle_replication_slot_timeout"
Next
From: "Euler Taveira"
Date:
Subject: Re: Starting a PostgreSQL server on a dynamic port (parameter port=0)