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

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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Murray S(dot) Kucherawy" <msk(at)cloudmark(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #5837: PQstatus() fails to report lost connection
Date: 2011-01-24 15:29:41
Message-ID: 6493.1295882981@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
"Murray S. Kucherawy" <msk(at)cloudmark(dot)com> writes:
> Given what you say here, this seems to be an exception for which there
> is currently no detection mechanism short of looking for that one
> specific error string indicating it was administrative action causing
> the error.

This is complete nonsense.  If you followed the documented method for
using PQgetResult -- ie, keep calling it till it returns NULL, rather
than assuming there will be a specific number of results --- then
PQstatus would show you the bad status afterwards.

			regards, tom lane

In response to

Responses

pgsql-bugs by date

Next:From: Murray S. KucherawyDate: 2011-01-24 17:26:36
Subject: Re: BUG #5837: PQstatus() fails to report lost connection
Previous:From: Tom LaneDate: 2011-01-24 15:23:10
Subject: Re: BUG #5837: PQstatus() fails to report lost connection

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