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

From: John R Pierce <pierce(at)hogranch(dot)com>
To: Neil Conway <neilc(at)samurai(dot)com>
Cc: Denis Vlasenko <vda(at)ilport(dot)com(dot)ua>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #1756: PQexec eats huge amounts of memory
Date: 2005-07-07 15:17:23
Message-ID: 42CD4783.80303@hogranch.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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!).

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Hans-Jürgen Schönig 2005-07-07 15:20:54 Re: Sun inline assembler ...
Previous Message Tom Lane 2005-07-07 15:16:13 Re: BUG #1759: domain check constraint ignored in prepared statement