Re: BUG #5837: PQstatus() fails to report lost connection - Mailing list pgsql-bugs

From Kevin Grittner
Subject Re: BUG #5837: PQstatus() fails to report lost connection
Date
Msg-id 4D3D74D60200002500039B3C@gw.wicourts.gov
Whole thread Raw
In response to Re: BUG #5837: PQstatus() fails to report lost connection  ("Murray S. Kucherawy" <msk@cloudmark.com>)
Responses Re: BUG #5837: PQstatus() fails to report lost connection  ("Murray S. Kucherawy" <msk@cloudmark.com>)
Re: BUG #5837: PQstatus() fails to report lost connection  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-bugs
"Murray S. Kucherawy" <msk@cloudmark.com> wrote:
> From: Kevin Grittner [mailto:Kevin.Grittner@wicourts.gov]

>> What do you think would make this more clear?

> So maybe something like this after the paragraph you cited would
> help:
>
> "Note that after returning a PGresult object, PQresultStatus()
> could indicate a fatal error.  The caller should still iterate
> calling PQgetResult() to completion (i.e. until it returns NULL)
> in order to allow libpq to process the error information
> completely."

A patch based on this suggestion attached for consideration by the
community.

-Kevin


Attachment

pgsql-bugs by date:

Previous
From: "Murray S. Kucherawy"
Date:
Subject: Re: BUG #5837: PQstatus() fails to report lost connection
Next
From: "Murray S. Kucherawy"
Date:
Subject: Re: BUG #5837: PQstatus() fails to report lost connection