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

> On 15 Jan 2024, at 16:49, Kirk Wolak <wolakk@gmail.com> wrote:
> On Mon, Jan 15, 2024 at 9:03 AM Daniel Gustafsson <daniel@yesql.se <mailto:daniel@yesql.se>> wrote:

> The script starts by creating 90 Million rows...  In my world that part of the script, plus the indexes, etc.  Takes
about8-9 minutes. 
> And has no memory loss.

That's expected, the memory leak did not affect those operations.

> I used the memory reported by HTOP to track the problem.  I Forgot to mention this.
> I am curious what you used?  (Because it doesn't display symptoms [running dog slow] until the backend has about 85%
ofthe machines memory) 

I use a combination of tools, in thise case I analyzed a build with Instruments on macOS.

> There are up to date snapshots of the upcoming v16 minor release which might
> make testing easier than building postgres from source?
>
>     https://www.postgresql.org/download/snapshots/ <https://www.postgresql.org/download/snapshots/>
>
> Thank you.  I have assigned that task to the guy who maintains our VMs/Environments.
> I will report back to you.

Great!

--
Daniel Gustafsson