Closed kyleconroy closed 3 years ago
Looks like a second user ran into the same problem, this time using generated columns, which were added in PostgreSQL 12.
A third user has run into this problem, this time due to PARTITION BY HASH
.
See work on the upstream parser here: https://github.com/lfittl/libpg_query/pull/67
This has been resolved, with pg_query 2.0 being released today (based on the Postgres 13 parser) - thanks for your patience on this @kyleconroy!
I'm using pg_query_go to power the PostgreSQL support in https://github.com/kyleconroy/sqlc. Someone ran into an issue where their CREATE TRIGGER statement was failing to parse because they used new syntax introduced in PostgreSQL 11.
Are there plans to upgrade the parser to the current version of PostgreSQL?