This does not help because if there is no connection in the connection pool the interface will open a new connection with previously supplied DSN from the sql.Open call.
Anthony On Tuesday, November 7, 2017 at 7:22:00 AM UTC-8, Konstantin Khomoutov wrote: > > On Tue, Nov 07, 2017 at 12:06:27AM -0800, agru...@gmail.com <javascript:> > wrote: > > > It appears the Generic Interface for SQL (database/sql) does not support > > the ability to use short lived DSN's for cases like AWS's IAM > > Authentication to RDS instances. It appears that when doing its > connection > > pooling activities it always uses whatever DSN was passed initially on > Open. > > > > 1) Is this correct. > > 2) Assuming one is correct would the Golang project every consider > adding > > this feature? > > 3) If the answer is yes. How would one go about either helping to get it > on > > the road map or better yet contributing this feature back to the > community? > > What is this process? > > Does setting the maximum number of the idle (that is, pooled) database > connections [1] to a value equal or less than zero helps with this? > > 1. https://golang.org/pkg/database/sql/#DB.SetMaxIdleConns > > -- 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.
