X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 2D612D1CCA7 for ; Fri, 30 Jan 2004 15:42:18 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 79490-01 for ; Fri, 30 Jan 2004 11:42:20 -0400 (AST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id E3756D1CCB6 for ; Fri, 30 Jan 2004 11:42:14 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i0UFg8iK013922; Fri, 30 Jan 2004 10:42:08 -0500 (EST) To: Jeff Cc: Mark Harrison , pgsql-admin@postgresql.org Subject: Re: hung postmaster when client machine dies? In-reply-to: <20040130101807.476528cc.threshar@torgo.978.org> References: <4019ACAB.4010600@pixar.com> <20040130101807.476528cc.threshar@torgo.978.org> Comments: In-reply-to Jeff message dated "Fri, 30 Jan 2004 10:18:07 -0500" Date: Fri, 30 Jan 2004 10:42:08 -0500 Message-ID: <13921.1075477328@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200401/295 X-Sequence-Number: 12158 Jeff writes: > Eventually PG would have found out the socket was dead. We do enable TCP keepalive on the client socket, so eventually the kernel will time out and notify us of a lost connection. Unfortunately the timeouts involved are long --- IIRC the relevant RFCs specify at least an hour. regards, tom lane