Downgrade llvm to 15 to fix jit support #1077
Merged
+73
−16
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
|
Hopefully If the |
tianon
reviewed
May 12, 2023
Thank you! |
docker-library-bot
added a commit
to docker-library-bot/official-images
that referenced
this pull request
May 12, 2023
Changes: - docker-library/postgres@18c1bef: Merge pull request docker-library/postgres#1077 from infosiftr/llvm-fix - docker-library/postgres@a3b0bb6: Downgrade llvm to 15 to fix jit support - docker-library/postgres@1c1e4ff: Add the ability for us to manually trigger GitHub tests
This was referenced May 13, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
PostgreSQL doesn't support llvm 16 (#1076 (comment)):
Thank you for your comments on #1076 pointing me in a direction for a fix ❤️. Apologies for any stress and work that this caused 🙇♂️. With the added test in docker-library/official-images#14646, we shouldn't run into this issue again.
Fixes #1076