Received: from localhost.localdomain (postgresql.org [64.49.215.8]) by localhost (Postfix) with ESMTP id 2EC274774AA for ; Fri, 14 Jun 2002 01:15:24 -0400 (EDT) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id 0C0814772AE for ; Fri, 14 Jun 2002 01:03:54 -0400 (EDT) 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 g5E52Kb03198; Fri, 14 Jun 2002 01:02:20 -0400 (EDT) To: Andrew Hammond Cc: pgsql-sql@postgresql.org Subject: Re: simple recursive function in plpgsql fails In-reply-to: <3D092D3B.3070308@xyzzy.dhs.org> References: <3D092D3B.3070308@xyzzy.dhs.org> Comments: In-reply-to Andrew Hammond message dated "Thu, 13 Jun 2002 19:39:39 -0400" Date: Fri, 14 Jun 2002 01:02:20 -0400 Message-ID: <3195.1024030940@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200206/204 X-Sequence-Number: 8169 Andrew Hammond writes: > [ problems with a recursive plpgsql function ] Yeah, there are some known bugs there :-(. AFAICS this cannot be fixed properly until we get around to doing the querytree restructuring that I keep ranting about --- in particular, making a clean distinction between plan tree and execution state. regards, tom lane