Quick Links

Re: Expose JIT counters/timing in pg_stat_statements

From:	Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
To:	Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject:	Re: Expose JIT counters/timing in pg_stat_statements
Date:	2022-02-28 16:00:05
Message-ID:	be49501d-71cc-5ceb-a60f-0d47f63ca3d6@enterprisedb.com
Views:	Raw Message \| Whole Thread \| Download mbox \| Resend email
Thread:
Lists:	pgsql-hackers

On 25.02.22 14:06, Magnus Hagander wrote:
> + OUT jit_generation_time float8,
> + OUT jit_inlining_time float8,
> + OUT jit_optimization_time float8,
> + OUT jit_emission_time float8

Perhaps those should be of type interval?

In response to

Expose JIT counters/timing in pg_stat_statements at 2022-02-25 13:06:29 from Magnus Hagander

Responses

Re: Expose JIT counters/timing in pg_stat_statements at 2022-02-28 16:24:49 from Julien Rouhaud

Browse pgsql-hackers by date

	From	Date	Subject
Next Message	Peter Eisentraut	2022-02-28 16:02:56	Re: Readd use of TAP subtests
Previous Message	Bharath Rupireddy	2022-02-28 15:33:07	Use "WAL segment" instead of "log segment" consistently in user-facing messages