| From: | "Luiz Bernardi" <lb(at)cplinformatica(dot)com> |
|---|---|
| To: | <pgsql-general(at)postgresql(dot)org> |
| Subject: | close inactive client connection |
| Date: | 2009-09-25 12:26:28 |
| Message-ID: | web-7612005@hm775.cl01.mobimail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
<div id="_htmlarea_default_style_" style="font:10pt arial,helvetica,sans-serif"><div id="result_box" dir="ltr">Hello,
<br>
<br> I am developing a system, using the ZeosLib, which maintains a permanent connection to the database.
<br>
<br> When the client loses the connection, the server does
not recognize this and keeps the connection as if it were active. When
the client attempts to reconnect, the server creates a new connection
and the previous remains active. <br>
<br> This has caused an excessive increase in the number of active connections and hampered the use of the system.
<br>
<br> Have any way or setting to make postgres close idle connections?</div><br>
--
<br>Luiz Agnaldo Bernardi<br>Fone 41
36755756<br> 41 99979849<br></div>
| Attachment | Content-Type | Size |
|---|---|---|
| unknown_filename | text/html | 776 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jaromír Talíř | 2009-09-25 12:39:36 | Re: lazy vacuum and AccessExclusiveLock |
| Previous Message | Johan Nel | 2009-09-25 11:25:54 | Re: generic modelling of data models; enforcing constraints dynamically... |