Skip to content
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

database/sql: segfault in connection pool when the driver frequently fails to connect [1.10 backport] #25235

gopherbot opened this issue May 3, 2018 · 3 comments


Copy link

@gopherbot gopherbot commented May 3, 2018

@andybons requested issue #24445 to be considered for backport to the next 1.10 minor release.

@gopherbot please backport to 1.10 with CL

Copy link

@katiehockman katiehockman commented Oct 29, 2018

Approved since this is a regression. Please follow the instructions at to create the cherrypick CL.

@dmitshur dmitshur modified the milestones: Go1.10.5, Go1.10.6 Nov 1, 2018
Copy link

@gopherbot gopherbot commented Nov 1, 2018

Change mentions this issue: [release-branch.go1.10] database/sql: check for nil connRequest.conn before use

Copy link

@gopherbot gopherbot commented Nov 1, 2018

Closed by merging edd28f1 to release-branch.go1.10.

@gopherbot gopherbot closed this Nov 1, 2018
gopherbot pushed a commit that referenced this issue Nov 1, 2018
…before use

The connRequest may return a nil conn value. However in a rare
case that is difficult to test for it was being passed to
DB.putConn without a nil check. This was an error as this
made no sense if the driverConn is nil. This also caused
a panic in putConn.

A test for this would be nice, but didn't find a sane
way to test for this condition.

Updates #24445
Fixes #25235

Change-Id: I827316e856788a5a3ced913f129bb5869b7bcf68
Run-TryBot: Daniel Theophanes <>
TryBot-Result: Gobot Gobot <>
Reviewed-by: Alexey Palazhchenko <>
Reviewed-by: Brad Fitzpatrick <>
(cherry picked from commit b98ffdf)
Run-TryBot: Brad Fitzpatrick <>
Reviewed-by: Katie Hockman <>
@golang golang locked and limited conversation to collaborators Nov 1, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
5 participants
You can’t perform that action at this time.