pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
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:14:36 -0500
Message-ID: <24326.1485789276@sss.pgh.pa.us> (raw)
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>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>

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



view thread (45+ messages)  latest in thread

Message-ID: <24326.1485789276@sss.pgh.pa.us>
Permalink:  ../24326.1485789276@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/24326.1485789276@sss.pgh.pa.us

 · 

reply
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: <24326.1485789276@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