Horton

Re: 15beta1 tab completion of extension versions

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Noah Misch <noah@leadboat.com>
Cc: Jeff Janes <jeff.janes@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2022-07-03T19:28:15Z
Lists: pgsql-hackers 
Noah Misch <noah@leadboat.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

Commits

  1. Simplify tab completion of extension versions, redux.

  2. Simplify tab completion of extension versions.

  3. Fix busted tab completion of extension versions.

  4. psql: improve tab-complete's handling of variant SQL names.