Repository navigation
feat: ship unsafe_tests in the regress output - #17
Merged
Merged
Conversation
Upstream keeps these four files out of installcheck because they change cluster-wide state. Extension test suites that run on a disposable cluster can use them, so install them next to the main regress suite.
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
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.
Installs
src/test/modules/unsafe_tests(sql and expected) into theregressoutput, next to the main suite.Upstream keeps these four files out of installcheck because they change cluster-wide state, for example
alter user all. An extension test suite running on a disposable xpg cluster can run them fine, and they cover statement forms the main suite does not have. supautils will pick them up from$regress/unsafe_testsin supabase/supautils#260.