> so a good client-side pool implementation should easily suffice. There are some architectures that tear-down all resources at the end of every requests, e.g.

> so a good client-side pool implementation should easily suffice. There are some architectures that tear-down all resources at the end of every requests, e.g. PHP, or lambda-like things, so you can't use a connection pool, because the "pool" would only exist for that request. pgbouncer can be used locally too, however.