Re: Psql meta-command conninfo+

From: Hunaid Sohail <hunaidpgml(at)gmail(dot)com>
To: Maiquel Grassi <grassi(at)hotmail(dot)com(dot)br>
Cc: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Sami Imseih <samimseih(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Jim Jones <jim(dot)jones(at)uni-muenster(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Nathan Bossart <nathandbossart(at)gmail(dot)com>, "Imseih (AWS), Sami" <simseih(at)amazon(dot)com>, Peter Eisentraut <peter(at)eisentraut(dot)org>, Pavel Luzanov <p(dot)luzanov(at)postgrespro(dot)ru>, Erik Wienhold <ewie(at)ewie(dot)name>, Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>
Subject: Re: Psql meta-command conninfo+
Date: 2025-01-21 10:17:21
Message-ID: CAMWA6yZ=X=11ccJH86SDOOP-QCQp7Z3bHSWjJNOzxfnNF=OXYg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On Mon, Jan 20, 2025 at 6:34 PM Maiquel Grassi <grassi(at)hotmail(dot)com(dot)br>
wrote:

> >That leads me to also wonder why don't we change \conninfo to have this
> >tabular behavior instead of creating a separate command for it. Why do
> >we need to keep the existing form of \conninfo? To me it seems strictly
> >less useful, as it is harder to read.
>
> Here, you're suggesting that it would be useful to keep the \conninfo
> meta-command, improve it with a "new version," and display the returned
> content as a table instead of text. If that's the case, I think it's a
> good idea
> since it would show the "new settings" that the current version doesn't
> display and, yes, it would serve the same purpose as \conninfo+.
>

Sure, we can proceed with that. I do hope this will be the final one we try
:)

> Regarding which settings to display, the discussion tends to get very
> broad,
> and we can never settle on what should be shown definitively. I believe
> that, often, less is more, so showing only the essential settings would be
> enough.
>

In that case, we can collectively decide which parameters should be shown
in this command. My suggestion:
- application_name
- encodings (maybe?)
- role (new patch)
- is_superuser
- session_authorization
- in_hot_standby

Feel free to suggest any additions or removals.

Regards,
Hunaid Sohail

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Ashutosh Bapat 2025-01-21 10:44:53 Re: pgbench without dbname worked differently with psql and pg_dump
Previous Message Alexander Korotkov 2025-01-21 10:05:34 Re: table_tuple_lock's snapshot argument