Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WuOPU-0002lb-Bj for pgsql-hackers@arkaria.postgresql.org; Tue, 10 Jun 2014 15:56:28 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1WuOPT-0006jx-QY for pgsql-hackers@arkaria.postgresql.org; Tue, 10 Jun 2014 15:56:27 +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 ) id 1WuOPS-0006hl-Ao for pgsql-hackers@postgresql.org; Tue, 10 Jun 2014 15:56:26 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1WuOPP-0005RE-2W for pgsql-hackers@postgresql.org; Tue, 10 Jun 2014 15:56:25 +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 s5AFuExQ031430; Tue, 10 Jun 2014 11:56:14 -0400 From: Tom Lane To: Robert Haas cc: Gurjeet Singh , Andres Freund , Peter Eisentraut , PGSQL Hackers Subject: Re: /proc/self/oom_adj is deprecated in newer Linux kernels In-reply-to: References: <29121.1316185073@sss.pgh.pa.us> <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> <20140610143202.GI8406@alap3.anarazel.de> <30893.1402414198@sss.pgh.pa.us> Comments: In-reply-to Robert Haas message dated "Tue, 10 Jun 2014 11:39:13 -0400" Date: Tue, 10 Jun 2014 11:56:14 -0400 Message-ID: <31429.1402415774@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 Robert Haas writes: > On Tue, Jun 10, 2014 at 11:29 AM, Tom Lane wrote: >> If you think your users might want to give the postmaster OOM-exemption, >> why don't you just activate the existing code when you build? Resetting >> the OOM setting to zero is safe whether or not the startup script did >> anything to the postmaster's setting. > The whole scenario here is that the user *doesn't want to recompile*. Yeah, I understood that. The question is why EDB isn't satisfied to just add "-DLINUX_OOM_ADJ=0" to their build options, but instead would like to dump a bunch of uncertainty on other packagers who might not like the implications of a GUC. 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