From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | Maiquel Grassi <grassi(at)hotmail(dot)com(dot)br> |
Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Rename Function: pg_postmaster_start_time |
Date: | 2024-11-05 19:05:11 |
Message-ID: | CAKFQuwbvbYj21cwfVhg97gzNnq5Ua60z2+5bjgZuZiEu=Pvtww@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Nov 5, 2024 at 11:59 AM Maiquel Grassi <grassi(at)hotmail(dot)com(dot)br>
wrote:
> >> I suggest this change to simplify the terminology and make the function
> >> name more intuitive, as "postgres" directly refers to the database
> server.
> >> This seems more suitable to me.
>
> >Seems like an unnecessary change of a publicly facing feature. IMO
> >stability wins out over any debatable improvement the change may bring.
>
> There are several parts of the system where the term 'postmaster' appears
> and could potentially be changed to 'postgres'. In most cases, I agree with
> you: keeping the current term is a more cautious approach and ensures
> stability. However, in the case of this function, the adjustment is quite
> simple and doesn’t involve significant changes to the files; it’s really
> just a matter of 'replacing' the term.
>
The ease or difficulty of making the change in the server has no meaningful
bearing on whether breaking this public API is warranted or not.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Jelte Fennema-Nio | 2024-11-05 20:21:35 | Re: Interrupts vs signals |
Previous Message | Maiquel Grassi | 2024-11-05 18:59:48 | RE: Rename Function: pg_postmaster_start_time |