Raise error on concurrent drop of partitioned index
Alvaro Herrera <alvherre@alvh.no-ip.org>
Raise error on concurrent drop of partitioned index We were already raising an error for DROP INDEX CONCURRENTLY on a partitioned table, albeit a different and confusing one: ERROR: DROP INDEX CONCURRENTLY must be first action in transaction Change that to throw a more comprehensible error: ERROR: cannot drop partitioned index \"%s\" concurrently Michael Paquier authored the test case for indexes on temporary partitioned tables. Backpatch to 11, where indexes on partitioned tables were added. Reported-by: Jan Mussler <jan.mussler@zalando.de> Reviewed-by: Michael Paquier <michael@paquier.xyz> Discussion: https://postgr.es/m/16594-d2956ca909585067@postgresql.org
Files
| Path | Change | +/− |
|---|---|---|
| doc/src/sgml/ref/drop_index.sgml | modified | +2 −0 |
| src/backend/commands/tablecmds.c | modified | +11 −0 |
| src/test/regress/expected/indexing.out | modified | +20 −0 |
| src/test/regress/sql/indexing.sql | modified | +13 −0 |
Documentation touched
Discussion
- BUG #16594: DROP INDEX CONCURRENTLY fails on partitioned table with a non helpful error message. 13 messages · 2020-08-26 → 2020-09-01