| From: | Vik Fearing <vik(at)postgresfriends(dot)org> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, David Fetter <david(at)fetter(dot)org>, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, "bashtanov(at)imap(dot)cc" <bashtanov(at)imap(dot)cc>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [patch] bit XOR aggregate functions |
| Date: | 2021-03-07 10:28:55 |
| Message-ID: | 7a7541d6-0311-38ee-701e-f89a5fe8b583@postgresfriends.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 3/7/21 11:24 AM, Pavel Stehule wrote:
>>
>> And so you are now mandating an ORDER BY on every query and in every
>> aggregate and/or window function. Users will not like that at all. I
>> certainly shan't.
>>
>
> The mandatory ORDER BY clause should be necessary for operations when the
> result depends on the order. You need an order for calculation of median.
> And you don't need to know an order for average. More if the result is one
> number and is not possible to do a visual check of correctness (like
> median).
The syntax for median (percentile_cont(0.5)) already requires an order
by clause. You are now requiring one on array_agg().
--
Vik Fearing
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2021-03-07 10:37:31 | Re: [patch] bit XOR aggregate functions |
| Previous Message | Pavel Stehule | 2021-03-07 10:24:02 | Re: [patch] bit XOR aggregate functions |