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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
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 15:23:10
Message-ID: 6379.1295882590@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> 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.

Yeah, that was my first cut at it too, but it's not terribly interesting
because it doesn't tell you anything about what PQstatus says after the
first failed PQexec.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2011-01-24 15:29:41 Re: BUG #5837: PQstatus() fails to report lost connection
Previous Message Xiaobo Gu 2011-01-24 14:02:09 Re: Is there a way to build PostgreSQL client libraries with MinGW