Re: ANY_VALUE aggregate

Peter Eisentraut <peter.eisentraut@enterprisedb.com>

From: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
To: Vik Fearing <vik@postgresfriends.org>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2023-01-19T14:27:20Z
Lists: pgsql-hackers
On 18.01.23 18:01, Vik Fearing wrote:
> 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.

This looks good to me now.



Commits

  1. Implement ANY_VALUE aggregate

  2. Generalize ri_RootToPartitionMap to use for non-partition children