Re: Psql meta-command conninfo+

From: Sami Imseih <samimseih(at)gmail(dot)com>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Maiquel Grassi <grassi(at)hotmail(dot)com(dot)br>, Hunaid Sohail <hunaidpgml(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, 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>
Subject: Re: Psql meta-command conninfo+
Date: 2025-01-09 20:45:55
Message-ID: CAA5RZ0uF6yhEM=r5yz_5bHRssHxnQkfe38=+MrwTP+of1bV+YA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> 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 ?

We can probably make due without a category as
the name of the setting is informative enough, right?

If we go with the 3 column format, then we will just
have a bunch of repeated values for Category, which
looks cluttered, IMO.

Regards,

Sami

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Sami Imseih 2025-01-09 20:50:18 Re: Psql meta-command conninfo+
Previous Message Melanie Plageman 2025-01-09 20:42:54 Re: Adjusting hash join memory limit to handle batch explosion