| From: | Hüseyin Demir <huseyin(dot)d3r(at)gmail(dot)com> |
|---|---|
| To: | Peter Smith <smithpb2250(at)gmail(dot)com> |
| Cc: | "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: PSQL - improve tab completion for pub/sub options |
| Date: | 2026-08-12 16:20:04 |
| Message-ID: | CAB5wL7bz_7_R0VmsKi+wtHMbkJ0UFAtu-4x8zbjGcYwYWUz+CA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> --> but MatchAnyN is not compatible with HeadMatches
> --> need to use Matches
> --> but Matches cannot work, because logic needs needs HeadMatches
> ;-(
>
> ~~
>
> I've experimented with other things like:
>
> else if (Matches("CREATE", "PUBLICATION", MatchAny, MatchAnyN, "WITH", "(*") ||
> Matches("CREATE", "PUBLICATION", MatchAny, MatchAnyN, "WITH", "(", MatchAnyN))
>
> ... but, apparently the Matches() logic only recognizes the first MatchAnyN.
>
> To cut a long story short, the only approach that I found that works
> was the `seen_with` scan.
Thank you for shedding light on this.
v4 LGTM. If no barring objections marked this patch as ready for committer.
Regards,
Demir.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2026-08-12 16:21:36 | Re: RI fast path gets cross-type foreign keys wrong |
| Previous Message | Tom Lane | 2026-08-12 16:16:20 | Re: Disallow outer-level and WHERE-clause aggregates in GRAPH_TABLE |