Skip site navigation (1) Skip section navigation (2)

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: (view raw, whole thread or download thread mbox)
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


pgsql-bugs by date

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

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group