| From: | Joseph Hammerman <joe(dot)hammerman(at)datadoghq(dot)com> |
|---|---|
| To: | pgsql-admin(at)lists(dot)postgresql(dot)org |
| Subject: | Getting out ahead of OOM |
| Date: | 2025-03-07 19:07:58 |
| Message-ID: | CAHs7QM_8SRfybxg_Pq3orGw5anMkV7OzKYfxDXSBQVWzcXf3Bw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Hello admins,
We run Postgres in a Kubernetes environment, and we have not to date been
able to convince our Compute team to create a class of Kubernetes hosts
that have memory overcommit disabled.
Has anyone had success tracking all the Postgres memory allocation
configurables and using that to administratively prevent OOMing?
Alternatively, has anyone has success implementing an extension or periodic
process to monitor the memory consumption of the Postgres children and
killing them before the OOM event occurs?
If there are adjacent ideas or approaches that I have not considered,
please feel free to share those with me as well.
Thanks in advance for any assistance anyone can provide,
Joseph Hammerman
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2025-03-07 19:26:03 | Re: Getting out ahead of OOM |
| Previous Message | Achilleas Mantzios - cloud | 2025-03-06 08:28:00 | Re: Comparing Parameters PRE- and POST- Upgrade - Any script? |