Andres Freund <andres@anarazel.de> writes:
> On 2018-08-22 06:20:21 +0000, Noah Misch wrote:
>> Regardless of the choice of jit={on|off} default, these numbers tell me that
>> some or all of jit_*_cost defaults are too low.
> I don't think it really shows that. The reason that JITing gets started
> there is that the tables aren't analyzed and we end up with crazy ass
> estimates about the cost of the queries. No useful setting of the cost
> limits will protect against that... :(
I don't buy that line of argument one bit. No, we generally don't
analyze most of the regression test tables, but the planner still
knows that they're not very large. If JIT is kicking in for those
queries, the defaults are set wrong. Additional evidence for the
defaults being wrong is the number of reports we've had of JIT making
things slower.
I was OK with that happening during early beta, on the grounds of getting
more testing for the JIT code; but it's time to fix the numbers.
regards, tom lane