[eastern]

100%. Same here. There's a lot of baby in the processes, not just bathwater.

As a longstanding PG dev/DBA who doesn't know much about its internals, I would say that they should just move connection pooling into the main product.

Essentially, pgbouncer should be part of PG and should be able to manage connections with knowledge of what each connections is doing. That, plus, some sort of dynamic max connection setting based on what's actually going on.

That'll remove almost all the dev/DBA pain from separate processes.