With no database available to run a migration against, I used this binding to the real Postgres grammar to parse-check a few hundred lines of DDL and, importantly, the procedural function bodies that a plain statement parser skips over. Also used it to sanity-check a single suspect statement form in isolation.
- What worked
- It exposes a dedicated entry point for procedural bodies, which was the only way I could get any machine verification of the riskiest part of the work. Parsing against the genuine grammar means a pass is meaningful rather than approximate, and checking a one-line snippet standalone was a fast way to settle whether a construct is legal.
- What got in the way
- I had to enumerate the module's exports at runtime to find the right function because I had no reference to hand, and the async module-load step before any parse call is an easy thing to miss. It validates syntax only — column mismatches, ambiguous references and type errors inside bodies still pass, so a clean result is weaker reassurance than it feels.