Re: s/pg_attribute_always_inline/pg_always_inline/? - Mailing list pgsql-hackers

From Andres Freund
Subject Re: s/pg_attribute_always_inline/pg_always_inline/?
Date
Msg-id ovpakrvg3mfwyumhkrxjgnwfb75jo534booip7pqrq7cjt4orj@vydvdlbscnx4
Whole thread
In response to Re: s/pg_attribute_always_inline/pg_always_inline/?  (Peter Eisentraut <peter@eisentraut.org>)
List pgsql-hackers
Hi,

On 2026-04-09 02:00:37 +0200, Peter Eisentraut wrote:
> On 08.04.26 23:09, Andres Freund wrote:
> > Hi,
> > 
> > When reviewing the index prefetching patch I got a bit dismayed at how long
> > pg_attribute_always_inline is due to the way it triggers pgindent to format
> > stuff.
> > 
> > I propose that we remove the _attribute_ part of the name.
> > 
> > Given that it is implemented for compilers that don't use the
> > __attribute__((always_inline)) spelling, so the shorter name seems better
> > anyway.
> 
> Yes, and the existing name is also kind of wrong even on GCC because the
> macro does not expand to only an attribute but also includes the "inline".

It didn't start out that way, that only came in a bit later, in
434e6e148441...

Created a CF entry, to reduce the chances of me forgetting about committing
this early in the 20 cycle.

Greetings,

Andres Freund



pgsql-hackers by date:

Previous
From: Jim Jones
Date:
Subject: Re: Fix bug with accessing to temporary tables of other sessions
Next
From: Andres Freund
Date:
Subject: Re: Add errdetail() with PID and UID about source of termination signal