From: Tom Lane <tgl@sss.pgh.pa.us>
To: Daniel Verite <daniel@manitou-mail.org>
Cc: Christoph Berg <christoph.berg@credativ.de>
Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Subject: Re: One-shot expanded output in psql using \G
Date: Mon, 30 Jan 2017 10:00:02 -0500
Message-ID: <23622.1485788402@sss.pgh.pa.us> (raw)
In-Reply-To: <7c9af633-cbaa-4288-8efa-15dcfdf7094b@manitou-mail.org>
References: <7c9af633-cbaa-4288-8efa-15dcfdf7094b@manitou-mail.org>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
"Daniel Verite" <daniel@manitou-mail.org> writes:
>> \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.
> That's a good argument, but if it's pitted against psql's
> consistency with itself, I'd expect the latter to win.
FWIW, \gx makes sense to me as well, particularly if we make it a
complete extension of \g and allow an optional target file name.
Does that functionality exist in mysql's \G ?
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, daniel@manitou-mail.org, christoph.berg@credativ.de
Subject: Re: One-shot expanded output in psql using \G
In-Reply-To: <23622.1485788402@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