fix unsafe rows.Close() race #726
Open
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
According to https://godoc.org/database/sql/driver#Rows, the Close operation should not affect the values returned by Scan. In normal flow, this is not an issue, but if Rows is closed by a cancelled context or another routine, it can be. This changes the scratch to be a slice, and changes its memory location when rows are closed before they are done, so that any scanning will not be affected.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
According to https://godoc.org/database/sql/driver#Rows, the Close
operation should not affect the values returned by Next. In normal flow,
this is not an issue, but if Rows is closed by a cancelled context or
another routine, it can be.
This changes the scratch to be a slice, and changes its memory location
when rows are closed before they are done, so that any scanning will not
be affected.
In an attempt to prevent allocations every time the rows are closed,
this only creates a new scratch when rows are closed before they
are done.