| From: | "Daniel Verite" <daniel(at)manitou-mail(dot)org> |
|---|---|
| To: | "Christoph Berg" <christoph(dot)berg(at)credativ(dot)de> |
| Cc: | "PostgreSQL Hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: One-shot expanded output in psql using \G |
| Date: | 2017-01-28 17:42:49 |
| Message-ID: | 74e7fd23-f5a9-488d-a8c4-1e0da674b27c@manitou-mail.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Christoph Berg wrote:
> A workaround is to submit queries using "\x\g\x", but that's ugly,
> clutters the output with toggle messages, and will forget that "\x
> auto" was set.
>
> Mysql's CLI client is using \G for this purpose, and adding the very
> same functionality to psql fits nicely into the set of existing
> backslash commands: \g sends the query buffer, \G will do exactly the
> same as \g (including parameters), but forces expanded output just for
> this query.
+1 for the functionality but should we choose to ignore the comparison
to mysql, I'd suggest \gx for the name.
Best regards,
--
Daniel Vérité
PostgreSQL-powered mailer: http://www.manitou-mail.org
Twitter: @DanielVerite
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Corey Huinker | 2017-01-28 17:46:05 | Re: \if, \elseif, \else, \endif (was Re: PSQL commands: \quit_if, \quit_unless) |
| Previous Message | Pavel Stehule | 2017-01-28 17:14:26 | Re: proposal: EXPLAIN ANALYZE formatting |