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 C8EABD1E934 for ; Thu, 25 Mar 2004 22:57:46 +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 20513-06 for ; Thu, 25 Mar 2004 18:57:51 -0400 (AST) Received: from megazone.bigpanda.com (megazone.bigpanda.com [64.147.171.210]) by svr1.postgresql.org (Postfix) with ESMTP id 791CCD1DC6B for ; Thu, 25 Mar 2004 18:57:44 -0400 (AST) Received: by megazone.bigpanda.com (Postfix, from userid 1001) id 6CAB735099; Thu, 25 Mar 2004 14:57:28 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by megazone.bigpanda.com (Postfix) with ESMTP id 688FB35091; Thu, 25 Mar 2004 14:57:28 -0800 (PST) Date: Thu, 25 Mar 2004 14:57:28 -0800 (PST) From: Stephan Szabo To: Qing Zhao Cc: pgsql-performance@postgresql.org Subject: Re: column size too large, is this a bug? In-Reply-To: <082D0538-7E86-11D8-8B9C-000A95AB8896@quotefx.net> Message-ID: <20040325145525.V50544@megazone.bigpanda.com> References: <082D0538-7E86-11D8-8B9C-000A95AB8896@quotefx.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200403/365 X-Sequence-Number: 6221 On Thu, 25 Mar 2004, Qing Zhao wrote: > select > _level_ as l, > nextval('seq_pk_bom_detail') as bom_detail, > prior nextval('seq_pk_bom_detail') as parent_subassembly, > parent_part_number, > customer_part_number, > /* mfr_name, > mfr_part, > description,*/ > commodity, > needs_date, > target_price, > comments, > case qty_per > when null then 0.00001 > when 0 then 0.00001 > else qty_per > end, > qty_multiplier1, > qty_multiplier2, > qty_multiplier3, > qty_multiplier4, > qty_multiplier5 > from bom_detail_work_clean > where (0=0) > and bom_header=20252 > and file_number = 1 > start with customer_part_number = 'Top Assembly 1' > connect by parent_part_number = prior customer_part_number; What version are you running, and did you apply any patches (for example one to support the start with/connect by syntax used above?)