pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Greg Stark <stark@mit.edu>
Cc: pgsql-hackers@postgresql.org
Subject: Re: /proc/self/oom_adj is deprecated in newer Linux kernels
Date: Fri, 16 Sep 2011 12:37:46 -0400
Message-ID: <3624.1316191066@sss.pgh.pa.us> (raw)
In-Reply-To: <CAM-w4HMsQpi_v=0NK34t3xKtpkJiadTD04Xhrr2_OP8YO+y1Nw@mail.gmail.com>
References: <29121.1316185073@sss.pgh.pa.us>
	<CAM-w4HMsQpi_v=0NK34t3xKtpkJiadTD04Xhrr2_OP8YO+y1Nw@mail.gmail.com>

Greg Stark <stark@mit.edu> writes:
> On Fri, Sep 16, 2011 at 3:57 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Does anyone want
>> to argue for doing something more complicated, and if so what exactly?

> Well there's no harm trying to write to oom_score_adj and if that
> fails with EEXISTS trying to write to oom_adj.

Well, (1) what value are you going to write (they need to be different
for the two files), and (2) the main point of the exercise, at present,
is to avoid kernel log messages.  I'm not sure that trying to create
random files under /proc isn't going to draw bleats in the kernel log.

			regards, tom lane



view thread (66+ messages)  latest in thread

Message-ID: <3624.1316191066@sss.pgh.pa.us>
Permalink:  ../3624.1316191066@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/3624.1316191066@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: tgl@sss.pgh.pa.us, stark@mit.edu
  Subject: Re: /proc/self/oom_adj is deprecated in newer Linux kernels
  In-Reply-To: <3624.1316191066@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox