Re: One-shot expanded output in psql using \gx

From: Christoph Berg <christoph(dot)berg(at)credativ(dot)de>
To: David Fetter <david(at)fetter(dot)org>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: One-shot expanded output in psql using \gx
Date: 2017-02-09 10:12:00
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

Re: David Fetter 2017-02-08 <20170208151214(dot)GA8118(at)fetter(dot)org>
> Would you be open to saving the next person some work by doing
> something similar to how \d is done, namely looking for an 'x'
> modifier after g without regard to how far after? As of this writing,
> the \d version starts at line 398 in master.

I think that ship has sailed, given there's already \gset.
Supporting \g[optionset] next to it *now*, given no one knows how
"optionset" is going to evolve seems like premature optimization.

Mit freundlichen Grüßen,
Christoph Berg
Senior Berater, Tel.: +49 2166 9901 187
credativ GmbH, HRB Mönchengladbach 12080, USt-ID-Nummer: DE204566209
Trompeterallee 108, 41189 Mönchengladbach
Geschäftsführung: Dr. Michael Meskes, Jörg Folz, Sascha Heuer
pgp fingerprint: 5C48 FE61 57F4 9179 5970 87C6 4C5A 6BAB 12D2 A7AE

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2017-02-09 10:34:19 Re: Parallel Index Scans
Previous Message Antonin Houska 2017-02-09 09:45:56 Re: pg_bsd_indent: implement -lps ("leave preprocessor space")