Re: Expose JIT counters/timing in pg_stat_statements

From: Julien Rouhaud <rjuju123(at)gmail(dot)com>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Expose JIT counters/timing in pg_stat_statements
Date: 2022-02-25 15:40:01
Message-ID: 20220225154001.5bwofhgxunoqe6rc@jrouhaud
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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 :)

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2022-02-25 15:41:22 Re: Expose JIT counters/timing in pg_stat_statements
Previous Message David Christensen 2022-02-25 15:35:03 Re: [PATCH] add relation and block-level filtering to pg_waldump