Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id 0D4F2477309 for ; Wed, 13 Mar 2002 10:08:12 -0500 (EST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id g2DF8ES08571; Wed, 13 Mar 2002 10:08:14 -0500 (EST) To: Bo Lorentsen Cc: pgsql-sql Subject: Re: Large data sets and FOR LOOP's In-reply-to: <1016012241.1094.90.camel@netgroup> References: <1016012241.1094.90.camel@netgroup> Comments: In-reply-to Bo Lorentsen message dated "13 Mar 2002 10:37:21 +0100" Date: Wed, 13 Mar 2002 10:08:14 -0500 Message-ID: <8568.1016032094@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200203/142 X-Sequence-Number: 7022 Bo Lorentsen writes: > But, if I, in my code, make "for loop" on a huge select result (about > 1.7 mil. rows), my function begin to consume alot of memory. What PG version? We fixed quite a few transient-memory-leak problems in plpgsql in 7.2. regards, tom lane