warn-concurrent-index-invalid

What It Detects

CREATE INDEX CONCURRENTLY can leave an invalid index on failure. Add DROP INDEX IF EXISTS before retrying.

Why It's Dangerous

If CREATE INDEX CONCURRENTLY fails, it leaves behind an INVALID index that slows writes but is never used for queries. Retrying without first dropping the invalid index fails with "relation already exists".

Bad Example

CREATE INDEX CONCURRENTLY idx_email ON users (email);

Good Example

DROP INDEX IF EXISTS idx_email;
CREATE INDEX CONCURRENTLY idx_email ON users (email);

Configuration

Disable this rule:

# .migrationpilotrc.yml
rules:
  MP070: false

Or change its severity:

# .migrationpilotrc.yml
rules:
  MP070:
    severity: warning