Bullet proof means a few different things and will depend on other
details. It's best to run your own simulation of the edge cases. One I
can think of is: what happens if the old pool / db instance opens a new
connection during the split second after the credential change at the
backend but before the new instance has been created.
The initially proposed solution in the OP also didn't address this so
the new code should do no worse.
--
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.
