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

From David G. Johnston
Subject Re: Psql meta-command conninfo+
Date
Msg-id CAKFQuwZNy9CE-A0frjhupV9dsr6BBiiOQch34z-opf=76FBt-w@mail.gmail.com
Whole thread Raw
In response to Re: Psql meta-command conninfo+  (Hunaid Sohail <hunaidpgml@gmail.com>)
List pgsql-hackers
On Sun, Oct 6, 2024 at 11:17 PM Hunaid Sohail <hunaidpgml@gmail.com> wrote:

PQpass - no need
 
I would include this as presence/absence.

I concur on all of the rest.
 

For PQparameterStatus, some parameters are already used.
server_version and application_name were already discussed and removed in v12 and v29 respectively. Do we need other parameters?

Ok, I'll need to go read the reasoning for why they are deemed unneeded and form an opinion one way or the other.

 
Within that framework having \conninfo[+[CSE][…]] be the command - printing out only the table specified would be the behavior (specifying no suffix letters prints all three) - would be an option.

3 separate tables without suffix?

Yes, the tables need headers specific to their categories.

I do like the idea of having 4 though, placing settings into their own.  Premised on having all or most of the available parameters being on the table.  If it only ends up being a few of them then keeping those in the status table makes sense.

David J.

pgsql-hackers by date:

Previous
From: Fujii Masao
Date:
Subject: Re: [BUG FIX]Connection fails with whitespace after keepalives parameter value
Next
From: Tom Lane
Date:
Subject: Re: Converting tab-complete.c's else-if chain to a switch