Re: bad JIT decision - Mailing list pgsql-general

From Tom Lane
Subject Re: bad JIT decision
Date
Msg-id 673332.1595688858@sss.pgh.pa.us
Whole thread Raw
In response to Re: bad JIT decision  (David Rowley <dgrowleyml@gmail.com>)
Responses Re: bad JIT decision
Re: bad JIT decision
List pgsql-general
David Rowley <dgrowleyml@gmail.com> writes:
> ... nested at the bottom level join, about 6 joins deep.  The lack of
> any row being found results in upper level joins not having to do
> anything, and the majority of the plan is (never executed).

On re-reading this, that last point struck me forcibly.  If most of
the plan never gets executed, could we avoid compiling it?  That is,
maybe JIT isn't JIT enough, and we should make compilation happen
at first use of an expression not during executor startup.

            regards, tom lane



pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: bad JIT decision
Next
From: Ron
Date:
Subject: Re: TDE implementation in postgres which is in docker container