Horton

Re: Psql meta-command conninfo+

Peter Eisentraut <peter@eisentraut.org>

View thread View on postgr.es
From: Peter Eisentraut <peter@eisentraut.org>
To: Maiquel Grassi <grassi@hotmail.com.br>, "Imseih (AWS), Sami" <simseih@amazon.com>, Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: Nathan Bossart <nathandbossart@gmail.com>, Jim Jones <jim.jones@uni-muenster.de>, Pavel Luzanov <p.luzanov@postgrespro.ru>, Erik Wienhold <ewie@ewie.name>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2024-04-04T15:19:53Z
Lists: pgsql-hackers 
The existing \conninfo command gets its values from libpq APIs.  You are 
changing all of this to make a server query, which is a totally 
different thing.  If we wanted to take a change like this, I don't think 
it should be reusing the \conninfo command.

But I don't really see the point of this.  The information you are 
querying is already available in various system views.  This proposal is 
just a shorthand for a collection of various random things some people 
like to see.  Like, by what reason is application name included as 
connection info?  Why not any other session settings?  What about 
long-term maintenance: By what logic should things be added to this?

Commits

  1. psql: Change new \conninfo to use SSL instead of TLS

  2. Change \conninfo to use tabular format

  3. Update extension lookup routines to use the syscache

  4. Improve COPY TO performance when server and client encodings match

  5. doc: Remove superfluous bracket in synopsis

  6. Remove psql support for server versions preceding 9.2.