-
-
Notifications
You must be signed in to change notification settings - Fork 992
pgconn: fix panic on Pipeline.Close when server sends multiple FATAL errors #2501
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
Open
veeceey
wants to merge
2
commits into
jackc:master
Choose a base branch
from
veeceey:fix-pipeline-close-panic
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+128
−7
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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.
Uh oh!
There was an error while loading. Please reload this page.
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.
How can this path be executed? I thought that
getResultswould always either return results or an error. But this would only happen if it returnsnil, nil.If any change is to happen around here I would expect there to be more error cases that trigger
asyncClose()andbreak.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.
Good question.
getResults()does return(nil, nil)-- it happens at thepipelineNilcase (line 2514-2515) whenExtractFrontRequestType()finds the request event queue empty.Here's the exact sequence in the double-FATAL scenario:
Iteration 1 -- pops
Preparefrom queue,getResultsPrepare()reads ParseComplete + ParameterDescription + RowDescription, returns(psd, nil). Loop continues.Iteration 2 -- pops
Preparefrom queue,getResultsPrepare()callsreceiveMessage()which reads the first FATAL.OnPgErrorreturns false, connection is closed,cleanupDoneis closed.Pipeline.receiveMessage()returns the error. Back inClose(): it's aPgError, so the loop continues (doesn't break).Iteration 3 -- pops
Syncfrom queue,getResultsSync()callsreceiveMessage()which reads the second FATAL. The guard prevents the double-close ofcleanupDone.Pipeline.receiveMessage()returns the error. Back inClose(): it's again aPgError, so the loop continues.Iteration 4 -- queue is now empty.
ExtractFrontRequestType()returnspipelineNil.getResults()returns(nil, nil). ButExpectedReadyForQuery()is still 1 becauseReadyForQuerywas never received (the server sent FATALs instead). Without thenilcheck, this spins forever.The key insight is that FATAL
PgErrors don't causeClose()to break (only non-PgErrorerrors do), and FATAL errors consume queued request slots without the server ever sendingReadyForQuery, soexpectedReadyForQueryCountis never decremented.I've updated the comment in the latest push to explain this flow explicitly.