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

Поиск
Список
Период
Сортировка
От Daniel Gustafsson
Тема Re: Oom on temp (un-analyzed table caused by JIT) V16.1 [Fixed Already]
Дата
Msg-id 5B6A3BA1-43D5-4F69-9E1E-8B443C220BDF@yesql.se
обсуждение исходный текст
Ответ на Re: Oom on temp (un-analyzed table caused by JIT) V16.1 [Fixed Already]  (Michael Banck <mbanck@gmx.net>)
Список pgsql-hackers
> On 19 Jan 2024, at 11:04, Michael Banck <mbanck@gmx.net> wrote:
> 
> 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?

Ah, it is, I completely forgot we had that one. Thanks!

--
Daniel Gustafsson




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

Предыдущее
От: Michael Banck
Дата:
Сообщение: Re: Oom on temp (un-analyzed table caused by JIT) V16.1 [Fixed Already]
Следующее
От: Matthias Kuhn
Дата:
Сообщение: Re: Build versionless .so for Android