Re: JIT compilation per plan node

Поиск
Список
Период
Сортировка
От David Rowley
Тема Re: JIT compilation per plan node
Дата
Msg-id CAApHDvqMWpwHjCP0H+xJS15LwnApYNY0hn6ya9EQF4RSv+oK6A@mail.gmail.com
обсуждение исходный текст
Ответ на Re: JIT compilation per plan node  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: JIT compilation per plan node  (Tomas Vondra <tomas.vondra@enterprisedb.com>)
Re: JIT compilation per plan node  (Jelte Fennema-Nio <postgres@jeltef.nl>)
Список pgsql-hackers
On Tue, 20 Feb 2024 at 18:31, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> FWIW, I seriously doubt that an extra walk of the plan tree is even
> measurable compared to the number of cycles JIT compilation will
> expend if it's called.  So I don't buy your argument here.
> We would be better off to do this in a way that's clean and doesn't
> add overhead for non-JIT-enabled builds.

The extra walk of the tree would need to be done for every plan, not
just the ones where we do JIT. I'd rather find a way to not add this
extra plan tree walk, especially since the vast majority of cases on
an average instance won't be doing any JIT.

David



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

Предыдущее
От: Michael Paquier
Дата:
Сообщение: Re: Fix race condition in InvalidatePossiblyObsoleteSlot()
Следующее
От: Bharath Rupireddy
Дата:
Сообщение: Re: Switching XLog source from archive to streaming when primary available