On Tue, Jan 25, 2011 at 10:54 AM, Kevin Grittner
> Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>> I think this patch would only be adding to the confusion. When
>> PQgetResult() is called, we read enough data from the connection
>> to create and return one result object. It's true that this
>> doesn't necessarily detect an EOF, but IIUC calling PQgetResult()
>> again is just ONE way that you could trigger another read against
>> the socket, not the only one. I think it would also work to call
>> PQconsumeInput(), for example.
> I find it hard to reconcile the above with this:
> and the quote from our documentation referenced here:
IIUC, Tom's point was that doing it that way would detect the error,
not that it was the ONLY way to detect the error.
But it's easily testable.
>> I think the real, underlying problem here is that Murray would
>> like a behavior change
> More than that I think he wants to be able to read the manual and
> know what will work, without spending loads of time getting in tune
> with The Tao of Libpq. Based on his initial reading of the docs he
> expected different behavior; that can be fixed by changing the
> behavior or changing the docs.
That is why I suggested the type of doc correction that I thought
would be most helpful and accurate.
The Enterprise PostgreSQL Company
In response to
pgsql-bugs by date
|Next:||From: Josh Berkus||Date: 2011-01-25 20:05:36|
|Subject: Multicolun index creation never completes on 9.0.1/solaris|
|Previous:||From: Murray S. Kucherawy||Date: 2011-01-25 18:01:58|
|Subject: Re: BUG #5837: PQstatus() fails to report lost connection|