Re: column size too large, is this a bug?

From: Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com>
To: Qing Zhao <qzhao(at)quotefx(dot)net>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: column size too large, is this a bug?
Date: 2004-03-25 22:57:28
Message-ID: 20040325145525.V50544@megazone.bigpanda.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

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?)

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Qing Zhao 2004-03-25 23:11:03 Re: column size too large, is this a bug?
Previous Message Tom Lane 2004-03-25 22:28:19 Re: column size too large, is this a bug?