pgxpool hangs after number of queries on the order of max connections

Nobody has claimed this yet.

Hi,

Thanks so much for putting up this example. I've been trying to learning golang web services and was using your booklog as one of the core examples.

Currently, I'm using pgx v4 + gochi v5, I'm using code similar to your DbConn interface to hide the Pool pointer, but after handling a number of db-heavy (calling stored procs, etc, but never batched, always single statement) web requests, the pool just hangs (presumably getting a new connection) afterwards.

I feel like I must be doing something wrong. However, your booklog example doesn't do anything to close connections explicitly. If you have any pointers as to why Pool is hanging after some number of query executions, I would really appreciate it!

Best,

Tom

Start by reviewing the booklog example and its DbConn interface, then reproduce the reported hang with pgx v4 and go-chi v5 after repeated database-heavy requests. Trace pool usage and connection handling; done means identifying the cause of the pool waiting and documenting or correcting the example accordingly.

Written by the indexing model from the issue text.