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

From Maciej Jaros
Subject Re: BUG #18675: Postgres is not realasing memory causing OOM
Date
Msg-id 699c1599-d0f0-4efe-a7de-660604b28d4c@gmail.com
Whole thread Raw
In response to Re: BUG #18675: Postgres is not realasing memory causing OOM  (Daniel Gustafsson <daniel@yesql.se>)
Responses Re: BUG #18675: Postgres is not realasing memory causing OOM
List pgsql-bugs
Daniel Gustafsson (28.10.2024 14:34):
On 28 Oct 2024, at 09:30, PG Bug reporting form <noreply@postgresql.org> wrote:
Hi. We have a DB server running on a VM hosted on Proxmox (ZFS). We recently
upgraded from PG10 to PG16 and noticed an increase in load and, most
importantly, **uncontrolled** RAM usage growth.
Are you running with or without JIT?

Hi. Yes, JIT is enabled:
^                    name ^   value ^
|                     jit |      on |
|          jit_above_cost |  100000 |
|   jit_debugging_support |     off |
|        jit_dump_bitcode |     off |
|         jit_expressions |      on |
|   jit_inline_above_cost |  500000 |
| jit_optimize_above_cost |  500000 |
|   jit_profiling_support |     off |
|            jit_provider | llvmjit |
|     jit_tuple_deforming |      on |

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #18676: Execute function while selecting from table with partial index using this function.
Next
From: Tom Lane
Date:
Subject: Re: BUG #18675: Postgres is not realasing memory causing OOM