| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Michael Banck <mbanck(at)gmx(dot)net> |
| 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:06:42 |
| Message-ID: | 5B6A3BA1-43D5-4F69-9E1E-8B443C220BDF@yesql.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 19 Jan 2024, at 11:04, Michael Banck <mbanck(at)gmx(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matthias Kuhn | 2024-01-19 10:08:59 | Re: Build versionless .so for Android |
| Previous Message | Michael Banck | 2024-01-19 10:04:49 | Re: Oom on temp (un-analyzed table caused by JIT) V16.1 [Fixed Already] |