CI: test against PostgreSQL 17 and 18 #929
Open
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
Postgres 17.6 added \restrict and \unrestrict metacommands to pg_dump to mitigate a security issue. This code skips these lines when restoring roles. 17.6 release: https://www.postgresql.org/docs/17/release-17-6.html#RELEASE-17-6-CHANGES CVE: https://www.postgresql.org/support/security/CVE-2025-8714/
rud
force-pushed
the
rud/add-pg-17-and-18-to-test-matrix
branch
from
fd3d4fb to
82166af
Compare
Author
|
Preview: I've run the tests in my fork of this repo, and it's all green: rud#1. Enjoy! |
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 builds on the fix from #925 (for green tests).
Related to #928.
What else needs to be added for official PostgreSQL 17 and 18 support?