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

From: Tristen Raab <tristen(dot)raab(at)highgo(dot)ca>
To: pgsql-hackers(at)lists(dot)postgresql(dot)org
Cc: Yurii Rashkovskii <yrashk(at)gmail(dot)com>
Subject: Re: [PATCH] Allow Postgres to pick an unused port to listen
Date: 2023-05-17 18:37:49
Message-ID: 168434866923.1144.17948629630066944490.pgcf@coridan.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

The following review has been posted through the commitfest application:
make installcheck-world: tested, passed
Implements feature: tested, passed
Spec compliant: not tested
Documentation: tested, passed

Hello Yurii,

I've retested your latest patch and tested building the documentation.

I agree with the general sentiment that this is an interesting, albeit specific feature. Nevertheless, I would still like to see this integrated. My only concern, like many others have voiced, is in regard to the port number. When I was reviewing this patch I found it quite unintuitive to rummage through the postmaster.pid to find the correct port. I think either a specific pg_ctl command to return the port like Greg had initially mentioned or simply a separate file to store the port numbers would be ideal. The standalone file being the simpler option, this would free up postmaster.pid to allow any future alterations and still be able to reliably get the port number when using this wildcard. We can also build on this file later to allow for multiple ports to be listened on as previously suggested.

Kind regards,
Tristen

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2023-05-17 19:19:24 Re: pg_stat_io not tracking smgrwriteback() is confusing
Previous Message Tom Lane 2023-05-17 18:13:30 Re: psql: Could we get "-- " prefixing on the **** QUERY **** outputs? (ECHO_HIDDEN)