| From: | David Rowley <dgrowleyml(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Scott Ribe <scott_ribe(at)elevated-dev(dot)com>, PostgreSQL General <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: bad JIT decision |
| Date: | 2020-07-25 23:53:34 |
| Message-ID: | CAApHDvqx+Mi548unSvFCX5icKARB1GT66EZzHZwnKXUqaeCjKg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sun, 26 Jul 2020 at 02:17, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> David Rowley <dgrowleyml(at)gmail(dot)com> writes:
> > On Sat, 25 Jul 2020 at 10:42, David Rowley <dgrowleyml(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Rowley | 2020-07-26 00:03:42 | Re: bad JIT decision |
| Previous Message | karsten | 2020-07-25 21:50:44 | RE: plphyton function - return each list value as a row ? |