X-Original-To: pgsql-www-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id E6A48DA463 for ; Wed, 2 Nov 2005 22:52:34 -0400 (AST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 43889-04 for ; Thu, 3 Nov 2005 02:52:30 +0000 (GMT) Received: from fetter.org (dsl092-188-065.sfo1.dsl.speakeasy.net [66.92.188.65]) by svr1.postgresql.org (Postfix) with ESMTP id 0B556D99BC for ; Wed, 2 Nov 2005 22:52:31 -0400 (AST) Received: from fetter.org (localhost.localdomain [127.0.0.1]) by fetter.org (8.13.4/8.12.10) with ESMTP id jA32qYA4001972; Wed, 2 Nov 2005 18:52:34 -0800 Received: (from shackle@localhost) by fetter.org (8.13.4/8.13.4/Submit) id jA32qYYL001971; Wed, 2 Nov 2005 18:52:34 -0800 Date: Wed, 2 Nov 2005 18:52:33 -0800 From: David Fetter To: "Jim C. Nasby" Cc: Merlin Moncure , pgsql-www@postgresql.org Subject: Re: [PERFORM] improvise callbacks in plpgsql Message-ID: <20051103025233.GG29465@fetter.org> References: <6EE64EF3AB31D5448D0007DD34EEB3417DD76D@Herge.rcsinc.local> <20051102234430.GA55520@pervasive.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051102234430.GA55520@pervasive.com> User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.05 required=5 tests=[AWL=0.050] X-Spam-Score: 0.05 X-Spam-Level: X-Archive-Number: 200511/14 X-Sequence-Number: 8729 On Wed, Nov 02, 2005 at 05:44:30PM -0600, Jim C. Nasby wrote: > Can we get a link to this posted somewhere? I guess on techdocs? > > On Wed, Nov 02, 2005 at 08:45:02AM -0500, Merlin Moncure wrote: > > > Would you be willing to write up an example of this? We often get > > asked > > > about support for WITH, so I bet there's other people who would be > > very > > > interested in what you've got. > > > > Sure. In fact, I had already decided this to be the next topic on > > my blog. I'm assuming you are asking about tools to deal with > > recursive sets in postgresql. A plpgsql solution is extremely > > fast, tight, and easy if you do it right...Tom's latest > > suggestions (I have to flesh this out some more) provide the > > missing piece puzzle to make it really tight from a classic > > programming perspective. I don't miss the recursive query syntax > > at all...IMO it's pretty much a hack anyways (to SQL). This might be worth putting in the docs somewhere. Tutorial? Cheers, D -- David Fetter david@fetter.org http://fetter.org/ phone: +1 510 893 6100 mobile: +1 415 235 3778 Remember to vote!