MIME-Version: 1.0
References: <bqqdehahpoa36igpictuqyn2s2mexk3t3ehidh2ffd2slb35e5@rzgksuiszgbg>
 <56def459-2b95-42bc-b4e4-26e57f08b064@eisentraut.org>
 <ovpakrvg3mfwyumhkrxjgnwfb75jo534booip7pqrq7cjt4orj@vydvdlbscnx4>
 <CAH2-WznHSUJcV47OhoisvABjN2xjVOYh0_bRagUE6ir5zGJzow@mail.gmail.com>
 <adee40b0-ee0d-40a8-abe7-61784db3ec6c@vondra.me>
 <CAH2-Wzm3ev6uGsf4QddpaZamzsb3ATvanggEHxnhRSkdd52bnA@mail.gmail.com>
 <4370bec0-df13-40f3-92ee-75974182e41f@vondra.me>
In-Reply-To: <4370bec0-df13-40f3-92ee-75974182e41f@vondra.me>
From: David Rowley <dgrowleyml@gmail.com>
Date: Thu, 9 Jul 2026 12:02:03 +1200
Message-ID: 
 <CAApHDvpwjsxBYEsLLj5Z==zqZK4JZn2S_uc0Pi3dGACSsgOQyw@mail.gmail.com>
Subject: Re: s/pg_attribute_always_inline/pg_always_inline/?
To: Tomas Vondra <tomas@vondra.me>
Cc: Peter Geoghegan <pg@bowt.ie>, Andres Freund <andres@anarazel.de>,
	Peter Eisentraut <peter@eisentraut.org>, pgsql-hackers@postgresql.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: 
 <https://www.postgresql.org/message-id/CAApHDvpwjsxBYEsLLj5Z%3D%3DzqZK4JZn2S_uc0Pi3dGACSsgOQyw%40mail.gmail.com>
Precedence: bulk

On Thu, 9 Jul 2026 at 09:42, Tomas Vondra <tomas@vondra.me> wrote:
> So, what shall we do about this? I've been looking at the v29 of the
> index prefetching patch series, which is using this attribute in a bunch
> of places. And that reminded me of this thread.
>
> I guess we should just commit that, so unless someone objects soon I'll
> just do that. ISTM the agreement is to backpatch this too.

How about just backpatching the new macro and leaving the old one in
place back branches? There should be slightly less backpatching pain
that way, for us, and fewer merge issues for people maintaining forks
on existing versions.

David