| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | "a(dot)mitrokhin(at)postgrespro(dot)ru" <a(dot)mitrokhin(at)postgrespro(dot)ru> |
| Cc: | Kirill Reshke <reshkekirill(at)gmail(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Starting a PostgreSQL server on a dynamic port (parameter port=0) |
| Date: | 2025-07-10 13:21:45 |
| Message-ID: | CAKFQuwbO6frSLj3w+UYV9reoML=3UFkXbvH5+QJsCNMdaQAxxA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Thursday, July 10, 2025, <a(dot)mitrokhin(at)postgrespro(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Euler Taveira | 2025-07-10 14:12:22 | Re: Starting a PostgreSQL server on a dynamic port (parameter port=0) |
| Previous Message | Laurenz Albe | 2025-07-10 11:58:44 | Re: Unexpected behavior when setting "idle_replication_slot_timeout" |