| From: | andres(at)anarazel(dot)de (Andres Freund) |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Gurjeet Singh <gurjeet(at)singh(dot)im>, Peter Eisentraut <peter_e(at)gmx(dot)net>, PGSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: /proc/self/oom_adj is deprecated in newer Linux kernels |
| Date: | 2014-06-10 15:33:47 |
| Message-ID: | 20140610153347.GM8406@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2014-06-10 11:20:28 -0400, Tom Lane wrote:
> Andres Freund <andres(at)2ndquadrant(dot)com> writes:
> > On 2014-06-10 11:04:52 -0400, Tom Lane wrote:
> >> But anyway, yeah, the point of this feature is that the OOM priority
> >> of the postmaster, and *only* the postmaster, should be raised. Allowing
> >> unprivileged people to break that is not attractive on any level.
>
> > A superuser could already write a function that echoes into /proc?
>
> Maybe I'm mistaken, but I thought once the fork_process code has reset our
> process's setting to zero it's not possible to lower it again (without
> privileges we'd not have).
No, doesn't look that way. It's possible to reset it to the value set at
process start. So unless we introduce double forks for every backend
start it can be reset by ordinary processes.
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2014-06-10 15:35:23 | Re: /proc/self/oom_adj is deprecated in newer Linux kernels |
| Previous Message | Tom Lane | 2014-06-10 15:29:58 | Re: /proc/self/oom_adj is deprecated in newer Linux kernels |