Re: JIT compilation per plan node - Mailing list pgsql-hackers

From David Rowley
Subject Re: JIT compilation per plan node
Date
Msg-id CAApHDvqMWpwHjCP0H+xJS15LwnApYNY0hn6ya9EQF4RSv+oK6A@mail.gmail.com
Whole thread Raw
In response to Re: JIT compilation per plan node  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: JIT compilation per plan node
Re: JIT compilation per plan node
List 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 by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Fix race condition in InvalidatePossiblyObsoleteSlot()
Next
From: Bharath Rupireddy
Date:
Subject: Re: Switching XLog source from archive to streaming when primary available