| From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
|---|---|
| To: | Laetitia Avrot <laetitia(dot)avrot(at)gmail(dot)com>, Christoph Moench-Tegeder <cmt(at)burggraben(dot)net> |
| Cc: | Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Adding a pg_servername() function |
| Date: | 2023-08-09 08:26:38 |
| Message-ID: | 21f16cbb-3e39-3da9-4968-63c27e04ad94@eisentraut.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 09.08.23 08:42, Laetitia Avrot wrote:
> I agree that the feature I'm suggesting could be done with a few tricks.
> I meant to simplify the life of the user by providing a simple new
> feature. (Also, I might have trust issues with DNS due to several past
> production disasters.)
>
> My question is very simple: Do you oppose having this feature in Postgres?
I think this is pretty harmless(*) and can be useful, so it seems
reasonable to pursue.
(*) But we should think about access control for this. If you're in a
DBaaS environment, providers might not like that you can read out their
internal host names. I'm not sure if there is an existing permission
role that this could be attached to or if we need a new one.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Anthonin Bonnefoy | 2023-08-09 08:34:41 | Re: POC: Extension for adding distributed tracing - pg_tracing |
| Previous Message | Yuya Watari | 2023-08-09 08:14:56 | Re: [PoC] Reducing planning time when tables have many partitions |