Expose JIT counters/timing in pg_stat_statements - Mailing list pgsql-hackers

From Magnus Hagander
Subject Expose JIT counters/timing in pg_stat_statements
Date
Msg-id CABUevEySt4NTYqvWzwyAW_0-jG1bjN-y+tykapAnA0FALOs+Lw@mail.gmail.com
Whole thread Raw
Responses Re: Expose JIT counters/timing in pg_stat_statements  (Julien Rouhaud <rjuju123@gmail.com>)
Re: Expose JIT counters/timing in pg_stat_statements  (Peter Eisentraut <peter.eisentraut@enterprisedb.com>)
List pgsql-hackers
Here's a patch to add the sum of timings for JIT counters to
pg_stat_statements, as a way to follow-up on if JIT is doing a good or
a bad job in a configuration.

I decided to only store the total time for the timings, since there
are 4 different timings and storing max/min/etc for each one of them
would lead to a bit too much data. This can of course be reconsidered,
but I think that's a reasonable tradeoff.

Another option I guess could be to store the max/min/etc, but only
store for the total jit time instead of for each individual one. Maybe
that'd actually be more useful?


-- 
 Magnus Hagander
 Me: https://www.hagander.net/
 Work: https://www.redpill-linpro.com/

Attachment

pgsql-hackers by date:

Previous
From: Dilip Kumar
Date:
Subject: Re: should vacuum's first heap pass be read-only?
Next
From: Japin Li
Date:
Subject: Re: [PATCH] add relation and block-level filtering to pg_waldump