Jack Christensen

@jaitaiwan You are on v5.5.1. If you have the ability to reproduce the error can you upgrade to v5.5.5? There is a change that should have fixed this issue.

You might try looking at the [pg_stat_activity view](https://www.postgresql.org/docs/current/monitoring-stats.html#MONITORING-PG-STAT-ACTIVITY-VIEW) when the pool is exhausted. That view should show the last query each connection executed. That may give you information on where...

Can you try it with this code? ```go for _, fc := range fallbackConfigs { pgConn, err = connect(ctx, config, fc) if err == nil { break } var pgErr...

I have two concerns with this. Types errors, whether directly exposed as public types or through `Is*` methods as you have done here, become part of the public interface of...

This is much better. I think we are getting really close to an ideal solution. But I have two more small points to bring up. First, in general it is...

Not sure. To be honest I don't think I ever use a password for a Unix connection. It does seem odd to force the host to localhost instead of using...

Change `AvatarUrl` and `Email` to `*string` or `pgtype.Text`.

@quanqqqqq The example in the docs seems to show that the base type is used rather than a nullable wrapper: https://pkg.go.dev/database/sql/driver#RowsColumnTypeScanType. Notice that it says `bigint` should be `reflect.TypeOf(int64(0))` and...

@benjamincudi The error makes more sense when it comes directly from a `Scan` call. It's very clear that a pointer is being passed in. But the `Collect*` and `RowToStruct*` functions...

I think that is the right place.