| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Ankur Kaushik <ankurkaushik(at)gmail(dot)com> |
| Cc: | pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Use of PgBouncer |
| Date: | 2015-10-07 22:34:48 |
| Message-ID: | CAKFQuwYTyU07bAeQOkkUWFj0tXWe7xGLdfBynxcsys-P_Tdbiw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Wed, Oct 7, 2015 at 6:05 PM, Ankur Kaushik <ankurkaushik(at)gmail(dot)com>
wrote:
> so that mean only one type connection pooling is recommended either
> application side or database side using PgBouncer .
>
>
That isn't what I said. Given that you provided zero details regarding
your environment I will not make any specific recommendations.
How good could be using the PgBouncer If data is coming at the rate of 200
> MB/hour , And there need about 100 concurrent connections for read purpose .
>
Any solution is likely to operate adequately at 200MB/hour; and 100
connections - no matter how you define them - seems within its capability.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Evgeniy Losev | 2015-10-08 09:46:24 | Moving tablespace pg_global to custom location |
| Previous Message | Ankur Kaushik | 2015-10-07 22:05:51 | Re: Use of PgBouncer |