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

On Fri, Jan 19, 2024 at 7:03 PM Daniel Gustafsson wrote: > > On 19 Jan 2024, at 23:09, Kirk Wolak wrote: > > > From a FUTURE email, I noticed pg_jit_available() and it's set to f?? > > Right, then this installation does not contain the necessary library to JIT > compile the query. > > > Okay, s

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

> On 19 Jan 2024, at 23:09, Kirk Wolak wrote: > From a FUTURE email, I noticed pg_jit_available() and it's set to f?? Right, then this installation does not contain the necessary library to JIT compile the query. > Okay, so does this require a special BUILD command? Yes, it requires that you

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

On Fri, Jan 19, 2024 at 4:20 AM Laurenz Albe wrote: > On Thu, 2024-01-18 at 19:50 -0500, Kirk Wolak wrote: > > I did a little more checking and the reason I did not see the link > MIGHT be because EXPLAIN did not show a JIT attempt. > > I tried to use settings that FORCE a JIT... But to no ava

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

> On 19 Jan 2024, at 11:04, Michael Banck 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 quer

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

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).

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

> On 19 Jan 2024, at 01:50, Kirk Wolak wrote: > I did a little more checking and the reason I did not see the link MIGHT be > because EXPLAIN did not show a JIT attempt. > I tried to use settings that FORCE a JIT... But to no avail. Are you sure you are running a JIT enabled server? Did you

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

On Thu, 2024-01-18 at 19:50 -0500, Kirk Wolak wrote: >   I did a little more checking and the reason I did not see the link MIGHT be > because EXPLAIN did not show a JIT attempt. > I tried to use settings that FORCE a JIT...  But to no avail. > >   I am now concerned that the problem is more hidd

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

On Tue, Jan 16, 2024 at 3:43 AM Daniel Gustafsson wrote: > > On 16 Jan 2024, at 02:53, Kirk Wolak wrote: > > > > On Mon, Jan 15, 2024 at 9:03 AM Daniel Gustafsson > wrote: > > > On 15 Jan 2024, at 07:24, Kirk Wolak wol...@gmail.com>> wrote: > >... > > Okay, I took the l

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

> On 16 Jan 2024, at 02:53, Kirk Wolak wrote: > > On Mon, Jan 15, 2024 at 9:03 AM Daniel Gustafsson > wrote: > > On 15 Jan 2024, at 07:24, Kirk Wolak > > wrote: > > > You have a commit [1] that MIGHT fix this. > > I have a script that recreate

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

On Mon, Jan 15, 2024 at 9:03 AM Daniel Gustafsson wrote: > > On 15 Jan 2024, at 07:24, Kirk Wolak wrote: > > > You have a commit [1] that MIGHT fix this. > > I have a script that recreates the problem, using random data in pg_temp. > > And a nested cursor. > > Running your reproducer script in