Re: DROP COLUMN status - Mailing list pgsql-hackers

From Tom Lane
Subject Re: DROP COLUMN status
Date
Msg-id 15722.960474011@sss.pgh.pa.us
Whole thread Raw
In response to RE: DROP COLUMN status  ("Hiroshi Inoue" <Inoue@tpf.co.jp>)
Responses Re: DROP COLUMN status  (Bruce Momjian <pgman@candle.pha.pa.us>)
RE: DROP COLUMN status  ("Hiroshi Inoue" <Inoue@tpf.co.jp>)
List pgsql-hackers
"Hiroshi Inoue" <Inoue@tpf.co.jp> writes:
> The implementation makes the dropped column invisible by
> changing its attnum to -attnum - offset(currently 20) and
> attnam to ("*already Dropped%d",attnum).

Ugh.  No wonder you had to hack so many places in such an ugly fashion.
Why not leave the attnum as-is, and just add a bool saying "column is
dropped" to pg_attribute?  As long as the parser ignores columns marked
that way for field lookup and expansion of *, it seems the rest of the
system wouldn't need to treat dropped columns specially in any way.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [GENERAL] NOTIFY/LISTEN in pgsql 7.0
Next
From: Zeugswetter Andreas SB
Date:
Subject: AW: Proposal: TRUNCATE TABLE table RESTRICT