Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154])
	by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f2E5qOx43006
	for <pgsql-interfaces@postgresql.org>;
	Wed, 14 Mar 2001 00:52:24 -0500 (EST)
	(envelope-from tgl@sss.pgh.pa.us)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.11.1/8.11.1) with ESMTP id f2E5q6t23885;
	Wed, 14 Mar 2001 00:52:06 -0500 (EST)
To: philip.howell@cit.act.edu.au
cc: pgsql-interfaces@postgresql.org
Subject: Re: libpq PQstatus problem 
In-reply-to: <0103149845.AA984548336@mh-cit.cit.act.edu.au> 
References: <0103149845.AA984548336@mh-cit.cit.act.edu.au>
Comments: In-reply-to <philip.howell@cit.act.edu.au>
	message dated "Wed, 14 Mar 2001 14:45:07 +1000"
Date: Wed, 14 Mar 2001 00:52:06 -0500
Message-ID: <23882.984549126@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Archive-Number: 200103/122
X-Sequence-Number: 1283

<philip.howell@cit.act.edu.au> writes:
> Then I stopped the network (eth0) on the postgreSQL server and hit <return>
> again and still got

>> Connection status... OK 

I don't believe this is a bug.  PQstatus indicates whether you did make
a successful connection to the database server --- it is not intended to
be an up-to-the-nanosecond report on whether the network is still up or
not.  In particular, the status will *not* be updated if you haven't
executed any new operations on the connection lately.

If you have a network that's so unstable that you need to program around
problems like this, consider 'ping'.

			regards, tom lane