Re: [PATCH v1] Fix tab completion for DROP INDEX CONCURRENTLY

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Sho Ito <i(dot)sho(dot)0628(at)gmail(dot)com>
Cc: shihao zhong <zhong950419(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: [PATCH v1] Fix tab completion for DROP INDEX CONCURRENTLY
Date: 2026-10-21 07:15:34
Message-ID: CAHGQGwHhhidGfLC5Dn+0U_AUJB-=hQy9g1xoMEnDwKT13dZ8bg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Oct 21, 2026 at 2:12 PM Sho Ito <i(dot)sho(dot)0628(at)gmail(dot)com> wrote:
> Agreed. Since `RESTRICT` is the default, there is little benefit in offering
> it here.

We already offer completion for optional clauses that make the default explicit,
such as WITH after REFRESH MATERIALIZED VIEW CONCURRENTLY <name>.
So I think v1 is fine too.

Regards,

--
Fujii Masao

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Yilin Zhang 2026-10-21 07:16:50 Re: [PATCH] pageinspect: validate line pointers before using them
Previous Message Takeshi Ideriha 2026-10-21 06:52:40 Re: [PATCH] reindexdb: Fix schema name lookup in parallel mode