I’ve been working on a tool related to this for Database migrations. Most current tooling is similar to this: parse the SQL, find specific statements and highl

I’ve been working on a tool related to this for Database migrations. Most current tooling is similar to this: parse the SQL, find specific statements and highlight “dangerous” locks. But that lacks all context and doesn’t account for changes or schema specific stuff related to rewrites/existing constraints/etc. Why not… just get Postgres to tell you what locks or rewrites a given DDL statement will take? Why do we need to take the logic defined in the Postgres source code and spit it into a human readable form, for us to then take a given SQL statement, parse it in our head and cross reference it with this (or other) documentation? Am I missing something?