Re: s/pg_attribute_always_inline/pg_always_inline/?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Tomas Vondra <tomas(at)vondra(dot)me>
Cc: David Rowley <dgrowleyml(at)gmail(dot)com>, 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-10 00:14:12
Message-ID: 2811067.1783642452@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tomas Vondra <tomas(at)vondra(dot)me> writes:
> Does "backpatching the new macro" mean we'd also adjust all existing
> places to use the new macro or not? I mean, we could backpatch just the
> bit in c.h. I plan to adjust the places, to minimize possible conflicts
> when backpatching other stuff.

I think it'd be sufficient to add the new macro to the old branches.
The point of back-patching at all, I think, is to save ourselves
work if we have to back-patch some new code that uses the new style.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Ewan Young 2026-07-10 02:44:12 Re: Fix duplicate detection for null-treatment window functions
Previous Message Fujii Masao 2026-07-10 00:12:29 Re: Fix data checksum processing for temp relations and dropped databases