Re: Psql meta-command conninfo+ - Mailing list pgsql-hackers

From David G. Johnston
Subject Re: Psql meta-command conninfo+
Date
Msg-id CAKFQuwaCQsTkCmbpZ_e7umZzqsPut1Q53hBNgWPP=Zw1EKmuEw@mail.gmail.com
Whole thread Raw
In response to Re: Psql meta-command conninfo+  (Sami Imseih <samimseih@gmail.com>)
Responses Re: Psql meta-command conninfo+
List pgsql-hackers
On Thu, Jan 9, 2025 at 12:28 PM Sami Imseih <samimseih@gmail.com> wrote:
> v35 seems fine to me from a UI standpoint; I suggest we move forward
> with that.

I am also OK with moving forward with a single \conninfo+, but
I think we should include all parameters in [1] as part of the output.
These are the parameters the server reports back to the client. I think
they are all useful to report in this command.
 
I dislike totally discarding the category information we have available to us.  How about making a long output with just three columns in non-expanded mode.  Setting, Value, Category ?

This also makes the non-expanded output, the default, the readable one.

David J.

pgsql-hackers by date:

Previous
From: Sami Imseih
Date:
Subject: Re: Psql meta-command conninfo+
Next
From: Alvaro Herrera
Date:
Subject: Re: why there is not VACUUM FULL CONCURRENTLY?