aa4c504c78
position ranks an issue inside its own (workspace, status) column, but a status change carried the old column's value over unchanged. The value that put an issue on top of Todo is roughly zero, and lands it below every hand-dragged issue in Done — so agent-completed work sank into the middle of a long Done column and read as "the task disappeared". Re-rank to the top of the destination column on both status-write paths, reusing the MIN(position) - 1 policy new issues already get. An explicit position still wins, so cross-column drag-and-drop keeps the slot it dropped on, and a same-status write leaves position alone. The re-rank reads MIN(position) for the destination (workspace, status), which idx_issue_status could only serve with a heap fetch per issue in the column — paid on every completion against the column that grows without bound. Add (workspace_id, status, position) to make it an index-only min. Closes #7410 Co-authored-by: J <[email protected]> Co-authored-by: multica-agent <[email protected]>
Migration runner operations
Recover the comment content search index
Migration 371 keeps exactly one comment-content search index per environment:
idx_comment_content_bigm when pg_bigm is usable, otherwise the portable
idx_comment_content_trgm fallback. A conditionally skipped migration is still
recorded in schema_migrations, so rerunning migrate up does not recreate the
fallback if the selected bigram index is later dropped or becomes invalid.
First check whether either index is live, ready, and valid:
SELECT indexrelid::regclass AS index_name, indisvalid, indisready, indislive
FROM pg_index
WHERE indexrelid IN (
to_regclass('idx_comment_content_bigm'),
to_regclass('idx_comment_content_trgm')
);
If neither index is usable, restore the portable fallback before serving search traffic. Run each statement separately and outside a transaction so the concurrent index build is valid:
CREATE EXTENSION IF NOT EXISTS pg_trgm;
DROP INDEX CONCURRENTLY IF EXISTS idx_comment_content_trgm;
CREATE INDEX CONCURRENTLY idx_comment_content_trgm
ON comment USING gin (LOWER(content) gin_trgm_ops);
Verify that idx_comment_content_trgm reports all three flags as true before
resuming traffic. If idx_comment_content_bigm is repaired later, keep the
fallback until the bigram index also reports all three flags as true and
has the exact migration 036 shape: a non-unique, non-partial GIN index on
LOWER(content) using the pg_bigm-owned gin_bigm_ops operator class. Only
then can the fallback be dropped with DROP INDEX CONCURRENTLY during a
maintenance window.