-
-
Notifications
You must be signed in to change notification settings - Fork 217
feat: support multiple versions of the plpgsql_check extension #1684
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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
hunleyd
previously requested changes
Aug 27, 2025
Contributor
hunleyd
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
rebase to fix conflicts?
65e9e63 to
8d97eca
Compare
6da8282 to
fc6453e
Compare
a916d80 to
322faab
Compare
Build multiple versions of the plpgsql_check extension on different PostgreSQL versions. Add test for the extensions and their upgrade on PostgreSQL 15 and 17.
Generate empty SQL files for version-to-version upgrade paths to satisfy PostgreSQL extension upgrade requirements.
1acd2db to
38c2763
Compare
rebase was successful thanks for reviewing this PR. will close this change request to unblock merging all testing was successful
samrose
approved these changes
Oct 22, 2025
hunleyd
added a commit
that referenced
this pull request
Oct 23, 2025
* origin: refactor(ansible): bring our ansible up to modern ansible-lint standards (#1852) chore: bump to release (#1855) docs: getting started nix install or config revised (#1853) docs: how to update new structure (#1851) feat: support multiple versions of the plpgsql_check extension (#1684) refactor(ansible): bring our ansible up to modern ansible-lint standards (#1848) feat(wrappers): support more versions (#1831) refactor(ansible): bring our ansible up to modern ansible-lint standards (#1833) fix: fine tune protection rules to unblock wal-g functionality (#1846) fix: incorporate v3.0.0 supautils (#1844) fix: remove git revision from postgres package
encima
pushed a commit
that referenced
this pull request
Oct 28, 2025
* feat: support multiple versions of the plpgsql_check extension Build multiple versions of the plpgsql_check extension on different PostgreSQL versions. Add test for the extensions and their upgrade on PostgreSQL 15 and 17. * tests: refactor to use the default nixos tests * fix(plpgsql-check): add missing upgrade path files between versions Generate empty SQL files for version-to-version upgrade paths to satisfy PostgreSQL extension upgrade requirements. * feat: requires switch version script due to shared_preload * fix: test with plpgsql_check extension --------- Co-authored-by: Sam Rose <[email protected]>
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.
Build multiple versions of the plpgsql_check extension on different PostgreSQL versions.
Add test for the extensions and their upgrade on PostgreSQL 15 and 17.