From: Cat <cat@zip.com.au>
To: Stephen Frost <sfrost@snowman.net>
Cc: David G. Johnston <david.g.johnston@gmail.com>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: D'Arcy Cain <darcy@druid.net>
Cc: pgsql-hackers@postgresql.org <pgsql-hackers@postgresql.org>
Subject: Re: One-shot expanded output in psql using \G
Date: Sun, 29 Jan 2017 09:20:01 +1100
Message-ID: <20170128222000.mnliffc3pwebz63j@zip.com.au> (raw)
In-Reply-To: <20170127160305.GH9812@tamriel.snowman.net>
References: <8b8068d9-b218-06c6-6b98-8d7f1a365449@druid.net>
<20170127152609.hsjdr5cetlxm47ke@alvherre.pgsql>
<20170127153116.GF9812@tamriel.snowman.net>
<CAKFQuwY7s9RAFy-05KH=ngQy-RYPfcWSuJBESkheTF0VFaw4yA@mail.gmail.com>
<20170127160305.GH9812@tamriel.snowman.net>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
On Fri, Jan 27, 2017 at 11:03:05AM -0500, Stephen Frost wrote:
> Well, I did get the impression that you weren't thinking about that,
> which is actually kind of surpirsing to me. Lots of things work on "the
> current query buffer", which is the last query (successful or not, to be
> clear..):
>
> \crosstabview
> \e
> \g
> \gexec
> \gset
> \p
> \w
> \watch
>
> It's not entirely clear to me why the docs sometimes say "current query
> buffer" and somtimes say "current query input buffer".
I would expect the "current query input buffer" to be what is used to
enter the next query. When you hit enter that goes into the "current query
buffer" (as the entered query is now officially complete and thus becomes
the current query) and then "current query input buffer" is cleared for
the next action to be dealt with, be it a query or psql command.
--
"A search of his car uncovered pornography, a homemade sex aid, women's
stockings and a Jack Russell terrier."
- http://www.dailytelegraph.com.au/news/wacky/indeed/story-e6frev20-1111118083480
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
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: cat@zip.com.au, sfrost@snowman.net, david.g.johnston@gmail.com, alvherre@2ndquadrant.com, darcy@druid.net
Subject: Re: One-shot expanded output in psql using \G
In-Reply-To: <20170128222000.mnliffc3pwebz63j@zip.com.au>
* 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