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

From Stephen Frost
Subject Re: [HACKERS] One-shot expanded output in psql using \G
Date
Msg-id 20170127160544.GI9812@tamriel.snowman.net
Whole thread Raw
In response to Re: [HACKERS] One-shot expanded output in psql using \G  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: [HACKERS] One-shot expanded output in psql using \G  (Christoph Berg <christoph.berg@credativ.de>)
List pgsql-hackers
* Alvaro Herrera (alvherre@2ndquadrant.com) wrote:
> Stephen Frost wrote:
> > * Alvaro Herrera (alvherre@2ndquadrant.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;

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] Performance improvement for joins where outer side is unique
Next
From: Stephen Frost
Date:
Subject: Re: [HACKERS] pg_ls_dir & friends still have a hard-coded superusercheck