Parses migrations with the real Postgres parser (libpg_query via libpg-query), classifies the lock each statement takes, and — unlike static-only linters (Squawk, Atlas free tier) — optionally connects to the real target database (Supabase/Neon/plain Postgres) to re-score severity against that table's actual row count, dead-tuple ratio, and currently-active lock holders, with an optional AI explain+rewrite layer gated on ANTHROPIC_API_KEY. Verified against a real local Postgres with a seeded 150k-row table and a real concurrent lock holder: same static rule produces BLOCK on the large table and INFO on a 3-row table, and escalates to BLOCK when a real backend is holding a lock on the target table at check time. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
7 lines
318 B
SQL
7 lines
318 B
SQL
-- Same intent as risky-migration.sql, written the safe way.
|
|
CREATE INDEX CONCURRENTLY idx_orders_status_safe ON orders (status);
|
|
|
|
ALTER TABLE orders ADD CONSTRAINT fk_orders_customer_safe
|
|
FOREIGN KEY (customer_id) REFERENCES customers (id) NOT VALID;
|
|
ALTER TABLE orders VALIDATE CONSTRAINT fk_orders_customer_safe;
|