pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Robert Haas <robertmhaas@gmail.com>
To: Dave Page <dpage@pgadmin.org>
Cc: Stephen Frost <sfrost@snowman.net>
Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Subject: Re: Monitoring roles patch
Date: Tue, 28 Mar 2017 11:37:42 -0400
Message-ID: <fc6b6953-7a00-3c84-1a58-3f5aa5c330a6@2ndquadrant.com> (raw)
In-Reply-To: <CA+TgmoaQLSKCKe5pPB6L9=L4tX5kLJKOx8G0khubLOucDV_m=Q@mail.gmail.com>
References: <CA+OCxoyRdsc1xyLfF9s698gUGyPXBs4CvJ+0Gwo8U65NmYJ7pw@mail.gmail.com>
	<CA+TgmobveXzVPytFOO3AkmsM+Y=YEG+UXcCvgwAt+SgYj85OCA@mail.gmail.com>
	<CA+OCxox9c9-1=bXxA6-gr-iWZbD5zdHYMz=cpC034RKB7zX40Q@mail.gmail.com>
	<c99cde7f-0aa7-ebaa-b9f4-ee75522554a4@2ndquadrant.com>
	<20170322131730.GD9812@tamriel.snowman.net>
	<d3e2e808-50fd-daca-fc07-8863930cae7d@2ndquadrant.com>
	<20170324123031.GD9812@tamriel.snowman.net>
	<CA+TgmobXyfkR2nL6jSYHCNHe6ovAw13eyY3ga39DN=J4Dd=idQ@mail.gmail.com>
	<CA+OCxoyuW71uA8TqLpiOk33gB38fwZAUL=1L5wWcGCTu2SAiwg@mail.gmail.com>
	<CA+TgmoadTvGh9_O71iQ8vjEePhSwtPo148We15+k568hXHMEJw@mail.gmail.com>
	<20170325155520.GW9812@tamriel.snowman.net>
	<0C373C5B-2291-4608-A349-4F57D694F533@pgadmin.org>
	<CA+TgmoaQLSKCKe5pPB6L9=L4tX5kLJKOx8G0khubLOucDV_m=Q@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>

On 3/27/17 08:54, Robert Haas wrote:
> OK, I see the points that both of you are making and I admit that
> they've got some validity to them.  Let me make a modest proposal.
> Suppose we define the pg_monitor role as strictly a bundle of
> privileges that could be granted individually if desired, and
> similarly define pg_read_all_settings and pg_read_all_stats as roles
> that are strictly recognized by the code, without any grants.

I think this is very important.  We can't have roles that do both.  That
will just cause confusion.  Security confusion.

I'm confused about the definition of the pg_read_all_stats role.  It
seems to give read access to just about everything that rhymes with
"stats" as well as a random collection of other things such as table
sizes.  Except actual table statistics, which was my first guess.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers



view thread (61+ messages)  latest in thread

Message-ID: <fc6b6953-7a00-3c84-1a58-3f5aa5c330a6@2ndquadrant.com>
Permalink:  ../fc6b6953-7a00-3c84-1a58-3f5aa5c330a6@2ndquadrant.com/
Also on:    postgresql.org/message-id/fc6b6953-7a00-3c84-1a58-3f5aa5c330a6@2ndquadrant.com

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: peter.eisentraut@2ndquadrant.com, robertmhaas@gmail.com, dpage@pgadmin.org, sfrost@snowman.net
  Subject: Re: Monitoring roles patch
  In-Reply-To: <fc6b6953-7a00-3c84-1a58-3f5aa5c330a6@2ndquadrant.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox