From: Stephen Frost <sfrost@snowman.net>
To: Christoph Berg <christoph.berg@credativ.de>
To: Daniel Verite <daniel@manitou-mail.org>
To: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Subject: Re: One-shot expanded output in psql using \G
Date: Mon, 30 Jan 2017 08:46:08 -0500
Message-ID: <20170130134608.GA9812@tamriel.snowman.net> (raw)
In-Reply-To: <20170130101424.fo4knpn4blaohazk@msg.df7cb.de>
References: <20170127132737.6skslelaf4txs6iw@msg.credativ.de>
<74e7fd23-f5a9-488d-a8c4-1e0da674b27c@manitou-mail.org>
<20170130101424.fo4knpn4blaohazk@msg.df7cb.de>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
* Christoph Berg (christoph.berg@credativ.de) wrote:
> Re: Daniel Verite 2017-01-28 <74e7fd23-f5a9-488d-a8c4-1e0da674b27c@manitou-mail.org>
> > > Mysql's CLI client is using \G for this purpose, and adding the very
> > > same functionality to psql fits nicely into the set of existing
> > > backslash commands: \g sends the query buffer, \G will do exactly the
> > > same as \g (including parameters), but forces expanded output just for
> > > this query.
> >
> > +1 for the functionality but should we choose to ignore the comparison
> > to mysql, I'd suggest \gx for the name.
>
> IMHO \G is a tad easier to type than \gx, though the difference isn't
> huge, so I would be fine with either. But do we really want to choose
> something different just because MySQL is using it? \G will be much
> easier to explain to existing users (both people coming from MySQL to
> PostgreSQL, and PostgreSQL users doing a detour into foreign
> territory), and it would be one difference less to have to care about
> when typing on the CLIs.
>
> +1 on \G.
Agreed, +1 on \G and with the above argument- why in the world would we
want to avoid using \G just because MySQL uses it?
Thanks!
Stephen
Attachments:
signature.asc (application/pgp-signature, 818B) download
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: sfrost@snowman.net, christoph.berg@credativ.de, daniel@manitou-mail.org
Subject: Re: One-shot expanded output in psql using \G
In-Reply-To: <20170130134608.GA9812@tamriel.snowman.net>
* 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