Re: Query is over 2x slower with jit=on - Mailing list pgsql-hackers

From Amit Khandekar
Subject Re: Query is over 2x slower with jit=on
Date
Msg-id CAJ3gD9d+nBaFby8Frnyrd4Y1ha9yqYsQQ9XP_e9JnVrFeZAUbg@mail.gmail.com
Whole thread Raw
In response to Re: Query is over 2x slower with jit=on  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 18 September 2018 at 03:20, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Amit Khandekar <amitdkhan.pg@gmail.com> writes:
>>>>> I think we better show per-worker jit info also.
>
> Just to throw a contrarian opinion into this: I find the current EXPLAIN
> output for JIT to be insanely verbose already.

One option is to make the jit info displayed on a single line, with
optimize and inlining counters shown only when the corresponding
optimization was attempted. Currently they are shown even if they are
disabled.

In the patch, I have kept the per-worker output verbose-only.

Thanks,
-Amit Khandekar
EnterpriseDB Corporation
The Postgres Database Company


pgsql-hackers by date:

Previous
From: Amit Khandekar
Date:
Subject: Re: Query is over 2x slower with jit=on
Next
From: Rajkumar Raghuwanshi
Date:
Subject: Re: Getting ERROR: could not open file "base/13164/t3_16388" withpartition table with ON COMMIT