Re: ANY_VALUE aggregate
Vik Fearing <vik@postgresfriends.org>
From: Vik Fearing <vik@postgresfriends.org>
To: Peter Eisentraut <peter.eisentraut@enterprisedb.com>,
PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2023-01-18T17:01:34Z
Lists: pgsql-hackers
Attachments
- 0001-Implement-ANY_VALUE-aggregate.v03.patch (text/x-patch) patch v3-0001
On 1/18/23 16:06, Peter Eisentraut wrote:
> On 05.12.22 21:18, Vik Fearing wrote:
>> On 12/5/22 15:57, Vik Fearing wrote:
>>> 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.
>>
>> Here is v2 of this patch. I had forgotten to update sql_features.txt.
>
> In your patch, the documentation says the definition is any_value("any")
> but the catalog definitions are any_value(anyelement). Please sort that
> out.
>
> Since the transition function is declared strict, null values don't need
> to be checked.
Thank you for the review. Attached is a new version rebased to d540a02a72.
--
Vik Fearing
Commits
-
Implement ANY_VALUE aggregate
- 2ddab010c277 16.0 landed
-
Generalize ri_RootToPartitionMap to use for non-partition children
- fb958b5da86d 16.0 cited