| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Maciej Jaros <eccenux(at)gmail(dot)com> |
| Cc: | Tomas Vondra <tomas(at)vondra(dot)me>, "David G(dot) Johnston" <david(dot)g(dot)johnston(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-29 16:13:52 |
| Message-ID: | 241665.1730218432@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Maciej Jaros <eccenux(at)gmail(dot)com> writes:
> So, that comment led me to suggest adding some kind of process. I called it
> a garbage collector, but maybe David is right; maybe that’s not accurate.
> Anyway, that process, in my view, could try to actually release memory to
> the system to prevent the OOM killer from doing its bidding. Is that
> possible?
We do not even know what is causing your problem, let alone know a
way that one process could command another one to stop doing it.
So no, this suggestion is not helpful.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2024-10-29 16:16:31 | Re: BUG #18675: Postgres is not realasing memory causing OOM |
| Previous Message | Maciej Jaros | 2024-10-29 12:26:09 | Re: BUG #18675: Postgres is not realasing memory causing OOM |