-
Notifications
You must be signed in to change notification settings - Fork 17.9k
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: improve documentation for DB.Close() (graceful close or not) #23753
Comments
It's generally best to ask questions in a forum, which is where more people will see them. See https://golang.org/wiki/Questions . I don't actually know the answer to this. |
/cc @kardianos Maybe retitle: |
That's reasonable doc request. I'll look into. |
I was wondering what the answer was to this question? |
Change https://golang.org/cl/103397 mentions this issue: |
@pjebs Can you inspect the above CL and see if that answers your question? |
Answers the question. |
It wasn't clear for existing docs if DB.Close forcefully closed connections or waited for them to finish. Fixes #23753 Change-Id: Id7df31224c93181c8d01bab7b0b23da25b42a288 Reviewed-on: https://go-review.googlesource.com/103397 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
The documentation doesn't make clear what DB.Close() does.
Does it close the Pool immediately even if there are still queries happening in some of the connections, or does it wait for the queries to finish and gradually closes the connections and then closes the pool?
The text was updated successfully, but these errors were encountered: