Re: Block various aggregate component functions from being called directly

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: David Rowley <dgrowleyml(at)gmail(dot)com>
Cc: PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Block various aggregate component functions from being called directly
Date: 2026-11-19 15:05:14
Message-ID: 976301.1795100714@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:
> I think we should just block these from being called directly by
> adding a new column to pg_proc that allows a function to be marked as
> internal.

+1, although instead of a new column, would it make more sense to
invent a new prokind value?

> I don't see any need to have CREATE FUNCTION support this
> for UDFs,

-1. Extensions could have use for doing this too, and not allowing
extensions to have access to a feature the core code has is kind
of antithetical to project spirit IMO.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Zhou, Zhiguo 2026-11-19 15:21:02 Re: [RFC] Lock-free XLog Reservation from WAL
Previous Message Tomas Vondra 2026-11-19 14:56:47 Re: [PATCH]Fix planner's strictness check for JsonExpr