Re: BUG #1756: PQexec eats huge amounts of memory

Alvaro Herrera wrote:
> On Sun, Jul 10, 2005 at 01:05:10PM +0300, Denis Vlasenko wrote:
>
>>On Thursday 07 July 2005 20:43, Alvaro Herrera wrote:
>
>
>>>Really? I thought what really happened is you had to get the results
>>>one at a time using the pg_fetch family of functions. If that is true,
>>>then it's possible to make the driver fake having the whole table by
>>>using a cursor. (Even if PHP doesn't do it, it's possible for OCI to do
>>>it behind the scenes.)
>>
>>Even without cursor, result can be read incrementally.
>>
>>I mean, query result is transferred over network, right?
>>We just can stop read()'ing before we reached the end of result set,
>>and continue at pg_fetch as needed.
>
>
> It's not that simple. [...]

It also requires that you assume there is only one set of query results
outstanding at a time. I know that you can't assume that in JDBC, and by
the sounds of it PHP's interface is similar in that you can have
multiple query result objects active at the same time.

-O