| From: | Sho Ito <i(dot)sho(dot)0628(at)gmail(dot)com> |
|---|---|
| To: | pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | [PATCH v1] Fix tab completion for DROP INDEX CONCURRENTLY |
| Date: | 2026-10-19 03:02:17 |
| Message-ID: | CAG7L5+7KXgvJUGCGXzyQrt7UysC9iytaYzx-7YyQTFYXjHVTWQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
psql currently offers `CASCADE` after `DROP INDEX CONCURRENTLY
<index_name>`,
although the backend rejects that combination [1].
The attached patch limits completion to `RESTRICT` for concurrent index
drops. Ordinary `DROP INDEX` continues to offer both `CASCADE` and
`RESTRICT`.
Kind regards,
Sho Ito
--
＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝
*Sho Ito (Sean)*
E-mail: i(dot)sho(dot)0628(at)gmail(dot)com
LinkedIn: *https://www.linkedin.com/in/sho-ito-0628/
<https://www.linkedin.com/in/sho-ito-0628/>*
GitHub: https://github.com/sean0628/
＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝
| Attachment | Content-Type | Size |
|---|---|---|
| v1-0001-Fix-tab-completion-for-DROP-INDEX-CONCURRENTLY.patch | application/octet-stream | 1.0 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2026-10-19 03:25:30 | Re: Reduce logging during prepared transaction recovery |
| Previous Message | Zhijie Hou | 2026-10-19 02:52:26 | Re: Fix WITHOUT OVERLAPS multirange with location replication |