| From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
|---|---|
| To: | Vik Fearing <vik(at)postgresfriends(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: ANY_VALUE aggregate |
| Date: | 2023-01-19 14:27:20 |
| Message-ID: | 64b62678-ca3e-36f8-f0f2-bb430493ef4d@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| 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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2023-01-19 15:04:11 | Re: CREATEROLE users vs. role properties |
| Previous Message | tushar | 2023-01-19 14:21:09 | Re: almost-super-user problems that we haven't fixed yet |