Re: wrong query result with jit_above_cost= 0

Поиск
Список
Период
Сортировка
От Andres Freund
Тема Re: wrong query result with jit_above_cost= 0
Дата
Msg-id 20180626205643.io2tbxtomkj3xzr2@alap3.anarazel.de
обсуждение исходный текст
Ответ на Re: wrong query result with jit_above_cost= 0  (Andrew Gierth <andrew@tao11.riddles.org.uk>)
Ответы Re: wrong query result with jit_above_cost= 0  (Dmitry Dolgov <9erthalion6@gmail.com>)
Список pgsql-hackers
On 2018-06-26 21:55:07 +0100, Andrew Gierth wrote:
> >>>>> "Dmitry" == Dmitry Dolgov <9erthalion6@gmail.com> writes:
> 
>  Dmitry> Yep, my bad, forgot to turn it on. Now I see what's the
>  Dmitry> problem, one of the null fields is screwed up, will try to
>  Dmitry> figure out why is that.
> 
> The handling of nulls in grouping set results is a bit icky, see
> prepare_projection_slot in nodeAgg.c. The comment there lists a number
> of assumptions which may or may not hold true under JIT which might give
> a starting point to look for problems. (Unfortunately I'm not currently
> in a position to test on a JIT build)

I probably just screwed up a bit of code generation. I can't see any of
the more fundamental assumptions being changed by the way JITing is
done.

Greetings,

Andres Freund


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Andrew Gierth
Дата:
Сообщение: Re: wrong query result with jit_above_cost= 0
Следующее
От: Jonathan Lemig
Дата:
Сообщение: Name of main process differs between servers (postmaster vs postgres)