| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com>, Dave Page <dpage(at)pgadmin(dot)org> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Monitoring roles patch |
| Date: | 2017-03-28 15:37:42 |
| Message-ID: | fc6b6953-7a00-3c84-1a58-3f5aa5c330a6@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2017-03-28 15:39:03 | Re: pg_dump emits ALTER TABLE ONLY partitioned_table |
| Previous Message | Robert Haas | 2017-03-28 15:35:15 | Re: [COMMITTERS] pgsql: Improve access to parallel query from procedural languages. |