Re: Fix doc about pg_get_multixact_stats()

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>
Cc: Yingying Chen <cyy9255(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Fix doc about pg_get_multixact_stats()
Date: 2026-06-25 23:41:39
Message-ID: aj28s7x9MofQ2pBl@paquier.xyz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Jun 26, 2026 at 07:15:37AM +0800, Chao Li wrote:
> From the implementation, for unprivileged (not super user and not
> pg_read_all_stats role) users, pg_get_multixact_stats doesn't raise
> an error, but just returns all NULL values. The current statement
> doesn't seem to explain that behavior clearly.
>
> How about rephrasing it like this?
> ```
> <para>
> Only superusers and roles with privileges of the
> <literal>pg_read_all_stats</literal> role can see details; other users
> receive null values.
> </para></entry>
> ```

Yeah, that looks like an improvement over the statu-quo. I was
looking for something similar but we don't have many functions hidden
behind a role privilege.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Smith 2026-06-25 23:53:12 Re: Support EXCEPT for ALL SEQUENCES publications
Previous Message feng wu 2026-06-25 23:24:32 Re: [PATCH] Check dead heap items before marking them unused