| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | jdavis(at)dynworks(dot)com |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: alter table drop column |
| Date: | 2001-01-12 05:37:22 |
| Message-ID: | 200101120537.AAA29879@candle.pha.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Added to TODO.detail/drop.
[ Charset ISO-8859-1 unsupported, converting... ]
>
> I read the transcript of the alter table drop column discussion (old
> discussion) at http://www.postgresql.org/docs/pgsql/doc/TODO.detail/drop,
> and I have something to add:
>
> People mentioned such ideas as a hidden column and a really deleted column,
> and it occurred to me that perhaps "vacuum" would be a good option to use.
> When a delete was issued, the column would be hidden (by a negative/invalid
> logical column number, it appears was the consensus). Upon issuing a
> vacuum, it could perform a complete deletion. This method would allow users
> to know that the process may take a while (I think the agreed method for a
> complete delete was to "select into..." the right columns and leave out the
> deleted ones, then delete the old table).
>
> Furthermore, I liked the idea of some kind of "undelete", as long as it was
> just hidden. This could apply to anything that is cleaned out with a vacuum
> (before it is cleaned out), although I am not sure how feasible this is,
> and it isn't particularly important to me.
>
> Regards,
> Jeff
>
> --
> Jeff Davis
> Dynamic Works
> jdavis(at)dynworks(dot)com
> http://dynworks.com
>
>
--
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 | 2001-01-12 05:39:23 | Re: CRCs (was Re: [GENERAL] Re: Loading optimization) |
| Previous Message | Bruce Momjian | 2001-01-12 05:24:25 | Re: postgresql.conf and postgres options |