-
-
Notifications
You must be signed in to change notification settings - Fork 249
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
FAQ: Migration to Postgres 16 #1298
Comments
My current hypothesis is that the Postgres 16 build errors might be induced by our conditional setting of |
Most concerns about migration to Postgres 16 should be addressed by using |
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There are some difficulties recently presented with migrating PGRX extensions to Postgres 16. Here I will attempt to answer these questions as they may arise.
Q. My build is failing with some sort of bindgen error, something about
<emmintrin.h>
?A. You may have too many clangs. Basically, with rustup, rust-bindgen, and a system's clang packages, there can be a situation where there are "too many clangs" on the system. Essentially:
<[aeinpstw-z]mmintrin.h>
).This may not be something PGRX can solve (this is still unclear), but it is something that can be easily resolved as a configuration issue. It is usually sufficient to remove all but one clang package on the system, preferably using a more recent one (as this was initially discovered when using clang 11 and compile-erroring on clang 14's intrinsic headers).
Q.
cargo pgrx install
(or other commands) on macOS doesn't work?A. Oops. Try pgrx v0.10.2! It should be patched now.
The text was updated successfully, but these errors were encountered: