Problem: Resume after interrupted clone always fails #698
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.
We use
done_time_epoch
fromtimings
to populaterunState
, which helps to skip already processed table sections.However, we call
summary_start_timing
regardless of whether the section has been already done or not., which causing insertion(insert or replace) of default value todone_time_epoch
becausesummary_start_timing
won't be called for already done section.Without this fix, while resuming after the interruption pgcopydb would do pre-data restore again leading to table already exists error.
Solution: Check whether the section is already completed using
runState
and exit early without callingsummary_start_timing
for already done section.Related to #692