Re: One-shot expanded output in psql using \G
Christoph Berg <christoph.berg@credativ.de>
From: Christoph Berg <christoph.berg@credativ.de>
To: Stephen Frost <sfrost@snowman.net>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>, D'Arcy Cain <darcy@druid.net>, pgsql-hackers@postgresql.org
Date: 2017-01-27T18:05:51Z
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
Re: Stephen Frost 2017-01-27 <20170127160544.GI9812@tamriel.snowman.net> > > > Uh, I figured it was more like \g, which just re-runs the last query.. > > > As in, you'd do: > > > > > > table pg_proc; % blargh, I can't read it like this > > > \G % ahh, much nicer > > > > Sure, that's exactly the same thing. (You can omit the query in either > > case which causes the previous query to be re-ran. \crosstabview, > > \gexec etc also work like that). > > Right, I agree it's the same thing, but (clearly), not everyone > discussing this realized that and, well, the \G-by-itself is a lot > easier for me, at least. I have a really hard time not ending things > with a semi-colon. ;) Heh, tbh even I as the patch other didn't realize that \G-by-itself just works, my intention was that it replaces the semicolon. :) So, to clarify, both ways work: select * from pg_class where relname = 'pg_class'; -- dang, much too wide, press <arrow-up> select * from pg_class where relname = 'pg_class' \G -- ah nice! select * from pg_class where relname = 'pg_class'; -- dang, much too wide \G -- ah nice! Christoph