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

From Kirk Wolak
Subject Re: Oom on temp (un-analyzed table caused by JIT) V16.1 [Fixed Already]
Date
Msg-id CACLU5mS7phwdcso8TkJrJ_QgH6kwxBA8y3Hvbt8y0b4vN3ZkzQ@mail.gmail.com
Whole thread Raw
In response to Re: Oom on temp (un-analyzed table caused by JIT) V16.1  (Daniel Gustafsson <daniel@yesql.se>)
Responses Re: Oom on temp (un-analyzed table caused by JIT) V16.1 [Fixed Already]
List pgsql-hackers
On Mon, Jan 15, 2024 at 9:03 AM Daniel Gustafsson <daniel@yesql.se> wrote:
> On 15 Jan 2024, at 07:24, Kirk Wolak <wolakk@gmail.com> 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 a tight loop for a fair bit of time on the
v16 HEAD I cannot see any memory growth, so it's plausible that the upcoming
16.2 will work better in your environment.

Okay, I took the latest source off of git (17devel) and got it to work there in a VM.

It appears this issue is fixed.  It must have been related to the issue originally tagged. 

Thanks!

pgsql-hackers by date:

Previous
From: Peter Smith
Date:
Subject: Re: Synchronizing slots from primary to standby
Next
From: Jeff Davis
Date:
Subject: Re: [17] CREATE SUBSCRIPTION ... SERVER