From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Noah Misch <noah(at)leadboat(dot)com> |
Cc: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: 15beta1 tab completion of extension versions |
Date: | 2022-07-03 19:28:15 |
Message-ID: | 1299663.1656876495@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Noah Misch <noah(at)leadboat(dot)com> writes:
> On Sun, Jul 03, 2022 at 02:00:59PM -0400, Tom Lane wrote:
>> This will require one extra <TAB> when what you want is to update to
>> a specific version, but I doubt that that's going to bother anyone
>> very much. I don't want to try to resurrect the v14 behavior exactly
>> because it's too much of a mess from a quoting standpoint.
> Works for me, and I agree the patch implements that successfully. "ALTER
> EXTENSION x UPDATE;" is an infrequent command, and "ALTER EXTENSION x UPDATE
> TO ..." is even less frequent. It's not worth much special effort to shave
> <TAB> steps.
Done that way then. Thanks for the report.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Jehan-Guillaume de Rorthais | 2022-07-03 20:12:13 | Re: Fix proposal for comparaison bugs in PostgreSQL::Version |
Previous Message | Tom Lane | 2022-07-03 19:14:09 | Re: automatically generating node support functions |