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

From Julien Rouhaud
Subject Re: Expose JIT counters/timing in pg_stat_statements
Date
Msg-id 20220225154001.5bwofhgxunoqe6rc@jrouhaud
Whole thread Raw
In response to Re: Expose JIT counters/timing in pg_stat_statements  (Magnus Hagander <magnus@hagander.net>)
Responses Re: Expose JIT counters/timing in pg_stat_statements
List pgsql-hackers
On Fri, Feb 25, 2022 at 04:19:27PM +0100, Magnus Hagander wrote:
> 
> So just to be clear, you're basically thinking:
> 
> jit_count = count of entries where jit_functions>0
> jit_functions = <same as now>
> jit_optimizatinos = count of entries where time spent on jit_optimizations > 0
> 
> etc?

Yes exactly, so 3 new fields on top of the one you already added.

> So we count the times with min/max like other times for the total one,
> but instead add a counter for each of the details?

I don't understand this one.  Did you mean we *don't* count times with min/max?
If that's the case then yes :)



pgsql-hackers by date:

Previous
From: David Christensen
Date:
Subject: Re: [PATCH] add relation and block-level filtering to pg_waldump
Next
From: Magnus Hagander
Date:
Subject: Re: Expose JIT counters/timing in pg_stat_statements