| From: | Craig Ringer <craig(at)2ndQuadrant(dot)com> |
|---|---|
| To: | tuanhoanganh <hatuan05(at)gmail(dot)com> |
| Cc: | John R Pierce <pierce(at)hogranch(dot)com>, PostgreSQL <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: PostgreSQL run as process in windows |
| Date: | 2013-01-08 02:31:48 |
| Message-ID: | 50EB8514.7020703@2ndQuadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 01/03/2013 12:51 PM, tuanhoanganh wrote:
> On Thu, Jan 3, 2013 at 11:04 AM, John R Pierce <pierce(at)hogranch(dot)com
> <mailto:pierce(at)hogranch(dot)com>> wrote:
>
> of course, a pooler only works right if the client applications
> are modified to open a connection, do a transaction, and close the
> connection. if the clients continue to hold idle connections, the
> pooler won't do anything useful for you.
>
>
> :-( My application continue to hold idle connections.
Idle CONNECTIONS are fine.
What you need to avoid is open transactions being held open and idle for
long periods.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2013-01-08 02:32:35 | Re: PostgreSQL run as process in windows |
| Previous Message | Moshe Jacobson | 2013-01-07 19:55:29 | Re: spring a string to rows (Postgresql 8.4) |