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

From Robert Haas
Subject Re: Query is over 2x slower with jit=on
Date
Msg-id CA+TgmoafkuABoe0exunBV+gDoVRJVQv7buT2XmhAF75T36LLGA@mail.gmail.com
Whole thread Raw
In response to Re: Query is over 2x slower with jit=on  (Andres Freund <andres@anarazel.de>)
Responses Re: Query is over 2x slower with jit=on  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
On Wed, Apr 18, 2018 at 3:29 PM, Andres Freund <andres@anarazel.de> wrote:
> Not convinced that that is true - the issue is more likely that JIT work in workers is counted as execute time...
Gottaadd that somehow, not sure what the best way would be.
 

Oh, that does seem like something that should be fixed.  If that's
what is happening here, it's bound to confuse a lot of people.
Probably you need to add some code to
ExecParallelRetrieveInstrumentation.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: WIP: Covering + unique indexes.
Next
From: Tom Lane
Date:
Subject: Re: pruning disabled for array, enum, record, range type partition keys