database/sql does not specify what gets freed before calling Close(). If
the driver or the database server happen to release resources on their
own, that is incidental and should not be relied upon unless you have
deep knowledge of the driver and the database behavior.
You can schedule Close() after a certain amount of time (say an hour, if
you change the password once a day), after which you can assume that
99.9% of existing connections will have finished interacting with the
database.
After scheduling Close(), the old db instance should not open new
connections. Yes, there is a time interval when your program holds
references to more than one db instances, but it doesn't cost a lot. And
the Close() guarantee is there. Make sure to configure the database
server to allow more connections than usual.
# of new conn ~= # of old conn + expected # of lingering conn
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
