oom_adj and -DLINUX_OOM_ADJ=0 should be used
Bug #854590 reported by
Franck
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
postgresql-9.1 (Ubuntu) |
Fix Released
|
Low
|
Unassigned | ||
postgresql-common (Ubuntu) |
Fix Released
|
Low
|
Martin Pitt |
Bug Description
I just had a bad exerience with oom_killer killing the postmaster, and I am wondering if debian/ubuntu package should use the oom_adj trick to avoid this.
As I understand it, this would imply:
1) set oom_adj to -17 in the init script (to make the postmaster unkillable)
2) compile postgresql with -DLINUX_OOM_ADJ=0 cflag (to allow the children processes to be killed)
Does it make sense and could it be considered ?
To post a comment you must log in.
Here is a link to a discussion on pgsql-hackers( at)postgresql( dot)org about the subject, in case that could help:
http:// archives. postgresql. org/pgsql- hackers/ 2010-01/ msg00170. php