From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
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:41:22 |
Message-ID: | CABUevEzZrQCvumYkEUA9-od0ysaurJB8VO0pGUHO_2z75_JuEg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Feb 25, 2022 at 4:40 PM Julien Rouhaud <rjuju123(at)gmail(dot)com> wrote:
>
> 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 :)
Hmm. Yeah, that was a bit unclear. I mean we track total time with
min/max, and detailed time not at all. For details, we only track
count, not time.
--
Magnus Hagander
Me: https://www.hagander.net/
Work: https://www.redpill-linpro.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Julien Rouhaud | 2022-02-25 16:01:41 | Re: Add parameter jit_warn_above_fraction |
Previous Message | Julien Rouhaud | 2022-02-25 15:40:01 | Re: Expose JIT counters/timing in pg_stat_statements |