Eno Compton

Thanks @mfridman. This at least shows us the background refresh isn't doing anything wrong. Based on past conversations with the backend team, I understand some small percentage of IAM authentication...

Right now the Go Connector doesn't understand the database protocol and just returns a connected socket to the driver. If you're using pgx directly, I wonder if you could retry...

Interesting. I don't know of any change, but this might have been a difference in how sql.DB initiates connections vs pgxpool? I'll close this but appreciate all the data. This...

Thanks for the info. It's too bad we can't hide that in the Connector here, but looks like a working solution.

This will be fixed with https://github.com/GoogleCloudPlatform/cloud-sql-go-connector/issues/731 most likely.

This bug has a few different manifestations. - https://github.com/GoogleCloudPlatform/cloud-sql-proxy/issues/2224 - https://github.com/GoogleCloudPlatform/cloud-sql-proxy/issues/2212

That's an artifact of how the Proxy path works -- it goes from the Go Connector to the Proxy server to the database server. The connection between the Proxy server...

> Am I right in assuming that if we enable the private-ip setting that Go Connector is talking to the proxy server on the private ip? As you mentioned that...

FWIW, it's possible to connect directly and still use Auto IAM AuthN (with a little know-how). In that scenario, you'd get the correct IP in the client logs. Also, a...

If you're using `database/sql`, you could write a driver like this: ``` golang import ( "context" "database/sql" "database/sql/driver" "github.com/jackc/pgx/v4" "github.com/jackc/pgx/v4/stdlib" "golang.org/x/oauth2" "golang.org/x/oauth2/google" ) func init() { sql.Register("gcp-postgres", &pgDriver{}) } type...