Re: s/pg_attribute_always_inline/pg_always_inline/?

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: Tomas Vondra <tomas(at)vondra(dot)me>
Cc: Peter Geoghegan <pg(at)bowt(dot)ie>, Andres Freund <andres(at)anarazel(dot)de>, Peter Eisentraut <peter(at)eisentraut(dot)org>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: s/pg_attribute_always_inline/pg_always_inline/?
Date: 2026-07-09 00:02:03
Message-ID: CAApHDvpwjsxBYEsLLj5Z==zqZK4JZn2S_uc0Pi3dGACSsgOQyw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, 9 Jul 2026 at 09:42, Tomas Vondra <tomas(at)vondra(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Smith 2026-07-09 00:02:29 Re: Per-table resync for logical replication subscriptions
Previous Message David Rowley 2026-07-08 23:55:48 Re: Add bms_offset_members() function for bitshifting Bitmapsets