| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Maciej Jaros <eccenux(at)gmail(dot)com> |
| Cc: | Tomas Vondra <tomas(at)vondra(dot)me>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #18675: Postgres is not realasing memory causing OOM |
| Date: | 2024-11-12 14:56:07 |
| Message-ID: | 5B1E7108-CB1F-4CE9-AC09-2C9299C097C2@yesql.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
> On 8 Nov 2024, at 11:29, Maciej Jaros <eccenux(at)gmail(dot)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 PG still 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2024-11-12 15:32:17 | Re: BUG #18700: pg_dump doesn't include definitions for collations nor types (e.g. enumeration) |
| Previous Message | David G. Johnston | 2024-11-12 14:21:39 | Re: BUG #18702: Critical & High Security vulnerability issue with Trivy Scan in postgres 16 |