Quick Links

Re: bad JIT decision

From:	Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To:	David Rowley <dgrowleyml(at)gmail(dot)com>
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-24 22:37:02
Message-ID:	629715.1595630222@sss.pgh.pa.us
Views:	Raw Message \| Whole Thread \| Download mbox \| Resend email
Thread:
Lists:	pgsql-general

David Rowley <dgrowleyml(at)gmail(dot)com> writes:
> However, for now, you might just want to try raising various jit
> thresholds so that it only is enabled for more expensive plans.

Yeah. I'm fairly convinced that the v12 defaults are far too low,
because we are constantly seeing complaints of this sort.

regards, tom lane

In response to

Re: bad JIT decision at 2020-07-24 22:26:05 from David Rowley

Responses

Re: bad JIT decision at 2020-07-24 22:42:56 from David Rowley
Re: bad JIT decision at 2020-07-24 22:46:35 from Scott Ribe
Re: bad JIT decision at 2020-07-25 00:16:05 from Andres Freund

Browse pgsql-general by date

	From	Date	Subject
Next Message	David Rowley	2020-07-24 22:42:56	Re: bad JIT decision
Previous Message	Tom Lane	2020-07-24 22:34:45	Re: Row estimates for empty tables