Re: Allow a prosupport function to be attached to an aggregate

From: Andrei Lepikhov <lepihov(at)gmail(dot)com>
To: David Rowley <dgrowleyml(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Corey Huinker <corey(dot)huinker(at)gmail(dot)com>
Subject: Re: Allow a prosupport function to be attached to an aggregate
Date: 2026-08-18 12:36:53
Message-ID: ca4ee281-f75b-445b-b57f-0b560067c1d7@gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 18/08/2026 08:31, Andrei Lepikhov wrote:
> On 18/08/2026 06:56, David Rowley wrote:
>> Is delaying this until v20 fine for you?
> Yes, I can do it manually in pg_catalog for now - rewriting prosupport and
> setting the dependency in the pg_depend. There’s no rush - it’s just about
> keeping things tidy.

However, I noticed that it is not documented yet.

There are also three other prosupport requests that are not documented. A quick
search showed that documentation usually depends on the author, so it makes
sense to add it now.

Since each was introduced at a different time and serves a different purpose, I
suggest we start by documenting SupportRequestSimplifyAggref, as I am more
familiar with it - see the patch in attachment.

--
regards, Andrei Lepikhov,
pgEdge

Attachment Content-Type Size
v0-0001-Document-the-SupportRequestSimplifyAggref-support.patch text/plain 1.8 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bertrand Drouvot 2026-08-18 12:39:42 Re: basebackup: do not verify checksums on pages written before enabling checksums
Previous Message Ilia Evdokimov 2026-08-18 12:31:32 Re: Tracking per-RelOptInfo uniqueness during planning