Has anyone had success tracking all the Postgres memory allocation configurables and using that to administratively prevent OOMing?
Don’t use memory limits in Kubernetes and we also run Postgres on dedicated Kubernetes clusters.
Shared memory will get counted multiple times. Each login session; as it maps in the shared buffers, it will get wrongly counted as memory used (it is shared memory!).
I have instances running on Kubernetes that only use 6GB of memory; however Kubernetes is wrongly reporting 50GB used due to number of active seasons. Our Postgres pods use to get terminated when “exceeding" the limit but not! Until removed the use of memory limits in Kubernetes.
