Forecast what your PostgreSQL migration will block, for how long, on your actual workload.
Linters tell you "this takes ACCESS EXCLUSIVE." pg-blast-radius tells you "this will queue 14,200 queries/min on your busiest table for 6..12 minutes."
It reads your migration SQL, connects read-only to your database, and produces workload-aware blast radius forecasts with explicit confidence accounting.
Identifies which production queries from pg_stat_statements will be blocked, calculates queue depth per second, and ranks by impact.
P50, P90, and worst-case estimates based on table size and observed transaction durations. Not single-point guesses.
Every forecast states what is known from PG docs, observed from catalog, inferred from workload, and what remains assumed.
Step-by-step safer SQL using expand/contract patterns. Each step tagged with its phase and lock impact.
Requires Rust 1.85+ and a C compiler for libpg_query. Read-only database connection for full analysis.
Static (no database): lock modes, rewrite detection, rollout recipes. Confidence: STATIC.
Catalog-aware (table sizes): size-adjusted risk, P50/P90/worst duration forecasts. Confidence: ESTIMATED.
Workload-aware (pg_stat_statements + pg_stat_activity): blocked query families, queue depth estimates, lock acquisition delay. Confidence: MEASURED.