Re: [patch] A \pivot command for psql - Mailing list pgsql-hackers

From Robert Haas
Subject Re: [patch] A \pivot command for psql
Date
Msg-id CA+TgmoaOHGAU8Or86TLaZKXNoVCd90OBBTgK0rmdWFoEW3E58g@mail.gmail.com
Whole thread Raw
In response to Re: [patch] A \pivot command for psql  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [patch] A \pivot command for psql  (David Fetter <david@fetter.org>)
List pgsql-hackers
On Sun, Aug 9, 2015 at 8:18 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> psql is a minority API, you know.

Not for me.  psql has already got a bunch of bells and whistles to
format things in particular ways that people have wanted, and I'm not
really sure why the bar for this proposal should be any higher.  Is
this less useful than \pset linestype unicode, complete with trying to
auto-detect whether to enable the feature?  Than automatically
switching between expanded mode and regular mode based on the width of
the TTY?  I considered those features rather frivolous, but it seemed
to me that their inclusion was widely supported and that a number of
people were really quite happy about them.

I guess you could argue that those are inherently client-side features
and this is not, and I'll grant that point.  But a client-side feature
in 9.5 beats a server-side feature in 10.6 every day of the week.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Reducing ClogControlLock contention
Next
From: Ted Toth
Date:
Subject: RLS and LEAKPROOF functions