| From: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp>, "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: RFC: Restructuring pg_aggregate |
| Date: | 2002-04-11 04:15:02 |
| Message-ID: | GNELIHDDFBOCMGBFGEFOKEBGCCAA.chriskl@familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> If the client has to bear the some part, isn't the invisible
> column approach much simpler ?
>
> I've put a pretty much time into DROP COLUMN feature but
> I am really disappointed to see the comments in this thread.
> What DROP COLUMN has brought me seems only a waste of time.
I kind of agree with Hiroshi here. All I want to be able to do is drop
columns from my tables, and reclaim the space. I've got all sorts of
production tables with columns just sitting there doing nothing, awaiting
the time that I can happily drop them. It seems to me that whatever we do
will require some kind of client breakage.
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2002-04-11 04:16:23 | Re: RFC: Restructuring pg_aggregate |
| Previous Message | Hiroshi Inoue | 2002-04-11 04:01:37 | Re: RFC: Restructuring pg_aggregate |