From: | "Sunil Khatri" <sunil(at)6dtech(dot)co(dot)in> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | <pgsql-interfaces(at)postgresql(dot)org> |
Subject: | Re: PQstatus is getting blocked when database sytem powered off |
Date: | 2008-07-23 06:48:18 |
Message-ID: | 009501c8ec90$18bf11c0$be00a8c0@6dBangalore.co.in |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-interfaces |
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(at)sss(dot)pgh(dot)pa(dot)us>
To: "Sunil Khatri" <sunil(at)6dtech(dot)co(dot)in>
Cc: <pgsql-interfaces(at)postgresql(dot)org>
Sent: Tuesday, July 22, 2008 10:58 PM
Subject: Re: [INTERFACES] PQstatus is getting blocked when database sytem
powered off
> "Sunil Khatri" <sunil(at)6dtech(dot)co(dot)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(at)postgresql(dot)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
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Francisco Figueiredo Jr. | 2008-07-29 22:02:09 | [ANN] Npgsql2 RC1 Released!! |
Previous Message | Tom Lane | 2008-07-22 17:28:46 | Re: PQstatus is getting blocked when database sytem powered off |