| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
| Cc: | 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-18 15:55:56 |
| Message-ID: | 3575780.1674057356@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> writes:
> 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.
> Since the transition function is declared strict, null values don't need
> to be checked.
Hmm, but should it be strict? That means that what it's returning
is *not* "any value" but "any non-null value". What does the draft
spec have to say about that?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vik Fearing | 2023-01-18 16:03:55 | Re: ANY_VALUE aggregate |
| Previous Message | David G. Johnston | 2023-01-18 15:55:28 | Re: [DOCS] Stats views and functions not in order? |