Received: from malur.postgresql.org ([217.196.149.56])
 by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from
 <pgsql-hackers-owner+M251470=pgsql-hackers-arkari@postgresql.org>)
 id 1WuOQl-0002nY-T4
 for pgsql-hackers@arkaria.postgresql.org; Tue, 10 Jun 2014 15:57:48 +0000
Received: from localhost ([127.0.0.1] helo=postgresql.org)
 by malur.postgresql.org with smtp (Exim 4.80) (envelope-from
 <pgsql-hackers-owner+M251470=pgsql-hackers-arkari@postgresql.org>)
 id 1WuOQk-0000A5-Vy
 for pgsql-hackers@arkaria.postgresql.org; Tue, 10 Jun 2014 15:57:47 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
 by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256)
 (Exim 4.80) (envelope-from <andres@anarazel.de>) id 1WuOQf-0008Su-Nx
 for pgsql-hackers@postgresql.org; Tue, 10 Jun 2014 15:57:41 +0000
Received: from mail.anarazel.de ([217.115.131.40])
 by magus.postgresql.org with esmtp (Exim 4.80)
 (envelope-from <andres@anarazel.de>) id 1WuOQb-0005Rd-Nq
 for pgsql-hackers@postgresql.org; Tue, 10 Jun 2014 15:57:40 +0000
Received: from intern.anarazel.de (p5DDC5B67.dip0.t-ipconnect.de
 [93.220.91.103]) (Authenticated sender: andres@anarazel.de)
 by mail.anarazel.de (Postfix) with ESMTPSA id 69FB64E8006;
 Tue, 10 Jun 2014 17:57:37 +0200 (CEST)
Date: Tue, 10 Jun 2014 17:57:36 +0200
From: Andres Freund <andres@anarazel.de>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Gurjeet Singh <gurjeet@singh.im>, Peter Eisentraut <peter_e@gmx.net>,
 PGSQL Hackers <pgsql-hackers@postgresql.org>
Subject: Re: /proc/self/oom_adj is deprecated in newer Linux kernels
Message-ID: <20140610155736.GP8406@alap3.anarazel.de>
References: <15953.1316362868@sss.pgh.pa.us>
 <1316420754.14001.3.camel@fsopti579.F-Secure.com>
 <16241.1316441883@sss.pgh.pa.us>
 <CABwTF4XDdYiBQXqj=CKrFXN7x2NiBbVnpHSJG6AVnMBLnLBmLA@mail.gmail.com>
 <20140610143202.GI8406@alap3.anarazel.de>
 <30402.1402412692@sss.pgh.pa.us>
 <20140610150933.GK8406@alap3.anarazel.de>
 <30709.1402413628@sss.pgh.pa.us>
 <20140610153347.GM8406@alap3.anarazel.de>
 <31348.1402415537@sss.pgh.pa.us>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <31348.1402415537@sss.pgh.pa.us>
X-Pg-Spam-Score: -3.3 (---)
List-Archive: <http://archives.postgresql.org/pgsql-hackers>
List-Help: <mailto:majordomo@postgresql.org?body=help>
List-ID: <pgsql-hackers.postgresql.org>
List-Owner: <mailto:pgsql-hackers-owner@postgresql.org>
List-Post: <mailto:pgsql-hackers@postgresql.org>
List-Subscribe: <mailto:majordomo@postgresql.org?body=sub%20pgsql-hackers>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
X-Mailing-List: pgsql-hackers
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org

On 2014-06-10 11:52:17 -0400, Tom Lane wrote:
> andres@anarazel.de (Andres Freund) writes:
> > On 2014-06-10 11:20:28 -0400, Tom Lane wrote:
> >> 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.
> 
> That's kind of annoying --- I wonder why they went to the trouble of doing
> that?

My guess is that they want to allow a process to only temporarily reduce
the likelihood of getting killed while it's doing something
important.

Greetings,

Andres Freund

-- 
 Andres Freund	                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers