Thread: Use of PgBouncer
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 ?
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.
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.g.johnston@gmail.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.
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.