Re: BUG #18675: Postgres is not realasing memory causing OOM - Mailing list pgsql-bugs

From Daniel Gustafsson
Subject Re: BUG #18675: Postgres is not realasing memory causing OOM
Date
Msg-id 5B1E7108-CB1F-4CE9-AC09-2C9299C097C2@yesql.se
Whole thread Raw
In response to BUG #18675: Postgres is not realasing memory causing OOM  (PG Bug reporting form <noreply@postgresql.org>)
List pgsql-bugs
> On 8 Nov 2024, at 11:29, Maciej Jaros <eccenux@gmail.com> wrote:
>
> I can now confirm that JIT is adding significant amount of memory on top of what PG SQL is using. Memory reserved by
PGstill grows every day, but doesn't grow as much as with JIT. So there is still something wrong with Postgres. 

Using memory isn't necessarily something wrong, it would be a lot worse if it
needed the memory and used swap instead.  Are you able to try with JIT inlining
turned off as I asked about upthread.

--
Daniel Gustafsson




pgsql-bugs by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: BUG #18702: Critical & High Security vulnerability issue with Trivy Scan in postgres 16
Next
From: Tom Lane
Date:
Subject: Re: BUG #18700: pg_dump doesn't include definitions for collations nor types (e.g. enumeration)