Closed jirutka closed 8 months ago
To understand why that is, see #299, where an update to the supported-right-now version is described. EDIT: TIL that this would be unrelated, thanks!
This isn’t a glibc issue, I’m building it on Alpine Linux with musl libc.
I think this is a problem with the include path - it appears that your libpg_query build is somehow pulling in the system's Postgres headers before looking at the local headers it should be using.
It would be helpful if you could confirm whether this can be reproduced in isolation, for example if you attempt to install the Ruby gem in an empty Alpine Linux system / container. If you could share the steps to reproduce with a container, that would make it easiest to investigate whether we can fix the include paths here.
I believe that this should be entirely unrelated to the fact that libpg_query isn't updated for Postgres 16 yet (FWIW, we're already working on that), and is a problem that should be fixed independently, since the Postgres headers installed in the system do not need to match the libpg_query version in use.
Okay, I’ll look at it, but please note that I maintain the ruby-pg_query since Alpine v3.14, i.e. it works with PostgreSQL 13, 14, 15 and fails just with PostgreSQL 16.
Closing this since v5.0.0 has been released, which is based on Postgres 16. Let us know if you're still seeing any issues!