feat: run pg_regress during extension tests #1812
Merged
+50
−5
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
|
@jfroche is this tested with for instance |
That's right |
samrose
approved these changes
Oct 1, 2025
While testing the upgrade of our PostgreSQL extensions, we also want to run the pg_regress tests that come with the extension. This ensures that the extension is functioning correctly after installation and upgrades.
jfroche
force-pushed
the
exts/run-pgregress
branch
from
54a68f1 to
7cd477c
Compare
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.
While testing the upgrade of our PostgreSQL extensions, we also want to run the pg_regress tests that come with the extension. This ensures that the extension is functioning correctly after installation and upgrades.