Files
multica/server/migrations/135_comment_workspace_index.down.sql
Multica Eve 75e8bd5b64 fix: make release index migrations concurrent (#4995)
Co-authored-by: Eve <eve@multica-ai.local>
Co-authored-by: multica-agent <github@multica.ai>
2026-07-06 19:06:53 +08:00

9 lines
450 B
SQL

-- Drop the comment.workspace_id supporting btree index (MUL-4059).
-- The search handler's WHERE clause will still work without it — the
-- planner will just fall back to a Seq Scan on `comment` filtered by
-- workspace_id, which is the pre-migration-135 behavior. Only run this
-- down migration if operating below the query-rewrite change; otherwise
-- expect search latency to regress.
DROP INDEX CONCURRENTLY IF EXISTS idx_comment_workspace;