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 4ACF2D1D803 for ; Sun, 28 Mar 2004 19:26:10 +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 35018-08 for ; Sun, 28 Mar 2004 15:26:09 -0400 (AST) Received: from davinci.ethosmedia.com (server228.ethosmedia.com [209.128.84.228]) by svr1.postgresql.org (Postfix) with ESMTP id E983AD1D707 for ; Sun, 28 Mar 2004 15:26:07 -0400 (AST) Received: from [63.195.55.98] (HELO spooky) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.1.8) with ESMTP id 4720604; Sun, 28 Mar 2004 11:27:27 -0800 Content-Type: text/plain; charset="iso-8859-1" From: Josh Berkus Organization: Aglio Database Solutions To: Andrew Rawnsley , Qing Zhao Subject: Re: column size too large, is this a bug? Date: Sun, 28 Mar 2004 11:25:41 -0800 User-Agent: KMail/1.4.3 Cc: Tom Lane , Stephan Szabo , pgsql-performance@postgresql.org References: <082D0538-7E86-11D8-8B9C-000A95AB8896@quotefx.net> <1DA4E1C7-7F4B-11D8-8D3D-000A95AB8896@quotefx.net> <8B3A05B5-7F51-11D8-93F3-000393A47FCC@ravensfield.com> In-Reply-To: <8B3A05B5-7F51-11D8-93F3-000393A47FCC@ravensfield.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <200403281125.41590.josh@agliodbs.com> X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200403/402 X-Sequence-Number: 6258 Andrew, > I used to use the connect-by patch, but have since rewritten everything > to use a nested set model. Cool! You're probably the only person I know other than me using nested sets in a production environment. -- Josh Berkus Aglio Database Solutions San Francisco