4 ms·
My large scale application certainly didn't run the pooler on the host. I don't see any reason to do this except for not wanting to become familiar with postgre
by mrits 3y ago
My large scale application certainly didn't run the pooler on the host. I don't see any reason to do this except for not wanting to become familiar with postgres itself.
- nickphx 3y agoI ran the Pooler on the host.. I ran a few hundred hosts, so having a central pool was not ideal.
- dkhenry 3y agoWhat about running PHP, Django, Node, or Ruby based applications ? They all do connection per request so the pooler on host gives you an immediate improvement to connection latency. Even if you are using a language with a built in connection pooler like Go or Java being able to manage your connections external to your application is enough of a benefit to keep the pooler separate.