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: pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: [PATCH v1] Fix tab completion for DROP INDEX CONCURRENTLY
Date: 2026-10-19 03:42:35
Message-ID: CAHGQGwEE-N782ph1OsbQNVfCJ7sCNNpaNaMXWJkasmzB-VxUEA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Oct 19, 2026 at 12:03 PM Sho Ito <i(dot)sho(dot)0628(at)gmail(dot)com> wrote:
> The attached patch limits completion to `RESTRICT` for concurrent index
> drops. Ordinary `DROP INDEX` continues to offer both `CASCADE` and `RESTRICT`.

Thanks for the patch! LGTM.

This patch should be backpatched to all supported versions?

Regards,

--
Fujii Masao

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message shihao zhong 2026-10-19 03:55:36 Re: [PATCH] Corruption Issue: Fix missing tts_tid in ExecForceStoreHeapTuple
Previous Message shveta malik 2026-10-19 03:42:05 Re: Proposal: Conflict log history table for Logical Replication