pg.ddx.io pgsql-sql@postgresql.org mailing list archive
help / color / mirror / Atom feedUnclosed connections
2+ messages / 2 participants
[nested] [flat]
* Unclosed connections
@ 2008-01-25 16:02 PostgreSQL Admin <postgres@productivitymedia.com>
0 siblings, 1 reply; 2+ messages in thread
From: PostgreSQL Admin @ 2008-01-25 16:02 UTC (permalink / raw)
To: ; +Cc: pgsql-admin@postgresql.org; pgsql-sql
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.
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: [SQL] Unclosed connections
@ 2008-01-25 16:19 Scott Marlowe <scott.marlowe@gmail.com>
parent: PostgreSQL Admin <postgres@productivitymedia.com>
0 siblings, 0 replies; 2+ messages in thread
From: Scott Marlowe @ 2008-01-25 16:19 UTC (permalink / raw)
To: PostgreSQL Admin <postgres@productivitymedia.com>; +Cc: pgsql-admin@postgresql.org; pgsql-sql
On Jan 25, 2008 10:02 AM, PostgreSQL Admin
<postgres@productivitymedia.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.
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2008-01-25 16:19 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2008-01-25 16:02 Unclosed connections PostgreSQL Admin <postgres@productivitymedia.com>
2008-01-25 16:19 ` Scott Marlowe <scott.marlowe@gmail.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox