Update to libpg_query 17-6.1.0

[lfittl]

This fixes strchrnul compatibility on macOS 15.4+

Note that the libpg_query release is technically not tagged yet (but this branch could be used in the interim), I plan to make a libpg_query release within the next day, and then release a new pg_query version as well.

Fixes #327

[simba909]

@lfittl Any chance we could get this back-ported to pg_query 5 or 4? We're using 4.2.3 in one of the projects I'm working on due to PostgreSQL 14 (maybe pg_query 6.1.0 will also work with PostgreSQL 14 in which case that's fine)

[lfittl]

@lfittl Any chance we could get this back-ported to pg_query 5 or 4? We're using 4.2.3 in one of the projects I'm working on due to PostgreSQL 14 (maybe pg_query 6.1.0 will also work with PostgreSQL 14 in which case that's fine)

It would be a decent amount of extra effort, since those are older parser versions too (where we'd have to update to the corresponding Postgres sources, etc).

Is there a reason you can't upgrade? The parser is generally compatible with older releases (so it shouldn't be an issue to be on pg_query 6.1.0 even when running against Postgres 14 type queries), the only concern could potentially be if you rely on any APIs that changed between the releases.

[simba909]

[...] The parser is generally compatible with older releases (so it shouldn't be an issue to be on pg_query 6.1.0 even when running against Postgres 14 type queries) [...]

Ah! That's nice, then I think we're good. Thank you! 🙏🏻