From: | "Deshpande, Yogesh Sadashiv (STSD-Openview)" <yogesh-sadashiv(dot)deshpande(at)hp(dot)com> |
---|---|
To: | Raghavendra <raghavendra(dot)rao(at)enterprisedb(dot)com>, Bill Moran <wmoran(at)potentialtech(dot)com> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Postgre Performance |
Date: | 2011-10-18 17:38:19 |
Message-ID: | D1845D432CC3A64F8653DFEFB3732D5017B327B4@G4W3296.americas.hpqcorp.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I am not able to find binary distribution of pgbouncer for windows.. Can you point me to the location?
From: Raghavendra [mailto:raghavendra(dot)rao(at)enterprisedb(dot)com]
Sent: Tuesday, October 18, 2011 10:33 PM
To: Bill Moran
Cc: Deshpande, Yogesh Sadashiv (STSD-Openview); pgsql-general(at)postgresql(dot)org
Subject: Re: [GENERAL] Postgre Performance
> We need following information
>
> 1. Is there any configuration we do that would pool the connection request rather than coming out with connection limit exceed.
Use pgpool or pgbouncer.
Use pgbouncer, which is a light weighted connection pooling tool, if you are not opting for load balancing.
> Basically we wanted to limit the number of processes so that client code doesn't have to retry for unavailability for connection or sub processes , but postgre takes care of queuing?
For controlling unavailability of connections, it may be possible at application level but its not possible at Database level. However, if connections reaches max limit, DB will alert you as it reached max_connection.
--Raghav
From | Date | Subject | |
---|---|---|---|
Next Message | Samuel Hwang | 2011-10-18 17:39:32 | Can someone help explain what's going on from the attached logs? |
Previous Message | Joshua D. Drake | 2011-10-18 17:18:14 | Re: Postgre Performance |