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
