| From: | Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at> |
|---|---|
| To: | "'The Hermit Hacker'" <scrappy(at)hub(dot)org> |
| 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: | AW: AW: AW: ALTER TABLE DROP COLUMN |
| Date: | 2000-10-13 11:22:14 |
| Message-ID: | 11C1E6749A55D411A9670001FA6879633680A6@sdexcsrv1.f000.d0188.sd.spardat.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Hiroshi's patch would make for a good starting point by bringing in the
> ability to do the DROP COLUMN feature, as I understand, without the
> rollback capability,
No Hiroshi's patch is rollback enabled, simply because all it does is change
some system tables. It only does not free space that is used by "old" phantom
columns. This cleanup would need extra work, but for now, I guess it would be fine
to simply say that if you want to regain the space create a new table and move the
data.
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Clark, Joel | 2000-10-13 12:33:53 | RE: [INTERFACES] Announcing PgSQL - a Python DB-API 2.0 compliant interface to PostgreSQL |
| Previous Message | The Hermit Hacker | 2000-10-13 11:06:05 | Re: AW: AW: ALTER TABLE DROP COLUMN |