From: | Vik Fearing <vik(at)postgresfriends(dot)org> |
---|---|
To: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: ANY_VALUE aggregate |
Date: | 2023-01-18 17:01:34 |
Message-ID: | 538ac95d-f12e-92b8-0e22-85b6e35fdec9@postgresfriends.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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 | Content-Type | Size |
---|---|---|
0001-Implement-ANY_VALUE-aggregate.v03.patch | text/x-patch | 6.2 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2023-01-18 17:15:33 | CREATEROLE users vs. role properties |
Previous Message | Bharath Rupireddy | 2023-01-18 16:34:31 | Re: Improve GetConfigOptionValues function |