Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1aCrOB-0004Hq-AN for pgsql-hackers@arkaria.postgresql.org; Sat, 26 Dec 2015 16:08:15 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84) (envelope-from ) id 1aCrO9-0001c5-Tz for pgsql-hackers@arkaria.postgresql.org; Sat, 26 Dec 2015 16:08:13 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1aCrMq-00008F-1E for pgsql-hackers@postgresql.org; Sat, 26 Dec 2015 16:06:52 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1aCrMi-0007uI-HQ for pgsql-hackers@postgresql.org; Sat, 26 Dec 2015 16:06:51 +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 tBQG6ba9023260; Sat, 26 Dec 2015 11:06:37 -0500 From: Tom Lane To: Andres Freund cc: =?utf-8?B?0JLQsNGB0LjQu9GM0LXQsiDQlNC80LjRgtGA0LjQuQ==?= , pgsql-hackers@postgresql.org Subject: Re: Performance degradation in commit ac1d794 In-reply-to: <20151226121114.x3mh4v33flkxnqgl@alap3.anarazel.de> References: <9F7A592C-323B-40CF-AEB6-20D28EAEFFDD@anarazel.de> <19322.1451067023@sss.pgh.pa.us> <19834.1451068135@sss.pgh.pa.us> <20151225211326.z4umuafvv27nczya@alap3.anarazel.de> <24833.1451078993@sss.pgh.pa.us> <20151226112248.uv3qxmroe4va7wke@alap3.anarazel.de> <20151226121114.x3mh4v33flkxnqgl@alap3.anarazel.de> Comments: In-reply-to Andres Freund message dated "Sat, 26 Dec 2015 13:11:14 +0100" Date: Sat, 26 Dec 2015 11:06:37 -0500 Message-ID: <23259.1451145997@sss.pgh.pa.us> X-Pg-Spam-Score: -1.9 (-) 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: > A unportable and easy version of this, actually making sense this time, > would be to use prctl(PR_SET_PDEATHSIG, SIGQUIT). That'd send SIGQUIT to > backends whenever postmaster dies. Obviously that's not portable > either - doing this for linux only wouldn't be all that kludgey tho. Hmm. That would have semantics rather substantially different from the way that the WL_POSTMASTER_DEATH code behaves. But I don't know how much we care about that, since the whole scenario is something that should not happen under normal circumstances. Maybe cross-platform variation is OK as long as it doesn't make the code too hairy. 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