Repository navigation
fix(postgres): track the ReadyForQuery owed by COPY TO STDOUT - #4454
Open
TannerRogalsky wants to merge 1 commit into
Open
TannerRogalsky wants to merge 1 commit into
TannerRogalsky wants to merge 1 commit into
Conversation
A copy_out_raw cancelled mid-exchange returned its connection to the pool with an untracked ReadyForQuery still pending. The release ping consumed it as its own reply, leaving the connection one reply behind, so its next query failed with "expected ParseComplete, got ReadyForQuery".
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
1 participant
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.
A copy_out_raw cancelled mid-exchange returned its connection to the pool with an untracked ReadyForQuery still pending. The release ping consumed it as its own reply, leaving the connection one reply behind, so its next query failed with "expected ParseComplete, got ReadyForQuery".
This is similar to #3138 and #3139 but related to errors rather than cancellations and timeouts.
#2762 also seems relevant as the copy-in counterpart.