Skip site navigation (1) Skip section navigation (2)

Re: BUG #5837: PQstatus() fails to report lost connection

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Murray S(dot) Kucherawy" <msk(at)cloudmark(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5837: PQstatus() fails to report lost connection
Date: 2011-01-24 04:26:49
Message-ID: AANLkTikkjFMKoa6PQfJSc31Yn_M5+T3u7dRO4zUi-Bw2@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-bugs
On Sat, Jan 22, 2011 at 10:44 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> What did you do exactly?  testlibpq.c just uses PQexec(), and AFAICS the
> connection status does end up BAD if the backend is terminated before a
> PQexec starts.

PFA.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Attachment: testlibpq-loop-hack
Description: application/octet-stream (619 bytes)

In response to

Responses

pgsql-bugs by date

Next:From: Robert HaasDate: 2011-01-24 04:58:44
Subject: Re: BUG #5837: PQstatus() fails to report lost connection
Previous:From: Xiaobo GuDate: 2011-01-24 04:11:18
Subject: Re: Is there a way to build PostgreSQL client libraries with MinGW

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group