Move extensions to pgxman #137
Merged
Conversation
This file contains 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
There is a circular dependency between pgxman & this repo.
owenthereal
force-pushed
the
owenthereal/pgxman_exts
branch
from
131f032 to
17a70a9
Compare
wuputah
approved these changes
Aug 24, 2023
JerrySievert
approved these changes
Aug 24, 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.
What's changed?
Move all extensions to be managed by pgxman except columnar which a bit special because it lives in this repo and have a circular dependency with pgxman/buildkit.
I also found a bug in the Spilo image that has some symlinking issue (see zalando/spilo@master...hydradatabase:spilo:hydra-2.1-p9) that can be contributed upstream. I'm unsure why this didn't pop in
main. Perhaps it's due to CI using caches.