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

From David G. Johnston
Subject Re: BUG #18675: Postgres is not realasing memory causing OOM
Date
Msg-id CAKFQuwY=-O7-Bnq8PuAtH1TR=y=nmj3U+YqKEeemCM91=or3OA@mail.gmail.com
Whole thread Raw
In response to BUG #18675: Postgres is not realasing memory causing OOM  (PG Bug reporting form <noreply@postgresql.org>)
List pgsql-bugs
On Monday, October 28, 2024, PG Bug reporting form <noreply@postgresql.org> wrote:
The following bug has been logged on the website:

Bug reference:      18675
Logged by:          Maciej Jaros
Email address:      eccenux@gmail.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.

pgsql-bugs by date:

Previous
From: Daniel Gustafsson
Date:
Subject: Re: BUG #18675: Postgres is not realasing memory causing OOM
Next
From: PG Bug reporting form
Date:
Subject: BUG #18676: Execute function while selecting from table with partial index using this function.