pg-sprite currently refuses any plan that builds an index on a partitioned parent (see docs/limitations.md): PostgreSQL cannot run CREATE INDEX CONCURRENTLY at the parent level, and pg-sprite refuses the blocking form by policy because it takes ACCESS EXCLUSIVE.
The safe flow exists and is planned: CREATE INDEX ON ONLY parent → per-partition CREATE INDEX CONCURRENTLY → ALTER INDEX ... ATTACH PARTITION, with crash-resume across the per-partition builds and a final validity check on the parent index. This issue tracks building that flow.
Until it lands, the engine refuses with typed causes parent-concurrent-index-build / parent-blocking-index-build rather than failing mid-change.
pg-sprite currently refuses any plan that builds an index on a partitioned parent (see docs/limitations.md): PostgreSQL cannot run
CREATE INDEX CONCURRENTLYat the parent level, and pg-sprite refuses the blocking form by policy because it takesACCESS EXCLUSIVE.The safe flow exists and is planned:
CREATE INDEX ON ONLY parent→ per-partitionCREATE INDEX CONCURRENTLY→ALTER INDEX ... ATTACH PARTITION, with crash-resume across the per-partition builds and a final validity check on the parent index. This issue tracks building that flow.Until it lands, the engine refuses with typed causes
parent-concurrent-index-build/parent-blocking-index-buildrather than failing mid-change.