Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lejAf-0000E4-Vu for pgsql-hackers@arkaria.postgresql.org; Thu, 06 May 2021 18:56:25 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lejAe-0008Vn-5N for pgsql-hackers@arkaria.postgresql.org; Thu, 06 May 2021 18:56:24 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lejAd-0008Ve-UA for pgsql-hackers@lists.postgresql.org; Thu, 06 May 2021 18:56:23 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lejAX-0004QH-DI for pgsql-hackers@lists.postgresql.org; Thu, 06 May 2021 18:56:23 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 146Iu9HI4174277; Thu, 6 May 2021 14:56:10 -0400 From: Tom Lane To: Robert Haas cc: vignesh C , Bharath Rupireddy , Andres Freund , Craig Ringer , Peter Eisentraut , PostgreSQL Hackers Subject: Re: Printing backtrace of postgres processes In-reply-to: References: <20210115201011.noomcygirzge43ir@alap3.anarazel.de> <3537.1610828491@sss.pgh.pa.us> <492025.1611078655@sss.pgh.pa.us> <523589.1611091371@sss.pgh.pa.us> <799340.1611194209@sss.pgh.pa.us> <20210127170958.vzo33jzmqwhmn7z6@alap3.anarazel.de> <3886673.1612337426@sss.pgh.pa.us> Comments: In-reply-to Robert Haas message dated "Thu, 06 May 2021 14:38:51 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <4174275.1620327369.1@sss.pgh.pa.us> Date: Thu, 06 May 2021 14:56:09 -0400 Message-ID: <4174276.1620327369@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Robert Haas writes: > On Wed, Feb 3, 2021 at 2:30 AM Tom Lane wrote: >> TBH, I'm leaning to the position that this should be superuser >> only. > I agree that ordinary users shouldn't be able to trigger it, but I > think it should be restricted to some predefined role, new or > existing, rather than to superuser. I see no reason not to let > individual users decide what risks they want to take. If we think it's worth having a predefined role for, OK. However, I don't like the future I see us heading towards where there are hundreds of random predefined roles. Is there an existing role that it'd be reasonable to attach this ability to? regards, tom lane