Re: s/pg_attribute_always_inline/pg_always_inline/?

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

David Rowley <dgrowleyml(at)gmail(dot)com> writes:
> On Thu, 9 Jul 2026 at 09:42, Tomas Vondra <tomas(at)vondra(dot)me> wrote:
>> 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?

+1. Breaking valid code in released branches is unfriendly.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Richard Guo 2026-07-09 01:01:35 Re: Add enable_groupagg GUC parameter to control GroupAggregate usage
Previous Message Peter Smith 2026-07-09 00:02:29 Re: Per-table resync for logical replication subscriptions