| From: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | "PostgreSQL Admin" <postgres(at)productivitymedia(dot)com> |
| Cc: | pgsql-admin(at)postgresql(dot)org, pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: [SQL] Unclosed connections |
| Date: | 2008-01-25 16:19:09 |
| Message-ID: | dcc563d10801250819h2260eafbl8f56b65b979b6c7d@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-sql |
On Jan 25, 2008 10:02 AM, PostgreSQL Admin
<postgres(at)productivitymedia(dot)com> wrote:
> We are using this bad piece of the software that does not close
> connections to the postgres server. Is there some setting for closing
> dead connections? And not TCP/IP keep alive does not work.
If the TCP keepalive can't detect them as dead, how is something else
supposed to? I.e. if a keepalive packet gets answered, then the
connection isn't dead, something is still connected to it.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Steven Rosenstein | 2008-01-25 18:53:57 | Recovering a database in danger of transaction wrap-around |
| Previous Message | PostgreSQL Admin | 2008-01-25 16:02:34 | Unclosed connections |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gary Stainburn | 2008-01-25 16:19:43 | Re: regex_replace problem -additional |
| Previous Message | Gary Stainburn | 2008-01-25 16:15:58 | regex_replace problem |