Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WuOAE-0002F0-WF for pgsql-hackers@arkaria.postgresql.org; Tue, 10 Jun 2014 15:40:43 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1WuOAE-0006MX-Eu for pgsql-hackers@arkaria.postgresql.org; Tue, 10 Jun 2014 15:40:42 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1WuOAC-0006J8-BN for pgsql-hackers@postgresql.org; Tue, 10 Jun 2014 15:40:40 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1WuOA5-0007sy-3U for pgsql-hackers@postgresql.org; Tue, 10 Jun 2014 15:40:38 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id s5AFePLf031104; Tue, 10 Jun 2014 11:40:25 -0400 From: Tom Lane To: Andres Freund cc: Robert Haas , Gurjeet Singh , Peter Eisentraut , PGSQL Hackers Subject: Re: /proc/self/oom_adj is deprecated in newer Linux kernels In-reply-to: <20140610152419.GL8406@alap3.anarazel.de> References: <1316355543.12186.9.camel@vanquo.pezone.net> <15953.1316362868@sss.pgh.pa.us> <1316420754.14001.3.camel@fsopti579.F-Secure.com> <16241.1316441883@sss.pgh.pa.us> <28946.1402408948@sss.pgh.pa.us> <30117.1402411876@sss.pgh.pa.us> <30601.1402413283@sss.pgh.pa.us> <20140610152419.GL8406@alap3.anarazel.de> Comments: In-reply-to Andres Freund message dated "Tue, 10 Jun 2014 17:24:19 +0200" Date: Tue, 10 Jun 2014 11:40:25 -0400 Message-ID: <31103.1402414825@sss.pgh.pa.us> X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org Andres Freund writes: > On 2014-06-10 11:14:43 -0400, Tom Lane wrote: >> Because it would convert the intended behavior (postmaster and only >> postmaster is exempt from OOM kill) into a situation where possibly >> all of the database processes are exempt from OOM kill, at the whim >> of somebody who should not have the privilege to decide that. > Meh^3. By that argument we need to forbid superusers to create any form > of untrusted functions. Forbid anything that does malloc(), system(), > fork(), whatever from a user's influence. That's utter and complete nonsense. We're discussing an operation that is root-privileged (ie, lowering a process's OOM score), not random stuff that unprivileged processes can do. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers