Re: One-shot expanded output in psql using \G
Daniel Verite <daniel@manitou-mail.org>
From: "Daniel Verite" <daniel@manitou-mail.org>
To: "Christoph Berg" <christoph.berg@credativ.de>
Cc: "PostgreSQL Hackers" <pgsql-hackers@postgresql.org>
Date: 2017-01-28T17:42:49Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
psql: Fix \gx when FETCH_COUNT is used
- 0cdc3e47bea4 11.0 landed
- 51d0fa8ed93f 10.0 landed
-
psql: Add \gx command
- b2678efd43f1 10.0 landed
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