From: Tom Lane <tgl@sss.pgh.pa.us>
To: 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 10:49:17 -0500
Message-ID: <4587.1485791357@sss.pgh.pa.us> (raw)
In-Reply-To: <20170130153532.GE9812@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>
<24326.1485789276@sss.pgh.pa.us>
<20170130153532.GE9812@tamriel.snowman.net>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
Stephen Frost <sfrost@snowman.net> writes:
> * Tom Lane (tgl@sss.pgh.pa.us) wrote:
>> 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.
> That's not how '\dx' works, as I pointed out, so I don't see having the
> second character being 'x' to imply "\x mode" makes sense.
It is how \d[tisv] works, or the S or + modifiers to \d. If you don't
like the "x" in particular, feel free to propose a different letter that
makes more sense to you --- but I'm pretty convinced that this ought to
be seen as \g-plus-a-modifier.
>> 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.
> I don't believe there's any reason to think someone else couldn't come
> along later and add \gq for whatever they want. Simply because we use
> \G for something doesn't mean \g can't ever be further extended.
So at some point we'd be documenting \G as a legacy mysql-compatible
spelling of \gx, because it would become blindingly obvious that it was
a non-orthogonal wart. Let's just skip that phase and get to the
extensible syntax.
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
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: 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: <4587.1485791357@sss.pgh.pa.us>
* 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