Re: pg_monitor role description

From: Julien Rouhaud <rjuju123(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: pluzanov(at)postgrespro(dot)ru, pgsql-docs(at)lists(dot)postgresql(dot)org
Subject: Re: pg_monitor role description
Date: 2021-05-20 08:54:27
Message-ID: CAOBaU_Y3b1Vet2UPDwjyi-pVv1wxT8fH4Fe4UKEZbZi6C-SGWQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

On Thu, May 20, 2021 at 3:01 PM Michael Paquier <michael(at)paquier(dot)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.

In response to

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message Pavel Luzanov 2021-05-20 12:44:52 Re: pg_monitor role description
Previous Message Masahiro Ikeda 2021-05-20 08:38:44 Re: more detailed description of tup_returned and tup_fetched