| From: | Amit Khandekar <amitdkhan(dot)pg(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Andreas Joseph Krogh <andreas(at)visena(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Query is over 2x slower with jit=on |
| Date: | 2018-09-18 04:52:20 |
| Message-ID: | CAJ3gD9d+nBaFby8Frnyrd4Y1ha9yqYsQQ9XP_e9JnVrFeZAUbg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 18 September 2018 at 03:20, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Amit Khandekar <amitdkhan(dot)pg(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rajkumar Raghuwanshi | 2018-09-18 05:31:26 | Re: Getting ERROR: could not open file "base/13164/t3_16388" with partition table with ON COMMIT |
| Previous Message | Amit Khandekar | 2018-09-18 04:33:02 | Re: Query is over 2x slower with jit=on |