| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, David Fetter <david(at)fetter(dot)org>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [COMMITTERS] pgsql: Make psql's \set display variables in alphabetical order. |
| Date: | 2017-02-01 21:38:59 |
| Message-ID: | CA+TgmoaCf3g+FfO=aRrq9B_znkiHGvcVqSg7AweYxqA9E0NWMA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On Wed, Feb 1, 2017 at 1:08 PM, Andres Freund <andres(at)anarazel(dot)de> wrote:
> On 2017-02-01 12:59:36 -0500, Tom Lane wrote:
>> David Fetter <david(at)fetter(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Fetter | 2017-02-01 21:56:31 | Re: [COMMITTERS] pgsql: Make psql's \set display variables in alphabetical order. |
| Previous Message | Tom Lane | 2017-02-01 21:13:38 | pgsql: Provide CatalogTupleDelete() as a wrapper around simple_heap_del |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Nasby | 2017-02-01 21:45:24 | Re: PoC plpgsql - possibility to force custom or generic plan |
| Previous Message | Craig Ringer | 2017-02-01 21:35:42 | Re: logical decoding of two-phase transactions |