Re: Suggestions for improving \conninfo output in v18

On 2025/06/02 21:53, David G. Johnston wrote:
> On Sunday, June 1, 2025, Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com <mailto:masao(dot)fujii(at)oss(dot)nttdata(dot)com>> wrote:
>
> On 2025/06/02 14:24, David G. Johnston wrote:
>
> On Sunday, June 1, 2025, Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com <mailto:masao(dot)fujii(at)oss(dot)nttdata(dot)com> <mailto:masao(dot)fujii(at)oss(dot)nttdata(dot)com <mailto:masao(dot)fujii(at)oss(dot)nttdata(dot)com>>> wrote:
>
>     Also, I noticed that the "Client User" column reflects the user at
>     the time of connection, while the "Superuser" column reflects whether
>     the current user in the current execution context is a superuser.
>     This means the users referred to in these columns can differ.
>     It might be worth aligning this behavior, or at least noting the distinction
>     clearly in the documentation?
>
>
> The behavior seems consistent with the reality of our protocol and libpq.  What did you have in mind for documentation changes?
>
>
> How about adding a note like this?
>
> ----------------------
> Note that the "Superuser" column does not necessarily reflect the privileges of the user shown in "Client User". "Client User" shows the user at the time of connection, while "Superuser" indicates whether the current user (in the current execution context) has superuser privileges. These users are usually the same, but they can differ, for example, if the current user was changed with the SET ROLE command.
> ----------------------
>
>
> Where would you put that?

I was thinking to add a note to the \conninfo documentation, as shown
in the attached patch. I don't have a better alternative at the moment.

Regards,

--
Fujii Masao
NTT DATA Japan Corporation