Re: Starting a PostgreSQL server on a dynamic port (parameter port=0)
David G. Johnston <david.g.johnston@gmail.com>
From: "David G. Johnston" <david.g.johnston@gmail.com>
To: "a.mitrokhin@postgrespro.ru" <a.mitrokhin@postgrespro.ru>
Cc: Kirill Reshke <reshkekirill@gmail.com>, "pgsql-bugs@lists.postgresql.org" <pgsql-bugs@lists.postgresql.org>
Date: 2025-07-10T13:21:45Z
Lists: 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.