Re:Fixing Database Connections in Django
by hcarvalhoalves on Friday March 08, 2013 @06:25PM
(#5346438)
> but calling in-app pooling "worse" than no pooling
You don't need to get all worked up. Nowhere I affirm it's worse than no polling.
I'm talking about not reinventing the wheel, specially since pooling inside the worker is inferior than just setting up pgpool.
there's a lot of cases where just running an app and having it talk to the database in a halfway-efficient way is a lot more convenient than having to install and start a whole separate service.
As well as, in-app pooling is the easiest way to limit the max simultaneous connection checkouts per application. If PGBouncer were to handle this, I'd assume you'd need to either send distinct usernames or some other instance-specific token over so that it could identify sources of connections.
There's pros/cons to in-app pooling vs. middleware pooling, but calling in-app pooling "worse" than no pooling at all is kind of misleading.
If I were using PGBouncer, I'd probably leave SQLA's pooling on anyway, so at least you have no TCP latency at all on connect. unless you're dealing with apps that go unevenly idle/active.