X-Original-To: pgsql-interfaces@postgresql.org
Received: from localhost (postgresql.org [64.49.215.8])
	by postgresql.org (Postfix) with ESMTP id 102E4475A09
	for <pgsql-interfaces@postgresql.org>;
	Mon, 10 Feb 2003 23:35:40 -0500 (EST)
Received: from sss.pgh.pa.us (unknown [192.204.191.242])
	by postgresql.org (Postfix) with ESMTP id 4DFA24759BD
	for <pgsql-interfaces@postgresql.org>;
	Mon, 10 Feb 2003 23:35:39 -0500 (EST)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.12.6/8.12.6) with ESMTP id h1B4Zi5u021916;
	Mon, 10 Feb 2003 23:35:44 -0500 (EST)
To: "Frankie Lam" <frankie@ucr.com.hk>
Cc: pgsql-interfaces@postgresql.org
Subject: Re: Any timeout feature(in libPQ) suitable for my case? 
In-reply-to: <b29s2v$2nlu$1@news.hub.org> 
References: <b29s2v$2nlu$1@news.hub.org>
Comments: In-reply-to "Frankie Lam" <frankie@ucr.com.hk>
	message dated "Tue, 11 Feb 2003 11:53:39 +0800"
Date: Mon, 10 Feb 2003 23:35:43 -0500
Message-ID: <21915.1044938143@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Virus-Scanned: by AMaViS new-20020517
X-Archive-Number: 200302/26
X-Sequence-Number: 3647

"Frankie Lam" <frankie@ucr.com.hk> writes:
> I wonder if there is a timeout feature for limiting the lifetime of a
> connection in libPQ.

There is not.  I don't think it's libpq's business to be deciding
whether the connection is lost or not --- that is the province of
the kernel's TCP stack.  IMHO we should not second-guess the transport
layer.

			regards, tom lane