| From: | Baji Shaik <baji(dot)pgdev(at)gmail(dot)com> |
|---|---|
| To: | Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: two small tab-completion patches (ALTER CONSTRAINT, CHECK modifiers) |
| Date: | 2026-10-20 01:11:11 |
| Message-ID: | CA+fm-ROd0SP_7V+3Bmg-AzUOdjpVVkjs_Cm0V544JzkcTh8=Lw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Oct 19, 2026 at 6:33 PM Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com> wrote:
>
>
> > On Oct 6, 2026, at 05:24, Baji Shaik <baji(dot)pgdev(at)gmail(dot)com> wrote:
>
> After NOT or NO, tab completion doesn’t suggest any further keywords. Here
> is an example from the same file for reference:
> ```
> /* ALTER STATISTICS <name> */
> else if (Matches("ALTER", "STATISTICS", MatchAny))
> COMPLETE_WITH("OWNER TO", "RENAME TO", "SET SCHEMA", "SET
> STATISTICS");
> /* ALTER STATISTICS <name> SET */
> else if (Matches("ALTER", "STATISTICS", MatchAny, "SET"))
> COMPLETE_WITH("SCHEMA", "STATISTICS");
> ```
>
> As you can see, besides suggesting SET SCHEMA and SET STATISTICS, there is
> a separate rule that matches SET and suggests SCHEMA and STATISTICS. I
> think we need similar rules for NOT and NO here. And 0001 has the same
> thing for INITIALLY.
>
ah, thank you so much for the review and guidance to fix, Chao. v2
attached.
Let me know if it still misses anything.
Thanks,
Baji Shaik.
| Attachment | Content-Type | Size |
|---|---|---|
| v2-0001-psql-Add-tab-completion-for-ALTER-TABLE-ALTER-CONSTR.patch | application/octet-stream | 2.2 KB |
| v2-0001-psql-Add-tab-completion-for-CHECK-constraint-modifie.patch | application/octet-stream | 2.1 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | shihao zhong | 2026-10-20 01:25:50 | Re: [PG19] Promotion hangs behind a backend blocked on a stuck client |
| Previous Message | Chao Li | 2026-10-20 01:09:53 | Re: [PATCH] Fix typos in comments |