From: Maciej Jaros <eccenux@gmail.com>
To: Daniel Gustafsson <daniel@yesql.se>
To: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18675: Postgres is not realasing memory causing OOM
Date: Mon, 28 Oct 2024 19:16:47 +0100
Message-ID: <699c1599-d0f0-4efe-a7de-660604b28d4c@gmail.com> (raw)
In-Reply-To: <315A5DE4-2689-4249-926B-0BBBC3A881D8@yesql.se>
References: <18675-39a45505fb472bf0@postgresql.org>
<315A5DE4-2689-4249-926B-0BBBC3A881D8@yesql.se>
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 |
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: eccenux@gmail.com, daniel@yesql.se, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18675: Postgres is not realasing memory causing OOM
In-Reply-To: <699c1599-d0f0-4efe-a7de-660604b28d4c@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox