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

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: D'Arcy Cain <darcy(at)druid(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: One-shot expanded output in psql using \G
Date: 2017-01-27 16:05:44
Message-ID: 20170127160544.GI9812@tamriel.snowman.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

* Alvaro Herrera (alvherre(at)2ndquadrant(dot)com) wrote:
> Stephen Frost wrote:
> > * Alvaro Herrera (alvherre(at)2ndquadrant(dot)com) wrote:
>
> > > 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
>
> 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. ;)

Thanks!;

Stephen;

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2017-01-27 16:34:54 Re: pg_ls_dir & friends still have a hard-coded superuser check
Previous Message Tom Lane 2017-01-27 16:04:57 Re: Performance improvement for joins where outer side is unique