Jack Christensen

> The thing which is not entirely clear to me is how you conditionally test features which are only available in PG18 like this OAuth stuff? Do we use t.Skip()...

It might be possible to add some additional diagnostics such as capturing a stack trace whenever a connection is acquired or a query is started. Then something could inspect the...

Can you provide an example that demonstrates this error?

I'd need an example I can run. Perhaps that's what you intended for #2127? It seems to work on master...

> Histogram could be taken if there were OnAcquireStart and OnAcquireComplete, which are called as the very first and very last operation in Pool.Acquire. Alternatively pgxpool could expose histogram in...

> Expected behavior > The underlying pgxpool is also closed when the *sql.DB is closed. That is not what I would expect to happen.

To elaborate a little further, whenever you have a parent and a child resource, it is normal that closing the child resource does not close the parent resource.

The intended use for `stdlib.OpenDBFromPool` is when an application uses pgx directly, but also needs to use database/sql. `stdlib.OpenDBFromPool` provides a way of using the same underlying connection pool. If...

I added a note to the docs.

Are you sure about the Go 1.24 requirement? It looks like 1.23 is sufficient to me. https://cs.opensource.google/go/x/crypto/+/master:go.mod I'd like to avoid that change as that would break pgx's Go compatible...