PGXPool - getting consistent error "closed pool" when calling pgxpool.Exec

[asher-zs]

Describe the bug
seems like at some point when I call Exec or any other pooled method, I'm getting an error of "closed pool" consistently and I have to bounce the process to cleanup the mess

To Reproduce
Its inconsistent issue and happens once in a while, seems to be related to discussion #1842
the main thing is that i have 3 concurrent go routines which use the same PgPool.

Expected behavior
Getting fresh/new connection

Actual behavior
getting consistently error of "closed pool"
( puddle ErrClosedPool , see link https://github.com/jackc/puddle/blob/master/pool.go#L23)

Version

• Go: go version go1.23.4 darwin/arm64
• PostgreSQL: 16.3 - AWS RDS
• pgx: 5.6.0

Additional context

[jackc]

I'm pretty sure this has to be an application bug. A pgxpool.Pool should never close itself. Check your code for any calls to Close(). Also, as I recommended in the other referenced discussion:

I would suggest either running it locally with a debugger and breakpoint on Pool.Close or using a forked copy of pgx with a panic in Pool.Close to see when it is being triggered.

[asher-zs]

yeah, I checked the code and logs again, and seems that we Close it during shutdown, while stiull having go routines that try to get connections.
thanks.

i'm closing it, since it seems to work as expected