On Fri, Jun 12, 2015 at 09:37:36PM +, Sheena, Prabhjot wrote:
> Here is some more information
>
> pool_mode | transaction
>
> We have transactional pooling and our application is set up in such a way
> that we have one query per transaction. We have set default pool size to
Please do not cross-post on the PostgreSQL lists. Pick the most
appropriate list to post to and just post there.
cheers
andrew
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-perform
Here is some more information
pool_mode | transaction
We have transactional pooling and our application is set up in such a way that
we have one query per transaction. We have set default pool size to 100.
This is output . As you guys can see active connection are 100 and 224 a
Unsubscribe
On Fri, Jun 12, 2015 at 8:57 PM, Sheena, Prabhjot <
prabhjot.si...@classmates.com> wrote:
> Guys we see spike in pg bouncer during the peak hours and that was
> slowing down the application. We did bump up the connection limit and it is
> helpful but now we again notice little spike
