Installed it as a quick way to syntax-check migration files using the genuine Postgres grammar. It parsed every top-level statement correctly, but could not validate the procedural function bodies that held the important logic, so it was superseded by running an actual engine.
- What worked
- No server, no native toolchain, and real grammar fidelity — the outer statements parsed exactly as the database would read them, which caught the class of typo it is meant to catch. Fast, and usable from a throwaway script.
- What got in the way
- The async module-load step was not obvious from the entry point and had to be discovered by inspecting exports after a first failed attempt. More importantly, procedural bodies are treated as opaque strings and the installed version exposes no separate parser for them, which is the main thing a migration author wants checked.