From f2edf5dd00d174c7b1396f0a777375368a26c752 Mon Sep 17 00:00:00 2001 From: Fujii Masao Date: Thu, 22 Oct 2026 10:49:40 +0900 Subject: [PATCH] psql: Fix tab completion for DROP INDEX CONCURRENTLY psql offered CASCADE after DROP INDEX CONCURRENTLY and an index name, even though CASCADE is not supported with CONCURRENTLY. Offer only RESTRICT in this case, while retaining both CASCADE and RESTRICT for ordinary DROP INDEX. Backpatch to all supported versions. Author: Sho Ito Reviewed-by: Chao Li Reviewed-by: Shihao Zhong Reviewed-by: Fujii Masao Discussion: https://postgr.es/m/CAG7L5+7KXgvJUGCGXzyQrt7UysC9iytaYzx-7YyQTFYXjHVTWQ@mail.gmail.com Backpatch-through: 14 --- 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 f86684edc08..a43034aa29b 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"))