[columnar] PostgreSQL 16 compatibility #200
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
|
The upgrade test is failing as it needs an initial image to pull, I believe the workaround is to build and push one manually for that to pass. |
|
unfortunately we have new test failures here because parquet s3 fdw doesnt exist for pg16. |
…16 (#207) * Skip acceptance tests for extensions that don't work in pg 16 Skip acceptance tests for extensions that don't work in pg 16 * Bump to Go 1.21 * Fix linting error * Skip more parquest_s3_fdw tests
wuputah
approved these changes
Dec 5, 2023
JerrySievert
approved these changes
Dec 5, 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.
PG16 compatibility