Re: psql output change in 9.4 - Mailing list pgsql-hackers

From Robert Haas
Subject Re: psql output change in 9.4
Date
Msg-id CA+TgmoYTj2zWoC=aSQFDKGsCi2gfezfdhkakxtzXEt85vUnJ+w@mail.gmail.com
Whole thread Raw
In response to Re: psql output change in 9.4  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: psql output change in 9.4
List pgsql-hackers
On Mon, Aug 11, 2014 at 1:52 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Robert Haas <robertmhaas@gmail.com> writes:
>> On Fri, Aug 8, 2014 at 9:34 PM, Peter Eisentraut <peter_e@gmx.net> wrote:
>>> What is the point of that change?
>
>> I think the output could justly be criticized for making it
>> insufficiently clear that the parenthesized text is, in fact, the name
>> of the pset parameter.
>
> Quite; that wasn't apparent to me either.
>
>> We could write something like:
>> Border style (parameter "border") is 1.
>
> How about
>
> Border style (\pset border) is 1.

That would look just fine as a response to \a or \x, but I'm not sure
it would look as good as a response to \pset, which prints out that
line for every parameter ("why does every line say \pset when the
command I just typed is \pset?").  However, I can certainly live with
it if others prefer that to what I suggested.

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



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: bad estimation together with large work_mem generates terrible slow hash joins
Next
From: Robert Haas
Date:
Subject: Re: jsonb format is pessimal for toast compression