Re: Adding a pg_servername() function

From: Laetitia Avrot <laetitia(dot)avrot(at)gmail(dot)com>
To: GF <phabriz(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter(at)eisentraut(dot)org>, Christoph Moench-Tegeder <cmt(at)burggraben(dot)net>, 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-10 07:06:31
Message-ID: CAB_COdhnETLz5r7VkAK8uziVJ_JnaR4MNS2Sub+vAKf9kjGPZA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Le mer. 9 août 2023 à 17:32, GF <phabriz(at)gmail(dot)com> a écrit :

>
> Would it be less problematic if the function were called pg_gethostname()?
> @Laetitia: why did you propose that name? maybe to avoid clashes with some
> extension out there?
>
>
I used that name to be kind of coherent with the inet_server_addr(), but I
see now how it is a bad decision and can add confusion and wrong
expectations. I think pg_gethostname() is better.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Richard Guo 2023-08-10 07:24:28 Re: Support "Right Semi Join" plan shapes
Previous Message Michael Paquier 2023-08-10 05:59:07 Re: Incorrect handling of OOM in WAL replay leading to data loss