From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Catalin Iacob <iacobcatalin(at)gmail(dot)com> |
Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com> |
Subject: | Re: prokind column (was Re: [HACKERS] SQL procedures) |
Date: | 2018-02-27 16:50:31 |
Message-ID: | 30721.1519750231@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Catalin Iacob <iacobcatalin(at)gmail(dot)com> writes:
> On Tue, Feb 27, 2018 at 4:03 AM, Michael Paquier <michael(at)paquier(dot)xyz> wrote:
>> I would just recommend users to use a version of psql matching
>> the one of the server instead of putting an extra load of maintenance
>> into psql for years to come
> Breaking tab completion in new psql against old servers might be
> acceptable as it's a fringe feature, but I don't think your
> recommendation of matching versions is practical. Lots of people
> manage multiple server versions and using the latest psql for all of
> them is currently, as far as I know, a perfectly supported way of
> doing that, getting new psql features and keeping compatibility. I
> think it would be a pity to loose that.
We support the various psql/describe.c features against old servers,
so it would be quite inconsistent for tab completion not to work
similarly. There are some gaps in that already, as per the other
thread, but we should clean those up not add more.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Andrey Borodin | 2018-02-27 16:51:29 | Re: Online enabling of checksums |
Previous Message | Greg Stark | 2018-02-27 16:50:24 | Re: jsonlog logging only some messages? |