Re: Expose JIT counters/timing in pg_stat_statements
Dmitry Dolgov <9erthalion6@gmail.com>
From: Dmitry Dolgov <9erthalion6@gmail.com>
To: Magnus Hagander <magnus@hagander.net>
Cc: Julien Rouhaud <rjuju123@gmail.com>, PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>
Date: 2022-03-07T13:01:08Z
Lists: pgsql-hackers
> On Mon, Mar 07, 2022 at 01:27:02PM +0100, Magnus Hagander wrote: > On Fri, Feb 25, 2022 at 5:40 PM Dmitry Dolgov <9erthalion6@gmail.com> wrote: > > One interesting not-very-relevant for the patch thing I've noticed while > > reading it, is that there seems to be no way to find out what fraction > > of time jit_tuple_deforming is taking alone, it's sort of merged > > together with jit_expressions in generation_counter. > > That's missing att a deeper level though, right? We don't have it in > EXPLAIN ANALYZE either. So while I agree that's useful, I think that's > the job of another patch, and these two sets of counters should be the > same. Right, it's missing on the instrumentation level, I was just surprised to notice that.
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Add JIT counters to pg_stat_statements
- 57d6aea00fce 15.0 landed