| From: | Pavel Luzanov <p(dot)luzanov(at)postgrespro(dot)ru> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pg_monitor role description |
| Date: | 2021-05-22 20:27:56 |
| Message-ID: | b5c19fd5-132b-168e-e361-26d882bfe019@postgrespro.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On 20.05.2021 21:25, Pavel Luzanov wrote:
> I'm totally confused. I'm taking timeout to think about it.
I got it! It wasn't my day.))
This wording worked for me:
The pg_monitor role is a member of the pg_read_all_settings role, which allows its privileges to be used. Therefore, pg_monitor can get the value of any configuration parameter.
Thanks for clarifying.
--
Pavel Luzanov
Postgres Professional: https://postgrespro.com
The Russian Postgres Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Masahiro Ikeda | 2021-05-24 02:37:09 | Re: more detailed description of tup_returned and tup_fetched |
| Previous Message | Fujii Masao | 2021-05-21 13:26:14 | Re: more detailed description of tup_returned and tup_fetched |