Received: from secure.webhotel.net (secure.webhotel.net [195.41.202.80]) by postgresql.org (Postfix) with SMTP id 5CF19476637 for ; Thu, 14 Mar 2002 10:56:25 -0500 (EST) Received: (qmail 69596675 invoked from network); 14 Mar 2002 16:01:07 -0000 Received: from unknown (HELO localhost.localdomain) (217.157.135.140) by mail.webhotel.net with SMTP; 14 Mar 2002 16:01:07 -0000 Subject: Re: Large data sets and FOR LOOP's From: Bo Lorentsen To: Jan Wieck Cc: pgsql-sql In-Reply-To: <200203141521.g2EFLUg02750@saturn.janwieck.net> References: <200203141521.g2EFLUg02750@saturn.janwieck.net> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/1.0.2 Date: 14 Mar 2002 16:56:28 +0100 Message-Id: <1016121388.878.132.camel@netgroup> Mime-Version: 1.0 X-Archive-Number: 200203/182 X-Sequence-Number: 7062 On Thu, 2002-03-14 at 16:21, Jan Wieck wrote: > > Would a cursor have helped any ? > > Sure, if they whould've been available in PL/pgSQL. This all > was a combined feature enhancement for 7.2. 1st cursor > support over SPI (an internal query interface inside the > backend), 2nd support for cursors and reference cursors in > PL/pgSQL, 3rd automatic usage of internal cursors in FOR > loops. I think I will update wery soon now (just need to woody package) :-) /BL