From: Stephen Frost <sfrost@snowman.net>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: D'Arcy Cain <darcy@druid.net>
Cc: pgsql-hackers@postgresql.org
Subject: Re: One-shot expanded output in psql using \G
Date: Fri, 27 Jan 2017 10:31:16 -0500
Message-ID: <20170127153116.GF9812@tamriel.snowman.net> (raw)
In-Reply-To: <20170127152609.hsjdr5cetlxm47ke@alvherre.pgsql>
References: <8b8068d9-b218-06c6-6b98-8d7f1a365449@druid.net>
<20170127152609.hsjdr5cetlxm47ke@alvherre.pgsql>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
* 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
Attachments:
signature.asc (application/pgp-signature, 818B) download
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: sfrost@snowman.net, alvherre@2ndquadrant.com, darcy@druid.net
Subject: Re: One-shot expanded output in psql using \G
In-Reply-To: <20170127153116.GF9812@tamriel.snowman.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox