pgsql: Add support for tab completion after ALTER EXTENSION ADD|DROP in

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Add support for tab completion after ALTER EXTENSION ADD|DROP in
Date: 2023-01-11 23:51:52
Message-ID: E1pFksq-003CI9-C0@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Add support for tab completion after ALTER EXTENSION ADD|DROP in psql

This appends the set of object types supported by these commands, and
the objects defined in the cluster are completed after that. Note that
these may not be in the extension being working on when using DROP, to
keep the code simple, but this is much more useful than the previous
behavior of not knowing the objects that can be touched.

Author: Vignesh C
Discussion: https://postgr.es/m/CALDaNm3LVM2QcUWqgOonKZH80TveT-tUthbw4ZhuE_6pD3yi-A@mail.gmail.com

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/2ff5ca86e816846743b31279a9f6b819d4cf4b11

Modified Files
--------------
src/bin/psql/tab-complete.c | 21 +++++++++++++++++++++
1 file changed, 21 insertions(+)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2023-01-12 00:41:21 pgsql: Get rid of the "new" and "old" entries in a view's rangetable.
Previous Message Peter Geoghegan 2023-01-11 23:32:49 Re: pgsql: Delay commit status checks until freezing executes.