X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id DDCFED1E195 for ; Tue, 30 Mar 2004 20:13:50 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 66159-05 for ; Tue, 30 Mar 2004 16:13:49 -0400 (AST) Received: from davinci.ethosmedia.com (server228.ethosmedia.com [209.128.84.228]) by svr1.postgresql.org (Postfix) with ESMTP id DF032D1D58C for ; Tue, 30 Mar 2004 16:13:47 -0400 (AST) Received: from [63.195.55.98] (HELO 192.168.1.29) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.1.8) with ESMTP id 4734093; Tue, 30 Mar 2004 12:15:07 -0800 From: Josh Berkus Reply-To: josh@agliodbs.com Organization: Aglio Database Solutions To: Robert Treat , Andrew Rawnsley Subject: Re: Nested Sets WAS: column size too large, is this a bug? Date: Tue, 30 Mar 2004 12:13:12 -0800 User-Agent: KMail/1.5.4 Cc: pgsql-performance@postgresql.org References: <082D0538-7E86-11D8-8B9C-000A95AB8896@quotefx.net> <200403300838.50538.josh@agliodbs.com> <200403301506.08882.xzilla@users.sourceforge.net> In-Reply-To: <200403301506.08882.xzilla@users.sourceforge.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200403301213.12424.josh@agliodbs.com> X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200403/427 X-Sequence-Number: 6283 Robert, > http://archives.postgresql.org/pgsql-sql/2002-11/msg00355.php > > Seemed to work though someone else had posted yet another version after > ours... and in fact the one posted is not exactly what I use now either :-) Hmmm ... I'd want to do a *lot* of testing before I trusted that approach. Seems like it could be very vunerable to order-of-exection issues. I'll start a GUIDE on it, people can post their various Nested Sets solutions. -- -Josh Berkus Aglio Database Solutions San Francisco