Re: [HACKERS] [COMMITTERS] pgsql: Make psql's \set display variablesin alphabetical order. - Mailing list pgsql-hackers

From Robert Haas
Subject Re: [HACKERS] [COMMITTERS] pgsql: Make psql's \set display variablesin alphabetical order.
Date
Msg-id CA+TgmoaCf3g+FfO=aRrq9B_znkiHGvcVqSg7AweYxqA9E0NWMA@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] [COMMITTERS] pgsql: Make psql's \set display variablesin alphabetical order.  (Andres Freund <andres@anarazel.de>)
Responses Re: [HACKERS] [COMMITTERS] pgsql: Make psql's \set display variablesin alphabetical order.  (David Fetter <david@fetter.org>)
List pgsql-hackers
On Wed, Feb 1, 2017 at 1:08 PM, Andres Freund <andres@anarazel.de> wrote:
> On 2017-02-01 12:59:36 -0500, Tom Lane wrote:
>> David Fetter <david@fetter.org> writes:
>> > On Wed, Feb 01, 2017 at 04:25:25PM +0000, Tom Lane wrote:
>> >> Make psql's \set display variables in alphabetical order.
>>
>> > This is a substantial usability improvement which nevertheless is hard
>> > to imagine changes things that scripts relied on. I think it's worth
>> > back-patching.
>>
>> I'm not that excited about it personally, but I agree it would be unlikely
>> to break anything.  Other votes?
>
> -0.5 - I see very little reason to backpatch this over dozes of other
> changes.

I'll vote -1. I don't think this is a bug fix.

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



pgsql-hackers by date:

Previous
From: Craig Ringer
Date:
Subject: Re: [HACKERS] logical decoding of two-phase transactions
Next
From: Jim Nasby
Date:
Subject: Re: [HACKERS] PoC plpgsql - possibility to force custom or generic plan