Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f1A8gFx12869 for ; Sat, 10 Feb 2001 03:42:15 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.1/8.11.1) with ESMTP id f1A8gB902921; Sat, 10 Feb 2001 03:42:11 -0500 (EST) To: m.proctor@bigfoot.com cc: pgsql-sql@postgresql.org Subject: Re: Recusrive Functions in 7.0.3 In-reply-to: <01021008430408.05071@localhost.localdomain> References: <01020920225704.05071@localhost.localdomain> <28783.981775759@sss.pgh.pa.us> <01021008430408.05071@localhost.localdomain> Comments: In-reply-to mark proctor message dated "Sat, 10 Feb 2001 08:43:04 +0000" Date: Sat, 10 Feb 2001 03:42:11 -0500 Message-ID: <2918.981794531@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200102/190 X-Sequence-Number: 1377 mark proctor writes: > However if I put the PERFORM line back in to create a recursive > function it just goes on forever, and I only have 6 nodes. Hm. There may be a bug here, or maybe you're still confused... but I'm not eager to reverse-engineer your table declarations and data from this sketch. Would you mind providing a complete example, ie a SQL script to reproduce the problem starting from an empty database? regards, tom lane