From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | "eccenux(at)gmail(dot)com" <eccenux(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-10-28 13:42:05 |
Message-ID: | CAKFQuwY=-O7-Bnq8PuAtH1TR=y=nmj3U+YqKEeemCM91=or3OA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Monday, October 28, 2024, PG Bug reporting form <noreply(at)postgresql(dot)org>
wrote:
> The following bug has been logged on the website:
>
> Bug reference: 18675
> Logged by: Maciej Jaros
> Email address: eccenux(at)gmail(dot)com
> PostgreSQL version: 16.4
> Operating system: Ubuntu 22.04
> Description:
> or maybe
> PostgreSQL should include garbage collection?
Garbage collection is typically used in relation to a programming language
feature to make writing applications in those languages easier.
Applications themselves don’t really implement garbage collection. And C,
the language PostgreSQL, is written in, doesn’t have garbage collection. To
our knowledge, though, there are no significant memory leaks in supported
versions.
>
> RAMforPG = shared_buffers + (temp_buffers + work_mem) * max_connections;
>
>
The expression: work_mem * max_connections is incorrect. See the doc for
work_mem for how it is used.
There is so much more info needed to conclude there is a bug here - which
there probably is not. Exploring the query and tuning the system is better
discussed on the -general mailing list.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | PG Bug reporting form | 2024-10-28 14:58:34 | BUG #18676: Execute function while selecting from table with partial index using this function. |
Previous Message | Daniel Gustafsson | 2024-10-28 13:34:15 | Re: BUG #18675: Postgres is not realasing memory causing OOM |