Re: Suggestions for improving \conninfo output in v18

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Suggestions for improving \conninfo output in v18
Date: 2025-06-02 05:24:15
Message-ID: CAKFQuwasj8LyAg1VQ088fecb1ee8WfE-K2a7io380RB0+Tp67Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sunday, June 1, 2025, Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com> wrote:
>
> In v18, the "Protocol Version" column shown by \conninfo reports only
> the major version (e.g., 3). Wouldn't it be more helpful to show the full
> version (e.g., 3.2) using PQfullProtocolVersion()? Since support for
> protocol version 3.2 was introduced in v18, users may want to know
> exactly which version the current session is using.

This seems like a probable oversight that should be corrected.

>
> 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?

David J.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Paul Jungwirth 2025-06-02 05:24:44 SQL:2011 Application Time Update & Delete
Previous Message Bertrand Drouvot 2025-06-02 04:59:18 Re: Add AioUringCompletion in wait_event_names.txt and a safeguard in generate-wait_event_types.pl