| From: | "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com> |
|---|---|
| To: | 'Virender Singla' <virender(dot)cse(at)gmail(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Dilip Kumar <DilipBalaut(at)gmail(dot)com> |
| Subject: | RE: Allow pg_read_all_stats to read replication origin status |
| Date: | 2026-09-18 05:17:11 |
| Message-ID: | TYRPR01MB12845B37AFFC332647F991C8FF5872@TYRPR01MB12845.jpnprd01.prod.outlook.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi Virender,
> > Looks like pg_read_all_stats was originally designed to grant access
> > to all pg_stats_* views, a few other monitoring views defined in
> > system_views.sql have been included over time. However, access to
> > pg_replication_origin_status remains restricted and is not currently
> > covered by existing roles such as pg_read_all_stats, pg_read_all_data,
> > or pg_monitor.
Not sure, does pg_replication_origin_status contain statistics? I expected
statistics means some cumulative data, but this view contains node ids and LSNs.
Can you give us a background why the idea allowing pg_monitor to read the view
was not accepted?
Best regards,
Hayato Kuroda
FUJITSU LIMITED
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Rowley | 2026-09-18 05:21:05 | Re: RANGE partition pruning can still exclude the default partition |
| Previous Message | shveta malik | 2026-09-18 04:47:38 | Re: Distinguish publication exclusions in object addresses |