{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/b263677aa49645799e8e09a3032a64e6\" frameborder=\"0\" width=\"1670\" height=\"1252\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1252,"width":1670,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1252,"thumbnail_width":1670,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/b263677aa49645799e8e09a3032a64e6-87f6b737b9ad727c.gif","duration":287.09,"title":"Governed Postgres Migrations With NOC Gate","description":"This Loom explains how AMP’s NOC governance layer helps prevent production outages from risky Postgres migrations. The speaker notes that existing SQL linters only check SQL structure, not real impacts like current table sizes and lock behavior, and can fail even when changes look fine on staging. Using an example migration to speed up archive search by adding an index, they show that the same change worked on staging but could block writes in production with 500,000 rows due to missing a needed CON clause. NOC is presented as a pre-check gate that can approve or block migrations and provide remediation across interfaces like a CLI, GitHub action, or MCP, using live estate data."}