Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id B038B650060 for ; Wed, 30 Jul 2008 01:21:49 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 89078-04; Wed, 30 Jul 2008 01:21:40 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from fetter.org (start.fetter.org [66.92.188.65]) by postgresql.org (Postfix) with ESMTP id 40D6564FCE1; Wed, 30 Jul 2008 01:21:41 -0300 (ADT) Received: by fetter.org (Postfix, from userid 500) id 520D4FBC8E1; Tue, 29 Jul 2008 21:21:39 -0700 (PDT) Date: Tue, 29 Jul 2008 21:21:39 -0700 From: David Fetter To: Tom Lane Cc: Andrew Gierth , Tatsuo Ishii , pgsql-hackers@postgresql.org Subject: Re: WITH RECUSIVE patches 0723 Message-ID: <20080730042139.GD6750@fetter.org> References: <20080725001513.GF16438@fetter.org> <20080725.092652.105178884.t-ishii@sraoss.co.jp> <87r69gs967.fsf@news-spur.riddles.org.uk> <20080728.162925.23020498.t-ishii@sraoss.co.jp> <877ib6rq6q.fsf@news-spur.riddles.org.uk> <23482.1217264813@sss.pgh.pa.us> <873altsyay.fsf@news-spur.riddles.org.uk> <25697.1217270941@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <25697.1217270941@sss.pgh.pa.us> User-Agent: Mutt/1.5.18 (2008-05-17) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200807/1412 X-Sequence-Number: 121672 On Mon, Jul 28, 2008 at 02:49:01PM -0400, Tom Lane wrote: > Andrew Gierth writes: > > "Tom" == Tom Lane writes: > > Tom> That whole business of using the EState to pass tuplestores back > > Tom> and forth looks fundamentally broken to me anyway; there's just > > Tom> no way it'll be certain to link the right nodes together in > > Tom> complicated cases with multiple recursions. > > > Mutual recursion is not allowed; > > Well, the spec allows it, so we're going to have to fix this kluge > sooner or later, even if it chances not to fail on the subset we > currently support. Any ideas how to approach this? Cheers, David. -- David Fetter http://fetter.org/ Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter Skype: davidfetter XMPP: david.fetter@gmail.com Remember to vote! Consider donating to Postgres: http://www.postgresql.org/about/donate