PostgreSQL and the OOM Killer: Why We Use Strict Memory Overcommit

Posted by levkk on Friday June 05, 2026 @11:10AM
from the ubicloud.com dept.

https://www.ubicloud.com/blog/postgresql-and-the-oom-killer-why-we-use-strict-memory-overcommit

( 3 comments | 4 points | on HN )

Re:PostgreSQL and the OOM Killer: Why We Use Strict Memory O... by pwmtr on Friday June 05, 2026 @11:23AM (#48413798)

The author of the blog post here.

In hindsight, the kernel bug seems obvious, but the process of tracking it down was quite interesting. I especially enjoyed the statistical analysis part, which isn't something you normally get to do while debugging :)

Anyway, I'd be happy to answer any questions you might have.

[ Parent | on HN ]

Re:PostgreSQL and the OOM Killer: Why We Use Strict Memory O... by __s on Friday June 05, 2026 @11:29AM (#48413875)

"it's always something stupid" has been my approach to bugs for a long time. hindsight 20/20

[ Parent | on HN ]

Re:PostgreSQL and the OOM Killer: Why We Use Strict Memory O... by __s on Friday June 05, 2026 @11:31AM (#48413905)

we recently ran into trouble where PGroonga on the other hand needs overcommit enabled, in direct opposition to postgres preferences: https://pgroonga.github.io/how-to/tuning.html

[ Parent | on HN ]