Re: bad JIT decision - Mailing list pgsql-general

From David Rowley
Subject Re: bad JIT decision
Date
Msg-id CAApHDvqx+Mi548unSvFCX5icKARB1GT66EZzHZwnKXUqaeCjKg@mail.gmail.com
Whole thread Raw
In response to Re: bad JIT decision  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
On Sun, 26 Jul 2020 at 02:17, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> David Rowley <dgrowleyml@gmail.com> writes:
> > On Sat, 25 Jul 2020 at 10:42, David Rowley <dgrowleyml@gmail.com> wrote:
> >> I think plan cost overestimation is a common cause of unwanted jit too.
> >> It would be good to see the EXPLAIN ANALYZE so we knew if that was the
> >> case here.
>
> > So Scott did send me the full EXPLAIN ANALYZE for this privately. He
> > wishes to keep the full output private.
>
> So ... what was the *top* line, ie total cost estimate?

Hash Right Join  (cost=1200566.17..1461446.31 rows=1651 width=141)
(actual time=5881.944..5881.944 rows=0 loops=1)

So well above the standard jit inline and optimize cost

David



pgsql-general by date:

Previous
From: "karsten"
Date:
Subject: RE: plphyton function - return each list value as a row ?
Next
From: David Rowley
Date:
Subject: Re: bad JIT decision