| From: | Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at> |
|---|---|
| To: | "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>, PostgreSQL Development <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | AW: AW: ALTER TABLE DROP COLUMN |
| Date: | 2000-10-13 08:06:03 |
| Message-ID: | 11C1E6749A55D411A9670001FA6879633680A3@sdexcsrv1.f000.d0188.sd.spardat.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> 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 ?
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2000-10-13 09:07:01 | Re: AW: AW: ALTER TABLE DROP COLUMN |
| Previous Message | Zeugswetter Andreas SB | 2000-10-13 07:53:20 | AW: Inserting a select statement result into another ta ble |