Re: Wrong aggregate result when sorting by a NULL value
| От | Tom Lane |
|---|---|
| Тема | Re: Wrong aggregate result when sorting by a NULL value |
| Дата | |
| Msg-id | 32176.1541172886@sss.pgh.pa.us обсуждение |
| Ответ на | Re: Wrong aggregate result when sorting by a NULL value (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: Wrong aggregate result when sorting by a NULL value
|
| Список | pgsql-bugs |
I wrote:
> =?UTF-8?Q?Ond=c5=99ej_Bouda?= <obouda@email.cz> writes:
>> the following seems as a bug to me on Postgres 11.0:
> Yeah, somebody broke this between 10.x and 11.0. ...
> I've not looked at the code yet, but it's acting like somebody changed the
> STRICT logic from "are any of the aggregate's arguments null" to "is any
> part of the whole row (including ordering values) null". Wrong ...
git bisect fingers this:
commit 69c3936a1499b772a749ae629fc59b2d72722332
Author: Andres Freund <andres@anarazel.de>
Date: Tue Jan 9 13:25:38 2018 -0800
Expression evaluation based aggregate transition invocation.
Andres, do you have time to look at this right now?
regards, tom lane
В списке pgsql-bugs по дате отправления: