Re: [HACKERS] One-shot expanded output in psql using \G - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: [HACKERS] One-shot expanded output in psql using \G
Date
Msg-id 20170127152609.hsjdr5cetlxm47ke@alvherre.pgsql
Whole thread Raw
In response to Re: [HACKERS] One-shot expanded output in psql using \G  (D'Arcy Cain <darcy@druid.net>)
Responses Re: [HACKERS] One-shot expanded output in psql using \G  (Stephen Frost <sfrost@snowman.net>)
List pgsql-hackers
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

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: D'Arcy Cain
Date:
Subject: Re: [HACKERS] One-shot expanded output in psql using \G
Next
From: Stephen Frost
Date:
Subject: Re: [HACKERS] One-shot expanded output in psql using \G