Re: Expose JIT counters/timing in pg_stat_statements

Поиск
Список
Период
Сортировка
От Julien Rouhaud
Тема Re: Expose JIT counters/timing in pg_stat_statements
Дата
Msg-id 20220225133322.ekhgqbf2r34isa73@jrouhaud
обсуждение исходный текст
Ответ на Expose JIT counters/timing in pg_stat_statements  (Magnus Hagander <magnus@hagander.net>)
Ответы Re: Expose JIT counters/timing in pg_stat_statements  (Magnus Hagander <magnus@hagander.net>)
Список pgsql-hackers
Hi,

On Fri, Feb 25, 2022 at 02:06:29PM +0100, Magnus Hagander wrote:
> 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.

+1, it seems like something quite useful.

> 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.

I think the cumulated total time is enough.  Looking at the patch, I think we
should also cumulate the number of time jit was triggered, and
probably the same for each other main operation (optimization and inlining).
Otherwise the values may be wrong and look artificially low.



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Peter Eisentraut
Дата:
Сообщение: Re: convert libpq uri-regress tests to tap test
Следующее
От: Bharath Rupireddy
Дата:
Сообщение: Re: [PATCH] add relation and block-level filtering to pg_waldump