| From: | Álvaro Herrera <alvherre(at)kurilemu(dot)de> |
|---|---|
| To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
| Cc: | Baji Shaik <baji(dot)pgdev(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: [PATCH] Fix psql tab completion for REPACK boolean options |
| Date: | 2026-05-13 12:41:13 |
| Message-ID: | agRwcVpUe_bJlHd7@alvherre.pgsql |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2026-May-13, Fujii Masao wrote:
> On Tue, May 12, 2026 at 4:45 AM Baji Shaik <baji(dot)pgdev(at)gmail(dot)com> wrote:
> > The fix is to use pipe-separated alternatives (matching any one of
> > the keywords), consistent with how VACUUM handles the same pattern:
> >
> > TailMatches("ANALYZE|CONCURRENTLY|VERBOSE")
> >
> > Patch attached.
>
> Thanks for the patch! It looks good to me.
> Unless there are objections, I will commit it.
Yeah, looks good to me, thanks.
> BTW, I found that the boolean options for CLUSTER and REINDEX have
> the same issue, i.e., tab completion does not suggest boolean values
> such as ON and OFF. However, this has existed for a while, and adding
> those completions seems more like an improvement than a bug fix,
> so it should probably be handled separately during v20 development.
Fine with me. I wouldn't have a problem saying it's a backpatchable
bugfix, but it's certainly not very high priority or criticality.
--
Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Álvaro Herrera | 2026-05-13 12:50:09 | Re: [PATCH] Fix errhint messages for REPACK (CONCURRENTLY) restrictions |
| Previous Message | Amit Kapila | 2026-05-13 12:34:17 | Re: Adding REPACK [concurrently] |