Re: BUG #1756: PQexec eats huge amounts of memory - Mailing list pgsql-bugs

From John R Pierce
Subject Re: BUG #1756: PQexec eats huge amounts of memory
Date
Msg-id 42CD4783.80303@hogranch.com
Whole thread Raw
In response to Re: BUG #1756: PQexec eats huge amounts of memory  (Neil Conway <neilc@samurai.com>)
Responses Re: BUG #1756: PQexec eats huge amounts of memory  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
List pgsql-bugs
Neil Conway wrote:
> Denis Vlasenko wrote:
>
>> The same php script but done against Oracle does not have this
>> behaviour.
>
>
> Perhaps; presumably Oracle is essentially creating a cursor for you
> behind the scenes. libpq does not attempt to do this automatically; if
> you need a cursor, you can create one by hand.

I do not understand how a cursor could be autocreated by a query like

    $result = pg_query($db, "SELECT * FROM big_table");

php will expect $result to contain the entire table (yuck!).

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #1759: domain check constraint ignored in prepared statement
Next
From: Hans-Jürgen Schönig
Date:
Subject: Re: Sun inline assembler ...