Re: AW: AW: ALTER TABLE DROP COLUMN

[ Charset ISO-8859-1 unsupported, converting... ]
> > we bite the bullet to the extent of supporting a distinction between
> > physical and logical column numbers, then ISTM there's no strong need
> > to do any of this other stuff at all.  I'd expect that an inserted or
> > updated tuple would have a NULL in any physical column position that
> > doesn't have an equivalent logical column, so the space cost 
> > is minimal
> > (zero, in fact, if there are any other NULLs in the tuple).  Over time
> > the space occupied by deleted-column data would gradually go away as
> > tuples got updated.
> 
> This said, I think Hiroshi's patch seems a perfect starting point, no ?

Having phantom columns adds additional complexity to the system overall.
We have to decide we really want it before making things more complex
than they already are.

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026