-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PG 14, PG 15 support #21
Comments
Hi! (pardon the delay, I just fixed my notifs) https://github.com/pganalyze/libpg_query still is on 13, and therefore so are we. We can track and upgrade when they do. |
Hi there =) https://github.com/pganalyze/libpg_query is now for 14 (and 15), thanking you in advance |
Hello @pyramation, thank you for the work you've been doing in We noticed that you have the V15 PR ready here, and we wanted to ask if it would be possible to merge this in, assuming it's ready. If not, could we get a timeline on how long before it can be merged? |
hey there @nith2001 — we have documented the issue here launchql/pgsql-parser#107 This is now closing and anyone who needs |
I ran into this issue using a vscode extension Plpgsql language server, https://github.com/UniqueVision/plpgsql-lsp/.
PG14 introduced "create or replace trigger" which causes a parse error in libpg-query-node.
Do you intend to introduce support at some point for PG14?
The text was updated successfully, but these errors were encountered: