Message-ID: <0ae1aa4b0e3343e2bd2c1b7c41ebeccfe0f65188.camel@cybertec.at>
Subject: Re: Starting a PostgreSQL server on a dynamic port (parameter
 port=0)
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: a.mitrokhin@postgrespro.ru, Kirill Reshke <reshkekirill@gmail.com>
Cc: pgsql-bugs@lists.postgresql.org
Date: Thu, 10 Jul 2025 10:53:17 +0200
In-Reply-To: <a03d0696a0b98a1e91947ffdefa9d6fc@postgrespro.ru>
References: <824bbf6be5fa0edf6a7d4c8371ce67ce@postgrespro.ru>
	 <CALdSSPgNJWenx+wGt2pL4oFcuZw21=C3B8AB27b_kayuWZB6yw@mail.gmail.com>
	 <a03d0696a0b98a1e91947ffdefa9d6fc@postgrespro.ru>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.56.2 (3.56.2-1.fc42) 
MIME-Version: 1.0
Archived-At: 
 <https://www.postgresql.org/message-id/0ae1aa4b0e3343e2bd2c1b7c41ebeccfe0f65188.camel%40cybertec.at>
Precedence: bulk

On Thu, 2025-07-10 at 15:29 +0700, a.mitrokhin@postgrespro.ru wrote:
> > > Postgres does not allow starting the server with port=3D0, which prev=
ents
> > > it from obtaining an arbitrary free port from the kernel.
>=20
> This has nothing to do with Postgres regression tests. The issue is
> the practical benefit of using a dynamic port, which we're depriving
> ourselves of.
>=20
> 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?

I have never wished for such a feature, and I can see negative side
effects.  If the server listens on a different port than you expect,
it is easier to connect to the wrong server by mistake.

Yours,
Laurenz Albe