Postgres Migration Lock check — check migration locks free

Find the statements in your Rails, Django or raw SQL migrations that take a table-blocking Postgres lock - and the safe rewrite - before you deploy. Runs entirely in your browser — nothing is uploaded.

-- orders: add tenancy + tighten money columns (generated, reviewed by nobody)
BEGIN;

ALTER TABLE orders ADD COLUMN tenant_id bigint NOT NULL;
ALTER TABLE orders ADD COLUMN external_ref text UNIQUE;
ALTER TABLE orders ADD COLUMN imported_at timestamptz DEFAULT now();
ALTER TABLE orders ALTER COLUMN amount_cents TYPE numeric(12,2);
ALTER TABLE orders ALTER COLUMN currency SET NOT NULL;
ALTER TABLE orders ADD CONSTRAINT orders_tenant_fk FOREIGN KEY (tenant_id) REFERENCES tenants (id);
ALTER TABLE orders ADD CONSTRAINT orders_amount_positive CHECK (amount_cents > 0);
ALTER TABLE orders ADD CONSTRAINT orders_ref_uniq UNIQUE (external_ref);
ALTER TABLE orders RENAME COLUMN legacy_total TO total_cents;
ALTER TABLE orders DROP COLUMN legacy_notes;

CREATE INDEX idx_orders_tenant ON orders (tenant_id);
CREATE INDEX CONCURRENTLY idx_orders_created ON orders (created_at);
DROP INDEX idx_orders_old_ref;
REINDEX TABLE orders;
CLUSTER orders USING idx_orders_tenant;

LOCK TABLE orders;
UPDATE orders SET tenant_id = 1;
DELETE FROM order_events;
TRUNCATE order_archive;
VACUUM FULL orders;

COMMIT;

as of

Free here: Audit the migration file you have open and name every statement that takes a blocking Postgres lock, with the safe rewrite for your framework.. In the editor: Audit every migration in the workspace in one pass and export the review as Markdown or JSON to attach to the change ticket, with a CI exit-code gate for the team. — that part asks for a licence key.

Same engine as the VS Code extension, byte for byte.