Re: [PATCH] psql: Fix REPACK index completion after a column list

From: Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>
To: Sho Ito <i(dot)sho(dot)0628(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: [PATCH] psql: Fix REPACK index completion after a column list
Date: 2026-11-10 05:40:09
Message-ID: ABA90750-AED8-4CD6-BD73-2634783ED763@gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On Nov 10, 2026, at 11:38, Sho Ito <i(dot)sho(dot)0628(at)gmail(dot)com> wrote:
>
> Hi Chao,
>
> Thank you for reviewing.
>
> Since these two patches are closely related, I would suggest combining them into a single patch. I applied this patch first, but when I tried to apply the other one, I encountered a conflict. Combining them would make it easier for reviewers and committers to review and apply the changes.
>
> I've combined both fixes in the attached v2 code
> patch (0001), with the regression tests in a separate patch (0002).
> The code combines the two v1 fixes.
>
> I will withdraw Commitfest entry #7610 [1].
>
> [1] https://commitfest.postgresql.org/patch/7610/
> Thanks,
> Sho
>
> --
> =======================================
> Sho Ito (Sean)
>
> E-mail: i(dot)sho(dot)0628(at)gmail(dot)com
> LinkedIn: https://www.linkedin.com/in/sho-ito-0628/
> GitHub: https://github.com/sean0628/
> =======================================
> <v2-0002-psql-Add-regression-tests-for-REPACK-tab-completi.patch><v2-0001-psql-Fix-REPACK-tab-completion-around-USING-INDEX.patch>

Thanks for updating the patch. When testing v2, I found a problem:
```
evantest=# repack t (a)USING INDEX ;
ERROR: ANALYZE option must be specified when a column list is provided
```

After I typed in “(a)”, a tab typing auto filled in “USING INDEX”, but you can see the error. A column list is only allowed with ANALYZE specified. So,
```
Matches("REPACK", MatchAny, "(*)")
```

is questionable. It matches to above example.

Best regards,
--
Chao Li (Evan)
HighGo Software Co., Ltd.
https://www.highgo.com/

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2026-11-10 05:42:47 Re: BGWORKER_INTERRUPTIBLE workers are never restarted after DROP/ALTER/CREATE DATABASE
Previous Message João Rito 2026-11-10 05:33:37 Re: Standby stuck after walreceiver restart just before a WAL segment boundary