Re: Oom on temp (un-analyzed table caused by JIT) V16.1 [Fixed Already]

From: Michael Banck <mbanck(at)gmx(dot)net>
To: Daniel Gustafsson <daniel(at)yesql(dot)se>
Cc: Kirk Wolak <wolakk(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Subject: Re: Oom on temp (un-analyzed table caused by JIT) V16.1 [Fixed Already]
Date: 2024-01-19 10:04:49
Message-ID: 20240119100418.GC17618@caipicrew.dd-dns.delightning.caipicrew.dd-dns.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On Fri, Jan 19, 2024 at 10:48:12AM +0100, Daniel Gustafsson wrote:
> This does bring up an interesting point, I don't think there is a way
> for a user to know whether the server is jit enabled or not (apart
> from explaining a query with costs adjusted but that's not all that
> userfriendly). Maybe we need a way to reliably tell if JIT is active
> or not.

I thought this is what pg_jit_available() is for?

postgres=> SHOW jit;
jit
-----
on
(1 Zeile)

postgres=> SELECT pg_jit_available();
pg_jit_available
------------------
f
(1 Zeile)

Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Daniel Gustafsson 2024-01-19 10:06:42 Re: Oom on temp (un-analyzed table caused by JIT) V16.1 [Fixed Already]
Previous Message John Naylor 2024-01-19 09:48:23 Re: [PoC] Improve dead tuple storage for lazy vacuum