Re: One-shot expanded output in psql using \G
Stephen Frost <sfrost@snowman.net>
From: Stephen Frost <sfrost@snowman.net>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: D'Arcy Cain <darcy@druid.net>, pgsql-hackers@postgresql.org
Date: 2017-01-27T15:31:16Z
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
* Alvaro Herrera (alvherre@2ndquadrant.com) wrote: > D'Arcy Cain wrote: > > > I am a pretty heavy user of psql but I don't think that that would be so > > helpful. I assume you mean a new option, let's call it "\X" the causes the > > next query to be expanded. I type "\X" then a query. I realize that I made > > a mistake and have to redo the query so I have to type "\X" again. If I > > forget then I have to run the query yet again. > > I think the suggestion is that \G replaces \g (which is the same thing > as the semicolon). So you would do this: > > SELECT * FROM table WHERE table_status = 1; % get a short list; normal output > SELECT * FROM table WHERE table_id = 123 \G % drill down to one ID 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 Thanks! Stephen