Re: Add callback in pgstats for backend initialization

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
Cc: bertranddrouvot(dot)pg(at)gmail(dot)com, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Add callback in pgstats for backend initialization
Date: 2024-09-05 03:41:09
Message-ID: ZtkoVZbi-eXWIwkY@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Sep 04, 2024 at 06:42:33PM +0900, Kyotaro Horiguchi wrote:
> More accurately, I believe this applies when the sentence follows a
> verb-object structure. In this case, the function’s meaning is “pgstat
> initialization on backend,” which seems somewhat different from the
> policy you mentioned. However, it could also be interpreted as
> “initialize backend status related to pgstat.” Either way, I’m okay
> with the current name if you are, based on the discussion above.

Not sure which one is better than the other, TBH. Either way, we
still have a full release cycle to finalize that, and I am OK to
switch the name to something else if there are more folks in favor of
one, the other or even something entirely different but descriptive
enough.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2024-09-05 03:55:51 Re: Introduce XID age and inactive timeout based replication slot invalidation
Previous Message jian he 2024-09-05 03:29:43 Re: meson and check-tests