Re: ANY_VALUE aggregate - Mailing list pgsql-hackers

From Vik Fearing
Subject Re: ANY_VALUE aggregate
Date
Msg-id 538ac95d-f12e-92b8-0e22-85b6e35fdec9@postgresfriends.org
Whole thread Raw
In response to Re: ANY_VALUE aggregate  (Peter Eisentraut <peter.eisentraut@enterprisedb.com>)
Responses Re: ANY_VALUE aggregate
Re: ANY_VALUE aggregate
List pgsql-hackers
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

Attachment

pgsql-hackers by date:

Previous
From: Bharath Rupireddy
Date:
Subject: Re: Improve GetConfigOptionValues function
Next
From: Robert Haas
Date:
Subject: CREATEROLE users vs. role properties