pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Stephan Szabo <sszabo@megazone.bigpanda.com>
To: Qing Zhao <qzhao@quotefx.net>
Cc: pgsql-performance@postgresql.org
Subject: Re: column size too large, is this a bug?
Date: Thu, 25 Mar 2004 14:57:28 -0800 (PST)
Message-ID: <20040325145525.V50544@megazone.bigpanda.com> (raw)
In-Reply-To: <082D0538-7E86-11D8-8B9C-000A95AB8896@quotefx.net>
References: <082D0538-7E86-11D8-8B9C-000A95AB8896@quotefx.net>

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




view thread (22+ messages)  latest in thread

Message-ID: <20040325145525.V50544@megazone.bigpanda.com>
Permalink:  ../20040325145525.V50544@megazone.bigpanda.com/
Also on:    postgresql.org/message-id/20040325145525.V50544@megazone.bigpanda.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: sszabo@megazone.bigpanda.com, qzhao@quotefx.net
  Subject: Re: column size too large, is this a bug?
  In-Reply-To: <20040325145525.V50544@megazone.bigpanda.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox