From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
cc: Robert Haas <robertmhaas@gmail.com>, vignesh C <vignesh21@gmail.com>,
        Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>,
        Craig Ringer <craig.ringer@enterprisedb.com>,
        Peter Eisentraut <peter.eisentraut@enterprisedb.com>,
        PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: Printing backtrace of postgres processes
In-reply-to: <20210506191905.24rprjcj5ssjqcb2@alap3.anarazel.de>
References: <20210127170958.vzo33jzmqwhmn7z6@alap3.anarazel.de>
 <CALDaNm1uWKn8KGD0q8HqCPhxSUDKWCEW55aidOiJwd+vfaB+gg@mail.gmail.com>
 <CALj2ACXfXefmdUWiF0twoYEfgJ6Xk4saXctoYyzXtzkjizCdBw@mail.gmail.com>
 <CALDaNm0aEUNLZeiDAXvPsgm4nFUjUhtfeztGofmVJU--irSD8Q@mail.gmail.com>
 <CALj2ACXybys_tzWeatb9htVTuxKp29VErc6iJQYJBbdBZXv2fg@mail.gmail.com>
 <CALj2ACUhgagr-nLcte2+61khpO6uxvERvZA28hQpxtTzbz3U2g@mail.gmail.com>
 <CALDaNm3HHMxUpYYbUFM3=RYBYZjQGgnULxdDrqwaH=DovuY! MSQ@mail.gmail.com>
 <3886673.1612337426@sss.pgh.pa.us>
 <CA+Tgmoa9jsOD3h3KmkZLTSpZy-oDazZqesKFquCiDBb6mQvppg@mail.gmail.com>
 <4174276.1620327369@sss.pgh.pa.us>
 <20210506191905.24rprjcj5ssjqcb2@alap3.anarazel.de>
Comments: In-reply-to Andres Freund <andres@anarazel.de>
	message dated "Thu, 06 May 2021 12:19:05 -0700"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <4175731.1620329462.1@sss.pgh.pa.us>
Date: Thu, 06 May 2021 15:31:02 -0400
Message-ID: <4175732.1620329462@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/4175732.1620329462%40sss.pgh.pa.us>
Precedence: bulk

Andres Freund <andres@anarazel.de> writes:
> On 2021-05-06 14:56:09 -0400, Tom Lane wrote:
>> 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?

> It does seem like it'd be good to group it in with something
> else. There's nothing fitting 100% though.

I'd probably vote for pg_read_all_data, considering that much of
the concern about this has to do with the possibility of exposure
of sensitive data.  I'm not quite sure what the security expectations
are for pg_monitor.

			regards, tom lane