Expose JIT counters/timing in pg_stat_statements

Поиск
Список
Период
Сортировка
От Magnus Hagander
Тема Expose JIT counters/timing in pg_stat_statements
Дата
Msg-id CABUevEySt4NTYqvWzwyAW_0-jG1bjN-y+tykapAnA0FALOs+Lw@mail.gmail.com
обсуждение исходный текст
Ответы Re: Expose JIT counters/timing in pg_stat_statements  (Julien Rouhaud <rjuju123@gmail.com>)
Re: Expose JIT counters/timing in pg_stat_statements  (Peter Eisentraut <peter.eisentraut@enterprisedb.com>)
Список pgsql-hackers
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/

Вложения

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

Предыдущее
От: Dilip Kumar
Дата:
Сообщение: Re: should vacuum's first heap pass be read-only?
Следующее
От: Japin Li
Дата:
Сообщение: Re: [PATCH] add relation and block-level filtering to pg_waldump