| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Andreas Joseph Krogh <andreas(at)visena(dot)com> |
| Subject: | Re: Query is over 2x slower with jit=on |
| Date: | 2018-04-18 22:37:30 |
| Message-ID: | CA+TgmoafkuABoe0exunBV+gDoVRJVQv7buT2XmhAF75T36LLGA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | Postg젠 토토SQL : |
On Wed, Apr 18, 2018 at 3:29 PM, Andres Freund <andres(at)anarazel(dot)de> wrote:
> Not convinced that that is true - the issue is more likely that JIT work in workers is counted as execute time... Gotta add 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-04-18 22:56:31 | Re: pruning disabled for array, enum, record, range type partition keys |
| Previous Message | Peter Geoghegan | 2018-04-18 22:04:06 | Re: WIP: Covering + unique indexes. |