From: | Ankur Kaushik <ankurkaushik(at)gmail(dot)com> |
---|---|
To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
Cc: | pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Use of PgBouncer |
Date: | 2015-10-07 22:05:51 |
Message-ID: | CALXoLqynC3pbSiDXc-Qw6z14DoXJthMXwNbebGSzDWdTR5M2DA@mail.gmail.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
so that mean only one type connection pooling is recommended either
application side or database side using PgBouncer .
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 .
On Thu, Oct 8, 2015 at 3:14 AM, David G. Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
> On Wed, Oct 7, 2015 at 5:15 PM, Ankur Kaushik <ankurkaushik(at)gmail(dot)com>
> wrote:
>
>>
>> As stated PgBouncer is used to manage connection pool , If the connection
>> pool is managed by java then May I now If this is still used ?
>>
>
> Whether you want to use an external connection pooler like pgBouncer when
> you are doing in-container/in-application connection pooling is a decision
> you will need to make based upon your specific circumstances.
>
> David J.
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | David G. Johnston | 2015-10-07 22:34:48 | Re: Use of PgBouncer |
Previous Message | David G. Johnston | 2015-10-07 21:44:17 | Re: Use of PgBouncer |