[pgpool-general: 3785] Re: Reg Connections limit pgpool can handle.

Alex Toth atoth at gravity.com
Fri Jun 5 00:01:02 JST 2015

There's an important distinction between Pgpool and Pgbouncer in your
example.  Pgpool is aware of the difference between reads and writes and
can route the requests to the correct backend, while Pgbouncer is not.
Pgpool can also handle failover/master failure if you configure it to do so
and Pgbouncer can't.

As far as scale, I think the issue for both is how much memory (and, to a
lesser extent, CPU) you can dedicate to the pool.  Both are going to create
processes to handle connections, so the more connections the more
processes/memory you'll use.


On Thu, Jun 4, 2015 at 3:48 AM, Gurunadh Venkata <gurunadh.venkata at gmail.com
> wrote:

> Hi Group,
> .
>  Can pg pool differentiate the read & write  requests from app server.?
>  DB Server goes down with say some 1000 hits or so.. How can we handle the
> traffic say, even 2000+.? Which of the Pgpool or Pgbouncer middleware will
> be used in this case?
> Thanks For Your Time.
> Thanks & Regards,
> G V Gurunadh.
> _______________________________________________
> pgpool-general mailing list
> pgpool-general at pgpool.net
> http://www.pgpool.net/mailman/listinfo/pgpool-general
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.sraoss.jp/pipermail/pgpool-general/attachments/20150604/87363837/attachment.html>

More information about the pgpool-general mailing list