Re: AW: AW: AW: ALTER TABLE DROP COLUMN - Mailing list pgsql-hackers

From The Hermit Hacker
Subject Re: AW: AW: AW: ALTER TABLE DROP COLUMN
Date
Msg-id Pine.BSF.4.21.0010131833410.696-100000@thelab.hub.org
Whole thread Raw
In response to AW: AW: AW: ALTER TABLE DROP COLUMN  (Zeugswetter Andreas SB <ZeugswetterA@wien.spardat.at>)
Responses Re: AW: AW: AW: ALTER TABLE DROP COLUMN  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Fri, 13 Oct 2000, Zeugswetter Andreas SB wrote:

> 
> > 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.

okay, but, again based on my impression of what Tom has stated, and
previous conversations on this topic, the key problem is what happens if I
drop a column and a later date decide add a new column of the same name,
what happens?

I *believe* its that condition that Tom's thought about physical vs
logical column names was about ... Tom?




pgsql-hackers by date:

Previous
From: "Ross J. Reedstrom"
Date:
Subject: Re: [GENERAL] Re: My new job
Next
From: Tom Lane
Date:
Subject: Re: AW: AW: ALTER TABLE DROP COLUMN