Bump pgrx, initial support for pg18 #68
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
gjtorikian
commented
Aug 3, 2025
| - name: Test | ||
| run: docker run test cargo pgrx test pg${{ matrix.postgres }} | ||
| run: | | ||
| PG_VERSION=$(echo "${{ matrix.postgres }}" | sed 's/[^0-9].*$//') |
Contributor
Author
There was a problem hiding this comment.
Although the image is tagged as 18beta1, pgrx expects just 18; this trims off any non-digit from the matrix string.
Owner
|
Yeah, we should support 18 in release only after it is out. |
Owner
|
@gjtorikian Would you mind finishing up the 18 support now that cargo-pgrx has been released? |
Contributor
Author
|
Sure, I opened #71 for it |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR updates pgrx to 0.16.0, which introduces support for pg18beta1.
The biggest change comes from 6dc6bef introducing an
unsafe; see pgcentralfoundation/pgrx@14dcb18 for more information.As well, even though I updated CI to start testing for pg18, I did not change release.yml to support pg18, because I wasn't sure if that's something you want to support. My only interest right now is to start testing against the beta builds, so that when the PG18 is out, this lib can be ready to support it.