-
Notifications
You must be signed in to change notification settings - Fork 90
Problem: pgcopydb copy extensi
8000
on
fails when sequences exists part of ext configuration
#621
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
pgcopydb copy extension
fails when sequence exists part of ext configuration
pgcopydb copy extension
fails when sequence exists part of ext configurationpgcopydb copy extension
fails when sequences exists part of ext configuration
012b391
to
f4879cb
Compare
This will be useful to revive #312. |
dimitri
requested changes
Jan 5, 2024
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.
First round of review is in, thanks!
f4879cb
to
8c42aa0
Compare
916ef30
to
a6adc0c
Compare
…f ext configuration Solution: Populate extension configuration objects along with their type values. Based on the type value, perform either table copy or sequence copy. At the moment we support only copying extension configuration tables & sequences. Signed-off-by: Arunprasad Rajkumar <ar.arunprasad@gmail.com>
a6adc0c
to
797522b
Compare
Thanks @dimitri , addressed your review comments. PTAL. |
dimitri
approved these changes
Jan 5, 2024
arajkumar
added a commit
to arajkumar/pgcopydb
that referenced
this pull request
Jan 17, 2024
…f ext configuration (dimitri#621) (dimitri#25) Solution: Populate extension configuration objects along with their type values. Based on the type value, perform either table copy or sequence copy. At the moment we support only copying extension configuration tables & sequences. Signed-off-by: Arunprasad Rajkumar <ar.arunprasad@gmail.com>
arajkumar
added a commit
to arajkumar/pgcopydb
that referenced
this pull request
Jan 18, 2024
…f ext configuration (dimitri#621) Solution: Populate extension configuration objects along with their type values. Based on the type value, perform either table copy or sequence copy. At the moment we support only copying extension configuration tables & sequences. Signed-off-by: Arunprasad Rajkumar <ar.arunprasad@gmail.com>
arajkumar
added a commit
to arajkumar/pgcopydb
that referenced
this pull request
Jan 18, 2024
…f ext configuration (dimitri#621) Solution: Populate extension configuration objects along with their type values. Based on the type value, perform either table copy or sequence copy. At the moment we support only copying extension configuration tables & sequences. Signed-off-by: Arunprasad Rajkumar <ar.arunprasad@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
<
3038
span class="js-add-to-batch-enabled">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.
Solution: Populate extension configuration objects along with their type values. Based on the type value, perform either table copy or sequence copy.
At the moment we support only copying extension configuration tables & sequences.
I didn't add test for this PR, because I've to hunt the extension which has sequence as part of the config table. I've manually tested with timescaledb which happens to have few sequences part of the extension config table.
With the fix, I could copy the timescale extension from source to target,