[*] allow Postgres sink schemas to exist before init/upgrade #1116
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
pashagolub
added
refactoring
Pull Request Test Coverage Report for Build 20783883445Details
💛 - Coveralls |
This change aims to ease v4 -> v5 migration be having `subpartitions` schema untouched. User will empty/drop `admin` schema and re-init it with pgwatch. Existing `subpartitions` and `public` tables should be used as is.
0xgouda
force-pushed
the
handle-sink-schemas
branch
from
7689ace to
3688f4e
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.
This change aims to ease v4 -> v5 migration be having
subpartitionsschema untouched. User will empty/dropadminschema and re-init it with pgwatch. Existingsubpartitionsandpublictables should be used as is.