Re: doc patch: clarify the naming rule for injection_points

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>
Cc: 'Aleksander Alekseev' <aleksander(at)timescale(dot)com>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: doc patch: clarify the naming rule for injection_points
Date: 2025-04-21 07:29:56
Message-ID: aAXz9MMKZvCPN-SC@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Apr 14, 2025 at 12:36:20PM +0000, Hayato Kuroda (Fujitsu) wrote:
> I also feel just converting lower case is not good. The point seems to locate in
> the end-of-transaction callback and it accepts invalidation messages. Based on the
> fact, how about "inval-process-invalidation-messages"?
> 0002 did simple replacements of these words.

- INJECTION_POINT("heap_update-before-pin");
+ INJECTION_POINT("heap-update-before-pin");

The former name is better IMO. heap_update() is the name of the
function where the point is defined.

- INJECTION_POINT("AtEOXact_Inval-with-transInvalInfo");
+ INJECTION_POINT("inval-process-invalidation-messages");

This naming has been puzzling me, though, so a rename looks fit. I am
not sure that this is the best name that matches with this code path,
as this lacks a reference regarding the end of a transaction. Perhaps
something like "end-transaction-process-inval" would be better?
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2025-04-21 08:02:29 Re: bug: virtual generated column can be partition key
Previous Message Michael Paquier 2025-04-21 07:02:37 Re: ZStandard (with dictionaries) compression support for TOAST compression