Expose JIT counters/timing in pg_stat_statements
Magnus Hagander <magnus@hagander.net>
From: Magnus Hagander <magnus@hagander.net>
To: PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>
Date: 2022-02-25T13:06:29Z
Lists: pgsql-hackers
Attachments
- pg_stat_statements_jit.patch (text/x-patch) patch
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/
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