Message-ID: <009501c8ec90$18bf11c0$be00a8c0@6dBangalore.co.in>
From: "Sunil Khatri" <sunil@6dtech.co.in>
To: "Tom Lane" <tgl@sss.pgh.pa.us>
Cc: <pgsql-interfaces@postgresql.org>
References: <001901c8ec12$66ad2990$be00a8c0@6dBangalore.co.in>
	<714.1216747726@sss.pgh.pa.us>
Subject: Re: PQstatus is getting blocked when database sytem powered off 
Date: Wed, 23 Jul 2008 12:18:18 +0530
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit

Thanks for your reply.
You are right PQstatus is not blocking, query-issuing call is getting
blocked.
Is there any way for handling this blocking situation?

Regards
Sk
----- Original Message ----- 
From: "Tom Lane" <tgl@sss.pgh.pa.us>
To: "Sunil Khatri" <sunil@6dtech.co.in>
Cc: <pgsql-interfaces@postgresql.org>
Sent: Tuesday, July 22, 2008 10:58 PM
Subject: Re: [INTERFACES] PQstatus is getting blocked when database sytem 
powered off


> "Sunil Khatri" <sunil@6dtech.co.in> writes:
>> Problem is : PQstatus is getting blocked If the system on which database 
>> server is running is powered off.
>
> Hardly likely, considering that PQstatus is just
>
> ConnStatusType
> PQstatus(const PGconn *conn)
> {
> if (!conn)
> return CONNECTION_BAD;
> return conn->status;
> }
>
>
> I have no doubt that a query-issuing call could get blocked if the
> postmaster stops responding, but not PQstatus.
>
> regards, tom lane
>
> -- 
> Sent via pgsql-interfaces mailing list (pgsql-interfaces@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-interfaces
>
>
> -- 
> No virus found in this incoming message.
> Checked by AVG.
> Version: 7.5.524 / Virus Database: 270.5.3/1565 - Release Date: 7/21/2008 
> 6:36 PM
>
>