From: David Fetter <david@fetter.org>
To: David G. Johnston <david.g.johnston@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Stephen Frost <sfrost@snowman.net>
Cc: Pavel Stehule <pavel.stehule@gmail.com>
Cc: Christoph Berg <christoph.berg@credativ.de>
Cc: Daniel Verite <daniel@manitou-mail.org>
Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Subject: Re: One-shot expanded output in psql using \G
Date: Mon, 30 Jan 2017 09:08:36 -0800
Message-ID: <20170130170836.GC24826@fetter.org> (raw)
In-Reply-To: <CAKFQuwasriva00vRe9f0TH9=FsVa5ejJDwuFaJF6rNwYrDw=ZA@mail.gmail.com>
References: <20170127132737.6skslelaf4txs6iw@msg.credativ.de>
<74e7fd23-f5a9-488d-a8c4-1e0da674b27c@manitou-mail.org>
<20170130101424.fo4knpn4blaohazk@msg.df7cb.de>
<20170130134608.GA9812@tamriel.snowman.net>
<CAFj8pRDLr=exBc4QZg7POLZcGHNi539ibhVqmGzWctyPo0TZ7A@mail.gmail.com>
<20170130150458.GC9812@tamriel.snowman.net>
<24326.1485789276@sss.pgh.pa.us>
<CAKFQuwasriva00vRe9f0TH9=FsVa5ejJDwuFaJF6rNwYrDw=ZA@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
On Mon, Jan 30, 2017 at 08:22:40AM -0700, David G. Johnston wrote:
> On Mon, Jan 30, 2017 at 8:14 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> > Stephen Frost <sfrost@snowman.net> writes:
> > > This particular bike-shedding really doesn't seem to be terribly useful
> > > or sensible, to me. \gx isn't "consistent" or "descriptive", frankly.
> >
> > Why not? To me it reads as "\g with an x option". The "x" refers to
> > the implied "\x", so it's not an arbitrary choice at all.
> >
> > The main problem I see with \G is that it's a dead end. If somebody
> > comes along next year and says "I'd like a variant of \g with some other
> > frammish", what will we do? There are no more case variants to use.
> >
> > In short, really the direction this ought to go in is \g[options] [file]
> > which is perfectly consistent with precedents in psql such as \d.
> > But there isn't any place where we've decided that upper case means
> > a variant of a lower case command.
> >
>
> +1
+1 from me, too, for what it's worth.
If we're expanding the meanings of \g, let's do it with at least some
eye to future expansions.
Best,
David.
--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: david(dot)fetter(at)gmail(dot)com
Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate
--
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: david@fetter.org, david.g.johnston@gmail.com, tgl@sss.pgh.pa.us, sfrost@snowman.net, pavel.stehule@gmail.com, christoph.berg@credativ.de, daniel@manitou-mail.org
Subject: Re: One-shot expanded output in psql using \G
In-Reply-To: <20170130170836.GC24826@fetter.org>
* 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