From 05e88529175287ef91947ff8ab3b7121371d5b27 Mon Sep 17 00:00:00 2001 From: Sho Ito Date: Mon, 19 Oct 2026 11:55:27 +0900 Subject: [PATCH v1] Fix tab completion for DROP INDEX CONCURRENTLY The backend rejects CASCADE with DROP INDEX CONCURRENTLY, but psql offers it as a completion. Offer only RESTRICT for concurrent index drops, retaining both choices for ordinary DROP INDEX. --- src/bin/psql/tab-complete.in.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/bin/psql/tab-complete.in.c b/src/bin/psql/tab-complete.in.c index f86684e..a43034a 100644 --- a/src/bin/psql/tab-complete.in.c +++ b/src/bin/psql/tab-complete.in.c @@ -4350,7 +4350,7 @@ match_previous_words(int pattern_id, else if (Matches("DROP", "INDEX", MatchAny)) COMPLETE_WITH("CASCADE", "RESTRICT"); else if (Matches("DROP", "INDEX", "CONCURRENTLY", MatchAny)) - COMPLETE_WITH("CASCADE", "RESTRICT"); + COMPLETE_WITH("RESTRICT"); /* DROP MATERIALIZED VIEW */ else if (Matches("DROP", "MATERIALIZED")) -- 2.50.1 (Apple Git-155)