| From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
|---|---|
| To: | Maiquel Grassi <grassi(at)hotmail(dot)com(dot)br>, "Imseih (AWS), Sami" <simseih(at)amazon(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Cc: | Nathan Bossart <nathandbossart(at)gmail(dot)com>, Jim Jones <jim(dot)jones(at)uni-muenster(dot)de>, Pavel Luzanov <p(dot)luzanov(at)postgrespro(dot)ru>, Erik Wienhold <ewie(at)ewie(dot)name>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Psql meta-command conninfo+ |
| Date: | 2024-04-04 15:19:53 |
| Message-ID: | f4fc729d-7903-4d58-995d-6cd146049992@eisentraut.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| 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?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Melanie Plageman | 2024-04-04 15:20:35 | Re: Streaming read-ready sequential scan code |
| Previous Message | Tom Lane | 2024-04-04 15:19:11 | Re: Building with musl in CI and the build farm |