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

Stephen Frost <sfrost@snowman.net>

From: Stephen Frost <sfrost@snowman.net>

To: Christoph Berg <christoph.berg@credativ.de>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>

Date: 2017-01-27T13:52:54Z

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,

* Christoph Berg (christoph.berg@credativ.de) wrote:
> The same idea was discussed back in 2008. Back then the outcome was
> that "\x auto" was implemented, but I still think that \G is a useful
> feature to have on its own, and several people in the thread seem to
> have agreed back then.

+1 for my part.  I often run a query and then realize that I really
wanted \x output.

Thanks!

Stephen