| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at> |
| Cc: | "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>, PostgreSQL Development <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Re: AW: AW: ALTER TABLE DROP COLUMN |
| Date: | 2000-10-13 09:07:01 |
| Message-ID: | 200010130907.FAA23006@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
[ 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(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2000-10-13 09:07:22 | Re: AW: Inserting a select statement result into another ta ble |
| Previous Message | Zeugswetter Andreas SB | 2000-10-13 08:06:03 | AW: AW: ALTER TABLE DROP COLUMN |