Re: DROP COLUMN

From: Hannu Krosing <hannu(at)tm(dot)ee>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>, Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Rod Taylor <rbt(at)zort(dot)ca>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: DROP COLUMN
Date: 2002-07-16 18:29:36
Message-ID: 1026844176.410.67.camel@taru.tm.ee
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, 2002-07-16 at 18:30, Bruce Momjian wrote:
> Hiroshi Inoue wrote:
> > > Makes sense. Of course, we could make a syscache that didn't return
> > > system columns either.
> > >
> > > Actually, the original argument for negative attno's for dropped columns
> > > was exactly for this case, that the system column check would catch
> > > dropped columns too,
> >
> > > but it causes other problems that are harder to fix
> > > so we _dropped_ the idea.
> >
> > What does this mean ?
>
> Client programmers prefered the dropped flag rather than negative
> attno's so we went with that.

While you are at it,could you add another flag is_system ?

<evil grin>

-----------
Hannu

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2002-07-16 19:36:17 Re: Issues Outstanding for Point In Time Recovery (PITR)
Previous Message Tom Lane 2002-07-16 18:07:05 Re: Spec on pg_cast table/CREATE CAST command