Received: from secure.webhotel.net (secure.webhotel.net [195.41.202.80]) by postgresql.org (Postfix) with SMTP id 868C6476171 for ; Wed, 13 Mar 2002 10:35:33 -0500 (EST) Received: (qmail 68578977 invoked from network); 13 Mar 2002 15:40:14 -0000 Received: from unknown (HELO localhost.localdomain) (217.157.135.140) by mail.webhotel.net with SMTP; 13 Mar 2002 15:40:14 -0000 Subject: Re: Large data sets and FOR LOOP's From: Bo Lorentsen To: Tom Lane Cc: pgsql-sql In-Reply-To: <8568.1016032094@sss.pgh.pa.us> References: <1016012241.1094.90.camel@netgroup> <8568.1016032094@sss.pgh.pa.us> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/1.0.2 Date: 13 Mar 2002 16:35:37 +0100 Message-Id: <1016033737.3729.8.camel@netgroup> Mime-Version: 1.0 X-Archive-Number: 200203/151 X-Sequence-Number: 7031 On Wed, 2002-03-13 at 16:08, Tom Lane wrote: > > What PG version? 7.1.3 (Debian woody) > We fixed quite a few transient-memory-leak problems in plpgsql in 7.2. Are there any changelog, that only regards the plpqsql ? It is hard to find any information about the development of this part of PG, like problems related to the "set of" problem (lake of functionality), where it is not possible to work (like append) with a "set of" something. /BL