| From: | Virender Singla <virender(dot)cse(at)gmail(dot)com> |
|---|---|
| To: | Shubhra Jain <shubhra(dot)jain(at)ksolves(dot)com>, Dilip Kumar <DilipBalaut(at)gmail(dot)com>, "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Allow pg_read_all_stats to read replication origin status |
| Date: | 2026-11-03 11:17:01 |
| Message-ID: | CAM6Zo8zG_9Dr4ia+KcyjE7X1G0vhsJxf0Uq6MxgRw69LHfhAQg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Thanks Subhra for thoroughly testing the patch, and sorry for the delayed
reply.
> pg_read_all_stats grant as proposed.
> Access can be widened later more easily than it can be narrowed, and the
> view is restricted today. In my testing the view showed only origin names
> and LSNs and no table data, so making it public later looks low-risk if
> a committer prefers that. I would leave that decision to a committer.
Hayato,
does this strategy sound good to you?
Thanks,
Virender
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jonathan Gonzalez V. | 2026-11-03 11:17:40 | Re: Avoid duplicate file references in backend .pot file |
| Previous Message | Michael Paquier | 2026-11-03 10:56:51 | Re: Assertion failure when importing expression statistics with nested JSON values |