| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Tomas Vondra <tomas(at)vondra(dot)me>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, David Rowley <dgrowleyml(at)gmail(dot)com>, 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 21:01:42 |
| Message-ID: | CAH2-Wzks_t1QrkZn=hNMsraaUSYfOE15d2Ra1QkMWr9H77hVgQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Jul 10, 2026 at 1:32 PM Andres Freund <andres(at)anarazel(dot)de> wrote:
> Same. Personally I'd not have adjusted the uses of the macro in the
> backbranches, but I don't have a problem with you doing that either.
FWIW a quick Debian code search shows the following Debian packages
depend on the current pg_attribute_always_inline spelling (excluding
Postgres itself):
pg-stat-plans, documentdb, timescaledb, mobilitydb, libpg-query, postgresql-rum
libpg-query and mobilitydb don't really count, because they seem to
vendor src/postgres/include/c.h directly. postgresql-rum and
pg-stat-plans definitely use pg_attribute_always_inline as
straightforward extensions. I think that the rest are also simple
extensions that rely on the authoritative pg_attribute_always_inline,
but I didn't check.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matheus Alcantara | 2026-07-10 21:13:43 | Re: Show expression of virtual columns in error messages |
| Previous Message | Haibo Yan | 2026-07-10 20:39:41 | Re: implement CAST(expr AS type FORMAT 'template') |