From: | Philip Semanchuk <philip(at)americanefficient(dot)com> |
---|---|
To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
Cc: | Scott Ribe <scott_ribe(at)elevated-dev(dot)com>, PostgreSQL General <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: is JIT available |
Date: | 2020-07-27 15:21:27 |
Message-ID: | F6E79F4C-15D6-4389-8860-442DA5F308F4@americanefficient.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> On Jul 25, 2020, at 8:21 AM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
>
>
>
> so 25. 7. 2020 v 14:04 odesílatel Scott Ribe <scott_ribe(at)elevated-dev(dot)com> napsal:
> > On Jul 24, 2020, at 9:55 PM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
> >
> > SELECT * FROM pg_config;
>
> That doesn't tell me whether or not it can actually be used.
>
> It shows if Postgres was compiled with JIT support.
>
> When you run EXPLAIN ANALYZE SELECT ... then you can see info about JIT overhead. If you don't see notices about JIT in EXPLAIN, then JIT was not used.
I like Pavel’s 'EXPLAIN ANALYZE SELECT’ suggestion a lot. I think setting jit=on and jit_above_cost=1 and then running 'EXPLAIN ANALYZE SELECT’ is a very effective way to see whether jit is available in practice.
On installations where jit isn’t available (like on my Mac or on AWS Aurora), you can still set jit=on in a session and Postgres doesn’t complain, but that doesn’t mean it’s actually enabled.
Cheers
Philip
From | Date | Subject | |
---|---|---|---|
Next Message | Susan Hurst | 2020-07-27 15:24:20 | Re: shp2pgsql is missing |
Previous Message | raf | 2020-07-27 00:08:12 | Re: TDE implementation in postgres which is in docker container |