connector_flow: Fix issue where it tries to update chunk status in a broken transaction#3
Closed
taezaz wants to merge 1 commit into
Closed
connector_flow: Fix issue where it tries to update chunk status in a broken transaction#3taezaz wants to merge 1 commit into
taezaz wants to merge 1 commit into
Conversation
…ored until end of transaction block" that occurs when trying to update chunk status after a postgresql error, which leaves transaction invalid
|
This is the same issue as #4 but I think the solution isn't correct. |
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
3 participants
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 might happen for example if multiple workers try to execute same job at the same time. It may cause an error "could not serialize access due to concurrent update", which will abort the transaction, yet it will still call chunk.write({'state': new_state}) after that.