From: Tom Lane <tgl@sss.pgh.pa.us>
To: Stephen Frost <sfrost@snowman.net>
cc: Pavel Stehule <pavel.stehule@gmail.com>,
        Christoph Berg <christoph.berg@credativ.de>,
        Daniel Verite <daniel@manitou-mail.org>,
        PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Subject: Re: One-shot expanded output in psql using \G
In-reply-to: <20170130150458.GC9812@tamriel.snowman.net>
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>
Comments: In-reply-to Stephen Frost <sfrost@snowman.net>
	message dated "Mon, 30 Jan 2017 10:04:59 -0500"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <24325.1485789276.1@sss.pgh.pa.us>
Date: Mon, 30 Jan 2017 10:14:36 -0500
Message-ID: <24326.1485789276@sss.pgh.pa.us>
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org

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.

			regards, tom lane


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers