Re: pg_monitor role description - Mailing list pgsql-docs

From Julien Rouhaud
Subject Re: pg_monitor role description
Date
Msg-id CAOBaU_Y3b1Vet2UPDwjyi-pVv1wxT8fH4Fe4UKEZbZi6C-SGWQ@mail.gmail.com
Whole thread Raw
In response to Re: pg_monitor role description  (Michael Paquier <michael@paquier.xyz>)
Responses Re: pg_monitor role description  (Pavel Luzanov <p.luzanov@postgrespro.ru>)
List pgsql-docs
On Thu, May 20, 2021 at 3:01 PM Michael Paquier <michael@paquier.xyz> wrote:
>
> On Thu, May 20, 2021 at 06:11:40AM +0000, PG Doc comments form wrote:
> > "This role is a member of pg_read_all_settings, pg_read_all_stats and
> > pg_stat_scan_tables."
> > Is it correct sentence?
> > It seems for me that pg_read_all_stats is a member of pg_monitor. But not
> > vice versa.
>
> Here is what I am getting:
> =# \dgS pg_monitor
>                                       List of roles
>  Role name  |  Attributes  |                         Member of
> ------------+--------------+--------------------------------------------------------------
>  pg_monitor | Cannot login | {pg_read_all_settings,pg_read_all_stats,pg_stat_scan_tables}
>
> =# \dgS pg_read_all_data
>                 List of roles
>
>     Role name     |  Attributes  | Member of
> ------------------+--------------+-----------
>  pg_read_all_data | Cannot login | {}
>
> So the docs look correct to me.

Indeed.  In other words pg_monitor is the sum of the authorizations
given by all those roles.



pgsql-docs by date:

Previous
From: Masahiro Ikeda
Date:
Subject: Re: more detailed description of tup_returned and tup_fetched
Next
From: Pavel Luzanov
Date:
Subject: Re: pg_monitor role description