| From: | Maciej Jaros <eccenux(at)gmail(dot)com> |
|---|---|
| To: | Daniel Gustafsson <daniel(at)yesql(dot)se>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #18675: Postgres is not realasing memory causing OOM |
| Date: | 2024-10-28 18:16:47 |
| Message-ID: | 699c1599-d0f0-4efe-a7de-660604b28d4c@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Daniel Gustafsson (28.10.2024 14:34):
>> On 28 Oct 2024, at 09:30, PG Bug reporting form<noreply(at)postgresql(dot)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 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2024-10-28 18:45:07 | Re: BUG #18675: Postgres is not realasing memory causing OOM |
| Previous Message | Maciej Jaros | 2024-10-28 18:07:45 | Re: BUG #18675: Postgres is not realasing memory causing OOM |