Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork213
feat: test pg_upgrade compatibility with older extension versions#1897
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Open
jfroche wants to merge3 commits intodevelopChoose a base branch
base:develop
Could not load branches
Branch not found:{{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline, and old review comments may become outdated.
Uh oh!
There was an error while loading.Please reload this page.
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
samrose approved these changesNov 6, 2025
samrose requested changesNov 6, 2025
Collaborator
samrose 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.
Looks great! Will just need to test before we merge it
Add test to verify that all extension versions from PostgreSQL 15 can successfully upgrade to PostgreSQL 17 using pg_upgrade.The test now validates:- Each PG 15 extension version can be upgraded to PG 17- Extension update scripts are properly generated during upgrade- Version handling works correctly with and without update scripts- Final extension versions match expected values after upgrade
…ade compatibilityWhen upgrading PostgreSQL versions, pg_upgrade needs access to old extensionversions sql to migrate from. This adds unsupported pg_graphql versions (those notcompilable with current PostgreSQL) as SQL-only packages, ensuring migrationpaths exist when upgrading from older PostgreSQL versions.
…pgrade compatibilityWhen upgrading PostgreSQL versions, pg_upgrade needs access to old extensionversions sql to migrate from. This adds unsupported pg_graphql versions (those notcompilable with current PostgreSQL) as SQL-only packages, ensuring migrationpaths exist when upgrading from older PostgreSQL versions.
8acfa60 tof59c791CompareSign up for freeto 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.
Uh oh!
There was an error while loading.Please reload this page.
Add test to verify that all extension versions from PostgreSQL 15 can successfully upgrade to PostgreSQL 17 using pg_upgrade.
The test now validates: