Hot-table awareness
Write-traffic counters from pg_stat: a lock on a hot table escalates even when the table is small — a brief lock still queues a damaging backlog. Hosted, Startup and above.
Size is not the whole story. A sessions table with a thousand rows and ten thousand writes a second is more dangerous to lock than a cold archive with a billion. The snapshot carries the write and read counters from pg_stat_user_tables, and lock rules escalate on a hot table regardless of its size: a brief exclusive lock behind heavy traffic still queues a backlog that takes minutes to drain.
Heavily read tables escalate too — a lock that blocks reads on a table the application hits constantly is a partial outage, however small the table.
The CLI is open source and needs no account: npx bolvrk check migration.sql