Re: /proc/self/oom_adj is deprecated in newer Linux kernels

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Greg Stark <stark(at)mit(dot)edu>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: /proc/self/oom_adj is deprecated in newer Linux kernels
Date: 2011-09-16 17:25:17
Message-ID: 4592.1316193917@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> Now the problem is that we have defined the LINUX_OOM_ADJ symbol as
> meaning the value we're going to write. Maybe this wasn't the best
> choice. I mean, it's very flexible, but it doesn't seem to offer any
> benefit over a plain boolean choice.

> Is your proposal to create a new LINUX_OOM_SCORE_ADJ cpp symbol with the
> same semantics?

Yes, that's what I was thinking. We could avoid that if we were going
to hard-wire a decision that zero is the thing to write, but I see no
reason to place such a restriction on users. Who's to say they might
not want backends to adopt some other value?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2011-09-16 17:27:33 Re: Improve lseek scalability v3
Previous Message Alvaro Herrera 2011-09-16 17:17:35 Re: /proc/self/oom_adj is deprecated in newer Linux kernels