From: | Vik Fearing <vik(at)postgresfriends(dot)org> |
---|---|
To: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | ANY_VALUE aggregate |
Date: | 2022-12-05 14:57:13 |
Message-ID: | 5cff866c-10a8-d2df-32cb-e9072e6b04a2@postgresfriends.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
The SQL:2023 Standard defines a new aggregate named ANY_VALUE. It
returns an implementation-dependent (i.e. non-deterministic) value from
the rows in its group.
PFA an implementation of this aggregate.
Ideally, the transition function would stop being called after the first
non-null was found, and then the entire aggregation would stop when all
functions say they are finished[*], but this patch does not go anywhere
near that far.
This patch is based off of commit fb958b5da8.
[*] I can imagine something like array_agg(c ORDER BY x LIMIT 5) to get
the top five of something without going through a LATERAL subquery.
--
Vik Fearing
Attachment | Content-Type | Size |
---|---|---|
0001-Implement-ANY_VALUE-aggregate.patch | text/x-patch | 7.3 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2022-12-05 14:59:45 | Re: pg_basebackup: add test about zstd compress option |
Previous Message | Tom Lane | 2022-12-05 14:43:35 | Re: Missing MaterialPath support in reparameterize_path_by_child |